the proof wall · cohort one · publicly recorded
cohorts pass. receipts hold.
an institution is what it ships, signs, and lets the world read. below is the working record of agentic-u so far. no testimonials in the marketing sense. only artefacts.
We refuse the testimonial pattern. It is the lowest form of proof an institution can offer, because the operator who is being quoted has not, in most cases, been asked to sign anything. Their words are good — but their words are not a receipt. A receipt is an artefact, dated, signed, that can be held against the producer's later work.
Below is the proof wall. It is the working record of what has actually been produced under the standard. Cohort one is in progress; some artefacts are redacted to operator preference; none of them are fabricated. When something is provisional, we say so. When something is a benchmark in motion, we say so. When a receipt has been signed and held, we publish it.
how the receipts work.
Every operator in the initiation produces six receipts across thirteen weeks. Each receipt is a working artefact — a memo, a runbook, a governance draft, a one-page architecture — produced under load and submitted to the council. The council marks each receipt against the standard; the operator signs; the artefact is held. Held receipts are what the operator carries out of the initiation.
-
weeks 1–3
diagnosis + setting
1 receipt signed in council
-
weeks 4–9
pillar progression
3 receipts signed in council
-
weeks 10–13
portfolio + standing
2 receipts signed in council
the published wall (so far).
SOV-001cohort 1 · week 3
A sovereignty memo, signed by an operator on the eve of a quarterly board.
One operator named the three places in their company where an agent was acting unsupervised, and the two places where they themselves had effectively delegated their own judgment to chat completions. The memo was eight paragraphs. It changed the board agenda.
pillar: sovereignty · marked: held · operator: redacted by request
SYS-002cohort 1 · week 5
A systems-literacy diagnosis of an internal agent stack, traced to a single missing handoff.
Operator traced six months of "weird agent behaviour" to one unstaffed handoff between an LLM router and a human approver. The runbook patch was two paragraphs. The team had been throwing prompt-engineering at the problem for nine weeks.
pillar: systems · marked: held · operator: redacted by request
COO-003cohort 1 · week 7
A coordination charter for a five-person team holding seventy-three agents.
One page. Names every agent. Names who holds it. Names what it is allowed to act on. Names the review cadence. The charter was adopted at the next standup; the team reported two weeks later that "we know who owns what for the first time."
pillar: coordination · marked: held · operator: cohort 1 founder, redacted
NAV-004cohort 1 · week 9
A navigation receipt — a 12-month roadmap rewritten in 90 minutes against the standard.
The pre-initiation roadmap was 47 slides. The post-initiation roadmap was 5 paragraphs. The 5-paragraph version was signed by the CEO and posted on the company wiki the same day. The 47-slide deck has not been re-opened.
pillar: navigation · marked: held · operator: redacted by request
TRA-005cohort 1 · week 11 · in motion
Translation receipt: bridging an existing compliance regime to operator-grade AI governance.
In progress. Operator is at week 11. Receipt will be signed and published at the close of movement III. The brief is to translate an SOC2-shaped regime into a working agentic governance memo for a regulated industry.
pillar: translation · marked: in motion · publish target: 2026-05-29
DER-006cohort 1 · week 13 · pending
The derivation receipt — what each operator names as their own contribution to the standard.
Movement III, week thirteen. Each operator produces one paragraph naming a refinement, exception, or extension to the standard that arose from their own initiation. The strongest derivations are folded into the next version of the standard. This is how the standard evolves — through receipts.
pillar: derivation · marked: pending · publish target: 2026-06-12
The signed memo is the receipt. The standing is what the council says when they read it. The carry is what you take into your next quarter. Three things, in that order.
what receipts are not.
three categories we refuse to publish.
- screenshots of "this changed my life!" dms — we do not publish unsolicited testimonials. they are not signed; they are not artefacts; and they invite the worst form of social proof. if an operator wants to write a recommendation, we ask them to write it as a memo and sign it.
- anonymous "cohort one founder said…" pull-quotes — every pull-quote on the site is either attributed to a named role inside agentic-u (founder, councillor, registrar) or paraphrased as a pattern across the cohort and labelled as such. we do not invent quotes.
- polished case studies with no signed artefact behind them — we refuse the case-study genre. case studies are written by marketing; receipts are signed by operators. if there is no signed artefact, there is no entry on this wall.
the standing council, named.
The receipts above are marked by the founding council — three seated councillors who read every receipt before it is held. The council is named publicly on the council page, with bios, prior receipts of their own, and their councillor cadence. There is no anonymous review layer. There is no marketing-side editor. The council marks; the operator signs; the artefact is held.
why we publish at all.
Because an institution that asks operators to sign artefacts must be willing to sign its own. The receipts wall is, in this precise sense, agentic-u's receipt — to the cohort, to the broader operator community, and to the future versions of itself that will be measured against it. We publish so that we can be held to what we publish.
I trust an institution that publishes a wall of its own work. I do not trust an institution that publishes a wall of testimonials about its work. The difference is the receipt.
the receipts begin where the initiation begins.
If you want to produce a receipt of your own — six of them, in fact — the door is the initiation of initiation. Begin with the scorecard; we'll tell you whether the initiation is the right next room.
want a specific receipt referenced for due diligence? contact the registrar.