Protected, and able to prove it.

An agent that can act on its own is a liability. So ours cannot. The agent writes what it wants to send, shows you the exact text as it would go, says why it drafted it and what it flags as the risk, and then it waits. Nothing leaves until a person says yes.

• Approve and deny are the only two decisions, and each one is a permanent entry.
• Change your mind and the later decision is the one that counts. An approval you reversed does not go.
• One log holds every request, message, draft, decision and send. It is append only: there is no edit, so the record cannot be quietly rewritten.
• You can read that log yourself, at any time, on your own page.

This is built, not planned. The gate refuses an undecided draft, a denied one, an approval that was later denied, and a second send. There is a test for each of those, and they run on every release.

• Protection from AI-enabled attacks
• Your data, kept safe and accounted for
• Documented controls you can hand to an underwriter

Where something is not built yet, the page that shows it says so in plain words rather than leaving a blank. A page that shows you the no's is a page you can trust on the yeses.

A design target, not a promise. Your assessment replaces it with your own number, and the monthly ledger proves it or does not. See the ledger.

Least privilege, and you approve each connection

Read-only until you say otherwise. Revocable in one click. Every connection appears in the monthly access report, whether or not anything went wrong.

Three questions, then this stone is planned

Every stone opens with its own short questionnaire. Your answers generate two lists at once: the steps only you can take, and the work the agent takes over. The assessment runs all six stones in the arch order, then the keystone.

The parts we are still standing up, named

• Nobody has signed an engagement yet. You would be first, and we say so rather than implying a queue.
• The agent's own inbox answers from the tenant's own machine, and no tenant machine exists yet.
• The first backup and the first proven restore have not run, so no page claims either.
• Insurance is being placed now, with affirmative AI cover required in writing rather than assumed.

You will not find a blank where one of these should be. You will find a sentence saying it is not there.