The brief, as intent.

Every story below came from a heading of the brief or the memo, and lands on a page of this site. Nothing here was added that neither document says; where the site decided something they left open, the decision is in the corrections file, not here.

Status, from docs/reality.md: shipped v0.1.0 The review folder: the brief read as intent, each node anchored to a section of the brief, validated and rendered · proposed The derived half of the review folder: the code graph from parsers, the join with a coverage figure, every commit read upwards, the navigator as web components

Written by agent: the build session (Claude Code) on 2026-10-20: the brief and the memo as stories, rules and examples; nothing added that neither says. Accepted by: nobody yet; the lead accepts by a release.

Customers, not beta users

As the lead, I want the people in the first batch called customers, each starting with credit on a site that meters and bills, so that what they would pay is a real question from the first day. From Customers, not beta users · lands on /programme/.

• Each customer starts with credit, £5 or £50 or whatever the number turns out to be, to spend on a site we run. From Customers, not beta users.
  • The credit page says what the credit is, how the meter works, and that the meter is not wired to this site yet. · lands on /credit/
  • Every customer record carries credit granted, credit used and whether they topped up. · lands on /customers/
• From the first day, what they use is metered, the way the newsroom meters every page against a reader's credit. From Customers, not beta users.
  • The reality file says the meter is proposed until the lead wires it; the page uses the future tense. · lands on /docs/reality.html

A site of their own, with a start-here page

As a customer, I want one place that says what to do first, in order, and shows the objectives and milestones agreed with me and where I am. From A site of their own · lands on /start-here/.

• It starts with a start-here page: what to do first, in order, with clear instructions. From A site of their own.
  • Seven steps in order, each linked to the thing that does it and to its milestone. · lands on /start-here/
• Then a page for each customer, with the objectives and milestones we agreed with them, and where they are. From A site of their own.
  • One page per record in data/customers.json, with the objectives, the state of every step and the follow-up log. · lands on /customers/
  • A worked example with invented numbers, marked as not a customer, shows the shape. · lands on /customers/example/
• Even if all a customer does is use the website, we can measure it, and we can bill for it. From A site of their own.

Hand-holding, on purpose

As the lead, I want to follow each customer closely, an email every day if that helps, with three questions each time, so that the attentiveness makes up for an early product. From Hand-holding, on purpose · lands on /follow-up/.

• Each customer's follow-up asks three things: what they did, what got in the way, and what is next. From Hand-holding, on purpose.
  • The answers go on the customer page as a log of date plus three sentences, newest first. · lands on /customers/example/
  • The follow-up is a role file with the rules and the message template. · lands on /team/roles/customer-follow-up.html
• That will not scale, and it is not meant to yet. From Hand-holding, on purpose.

What we want to discover: the usage moment

As the lead, I want to find the moment a behaviour policy becomes worth something to a particular person, through three questions, with the things to track per customer kept simple. From What we want to discover · lands on /learning/.

• What is the simplest useful behaviour policy; what is the entry point with least friction; what is the price. From What we want to discover.
  • A findings table that starts empty and is filled with a count per finding. · lands on /learning/
• Track per customer: when they started, when they wrote their first behaviour policy, how many rows and gaps it has, which milestones are done, what they used of the credit, and whether they topped up. From What we want to discover.
  • The batch table is exactly those fields, one row per customer, and the home page counts are their sums. · lands on /customers/

Batches, and a list for the next one

As someone who asks to join, I want to be kept for the next batch with what I want to use it for, and for the next batch to start from what the first one taught. From Batches, and a list for the next one · lands on /next-batch/.

• Everyone who asks to join is kept for the next batch, with what they want to use it for. From Batches, and a list for the next one.
  • The page says how to ask today, what is kept, and that only the count is published. · lands on /next-batch/
• The programme is one people propose to join, because capacity is limited. From What it adds to the brief.

The first users are us, and the agents

As the lead, I want the first batch to be me, the co-founder and the agents I already run, with explicit behaviour policies for Claude and ChatGPT covering the agent rows and the hook rows, produced by the agent that is wired in. From What it adds to the brief · lands on /customers/.

• The main users are the lead, the co-founder, and about ten agents that need behaviour policies. From What it adds to the brief.
  • Three records: the lead, the co-founder, the agents as one customer. · lands on /customers/
• Two of the three places a behaviour policy can run: the rows for the agent, and the rows for the hooks. From What it adds to the brief.
  • Step S5 on the ladder, the hooks half. · lands on /milestones/#S5
• The agent that is wired in gets the responsibility and the requirement to create the end behaviour policy. From What it adds to the brief.
  • The reality file carries it as proposed; the agents record's objective names it. · lands on /customers/the-agents/

What this does not claim

As a reader, I want the site to say what is new, what is not set, what is real and what is not, and to name nobody who did not agree. From What this does not claim · lands on /docs/reality.html.

• The programme is new; the prices are not set; the metering is the newsroom's; no customer is named; everything is open. From What this does not claim.
  • data/reality.json carries each as shipped, proposed or absent, and the home page repeats the disclaimer. · lands on /docs/reality.html
  • Where the memo names the first users, C2 in the corrections file says how that was reconciled with no-customer-is-named. · lands on /docs/brief/BRIEF-CORRECTIONS.html

What is not here

The derived half: the code read bottom up by parsers, the join with a coverage figure, every commit read upwards, the navigator as web components, and the same folder for the tools. The folder's README says what exists and its corrections file says why the rest does not yet.