Where this goes

The trunk is what you can read today: the essay, the worked loop, the notation and kit. Below are the branches. They are scope, consciously deferred, not promises. Each one graduates to the navigation bar when it exists, and not before.

The trunk live

The essay makes the argument. The loop works it end to end on a real example. The notation defines the subset and ships the agent kit. This site is complete as it stands: if nothing below is ever built, nothing above is diminished.

Branch 1 · The runnable notebook next

The demo page walks the loop by hand; this automates it. A Jupyter notebook where a notation cell executes against a real interpreter (Dyalog's free non-commercial license, or J, or an embeddable open-source APL), an agent expands it in the next cell, and a harness cell runs the randomized comparison. What it takes: an interpreter bridge and a few hundred lines of glue. This is the highest-value branch because it turns the argument into a thing you can run.

Branch 2 · Sample workbooks deferred

The moving average is deliberately small. Workbooks would apply the loop to problems people recognize: portfolio return and risk statistics, a data-cleaning ruleset, an attention block, a windowed anomaly detector. What it takes: the notebook from branch 1, plus curation. Each workbook is one afternoon once the plumbing exists.

Branch 3 · The verification harness as a tool deferred

The generalization: a small CI step where notation files sit next to source files, and every build re-judges the generated code against its executable spec. Vibe verification with an independent oracle, as a `pytest` plugin or GitHub Action. What it takes: the harness from branch 1, packaged; a design decision about how specs and implementations declare their pairing.

Branch 4 · A fluent-agent kit for every tool deferred

The kit ships today as one markdown file. This branch grows it into first-class packaging: a Claude Code skill, a Cursor rules file, a system-prompt module, plus an eval set that measures whether an agent actually got more fluent with the kit in context. What it takes: mostly evaluation discipline, not code.

Branch 5 · Talks and writing deferred

The 20-minute meetup version of the essay, aimed at Amsterdam first. The essay is the citable artifact; talks are how ideas travel between people who will never read it. What it takes: the notebook demo on a projector and one good evening.

Community, borrowed on purpose

There is no forum here and there will not be one. A language may be 80 percent community, but an idea only needs rooms where the right people already talk, and those rooms exist: The Array Cast · r/apljk · the APL Farm · APL Wiki · Dyalog. If you want to talk about APLflow, do it there, or bring it to a meetup. That is the whole community plan, and it is deliberate.