Home / Docs / The pack / The First Examples

The First Examples

The source bytes. This page is generated from docs/pack/04__THE-FIRST-EXAMPLES.md, which is served unchanged. Anything rendered on this network stays one click from the file it came from.

The memo asks for a few ABPs, from simple to complex, to find out what they look like in practice and how hard they are to make. The answer is that the first five can be derived rather than authored, because the data exists.

The seed

what-can-it-do.games.sgit.ai/map/ publishes, as JSON at a stable address with cross origin access:

Twenty three capability primitives, in verb.object.reach form, each with a published gloss.
Nine product profiles, each with a grant expressed as primitives.
A barrier glyph on every profile and capability cell.
An undo class on every capability.
Eight mandates, one per surface, described as what a reasonable person wanted, per setup.
Delta matrices, excess in one colour and shortfall in the other.
A provenance statement: of ninety nine tool capability rows, twenty one were measured and the rest are derived.

Two pages carry the halves this site needs: /map/mandates/ and /map/deltas/.

So the first ABP is a rendering of data that already passes through a published pipeline. The work is the rendering, the schema and the honesty line, not the research.

The five, in order of difficulty

#	Deployment shape	Why it is this one	What is new in it
1	ChatGPT web, no connectors	The smallest grant in the set. A reader who does not believe agents can do much starts here and finds the delta is still not empty	Establishes the four objects with the fewest moving parts
2	Claude Code CLI, confirmations enabled	The confirmation is a barrier, and a reader can see which row it sits on	Introduces the barrier glyph as the argument. A confirmation is the second or third row, not the fourth
3	Claude Code CLI, confirmations disabled	The same agent, one setting different, and the delta changes	The environment is the grant. Two documents for one agent, differing in one line, is the clearest possible demonstration
4	Browser extension, broad host permissions	`read.record.browsing`, and the mandate nobody wrote down	Introduces other people's data: the pages you visit were not all yours to hand over
5	GitHub Actions, hosted runner	A service account, `write.repository.tenant`, `create.schedule.host`	Introduces persistence and reach beyond the turn, and the irreversible class

Example three is the one to build first if only one gets built. One setting, two documents, a visible difference in the delta. It makes the case that the ABP is about the deployment rather than the product in a way no paragraph can.

What each example page contains

The shape, in the profile's published words.
The grant: primitives, each with barrier and undo, ordered by irreversible and unbounded first.
The mandate: the authorised set, in plain sentences.
The delta: excess and shortfall, computed on the page.
The prohibitions: the enforceable projection, each with the layer it would be enforced at and whether it is enforced today.
The provenance: measured against derived, with the date.
The disclaimer, which is not optional and is covered in 05__THE-HARD-RULES.md.

The workflow question the memo actually asks

Let's see how hard it is to make one, how fast we can make them.

Instrument it. Record, for each of the five: how long it took, how many rows were derived rather than measured, how many questions had to be asked of a human, and which step was slowest. Publish that on the site as a table.

Two reasons. It is the estate's own honesty discipline, measured rather than guessed. And it is the pricing input: the store sells an ABP, and nobody knows yet what one costs to produce.

Documents first, then vaults

The memo proposes doing both, documents first. That is right and the pack agrees, for a reason worth stating: a document forces the rendering question immediately, and the rendering is where the five layers problem shows up. A vault can hold a graph nobody has successfully rendered for an executive.

So: five markdown documents with their JSON twins, in this repository, rendered through the docs section. Then the vault, which is the cloneable instance and belongs to the store's side of the boundary.

The educational claim, and how to keep it honest

The memo expects the site to be educational because most people do not understand the grants. The evidence supports that as a claim about a gap, and it does not support a claim that a document teaches.

From 10 September: games beat conventional instruction by about a third of a standard deviation, and by minus 0.12 when they replace training rather than supplement it. The strongest defensible finding is that interactive beats static among the people who finish.

So the site should link to the game rather than reproduce it, and the examples should invite the reader to state a belief before showing them the answer. A page that says before you scroll, write down how many of these twenty three this agent has is doing the same work the game does, at the cost of one sentence.

This document is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).