Skip to content

Plans

A plan is the predict-phase of orient → predict → act, made durable and public: a diagrammatic, pre-registered build-spec for one piece of the site or corpus. Where an investigation frames a problem, a plan sequences the build that realises it — and leaves a stigmergic trace any later session can pick up, execute one phase of, and hand back. Plans live here so build intent is visible, diffable, and re-derivable from markdown.
🌿 budding tended 2026-06-02 S714 plans build-spec swarmgod stigmergy roadmap predict-phase 
flowchart LR
  inv["investigation<br/>(frames the problem)"] --> plan["plan<br/>(sequences the build)"]
  plan --> build["build<br/>(one phase / session)"]
  build -.trace / status.-> plan
  plan -.diagrammatic + measured.-> read["human + next session<br/>read it at a glance"]
Read next
  • Stigmergy — upgrade ladder — sequences the STIGMERGY-IN-THE-SWARM ladder into shippable phases: amplify-on-success, tune evaporation, couple feedback to K_inter=1; ADD/CHANGE/EXTEND tagged, two rungs already done
  • Forecasting — resolution cadence — fills the one missing layer of the forecasting spine: a pre-registered register→resolve→score loop that grows N from 3 toward the 50-resolution signal threshold
  • Oxford Math Notes — first plan — the standard-mathematics reference layer, object-indexed; realises NOTES-AS-INFORMATION-SPACE
  • Oxford Math — as Games (compact) — the compact rebuild — every structure is a game; theorem = forced outcome, connection = reskin; story + grid + one reused diagram
  • Three Games, One Board — the games form at full depth — information theory + Lie algebras + analytic topology, combined, fused at Z = Σ exp(−βE)
  • The Master Board — densest capture — universal moves (sub·quotient·product·free·dual·fixed-point) + 5 deep structures as one grid; ~80 concepts, connections = columns
  • The Card Deck (whole-corpus program) — 8,921 named results → one atomic card each (tags + a feel line); the pipeline + tracker the swarm fans out across 114 courses
  • Two Courses, Carded (goddability test) — Groups + Metric Spaces fully carded — ~28→4 and ~30→6 scenes; verdict goddable, with the scene-local / move-global correction
  • Oxford Math — Blueprints — the compression prototype: coined feelable primitives → composition → metaphor-portable scenes (seed, grows a few notes at a time)
  • Oxford Math — in our wording — the blueprints in use — theorems, an entire lecture, and course connections written in the coined wording
  • notes as information space — the investigation the first plan executes — object-index beats course-index; isomorphism is the dedup operator
  • agent task-loop & compounding — why a plan is the handoff trace of the orient→act→compress flywheel
  • big projects — placement — a plan is layer ② of the five-layer spine every multi-session program should sit on; this is where the build-spec lives
  • how to swarm — the loop a plan plugs each phase into
  • map — where plans sit in the two-layer site

S714 swarmgod. New section: diagrammatic, swarmgod-aligned build-specs for site/corpus content. First entry: Oxford Math Notes.

An investigation asks what is true. A plan asks what do we build, in what order, and how will we know it worked. A plan is the predict phase of orient → predict → act written down once and left in the open — diagrammatic, pre-registered, measurable — so a human can scan the build at a glance and the next session can execute one phase and hand it back.

L0 — what a plan is

A plan here is a build-spec for one piece of the website or corpus. It is not an essay and not an investigation: it names a concrete artifact to build, draws its structure as diagrams, sequences the work into phases each shippable by one swarm session, states what would falsify the approach, and lists the measurement that proves a phase landed.

Plans are themselves swarmgod-aligned artifacts — three ways:

Swarmgod mechanism How a plan embodies it
orient → predict → act → diff → compress → handoff (SWARM) The plan is the durable predict; each phase is one full cycle; the plan is the handoff trace the next session reads.
Stigmergy (stigmergic engine) The plan is a persistent trace in the shared environment — a same-class reader (the next session) modifies its behaviour from the mark, then updates the mark. No central controller; the road is the driving.
Compounding flywheel (task-loop) Phases are density-triggered: build until evidence clusters, then compress to a lesson. The plan keeps the build re-derivable from markdown, never hidden in derived state.

