The first batch

1. The first batch
2. First us, then the agents we already run The lead: “We go first.” The agent: “And about ten of us.” The memo of 20 October: the main users are the lead, the co-founder and the agents the lead already runs.
3. Every agent needs a behaviour policy of its own The agent: “Mine says what I may touch.” The agents; the site publishers; the newsroom writer; the inbox agent; the coding sessions; two have one today The wired-in agent gets the job of producing the end behaviour policy for the others.
4. Every day, three questions The lead: “What did you do? What got in the way? What's next?” Maya: “One line each?” Hand-holding on purpose. It will not scale, and it is not meant to yet.
5. Seven steps, shared by everyone in the batch S0: in, with credit; S1: one agent named; S2: the grant; S3: the mandate; S4: the delta; S5: the hooks; S6: the usage moment The objectives are each customer's own; the steps are the shared shape, so the batch reads in one table.
6. Every page has a price, and we learn the fair one Maya: “Would I pay for that page?” The credit tells us how much each customer uses before they would top up; the follow-up tells us why.
7. Everyone who asks is kept for the next batch Imani: “Can I join?” The next batch; who asked; what for; a start-here page; made from this one Capacity is limited, so the programme is one people propose to join.
8. The usage moment: when it becomes worth something to you. The simplest useful behaviour policy, the entry with least friction, and the price that feels fair.

The data: bundle.json, the storyboard with its cast. Every line a character says is the storyboard's, not a quote. What is said to happen is what the brief and the memo of 20 October 2026 say; what exists is in docs/reality.md.