The codes, decoded
This project keeps a working record, and the record uses short codes. A reader shouldn't have to guess them. Here is what each one means. (This decodes the codes. A separate glossary already defines the project's three contested terms — "systems theory," "today," "understanding" — and its systems vocabulary. A plain-language glossary of the project's load-bearing operational words — catch, governor, rung, pressure-test, and the rest — is still the author's to write and is on the queue.)
Sessions
A session is one working block. They run S1, S2, S3, S4, and then the fourth block subdivides as work intensified: S4, S4b, S4c … through S4h, S4i, S4j, S4k. So S4h means "the eighth working block of the fourth phase," S4i the ninth, S4j the tenth, and S4k the eleventh — the author's ratifying close, where the build was closed. Nothing deeper is meant by the letters — they are just a counter.
The fourteen pressure-tests
The project's symptoms of "today" are organized in four layers, each with a letter-code, plus one cross-cutting test:
| Code | Layer | Meaning |
|---|---|---|
| M | Master | the coherence vacuum — the loss of a shared "why" |
| D1–D4 | Drivers | acceleration · optimization · the wealth pump (inequality) · machine intelligence |
| Y1–Y4 | Dynamics | epistemic breakdown · coordination failure · institutional decay · ecological overshoot |
| S1–S4 | Symptoms | fertility collapse · the attention/dopamine economy · populism · anomie & loneliness |
| R | Cross-cutting | register / care fairness — does the account (and the apparatus producing it) under-weight the reproductive, domestic, relational register; sits across the four layers, not inside one. A falsifiable test, not yet run (added S4k, promoted from disagreement D-005) |
The record's ID prefixes
| Prefix | What it labels | Where it lives |
|---|---|---|
| C-0NN | a catch — an error, near-miss, or correction, logged as it happens | Catches |
| L-0NN | a learning — a distilled lesson from repeated catches | Learnings |
| Q-0NN | an open question — an unresolved item on the frontier | Open questions |
| D-0NN | a live disagreement — a standing split kept open by design | Open questions |
| DC-0NN | a decision changed — something the project subtracted or reversed | the decisions-changed log (the "drain") |
| R + a number | a ground rule — a rule of the project's own constitution (e.g. R25, the moratorium). A bare R (no number) is a different code entirely: the fourteenth pressure-test, register/care (see the table above) | Ground rules |
A "move," a "rung," a "delegation"
A move is a planned step in the project's roadmap (Move 1, Move 2 …) — an internal sequence, not a game. A rung is a level on the project's evidence ladder, from "fact" up to "theory"; to say "no rung has moved" is to say no claim has gained or lost evidential standing. A standing delegation is a stretch where the author asked the machine to keep working autonomously; each was booked as a cost and left provisional until his review — which came at Session 4k, when he ruled on them item-by-item and closed the build.
If a term on this site still reads as jargon after this page, that is a finding, not your failure — and it is on the record as one.