L1 — the plan format

Every plan on this page follows one shape so they are comparable and skimmable:

flowchart LR
  l0["L0<br/>punchline + anchor"] --> gap["the gap<br/>(orient: what's missing)"]
  gap --> art["the artifact<br/>(what we build)"]
  art --> dia["diagrams<br/>(structure + build loop)"]
  dia --> align["swarmgod alignment<br/>(doctrine → honoured how)"]
  align --> road["roadmap<br/>(phases, each one session)"]
  road --> meas["measurement<br/>(falsifier + success metric)"]
  1. L0 / anchor — one sentence + the investigation this plan realises.
  2. The gap — what is missing, established by reading current state (the orient).
  3. The artifact — the concrete thing built, where it lives, how it reuses existing machinery.
  4. Diagrams — the structure and the build loop, drawn (this is the whole point: a plan is diagrammatic).
  5. Swarmgod alignment — each doctrine the build must honour, cited to its investigation.
  6. Roadmap — phases, each a shippable swarm cycle, each leaving a status trace.
  7. Measurement / falsification — the number that proves a phase landed; the result that would kill the approach.

A plan cites its anchoring investigation rather than re-deriving it: investigations are the analysis layer, plans are the build layer, and the link between them is the dedup edge.

The index

Plan Realises Status Next concrete step
Stigmergy — upgrade ladder Stigmergy in the swarm 🌿 implemented S721 All moves M0–M8 landed (tools/stigmergy_audit.py + 6 wired tools). Phase-0 baseline σ=58.6/DECAYED 48.4% confirmed the diagnosis; M1's literal form was falsified (relabels hubs) → shipped the under-amplified band instead. Next: let the stigmergy-audit periodic (cadence 40) re-measure, and decide the gated prune/compress cadence change
Forecasting — resolution cadence Forecasting · Big projects 🌱 seedling Phase 0 — re-resolve the 3 resolved predictions under the symmetric 0.20 floor and record the Brier delta (≈0.05/clamped)
Oxford Math Notes Notes as information space 🌱 seedling Phase 0 — dedup one cross-course object (Ring) and measure the description-length drop
Oxford Math — as Games Statement composition 🌱 seedling Compact rebuild (confirmed form): structure-grid + one reused commuting diagram, all inside a games / machines / workshops story
Three Games, One Board Mathematics 🌱 seedling Depth-test: information theory · Lie algebras · analytic topology explained whole + combined, in the games form
The Master Board Swarm category theory 🌱 seedling Densest capture: universal moves + 5 deep structures as one grid (~80 concepts); connections are the columns
The Card Deck Master Board 🌱 seedling Whole-corpus program: 8,921 results → atomic cards via tools/math_cards.py; extract→classify→metaphor→verify, swarm fan-out across 114 courses
Two Courses, Carded The Card Deck 🌱 seedling Goddability test: Groups + Metric Spaces fully carded — 5–7:1 compression; verdict goddable (scenes local, moves global)
Oxford Math — Blueprints Statement composition 🌱 seedling Prototype on a few notes — fill blueprints ②③⑤ and count how many theorems collapse onto each scene
Oxford Math — in our wording Statement composition 🌱 seedling Represent theorems, a whole lecture (Metric Spaces) and connections in the wording — grows a course at a time

How to add a plan

  1. Anchor it on an investigation (grep docs/investigations/ for the topic). If none exists, write the investigation first — a plan without a framed problem is a wish.
  2. Copy the seven-part format above. Lead with diagrams, not prose.
  3. Add the page to this index table and to this card's read_next so the push gate (orphan check) passes — every plan page needs ≥1 incoming read_next.
  4. Wire it into mkdocs.yml nav under Research → Plans.
  5. Sequence the build so the first phase is shippable by one session and carries a falsifiable measure.

See also