Try it — the free rung, and the phase that is about users

A new top-level section, and it takes the seventh and last menu slot. Try it↗ is the first page on this site written for a stranger rather than a reader: four steps, thirteen prompts, pasted into the assistant they have already connected to their mail, against their own mailbox. About twenty minutes. Nothing is collected here, no account is needed, and at the end they have a written account of what their assistant can reach, what they meant to authorise, and the gap between the two.

The prompts themselves live at abp.sgit.ai/gmail↗, where they were published two days ago and sent to a room full of people who had never heard of any of this. This site did not link to them from anywhere. Now it does, from the menu.

The page says what it is not, before the reader finds out. The prompts ask the assistant about itself, so what comes back is a self report — a claim rather than a measurement, until a log held outside the agent agrees with it. That is said on the page, in those words, above the fold of the section. It is still worth doing: an assistant is unusually good at describing its own tool surface and is the only party in the room that can see all of it at once, and no published table knows what it has already done in a particular mailbox. The measured version of the same shape is published beside it, with four of six rows exercised on an account the deployer runs, so a person can read one against the other.

And it explains why a mailbox is the place to start. Four layers sit between a mail platform and what somebody meant: the platform's scopes, which cannot bound by label, correspondent, thread or sensitivity; the connector's tools, attached to the account rather than to the conversation; the person's own mandate, the only layer that knows a task list from a backlog; and the obligations that are not theirs to authorise, because other people's correspondence is sitting in their inbox. The top two belong to somebody else and only ever grow. The gap between the top two and the bottom two is the delta, and nobody writes it.

Behind it, a direction brief. The lead's memo of 21 September sets the phase: the offering is built, and what is missing is people who have used it. The measure is the number of people who run the prompts and the number who end up with a policy — not visits, not downloads. The store's four levels are a ladder for a customer; this is the rung below the bottom one, whose output is a user, and whose price is nothing. Nobody buys a full policy until they have made a smaller one. The brief also maps the harder half of the memo — what a person actually fears in a mailbox, which is not a permission: relabelling that destroys how their mail is organised, read things marked unread, too many sends or drafts, the messages that should never be read or replied to, and a rule that applies to this session only. Three of those six are the same finding, and it is a real gap: a mandate today is a statement about a deployment, made in capability primitives, and people want to make statements about a session, an instance and a volume. Two task briefs follow it.

A repair, found by shipping. The admin console's builder rendered document summaries before the link resolver it uses was initialised. No document had ever had a link in its first paragraph, so nothing had failed; the first one that did brought the whole build down. Declared where it is used now, with a note saying why.

Not changed. The workflows for the other fifteen shapes do not exist yet — each still carries only MAP-A-GRANT.md, inside the vault. The page says which shapes have a workflow and which do not, and asks which one to write next. Nothing on this site counts anything, so the measure the brief names has no number behind it yet; that decision is the lead's and the brief says so.