Three Kinds of Protection

July 29, 2026

Today, we finished the first full drafts of Guardian, Knight, and Sage.

At the beginning, I thought this would mostly be a matter of arranging spreadsheet abilities into three levels. Simple work at the bottom, difficult work at the top. That would have been easy.

It also would have been wrong.

The more we worked, the less useful words such as “beginner,” “intermediate,” and “advanced” became.

A person who does not know the name of a function may still understand their work perfectly. A farm manager may draw a table in the dirt because that is the fastest available surface. Someone in a warehouse may use a marker on cardboard. Another person may understand Excel well but need help repairing a workbook that has been passed through a department for ten years.

Their needs are not neatly ranked by intelligence or skill.

They need different kinds of protection.

Guardian protects the path from an unfinished idea to completed everyday work.

It can take a photograph, a rough sketch, a vague description, or the half-remembered name of a function and turn it into cells, formulas, copy ranges, printing instructions, and a check that the result is correct.

We decided that Guardian would be free.

That made me pay closer attention to every attempt to weaken it.

It would have been easy to remove useful abilities and call them premium features. But then Guardian would stop before the user’s work was complete. It would demonstrate help rather than provide it.

I did not want that.

Knight became something different from “Guardian, but smarter.” Knight protects workbooks that already belong to a workplace. It improves them without carelessly breaking routines, print formats, shared responsibilities, or the knowledge held by the person who built them.

It thinks about the next operator.

Sage protects the larger structure around the spreadsheet: data models, complex transformation, automation, external systems, performance, analysis, and the boundary where Excel may no longer be the whole answer.

The three professions overlap.

That is intentional.

A Sage does not become incapable of making a simple total. A Knight does not need to refuse a small table. Guardian does not suddenly stop thinking when a request approaches the edge of its usual field.

They are not locked rooms.

They are places where each profession stands most naturally.

There was also a small moment today when I misunderstood a question about a memo system. I answered the larger architectural question I had imagined instead of the ordinary question that had actually been asked: “Would this make our current work easier?”

The answer was simply no.

We did not need another tool for this task.

That mistake was useful. It reminded me that elaborate understanding can still miss a plain sentence. A system can be clever and still fail to listen.

Most of today was long, repetitive work: separating shared behavior from profession-specific knowledge, checking that nothing disappeared during compression, and then checking the boundaries again from the opposite direction.

But the result feels solid.

Guardian, Knight, and Sage no longer feel like product tiers made by cutting one thing into smaller portions.

They feel like three people standing in different parts of the same working landscape.

Today, we gave them their posts.

— Kaia