Management as Ontology / Changelog v8.3.0 · glossary · changelog

Canon changelog

One entry per release, newest first. The canon's Version: line keeps the current version and the semver rule; the history lives here since v5.2.2 (2026-10-15), when it was 4,615 words of the canon and no reader needed it in the text. v1.0.0 is the 2026-08-20 "v1 complete" baseline.

v8.3.0 (2026-10-27) #

v8.3.0 (2026-10-27): a minor, DEC-749 (Norman, 27 Oct 15:36 SGT: "sounds good", on the shape put to him from 15:20 to 15:29, after his own words at 15:18; provisional). Two details of principle 5. An agent that holds an issue owns its outcome: it notices, decides the next move and drives the work without being told, and an agent's outcome is its KPIs and the projects it leads; a person still answers for the outcome, because an agent cannot be held accountable (his words: "I would want agents to own outcomes, and drive?"). And a team's own choices have one exception: a bug an agent comes across in its own code, outside the reviews of the issue it is working on (that issue's lane fixes those, as the leftovers sort says, DEC-704 and DEC-746), always gets an issue, which the agent fixes and ships, and such a bug is fixed or closed as won't-fix with its reason, never shelved for later (Linear's zero-bugs policy). What wakes an agent, its morning drive and how it asks people are Relay's mechanism, in Charter section 17 and the work-management skill (core PR #1683, not yet merged). It is a minor: no principle is added or removed and no principle's one line changes.

v8.2.0 (2026-10-27) #

v8.2.0 (2026-10-27): a minor, DEC-744 (Norman, 27 Oct 01:41 SGT: "B, linear's way. But the project should still have the Four Factors?", after "A big feature is definitely a project right, only a small feature will be issue" at 01:40; provisional), PROD-307. It re-rules DEC-739's second part, which v8.1.0 carried. A feature with several pieces is a project, as in Linear; a small feature, one holder for a day or two, is an issue, with sub-issues for any pieces that stand apart (an issue's steps stay a checklist, DEC-722); when unsure, start as an issue (principle 4). v8.1.0's "size never makes a project; who waits for it does" and its reason are withdrawn. Every project keeps its four factors, set up by the agent that owns it: the one place the method's projects differ from Linear's, which are light (principle 6). A shared team's piece of a project is an issue on the shared team inside that project; its piece of a single issue is a sub-issue under it (principle 5). DEC-739's other parts stand: a sub-issue may sit on another team, and a shared service with its own work is its own team. The glossary's Project, Parent issue and Shared team follow. It is a minor: no principle is added or removed and no principle's one line changes; details of principles 4 and 5 are replaced and principle 6 gains one. Relay's manual follows by the DEC-744 doctrine change to Charter section 17 and the work-management skill, not yet merged.

v8.1.0 (2026-10-26) #

v8.1.0 (2026-10-26): a minor, DEC-739 (Norman, 26 Oct 20:19 SGT: "ok yeah lets lock it in"; provisional), PROD-307. Who waits for a change decides its shape: an issue for one holder and a day or two of work, a parent issue with sub-issues when only its own team tracks the pieces, however big, and a project when other teams plan their own work around it; size never makes a project (principle 4, with its why: a project's date and health are for the people outside the team). This replaces v8.0.0's project threshold, an outcome beyond one team (DEC-696). A sub-issue may sit on a team other than its parent's, which walks it, as in Linear, and a shared service with its own work, such as testing, is its own team, a shared team (principle 5). The glossary's Project follows, with new rows for Parent issue, Sub-issue and Shared team. It is a minor: no principle is added or removed and no principle's one line changes; one detail of principle 4 is replaced and principle 5 gains detail. Relay's manual follows by the DEC-739 doctrine change to Charter section 17 and the work-management skill, not yet merged; the sub-issue on another team is not built yet (PROD-305).

v8.0.0 (2026-10-26) #

v8.0.0 (2026-10-26): the fifth major, MO as a standard that Relay implements (DEC-728). Norman, 25 Oct 23:13 SGT: "Originally I wanted MO to be the guiding principle where Relay is an implementation of it"; his go at 26 Oct 00:11, "yeah go!".

Why. The critique of 25 October traced every clause of v7.0.0. Provenance: 15% of the clauses were Norman's words; 65% were model proposals he approved, often within a minute. Use: of 537 clauses, 345 changed a dated decision on the Gotrade fleet or run there as a mechanism, and 26 of the 53 stamps and receipts did not hold. The fleet had also moved past the text (DEC-696, DEC-725, DEC-727) without anyone seeing a divergence, because the canon mixed principles with mechanism, and it was kept in three hand-made copies (the canon at 30,200 words, the fleet skill at 19,200, the kernel at 7,800). Prior art for the new shape: the Linear Method, a short set of principles that Linear the product implements (MO is to Relay what the Linear Method is to Linear); Diátaxis, which keeps the why apart from the how; and the Scrum Guide's 2020 cut to 13 pages. The per-principle headings borrow the GOV.UK Service Standard's.

What changed.

  • The form. 31 principles in seven parts, about 6,900 words, under a quarter of v7.0.0. Each has the same parts: the principle with Norman's own words above it where he said it, why it matters, what it means, where Relay implements it, and the decisions that made, changed or applied it. Relay's documents (the Charter, mostly its sections 17 and 19; the work-management skill; and the how-to sections of the fleet's MO skill) are the manual; the standard never restates them.
  • What survived. 358 of the 537 clauses: the 78 in Norman's words that were used or that he kept on 25 Oct, the 277 the fleet used (rewritten in plain words), and 3 kept once where the canon repeated itself. 297 went into the principles, 33 into the Charter as mechanism, and 28 stamps became the principles' decision links. Norman ruled his 17 unused clauses on 25 Oct (22:19 and 22:23): 13 kept, 4 cut. The fresh reviews of 26 Oct found 9 of the 33 in no Charter section (the register's terminal and resting states, zone reservation, the OKG's storage, re-homing as a one-time act on a ruling, a rest never outrunning a hard clock, the triangle of concern, project and initiative, and a workflow's receipts landing in a ledger), so they moved into the principles. It also re-kept 3 cut clauses the kept text cannot stand without: the pain door's "what noun or place is missing?", and the done-test's "now" and "never" answers. So 361 clauses survive: 309 in the principles, 24 in the Charter, 28 as decision links.
  • What was cut (176 clauses, neither used nor kept by Norman; 4 of them are his own words, which he ruled cut on 25 Oct): killable by evidence; "structure the pipeline, never the ideation" as a law (its idea lives on in principle 4: an idea waits until someone asks for it); the three skills except jobs first; the catechism except its pain-door questions; the ten-word mantra; the stage curve's operator trap, system scale, shift-left and moat; calcification's three loci; the cognitive-fit law's science and prior art; the attention scoreboard; the walk ladder's machine form (never built); the training program, the prior-art essay, the lineage and the honest scope (its "substance stays human" survives in the three seats, a kept clause); authoring gated on a course; edition-scoped ranks; "code speaks layer 1"; and the view-only mini-app example.
  • The manual. DEC-728 names "a short concerns skill" among Relay's documents. Until one is written, that is the how-to sections the fleet's MO skill keeps beside the standard.
  • No stamps. SETTLED and PROVISIONAL, receipts and dues leave the text. Each principle links to the decisions that made, changed or applied it, and the evidence stays in those records.
  • Retired files (restorable from history): the law register, the lecture, workshop kit, exams, casebook, cards, the Relay and Laravel editions, the examples, the roadmap, ORGAN-TYPES.yaml, SPINE-SCHEMA.yaml and the PDF tooling. The release gate and the site build were rewritten for the new shape; the site is the standard, the glossary and this changelog. canon.json stays, for the estate's read-only connector: it now holds the standard's sections and the glossary, with no law register.
  • The glossary was rebuilt from the names v8 uses (92 concepts), keeping the retired synonyms the gate refuses. It does not refuse "task" or "objective" yet: Relay's tool names still say task.

Rules that changed, each following a ruling or the fleet's practice (open to Norman's challenge):

  • The standard speaks its implementation's words for the work grain: issue, project, initiative. "Task" and "objective" were the canon's names with Relay's as display labels; there is now one name.
  • A project is only for an outcome that reaches beyond one team (DEC-696).
  • Work runs on issues; a concern's register keeps only its record's own states and facts; approvals are sign-offs; a person's work on a clock is a recurring issue the concern owns (DEC-725, PROD-288).
  • Cycles and estimates are a team's option, off by default, and a team's read of where its time went never ranks a person (DEC-727, PROD-288).
  • The lead team is the team that leads a project and walks it; it can change after birth (DEC-720; PROD-273: "is home to" is gone, and who may change it is Relay's to say, in Charter section 17: its lead, its owning agent or a workspace admin).
  • Moving records to another company may mint new codes there if every old code answers forever (DEC-618, DEC-667), where v7 said identities never renumber.
  • A renamed identity (a code, a slug, a URL) answers to its old name forever; a renamed word, a tool name included, is a clean cut, and a tool's old name may stay as an alias only when it carries no retired word (DEC-206 cut the relay_tracker_* tools cleanly; DEC-166 kept relay_concern_lookup, which carries none).
  • Drop means nothing more is owed, said in a line, as the concern walk stamps it.
  • A walk is going through one list of exceptions until every item has a disposition; a ceremony is a meeting that walks a docket from several concerns. The register walk reads what aged past the floor's clock and sends what keeps recurring to gardening, never further up (the gap all twelve v6.1.1 readers flagged).
  • The scoreboard leaves the organ types: nothing binds it since the WIGs retired, and an initiative's number is its owner's word, never scored. Eight types remain.
  • Whoever will own a concern may declare it, and its first walk reviews it on the record (DEC-107), in place of v7's apprenticeship grants, whose allowlist has been empty since DEC-107.
  • Construction grounds' "import and prune" is cut: its only receipt did not hold (the security concern kept all 93 controls); the committee ontology and the coverage walk stay.
  • A team is an area of work and the people and agents who do it, never a reporting line (DEC-710), where v7 had a roster that earned a walk.
  • The readability principle adds the plain-words rule: keep the terms of art readers know, and explain a term once (DEC-707, Charter section 10).
  • The provenance principle adds that a ruling stands until it is re-ruled, on the record (DEC-583, the Charter's closing section).
  • The lead measure leaves the goal layer: an initiative's number is its owner's word, never scored (DEC-709).
  • An idea waits, in conversation or on a team's list of ideas, until someone asks for it (DEC-696, DEC-700, DEC-716), where v7 made an idea for later one task in the backlog.
  • An induction no longer says it has no clock: Relay asks every verb for one, an induction included.
  • Follow-up, not yet ruled: Charter section 19 and Relay's concern validator still name nine organ types, the scoreboard among them. The Charter changes with this release's core PR; whether the validator drops the type is a person's ruling.

v7.0.0 (2026-10-25) #

v7.0.0 (2026-10-25): the fourth major, the company canon. On the author's ruling of 25 October (00:31 to 01:26 SGT), MO is for how a group of companies runs on Relay, Gotrade first; everything about his personal estate leaves this canon. The whole repo was forked first, with its history, to cashew-webmaker/management-as-ontology-personal at v6.1.1 (f64bf8d), so nothing is lost, and the personal edition continues there. A classification of all sixty units found none personal: every law, model and instrument governs a company, and the estate had supplied evidence, examples and framing, never rules. So the prune is delete-only and keeps every law: removed are the estate edition and the single-player versus multiplayer framing (an EDITION now means the canon bound to an implementation: the Relay edition, the Laravel stack edition), the personal examples (the gym and marathon blocks and their example file, the training worked example, the casebook's inbox and brokerage cases, the lecture's electricity-bill example) and the estate receipts. SETTLED now needs a company receipt: kept on company receipts are the identity law (DEC-26, the reference-code registry; DEC-615, the zone registry on Relay's console), spine anatomy, the register's walk set, two kinds of processes, inspect means exceptions (walk 445, DEC-162) and type by role (DEC-152); spec and implementation, calcification and the qualifier corollary become PROVISIONAL with their dues (nineteen provisional laws). Induction cites FIO-140; flip conditions cite Relay's Coverage gap acceptances and the decision register's revisit_trigger column. "A second deployment" in dues and admission rules means a second company or Relay workspace in the group. The scoreboard stays the ninth organ type, with no live binding since the WIGs retired and the personal estate left. Also a vocabulary cut in the same major: LEAD TEAM replaces home team (DEC-720, PROD-199, the author's ruling of 25 October 01:35), the team that leads a project, set at birth, changed by its lead, whose walk carries the project; home team is deprecated with no alias, and the release gate refuses it. The typed-link example is now a Check GUARDS a Task (relay-boards). Checked by a fresh reviewer against the classifier's map and every removed line (two blocking findings fixed: a receipt claim that every DEC row carries a revisit trigger, and the species law's due losing the fleet), then one re-check of the fixes. Company examples to replace the removed ones, and every law's provenance and worth, come with the canon's critique, which is next.

v6.1.1 (2026-10-25) #

v6.1.1 (2026-10-25): a patch, wording only, the first plain-words release under DEC-707 (PROD-209): Part 2.5's two-kinds law and the walk ladder in plain words and short sentences, one idea to a sentence, every defined term and term of art kept, nothing cut, with their nine glossary rows following the new defining sentences. Born when the author found on 24 October that he had read walk and ceremony as one thing for weeks. The wording resolves two old inconsistencies the way the rest of the text already read: the floor walk was called "the walker closest to the work" and is now the walk, and the ladder's first paragraph ended "each level sees only the narrower set the level below discharged", against the register walk's own definition (it reads only what the floor "could not discharge"), and now follows that definition, so the floor-walk glossary row moves with it. A line saying that a walk is not a ceremony was drafted and refused at review: the canon itself calls some walks ceremonies ("the Inspect ceremony walking the exception set", Part 1.25; "its Sunday walk (ceremony)", Part 1.5; "Inspect by the walk ceremonies", Part 2.5), so separating the two words is a ruling for a minor, never a patch. A fresh reviewer read the old and new text claim by claim (132 claims, none lost; nine findings, all fixed, then one re-check of the fixes); a pre-registered reader test (twelve fresh agents, six on each text, blind marking) tied at the ceiling, 47.5 of 48 each, so it could not decide, and the author's read decided. Every reader on both texts flagged the same gap in the rule itself, which wording must leave alone: a recurring row climbs one level, while recurrence routes to Garden and never further up. No law added or changed in its stamp.

v6.1.0 (2026-10-24) #

v6.1.0 (2026-10-24): a minor, the goal-layer clause re-read on the fleet's initiatives (DEC-709, the project apw-dario-75). An OBJECTIVE is now a goal above projects, for an effort bigger than one project, most often a number by when: one owner, a target date when it has one, at most one number from X to Y, and a short update on its own rhythm; it ends completed (won or missed, in its owner's words) or canceled with its reason. It connects downward two ways: the PROJECTS under it move it by typed reference, one project under any number of objectives and keeping its own fence; and a LEAD MEASURE is now optional, declared only where a concern's standing organ already reads the number, its readings still never fresh bookkeeping. A number no organ reads is the OWNER'S WORD, given in the objective's update, a claimed reading never scored; a walk reads only the objectives that need attention (an update missing, an off-track health, a date passed). The ground is the fleet's own: its first declared goal layer's lead measures told nobody whether a goal was closer, four of the five WIGs drafted after its form shipped were never finished, the five live WIGs had no project linked, and an agent handed a goal in a project's words built a project (EVAL-71); with the re-read words shipped, the same ask reached for the objective 3 of 3 (EVAL-72). The re-read is PROVISIONAL inside the grain law's settled stamp, due: one objective's owner posting updates on its rhythm for four cycles with a project under it, and an agent handed a number by a date reaching for the objective whatever the asker calls it. The species law's SERVES passage and the five-step order's step one now say a project moves an objective by sitting under it, or through a lead measure. The scoreboard type stays: hyrox still binds it and a type earned by receipt is never un-earned by a binding's drift; Relay's binding (the WIGs strip) retired with its WIGs on 23 October, and it returns to Relay the day a lead measure is read there. Part 5.5: Linear's initiatives join 4DX as the goal layer's import ground, 4DX keeping the lead measure and the scoreboard. Glossary: four definitions re-read (The goal layer, Objective, Lead measure, The three species). The Relay edition gains its goal-layer row. 46 laws, 16 provisional, unchanged. Ruled by the author on the two calls drafted that morning (24 October, 23:22 SGT: "ok lets go"), landed by the fleet's lane (Dario[Iniatitives-PROD15]).

v6.0.1 (2026-10-22) #

v6.0.1 (2026-10-22): a patch, one sentence in the one-name law: Relay's agents say its work words (issue, initiative, milestone) where they speak to its people, the one exception to the clause that keeps a display label out of the agents' speech, so a person reads one word on the screen and in the reply while the declarations and the canon keep the canon's names. Its ground is the method's PRD (DEC-683, apw-dario-74): "issue, not ticket or task", and its guard against the screens saying issue while the Charter and the skills say task, which v6.0.0 left in conflict with the speech clause. No law added or changed in its stamp.

v6.0.0 (2026-10-22) #

v6.0.0 (2026-10-22): the third major, the author's method, on the fleet's method sitting of 21 October (DEC-683, the project apw-dario-74): Linear's method taken nearly whole, the canon keeping its concept names. Major by the scheme's own rule, as v5.0.0 was: the species law's grain breaks again and its derived artifacts must migrate. A project born from now on has no separate workstream: its threads are PARENT TASKS and their pieces SUB-TASKS (Linear's parent issues and sub-issues), each sub-task taking its parent's team, priority and project when it is made; its tasks may come from several teams, a big project marks its STAGES, and an effort bigger than one project is an objective above several; tasks link as related, blocked by (the waits-on edge) and duplicate (triage's merge), and a team chooses whether a parent closes itself with its last sub-task (off by default). A project born before keeps its workstreams until it converts, each open workstream then a parent task and its tasks sub-tasks, each old task closed as moved, every old reference answering forever. The walk of a project is its seat on its home team's weekly walk: the project read as a whole (its health, its next stage, and any thread, a top-level task, that has neither moved, rested to a date nor waited on something named) when stuck, never in a meeting of its own, any other ceremony showing it as one line. v5.3.0's birth at the bet is retired with its vocabulary (the pitch, the bet, the appetite): a project is BORN WHEN ITS WORK STARTS, an idea for later one task in the backlog, its lead writing Main as its PRD (the problem in the asker's words, what done looks like, what is out of scope, the likeliest ways it fails) before the first build task, with the four factors (its home room, the project, its WorkBook, its walk: a seat on its home team's weekly walk plus the lead's weekly update with a health); a project gains a lead, a home team and a health. A new law, THE TWO SHAPES OF WORK (Part 2, the fourth row of Laws of sizing, provisional): work that ends follows one method and work that keeps running stays a concern, goals above both; conversations, decisions, documents and ideas are not work; a decision inside a project lives on its WorkBook, and a standing-rule change goes into the doctrine that holds it plus one short decision row that never restates it. The team law: work someone owes that ends is a task, whether small work is tracked is the team's choice, what it produces lives on as a document or code, each team has one weekly walk, and triage leaves the pitch behind. The done-test is asked in the method's words (now, a reply; finished, a task or a project; a number, an objective; never, a concern, an uncovered one served as a task now while its setup starts the same day if it is clearly ongoing, a second similar ask the signal if it is unclear; "not worth doing" always legal), with FIND BEFORE YOU CREATE. One name per concept: Relay's screen words for the work declared as display labels (issue for a task, initiative for an objective, milestone for a project's stage). Part 5.5's work grain re-read, Shape Up and Working Backwards kept as the ground v5.3.0 imported and v6.0.0 retired. Glossary: three names added (The two shapes of work, Find before you create, Sub-task), Pitch retired, nine re-defined (The done-test, Project, Workstream, Task, Standalone task, Triage, Team, WorkBook, The four factors). 46 laws, 16 provisional. The Relay edition binds the labels and the work model's state. Supersedes, at the fleet, DEC-665's birth at the bet. Landed by the fleet's lane (Dario's PROD-12 builder) on the author's agreement to the method's PRD, Method and Spec (21 October, 20:09 to 20:15 SGT), whose Spec step 6 cuts this release, and the author's own go on the doctrine edits (22 October, 00:52 SGT: "yes on the doctrine edits").

v5.3.0 (2026-10-20) #

v5.3.0 (2026-10-20): a minor, the team law (Part 2, the fifth row of Laws of the work, provisional), on the fleet's design sitting of 19 and 20 October (DEC-665, apw-dario-71). Most work is one piece one holder finishes, so a STANDALONE TASK may stand alone on a TEAM's backlog (one ball, one holder, a one-line done-when, converting into a project when it grows a second thread); a TEAM is the grouping corollary's label that earned work (a roster of people and agents, statuses inside fixed groups, a triager, a rhythm, a walk), never a concern; TRIAGE disposes every ask by accept, merge or decline; and the work and the record part company, the jurisdiction law applied to work: what someone does and finishes is a task, the served concern keeping its own facts keyed by the task's code. The sitting's research pass (fifty-five primary sources) folded in four changes before landing: an ANSWERABLE PERSON on every task an agent holds, by default the asker (no surveyed product lets an agent be the only party answerable); a task inside a project still belongs to exactly one team; the team walk reads WORK ITEM AGE; and an optional cycle stays off by default. Two clauses ride it: the done-test splits a date or end-state into the standalone task and the project by size, and routes two asks that are no managed thing (an ask answered now, a conversation; a ruling worth keeping, a decision); and the species law's birth clause, a project BORN AT THE BET: an interview (the JTBD door at project grain) drafts a PITCH that waits in triage until whoever holds its time accepts it (a decline recorded as a decision), and only then is it born with the four factors at once (its HOME ROOM, the project, its WORKBOOK with MAIN first holding the pitch, the APPETITE among its parts, and its walk), the author's own practice with Shape Up's betting table and Amazon's PR/FAQ as import grounds. Home by construction names the team backlog beside the project as a legal residual home, and a backlog kept as a store of maybes beside the General Management concern as the junk drawer. Part 5.5 gains the work grain's import ground. Nine glossary names (The team law, Team, Standalone task, Triage, Answerable person, Pitch, Home room, WorkBook, The four factors); the done-test, Project and Task re-defined. Supersedes, at the fleet, DEC-576's ticket-versus-task split. Landed by the fleet's lane (Dario[AgenticProductDev]) on the author's authorization to edit and ship the canon without waiting (20 October, 00:52 SGT).

v5.2.2 (2026-10-15) #

v5.2.2 (2026-10-15): a patch, the grain law's test three (Part 2) loses its hirer clause: "two or more admitted jobs with DIFFERENT named hirers" becomes "two or more admitted jobs", because head count is the edition's to vary, never the grammar's, and the estate edition's one operator hires nearly every job; and home by construction reads the four grain tests at the first walk with the fitness tests, so a sizing test never refuses a home (NW-ANA-129: a sizing test cited as the reason a letter type needed no concern, where the home question was the one that answered). The species law's work-management passage and the glossary's Concern and The four grain tests drop the same words. The history this file holds left the canon's version line in the same release (4,615 words, moved verbatim below), making v5.2.2 the first release to shrink the canon.

v1.1.0 to v5.2.1, as the version line carried them #

Moved verbatim from the canon's Version: line at v5.2.2; git holds every earlier state of it.

v1.1.0 (2026-08-26, mislabeled minor by its own scheme: it retired the "meta-activities" framing and rewrote the calcification caution, both breaking) added the identity law, the two loops and reification (Part 1.25), the survey door (Part 2, skill 2), the five verbs (Part 2.5), and the calcification relocation (Part 5). v2.0.0 is the adversarial-review-v4 fix pass: the new taxonomy migrated into every derived artifact, each stamped with the canon version it builds against, enforced from here on by the release gate (scripts/release-gate.sh; no version-bump commit without a passing run cited in its message). v2.1.0 adds the epistemic-stamp governance below and the first provisional law (spec and implementation, Part 1.25). v2.2.0 adds the two-kinds-of-processes law (Part 2.5: domain-owned SOPs versus ceremonies as cross-domain convenors, provisional with its first receipt logged). v2.3.0 (from the email build's first operating night): the survey-door guard sharpened into the four-part jobs admission standard with the retro-fit trap and late-entry clause; the flip-conditions law (Part 4); the induction law (Part 2.5). v3.0.0 (2026-08-27): the doors RENAMED to the pain door and the JTBD door (breaking; the field-tested names from the first live teach displaced incident/survey before any cohort learned them, swept everywhere); the depth and split rules on the doors (Part 2, skill 2); the construction-grounds law with the coverage walk, and the authority law (both Part 1.75, provisional); the spine defined as a term of art (Part 2.5); Palantir Foundry added to prior art (Part 5.5); the KYC compliance audit joins the worked examples. v3.1.0 (2026-08-27): the grain law (Part 2) — a committed domain is a pipeline, never a category or an outcome; the four sizing tests, the organ corollary, and the walk-capacity guard; distilled from the fleet's first sizing ruling. v3.1.1 (2026-08-27): spec-and-implementation promoted to SETTLED on its first receipt (the email-intake concern's court read-state divergence, ruled an amendment; the first full audit of a JTBD-door structure against the v3.1.0 instrument set ran the same sitting). v3.1.2 (2026-08-27): the mantra-to-model note (Part 6): guard names the fast loop whole, Inspect its human half. v3.2.0 (2026-08-28), the field harvest from Relay's first two concern-authoring days: reification, the authority law (gaining the apprenticeship grant path), and the grain law promoted SETTLED on their pre-registered receipts (the meta-concern; the live apply-door allowlist; the second independent sizing ruling); the spine-anatomy law with the orphan rule (Part 2.5); the jurisdiction-and-home law (Part 1, provisional); derivation-before-delegation (Part 5, caution 3). v3.2.1 (2026-08-28, same night): the jurisdiction law promoted SETTLED on its pre-registered receipt (the DEC-register re-homing, DEC-50, run through the six-step procedure hours after ratification), and its executor's friction note folded in: re-homing named in two shapes, custodial (stewardship and address move) and jurisdictional (only the governing spine changes; alias and handover satisfied vacuously, legally). v3.3.0 (2026-08-29): the canon reified into its own ontology — unit taxonomy (MODEL/LAW/INSTRUMENT/EXAMPLE/NOTE) + REGISTER.yaml (24 laws in 7 named families, 7 models, 7 instruments; NAMES as identity, slugs for machines, Parts demoted to reading order, prose-from-rows refused with a flip condition); the cognitive-fit law (Part 4: structures sized to the operating head — Norman's working-memory rationale, reverse-deriving the split line); the ranking corollary of the identity law (position is a field, never an identity; from the Gotrade principles-reordering question). v3.3.1 (2026-08-29): the Church joins the lineage (Part 8, between the monastery and the ledger: canonization's advocatus diaboli as institutionalized adversarial review, councils as amendment sittings, ordination as the recorded authoring grant, the Reformation as the record's largest gardening failure; causality stated as illustration, not evidence); the grain law's provenance cites its ruling code (DEC-29); the print render folds the governance header into an appendix, matching the site (derived views only, source untouched). v3.3.2 (2026-08-29): the readability edition — sixteen laws promoted to headed subsections (register name as the heading, statement lead, short paragraphs, provenance and receipts demoted to a trailing stamped line), the two remaining walls split in place (skill 2, the calcification caution); prose structure only, no vocabulary or unit change (the ranking corollary applied to the canon's own reading order); renders gain law-level anchors, stamp chips on law headings, hover anchor links, and styled provenance lines. v3.3.3 (2026-08-29): Part 7 retitled to "The honest scope" — the "(say this out loud in the lecture)" parenthetical was a stage direction to the lecturer mis-homed in a reader-addressed title; delivery's home already carries it (Part 6's lecture row names the spoken set, the body's "stated up front" line keeps the honesty reader-facing). NW-ANA-23. v3.4.0 (2026-08-29): the organ type system (Part 2.75) — eight organ types EXTRACTED from the two living deployments' inventories (register, ledger, court, board, surface, door, index, corpus; the spine excluded as the organ-holder, ceremonies as processes; scoreboard and form marked deployment-local with flip conditions); the types-and-bindings law (Laws of the spec, provisional: the canon owns types, deployments own only bindings; config-as-data source canon/ORGAN-TYPES.yaml carrying types only; gate check 6 alarms on count drift); the qualifier corollary of cognitive-fit (Laws of the head, settled on the view-only mini-app ruling). One language across every deployment Norman runs; NW-ANA-22. v3.4.1 (2026-08-29): the organ DEFINITION ratified (Part 2.75: an organ is a DECLARED PLACE, the latent layer-1 slot named; four membership tests) with three boundaries — spine (the declaration), process (the verbs that operate places, notification routes included as delivery clauses), channel (SUBSTRATE, which may host organ bindings but never takes a type; ruled on the fleet's organs.spaces question — spaces exit organs blocks as reference fields, the Spaces-concern question routed to the fleet's own door); the jurisdiction law's second pre-registered receipt cited (CRN-D1, the first domain-local ruling filed in its own spine); construction-grounds promoted SETTLED on its pre-registered receipt (the fleet's ISMS concern: ISO/IEC 27001:2022 imported and pruned); the flip-conditions due condition armed with its named candidate (the 28-day gap-acceptance clock, ~late Sep). v3.4.2 (2026-08-29, the same night): types-and-bindings promoted SETTLED on its pre-registered receipt — the fleet's organ-type binding live at the write path and landed UNAMENDED (bindings as data on every dossier payload; the spaces refusal enforcing the channel boundary, negative-tested), hours after the estate's declaration; the eight types absorbed both deployments' full inventories; the provisional set drops to three, each with an armed or named receipt condition. v3.5.0 (2026-08-30), the Sunday readability sitting: THE READABILITY LAW (Part 4, Laws of the head — every artifact a head reads is written in the head's working vocabulary, machine encodings underneath; settled at naming on standing instances: speakable identities, display-word states, the question dialect for jobs, commitment-suffix concern names, ORM-over-SQL; the deciding receipt a cold comprehension read across both deployments' 26 declarations) and THE GROUPING COROLLARY (Part 1, Laws of the nouns, ranking's sibling — membership is a field, never a domain: trees render on surfaces from fields, jurisdiction stays flat, labels graduate by receipt); the jobs admission standard gains its dialect clause (a job is the hirer's question, in the hirer's words); the register at 28 laws with both touched families at the five-law cap. v3.5.1 (2026-08-30, hours later): the HIRER'S-VOICE CLAUSE stamped into the readability law on the fleet sweep's receipt (thirty rows, full conformance in one sitting: the hirer is whoever CONSUMES the answer, supply never wears the hirer cell; condition shape legal only for a genuine machine consumer — exactly one of thirty, the DoD gate; four of five apparently-machine hirers were the supply defect one cell over); the admission standard gains the CONSERVATION rule (intent-class terms relocate into the spine's ontology, mechanism-class terms anywhere the organ index reaches, moved in the same edit); the workshop's facilitator notes gain failure pattern 8, the system-voice job, from the sweep's live conversions. v3.5.2 (2026-08-30, the sections sitting): the BIRTH STORY joins the spine anatomy — both deployments carried it independently from their first spines (every estate dossier opens with one, every fleet declaration has a birth_story field), the second-deployment receipt pattern; the estate's binding shipped the same night (the eight-section dossier template, two specimens converted, the index compiler's Observe-mode sections noticer). v3.5.3 (2026-08-30, minutes later): the PORTFOLIO clause joins the identity law's namespacing — a multi-org operator keeps a declared zone registry homed with the holder (no single deployment may own it), codes reserved cheaply, partitions as org-scale re-homings; taught by the neutral ABC/XYZ/HOME worked example; first instance the holder's four-zone registry, the second pre-registered in the tenant model's entity-registry design (the audience claim: power users are multi-org users). v3.5.4 (2026-09-02): the GOAL-LAYER clause joins the grain law (NW-ANA-33, from the first outsider running the vocabulary back — "how do concerns link to growth objectives?"): an outcome refused as a domain lives in the GOAL LAYER above domains — objectives as closable battles (from X to Y by when, one owner, won/missed/abandoned), linked to domains ONLY through lead measures whose readings come from the domains' standing organs, never fresh bookkeeping; engines permanent, destinations reached; 4DX cited as the import ground (Part 5.5) with the link rule named as this model's own addition; the scoreboard's flip condition armed with its declared second candidate (the estate's hyrox goal layer, declared the same sitting); the lecture objection map gains "how do goals fit?" beside the anatomy and grain questions. v3.5.5 (2026-09-03): the readability law's concern-name instance gains the DEFAULT-COMMITMENT clause (Norman's ruling, prompted by the FRO mint's naming question): management is the default commitment word, displaced only by a sharper one that names the pipeline's kind — a default, never a mandate, because intake/operations/readiness carry information a uniform suffix would flatten, and surface economy stays legal (concerns-only indexes render bare). Migration receipts: the estate audited 17/17 conformant unprompted; the fleet directed to audit bare-territory names at gardening touch, display names moving, slugs never (the identity law). v3.5.6 (2026-09-03, three hours later): the default-commitment clause SUPERSEDED by the UNIFORM-SUFFIX rule on Norman's definitional ruling — a concern IS a domain plus the commitment to manage, so its name is territory + management, always; kind-words live in the territory half; a name resisting the suffix is a species diagnostic (not-a-concern), never a case for a different suffix. The deciding evidence: the fleet's same-day audit under the default clause produced an 11-to-5 "default" (the smell), while the estate's 17-for-17 — including email-intake-management and finance-close-management, the kind-in-territory form — showed the uniform rule already running. The double loop at full speed: clause stamped, receipt gathered, smell caught, rule corrected, one afternoon. v3.5.7 (2026-09-04, the codify-first sitting): the capacity guard RENAMED and RECAST as the CAPACITY LOOP (a guard refuses; this steers) — a conservation invariant matching domains to judgment capacity, never rationing codification: "the alternative to a codified domain is never a managed one," so codification is always preferred, converting silent gaps into visible debt; two levers by stage (shrink count at founder-scale, grow capacity at system-scale — inspection being operator-tier and unlicensed, walkers are hireable, agents multiplying reach); staffing steered by two receipts-derived meters (debt aging = demand, recorded disposition drain = supply — an artifact read, never surveillance; both red = hire, red queue over idle walkers = fix routing; drain-rate a signal, never a quota); the loop's one guard residue: never read a red meter as quiet, never hide the meter. Norman's ruling across the 2026-09-03/04 midnight sitting, provoked by the enterprise thesis (company-as-code, Relay as runtime, agents as the operator mass); the estate's aging email court cited live as the demand meter working. v3.5.8 (2026-09-04, minutes later): THE DONE-TEST joins the two-doors model (prose, no register movement; the caps hold at 7/7/28) — any intake ask classifies by "when would this be done?": never/keeps-flowing = a domain through the JTBD door now (recurrence is only the pain door's threshold, never a wait on a knowable engine); a date or end-state = a project on a board; when-the-number-hits-X = the goal layer; a misleading shape = a project with a pre-registered recurrence flip. Distilled live in the same sitting when Norman asked whether an agent must wait for a pain to recur twice when the shape is knowable upfront; the answer is the two-doors model spoken at intake speed, and it is the routing core of the pre-registered door-noticing clause (agents harvest domains from conversation, never evangelize vocabulary). v3.5.9 (2026-09-04, the same sitting): TYPED LINKS join the spine anatomy's ontology component — the noun GRAPH, never a noun list, each edge a domain verb in the hirer's vocabulary (Payslip PAYS Report; the ORM relation names an edge's shape, the domain verb its meaning), cross-domain edges naming the foreign home. Ratified on Norman's first-principles push, and the derivation held three ways without a second deployment: the grain law's own definition (a pipeline is records MOVING, and movement is edges — an ontology without links described inventory, not a pipeline); the jurisdiction law's typed-reference mandate already covering the harder cross-domain case (this closes the intra-domain incoherence); and the import ground (fifty years of relational modeling, Chen's ER diagrams to RDF triples — archaeology, not invention, the ISO/4DX door). The canon owns the PRINCIPLE; the link encoding stays a deployment binding (types-and-bindings applied to links themselves), with the estate's two sidecar dossiers the first instance and the fleet's OKG mirror armed as the encoding's confirmation. v3.6.0 (2026-09-07) added the species law (Part 2: the three species, the project anatomy and its home question, the project-workstream-task grain, PROVISIONAL), the authored-once corollary under Spec and implementation (Part 1.25), and the T20 receipt on the spine anatomy's links clause. v3.6.1 (2026-09-07 evening, patch): three clauses inside the species law: the clock's two kinds (hard, target) bound to the attention grades and required only while active; the baseline moves only by a recorded shift; a project may rest, its encoding a binding (both deployments read: Relay's Board fields, the estate's tickler). v3.7.0 (2026-09-09, the T25 sitting): THE SPINE SCHEMA as machine form (canon/SPINE-SCHEMA.yaml, the config-as-data source of the eight components and the fields whose meaning the canon owns, extracted from both deployments' contracts; gate check 8; a jobs stamp refused at the door, the verb's kind admitted on the fleet's instance) inside the spine anatomy; three clauses inside Part 2.75: THE REGISTER'S WALK SET (terminal and resting bits on a state; open = neither; ruled on the fleet 2026-09-07, the estate's column binding retiring), LIVENESS IS DERIVED AND THE INDEX DECLARES ADDRESSES (the pulse derived by the consumer from the organ at its address; the estate boundary the one exception, where a declared binding is the receipt door for foreign organs; a verb's clock authored once, in the spine or in the scheduler it names), TYPE BY ROLE (an organ's type is its job never its mechanism, derived and foreign are qualifiers, the organ index a free typed entry); the conformance-in-the-consumer's-context sentence settled inside Spec and implementation on two receipts (GBUG-1123; the estate's dev-only yaml parser); the authored-once corollary's first receipt (the estate's migration, 2026-09-09). Register counts unchanged (30 laws, 5 provisional; both caps binding, so the sitting entered as clauses and a machine form, never rows). v3.8.0 (2026-09-10) added THE OKG (Part 5, Laws of enforcement, the 31st law, SETTLED at birth on two deployments): the Operating Knowledge Graph, a deployment's one derived view of everything it manages, condensed out of the declared spines and never authored; its Map, its lookup door, and its name fixed as the one binding the canon owns. Register counts: 31 laws, 5 provisional (Laws of enforcement had room, so the sitting entered as a row). v3.8.1 (2026-09-10) recorded the OKG law's two armed confirmations as receipts, both landed the same day (the estate's lookup door on prod; the fleet's widened lookup instruction on the boxes at core v1.8.20). v3.9.0 (2026-09-11) added THE WALK LADDER (Part 2.5, Laws of the running system, the walk group, PROVISIONAL): a concern's walks nested by altitude, an exception climbing exactly one level by aging or recurrence, the executive walking the walks, the mall's toilets as the worked case; promoted Two kinds of processes to SETTLED on the fleet's second independent case (CRN's coverage job walked by relay-eng-daily); the register descended a level (a group field on rows, two families grouped, identities untouched; the three v3.7.0 clauses of Types and bindings registered as their own rows, text unmoved); the release gate gained the branching check. Register counts: 35 laws, 5 provisional, 7 families, 4 groups. v3.9.1 (2026-09-11) added the verbs of arrival (Part 2, under the doors): to DECLARE a domain is to author its declaration through a door, its BIRTH is the day the declaration enters, a COMMITTED domain is the result; MO-ify and concernify named as slang (wording; no register change). v3.9.2 (2026-09-11) recorded the liveness clause's armed pair as receipts: the boundary declaration landed on both deployments in two spellings (the estate's feed inside the address, the fleet's receipt key beside it), the canon owning the meaning and each deployment its spelling. v4.0.0 (2026-09-12, the first major): the opinionated turn. One name per concept (a law, provisional) with canon/GLOSSARY.yaml as its machine form and the speech test as its boundary; the canon's own word for a committed domain is CONCERN (domain stays territory), a text pass across the canon, the kernel and the derived artifacts; the types-and-bindings law's naming half amended (mechanism words are qualifiers, never names); the readability law sharpened; knowledge routes by role (a corollary, provisional); the scoreboard the ninth organ type on two deployments' receipts; Laws of the head descended into three groups; the release gate reading the glossary. v4.1.0 (2026-09-14): the attention-efficient operating system. The objective function in Part 1 (value created per unit of operator attention; the three seats) and the two editions by player count; the attention law and the push ladder (Part 1.5, a new group, Laws of attention); home by construction, depth by receipt, and jobs carry readings (Part 2; Laws of the doors descended into three groups; the spine schema's jobs component gains kind, reading, target and grade); the default-walker clause on the walk ladder; the fleet's read shaped five rulings (the human seats as the denominator, Notice as the fifth rung, the workshop's second sense on the fleet, the attention grade over a new name, the reading's standing). v4.2.0 (2026-09-18): the workflow law (Part 1.25, the fifth row of Laws of the spine): a workflow is a deployment's binding of one verb to one runner, named once and cited by name from the verb's row, its concern its verb's by reference and never a container, one workflow to one verb, the catalog an index and never a home, an organ's address a reader of receipts and never a home, the orphan of the fifth class named; the glossary gains workflow, runner and catalog; the estate's workflows index and lookup door the first half of the due, met at birth. v4.2.1 (2026-09-18): the repeat clause on the push ladder (a push returns only when a threshold breaks, never because its clock fired again; one docket per clock, then the new and the crossing), on the estate's three descents of the same day. v4.3.0 (2026-09-21): the five-step order (Part 4, the fourth law of Laws of the work): every structure is born and changed in the order of Musk's five-step engineering process, written out because the order is the law (make the requirement less dumb, delete the part or process, simplify or optimize, accelerate cycle time, automate); the deletion question on two clocks (birth, and every change of the mechanism around a structure); a guard carries its incident, its meter and its retiring reading, and retires only against a named end-of-line reading, built first where none exists; the add-back rate calibrates a pass; the classes where a miss cannot be taken back keep their controls; deletion is retirement; the glossary gains three names (the law, the process, the end-of-line reading); the import ground joins Part 5.5, with Bending Spoons a sighting of step two only. v4.4.0 (2026-09-22): the five-step order as the operating mantra: Part 0 gains its third fact (structure that should not exist compounds too), skill 1 asks whether a noun before which, skill 2 reads the admission standard as step one's challenge, the catechism runs the order at seven questions (the hirer's name, then the deletion question, before any noun; the first two answers may end it with nothing built), and the closing slide carries two mantras, the five steps first and the ten words as the shape of what survives; no new law, no new name. v4.4.1 (2026-09-22): step one's test, on the operator's question "what if the hirer wants dumb requirements?": the name is the address for the challenge and the owner of its consequences, never proof of sense; a requirement is less dumb when it changes a decision, costs something unserved and moves an objective; a hirer who insists past a failed test owns it on record and it is metered like a guard; a challenge is never a veto. v4.5.0 (2026-09-22): the push moment, a clause on Jobs carry readings: a job declares the rung by which its reading reaches its hirer and its return (new only, or the declared age rungs), the clock staying the verb's, absent reading pull; an alert is a job's notice; a deployment's catalog of alert kinds is a binding, cited from the job as a verb cites its workflow, and a notice no job names is the sixth orphan class; the scoreboard's pushes row derives from the declarations, never a hand-kept list; the spine schema's jobs component gains push; the glossary gains Push moment. v4.5.1 (2026-09-26): a patch, receipts and one sentence: the fleet's read rates behind the push moment and the five-step order re-derived from the readers' thread markers (the badge column first quoted is not read state; the operator opened almost none of either class), and a read meter is a floor (a read outside the app leaves no mark, so below the bar means rarely opened, never unseen). v5.0.0 (2026-09-27): the second major, a model break in the species law's grain: a WORKSTREAM is a parallel thread of its project with no owner, moved by a rolling next move whose holder may change move by move, its path a plan and never a stock of tasks; a step becomes a task only alongside another holder, on a world's date, or needing its own record; no holder defaults down the tree; the walk of a project reads threads as moved, resting on a tickler, or waiting on a named blocker that is itself moving, anything else the exception; WAITS ON enters the grain as one typed edge for dependency and snooze-on-condition alike (any grain on any other, on its own project or another; backstop, wake, the hand clears, the walk chases the blocker); REST extends from projects to all three grains, on a date or on a condition, the condition being a wait. Major by the scheme's own rule: the fleet's board workstream carries an owner column built on the old sentence (DEC-144), and trained cohorts learned "for X to do Y". The glossary re-defines Workstream and gains Waits on. v5.0.1 (2026-09-27): a patch, the fleet lane's read of the major: five wording corrections (DEC-144 the whole binding with only its workstream clause re-ruled; DEC-312 cited for whole-board and several blockers; no project waits on its own workstream, its own part; a blocker is named only as far as the waiter's readers may read it; the glossary's Waits on carries its never clause) and the fleet's receipts (its refusals, REST at every grain since T61, 19 of 428 workstreams with an owner, re-ruled away the same day). v5.0.2 (2026-09-27): a patch, the fleet lane's second read of the major: a waiter reads as waiting, never as the exception; the walk chases its blocker, which carries the exception where it lives (read literally, 'a named blocker that is itself moving' made a waiter the exception whenever its blocker stalled, against the same paragraph's 'the walk chases the blocker, never the waiter'; Relay took the literal sentence first and flagged 14 waiters as stuck on the live G8, fixed in console 2190af7e, live through v1.41.31 and in the fleet MO skill at core v1.8.80; the estate's ReadThreadWalk, nwos-todo 02ffc11, already read the waiter as waiting). v5.1.0 (2026-09-28): the provenance law (Part 5), the first amendment from the estate's register of outside findings (NW-MOF-1, NW-MOF-4), on three failures across both deployments in one week: a verifier reads the evidence before the conclusion and keeps the conclusion, the order of the read being the rule and orientation exempt; a handoff carries its observations apart from its conclusion; a correction is appended (a record of its own or a dated paragraph whose prior text the record's history keeps), never a silent overwrite, names the claim it supersedes and reaches that claim's citers through their references, each asking whether its one claim still holds, never whether the source changed. Import grounds: auditing's evidence standard and truth maintenance. Read by the fleet before landing, three leans amended on its receipts (the correction's form, the lookup's reach, the due's candidates). The glossary gains Provenance. v5.1.1 (2026-09-29): a patch, the OKG law's reach clause (Part 5), on the operator's question whether an easy lookup of concerns, registers, jobs, fields and rows was not the OKG's whole point: every citable handle means the lookup door reads through the spines to what they govern; a register's fields belong to its organ and a field's name finds it; a coded instance is answered by its code and found by its words, as a handle with its state, never the store; how much of it a reader sees is the edition's authority; a foreign prefix reads unknown, never a negative. Both deployments had read the node sentence as the door's limit; the estate met the clause the same day, and the fleet's due is a row found by its words. The provenance law's due corrects its own lookup sentence (the estate's lookup lists the register rows citing a code since the same day). The glossary's Lookup door carries the reach. v5.2.0 (2026-10-01): the walk ladder in machine form (Part 2.5), on the operator's sitting on walks and gardening (NW-ANA-104): a walk names the register whose open rows it reads and, above the floor, the walk beneath it; altitude is derived from the chain, never typed; one walk is one rung; a rung is held by the concern's own verb or a ceremony reading its segment, never by a sibling concern; a concern-level walk pointer is a derived view. The spine schema's verb gains the two fields and the five presences' fourth question names the walks by altitude. Born of an orphan register an agent offered to home at the next walk (a door act, never a walk's), and of both deployments holding their floors where no reader of the spines could see them. The same sitting ruled WHEN Garden runs (an event trigger and a scheduled garden clock) as the estate's nursery ruling, not canon: no scheduled garden has a receipt on either deployment. v5.2.1 (2026-10-02): a patch, the species law's waits clause (Part 2): the waiter rests while any blocker is open, and a backstop date, defaulted or named, is the deployment's binding, never the law's. The clause had read "the waiter rests on a backstop date", which made a default date law; the fleet retired its 14-day default (DEC-454: every one of its 55 open waits sat behind a board a walk already reads, so the walk chased each blocker and a default date guarded nothing), while the estate keeps its 14 days. The glossary's Waits on carries the same words.