geneseed 2.1.0 → 3.0.0

package/docs/web/plugin-ponytail.md

@@ -6,7 +6,7 @@ kind: "concept"
 ---
 The sustained counterpart to the `ponytail` skill: once you opt in, it appends the laziest-that-works ruleset to the system prompt **every turn**, so the agent doesn't drift back to over-building mid-session, and it persists the level across turns.
 
-- **Opt-in:** the mode starts at `off` and injects nothing until you switch it on. Geneseed treats ponytail as a skill, not an always-on Law.
+- **Opt-in:** the mode starts at `off` and injects nothing until you switch it on. Geneseed treats ponytail as a skill you reach for, not as part of the [constitution](#/docs/rules): it is neither an always-on invariant nor a doctrine pack you build in, so nothing about it binds until you ask for it.
 - **Toggle:** `/ponytail lite|full|ultra|off` (a bare `/ponytail` means `full`). The level is written to `.geneseed-ponytail` beside OpenCode's config and applies from the next turn.
 - **Hooks:** `experimental.chat.system.transform` appends the ruleset; `command.execute.before` records the switch. Every failure is swallowed; on a build without the system-transform hook it simply never injects (the skill still covers the invokable path).
 

package/docs/web/rules.md

@@ -1,8 +1,28 @@
 ---
 group: concepts
 order: 1
-title: "Rules (Laws)"
+title: "The constitution"
 kind: "concept"
-link: {"hash": "#/laws", "label": "Browse the ledger →"}
+link: {"hash": "#/laws", "label": "Browse the constitution →"}
 ---
-{N_LAWS} universal laws the agent obeys — secrets handling, scope discipline, verify-before-assert, surface-failures, context economy, load-the-docs, tool-discovery, non-interactive-shell, and more. They are authored as one numbered list in `src/laws/universal.md`, and the rendered list lives in `AGENT.md`. They bind regardless of theme: an imperial deploy reads them as *Dictates*, a neutral deploy as *Rules*, but the numbering and the rule itself never move.
+The agent's standing rules come in **three tiers**, and the tier decides how a rule binds and whether this install carries it at all. All three are authored under `src/` and rendered into `AGENT.md`; the console shows them as three bands under **Constitution**.
+
+### Ontology — always on
+
+{N_ONTOLOGY} sections of flowing prose in `src/ontology/universal.md`: what the agent is for, how it grades evidence, how it decides, how it conducts itself. It is the mind the other tiers govern — never numbered, never toggleable, and it is where the **Pact** (the mutual contract between you and the agent) is stated. Cited by section name, `Ontology: Decisions`, and its section names are theme-independent so a citation and its heading can never drift apart.
+
+### Invariants — always on
+
+{N_LAWS} rules in `src/laws/universal.md`, numbered in Roman from `I`: sealed secrets, one intent per act, verify before asserting, deliberate deletion, surface failures, data not orders, least privilege, cure the cause, and the external gate. They hold in every task and every repository, they are never traded away, and no install can switch one off. Cited by numeral — `Rule IV`.
+
+### Doctrines — chosen at build time
+
+Practices rather than principles: **craft** (how code is written), **rigor** (how work is proven), **ops** (how the machine is operated), **process** (how a task is run), one file each under `src/doctrines/`. A repository picks its set with `geneseed-build --doctrines <list>` or through the setup wizard — all {N_PACKS} are on by default. This install built in {N_PACKS_ACTIVE}, carrying {N_DOCTRINE_RULES} rules between them. Cited by pack and number — `Doctrine process 5`.
+
+A pack you leave out **still ships in the bundle**: every pack file lands under `doctrines/` beside `AGENT.md` whether or not it was built in. So a rule that cites one in an inactive pack still resolves on disk, and you can read the alternatives before turning one on. What an inactive pack loses is bindingness, not availability.
+
+### Which outranks which
+
+Ontology and Invariants first, then your own `user-rules.md`, then the active Doctrines, then `PROFILE.md`. A rule you write in `user-rules.md` **outranks a doctrine rule** — a practice pack chosen at build time never overrides an instruction you wrote for your own repo — and nothing outranks an invariant: a user rule or a doctrine rule may tighten one, never repeal it.
+
+Themes rename the nouns, never the structure: an imperial deploy reads the invariants as *Dictates*, a neutral deploy as *Rules*. The tier, the address and the rule itself do not move.

package/docs/web/setup-choices.md

@@ -1,10 +1,10 @@
 ---
 group: start
 order: 1
-title: "Posture & footprint"
+title: "Posture, doctrines & footprint"
 kind: "concept"
 ---
-The setup wizard asks four starting parameters. The first, the **theme**, is the *voice* — banner, sigil, prose register — previewed live as you move through the wizard; it never changes structure or rules, so pick whatever reads best to you ([voice vs structure](#/docs/themes)). The other three shape how the agent works and are explained below. All four have safe defaults — accept them and move on, or pick deliberately here. All are set-and-forget: preserved across every rebuild and re-theme, changeable later from **Settings**, the **Harnesses** page, or the wizard.
+The setup wizard asks five starting parameters. The first, the **theme**, is the *voice* — banner, sigil, prose register — previewed live as you move through the wizard; it never changes structure or rules, so pick whatever reads best to you ([voice vs structure](#/docs/themes)). The other four shape how the agent works and are explained below. All five have safe defaults — accept them and move on, or pick deliberately here. All are set-and-forget: preserved across every rebuild and re-theme, changeable later from **Settings**, the **Harnesses** page, or the wizard.
 
 ### Posture — the relationship register
 
@@ -27,13 +27,26 @@ How the session runs the work you hand it, fixed at build time:
 
 Pick **direct** unless you want the session managing a crew for you. Switch back any time with `--mode direct`.
 
-### Footprint — full or lean Rules
+### Doctrine packs — which practices bind
 
-How much of the Rules `AGENT.md` carries inline every turn. A token-cost dial, not a rules cut — every Rule always applies:
+Which practice rules this install adopts, fixed at build time. Unlike the dials above this one really does change *which rules apply*: the [Ontology and the Rules](#/docs/rules) are always on, the doctrines are yours to pick. All four ship enabled, and leaving one out is a deliberate choice, not a default:
 
-- **full** *(default)* — every Rule's text *and* rationale inline. Best when token cost is a non-issue or you run a smaller model.
-- **lean** — one line per Rule plus a pointer to the complete laws file, read on demand. Trims the Rules section by roughly 40% for long sessions or cost-sensitive runs.
+- **craft** — how code is written: reuse first, house conventions, docs in step, the smallest diff.
+- **rigor** — how work is proven: idempotence, honest tests, coverage, gates that can actually fail.
+- **ops** — how the machine is driven: tool discovery, commands that return, complete teardowns.
+- **process** — how a session runs: planning, context economy, docs first, and the **consent gate on every commit and push**.
+
+Turning **process** off takes that consent gate with it, at the tool boundary as well as in the prose: the OpenCode permission block and the Claude/Bob `PreToolUse` hook that ask before a commit or a push are wired only when the pack is built in, because a boundary that keeps asking for a rule the install never adopted is a gate arguing with its own harness. The invariant-territory refusals — `rm -rf`, a force-push — stay in every build; they are the Rules' territory, not the pack's.
+
+A pack you leave out still ships in the bundle under `doctrines/`, so you can read it before turning it on, and a rule that cites it still resolves. Change the set with `geneseed-build --doctrines craft,rigor` (or `--doctrines none`), or in `harness.config.json`.
+
+### Footprint — how much of the constitution loads inline
+
+How much of the constitution `AGENT.md` carries inline every turn. A token-cost dial, not a rules cut — whatever this install adopted always applies:
+
+- **lean** *(default)* — the Ontology whole, then each Rule and each doctrine rule as its heading plus its first line, with a pointer to the complete text shipped beside `AGENT.md` and read on demand.
+- **full** — every Rule's and every active doctrine rule's complete text *and* rationale inline. Best when token cost is a non-issue or you run a smaller model, which applies a rule's nuance more reliably with the *why* eagerly in context.
 
 ---
 
-**Deeper:** [The collaboration layer](#/docs/collaboration) · [Footprint (lean vs full)](#/docs/footprint) · **Next:** [Verify it works](#/docs/verify)
+**Deeper:** [The constitution](#/docs/rules) · [The collaboration layer](#/docs/collaboration) · [Footprint (lean vs full)](#/docs/footprint) · **Next:** [Verify it works](#/docs/verify)

package/docs/web/themes-author.md

@@ -5,4 +5,16 @@ title: "Write a new theme"
 kind: "concept"
 link: {"hash": "#/themes", "label": "Open the theme gallery →"}
 ---
-A theme is one JSON file under `themes/` declaring voice tokens only: `BANNER`, `TAGLINE`, `LOADED_SIGIL`, `VOICE`, the core nouns (`LAW(S)`/`AGENT(S)`/`SKILL(S)`/`MEMORY`/`NOTEBOOK`/`WIKI`), the law titles `LEX_*`, the section intros `INTRO_*`, the epigraphs `EPI_*`, the `BENEDICTION`, the `ROAST_PERSONA`, and `DESC_*` blurbs. Copy `themes/neutral.json` and edit. `geneseed build --theme yours` renders it; `doctor` checks for missing tokens.
+A theme is one JSON file under `themes/` declaring voice tokens only: `BANNER`, `TAGLINE`, `LOADED_SIGIL`, `VOICE`, the core nouns (`ONTOLOGY`/`LAW(S)`/`DOCTRINE(S)`/`AGENT(S)`/`SKILL(S)`/`MEMORY`/`NOTEBOOK`/`WIKI`), the section intros `INTRO_*`, the epigraphs `EPI_*`, the `BENEDICTION`, the `ROAST_PERSONA`, and `DESC_*` blurbs. Copy `themes/neutral.json` and edit. `geneseed build --theme yours` renders it; `doctor` checks for missing tokens.
+
+### The constitution's titles
+
+Every rule in the constitution gets its title from a theme key, and a theme that omits one ships a rule with a blank heading:
+
+- `LEX_I`…`LEX_IX` — one title per invariant. `doctor` holds this to an **equality**, not mere presence: a `LEX_*` outside `I`–`IX` is a title for a rule that does not exist and fails the check too.
+- `DOC_*` — one title per doctrine rule, named after its address (`DOC_CRAFT_1`, `DOC_PROCESS_5`, …). `doctor` reads the pack files under `src/doctrines/` and requires exactly the set they name — a missing one is a blank heading, an extra one is a dead key.
+- `PACK_*` — one name per pack (`PACK_CRAFT`, `PACK_RIGOR`, `PACK_OPS`, `PACK_PROCESS`), used for the pack's own sub-heading.
+
+The Ontology's section names are **not** theme keys: a citation reads `({{ONTOLOGY}}: {{ONT_TELOS}})`, token on both sides, so heading and reference always move together. They live in the build's fixed structure table and you neither declare nor rename them.
+
+> ⚠ `LAW` and `DOCTRINE` must each be a **single word**. Both heading parsers match the tier noun with `\S+`, so a two-word value does not error — the heading simply stops matching and the whole tier parses to nothing, in silence. `doctor` gates this for every real voice (`_TEMPLATE.json` is exempt; its values are placeholders).

package/docs/web-ui.md

@@ -50,14 +50,15 @@ The left rail mirrors the harness's own shape:
 
 | Group | Views |
 | --- | --- |
-| **🧬 Harness** | Dashboard · Rules · Library · Graph |
-| **📚 Learn** | Docs · Specs |
+| **🧬 Harness** | Dashboard · Activity · Constitution · Rules · Profile · Skills · Agents · Library · Docs · Graph |
 | **🔧 Maintain** | Changes · Doctor |
 | **🎨 Configure** | Harnesses · Themes · Settings |
 | **ℹ️ About** | About |
 
 A global **Spotlight** search lives in the topbar — press <kbd>/</kbd> to focus it, type
-to jump to any agent, skill, law, doc, spec, or MCP server; <kbd>↑</kbd>/<kbd>↓</kbd> to
+to jump to any agent, skill, doc, spec, MCP server, or constitutional rule — the `laws`
+catalog it indexes is the whole constitution, so an ontology section, an invariant and a
+doctrine rule are all reachable by name; <kbd>↑</kbd>/<kbd>↓</kbd> to
 move, <kbd>Enter</kbd> to open, <kbd>Esc</kbd> to clear. A bottom **Console** drawer
 streams the output of background jobs and keeps their history across reloads.
 
@@ -66,9 +67,17 @@ streams the output of background jobs and keeps their history across reloads.
 ### 🧬 Harness
 
 - **Dashboard** (`#/`) — a live readout of what's deployed. Three lenses: **Status**
-  (readiness ring, KPI counts of agents/skills/laws/memory, a genome grid, recent
-  activity), **Lineage** (a mini cross-link graph), and **Operator** (a searchable table
-  of every deployed capability). Headlines reflect the active theme's voice.
+  (readiness ring, a KPI band, a genome grid, recent activity), **Lineage** (a mini
+  cross-link graph), and **Operator** (a searchable table of every deployed capability).
+  Headlines reflect the active theme's voice.
+
+  The KPI band reads **Agents · Skills · Invariants · Local edits**. That third tile is
+  labelled *Invariants* and not *Constitution* on purpose: its value is the invariant count
+  alone, and calling it the constitution would under-report the ontology and the doctrine
+  packs. The two Status *layouts* that have room for it add the missing half: Greenhouse
+  puts an active-packs fraction under the tile (`3/4 packs · N rules`), and the Operator HUD
+  gives it its own cell (`PACKS 3/4`). That is what makes a narrowed install *look* different
+  from a full one at a glance.
 - **Rules** (`#/rules`) — your own standing rules, read from and written to the
   `user-rules.md` beside the deployed AGENT.md (the seed-once file no update ever
   touches). List with scope (user/project) and trial chips, add/edit/retire forms, a
@@ -76,17 +85,32 @@ streams the output of background jobs and keeps their history across reloads.
   amber as the always-loaded set gets heavy. Every write carries the fingerprint of the
   content the page last read — if an agent session edited the file meanwhile, the save
   409s and the page reloads instead of clobbering it.
-- **Library** (`#/library`) — browse the harness content: **Laws · Agents · Skills ·
-  Memory · Notebook** (plus Wiki/Config). Drill into a section, then an item, to read its
+- **Constitution** (`#/laws`) — the whole governance surface on one page, in three bands:
+  the **Ontology** (four prose sections), the **Invariants** (the nine numbered Rules, with
+  a class facet — only non-empty classes render, and two of the six have had no invariant
+  since the split), and the **Doctrines** (one group per pack, each marked active or not for
+  this install). Every row expands to its full body, lazily fetched. The rail entry is
+  labelled *Constitution* while the route, the id and the badge key stay `laws`; deep links
+  are `#/item/law/ont:telos`, `#/item/law/IV` and `#/item/law/process.5` — three address
+  shapes that cannot collide, because a slug carries a colon no numeral has and a doctrine
+  address carries a dot.
+- **Library** (`#/library`) — browse the content that has no tab of its own: **Memory ·
+  Notebook · Knowledge** (the wiki chip, which also carries the two setup manifests).
+  Constitution, Skills and Agents each have their own rail entry instead. Drill into a section, then an item, to read its
   rendered markdown body and follow its cross-links. On a memory fact, a **Forget this
   fact** control deletes it (token-gated; bare-slug guarded server-side), and a
   **Promote to rule** control turns a recurring lesson into a trial rule in
   `user-rules.md` — provenance recorded, the source fact deleted so it isn't loaded
   twice — landing you on the Rules page.
-- **Graph** (`#/graph`) — the full cross-link constellation across the whole harness:
-  every `[[wikilink]]` between agents/skills plus every `Rule N` mention that lands on a
-  real law. Hover to isolate a neighbourhood, scroll to zoom, drag to pan, search to
-  highlight; orphans dim out. Click a node to open its spec.
+- **Graph** (`#/graph`) — the cross-link constellation across agents, skills and the
+  **invariants only**: every `[[wikilink]]` between agents/skills, plus every `Rule N`
+  mention that lands on a real invariant. ⚠ The reference pattern matches the tier noun
+  followed by a **Roman numeral** — `Rule`, `Law`, or whatever the active theme calls one,
+  which is how `Dictate III` still resolves under `imperial`. A doctrine address is
+  `<pack> <n>` and matches nothing, so **doctrine cross-links are not drawn**; the graph is
+  a view of the invariant backbone, not of the whole constitution. Hover to isolate a
+  neighbourhood, scroll to zoom, drag to pan, search to highlight; orphans dim out. Click a
+  node to open its spec.
 
 ### 📚 Learn
 

package/harness.config.json

@@ -2,5 +2,5 @@
   "_comment": "version is a human-readable release label only; the canonical identity of an installed harness is the source fingerprint stamped in .geneseed-version (see `harness version`), not this string.",
   "theme": "neutral",
   "product": "Geneseed",
-  "version": "2.1.0"
+  "version": "3.0.0"
 }

package/js/catalog.mjs

@@ -29,15 +29,36 @@ import { defaultTheme, installedDefaults } from './installs.mjs';
 import { pyPrint } from './lib/fs.mjs';
 import { dwidth, fit, icon, truncd, tuiEntries } from './tui.mjs';
 
-/** The listing's section names, and the row kind each one selects. */
-export const CATALOG_KINDS = { agents: 'agent', skills: 'skill', laws: 'law' };
+/**
+ * The listing's section names, and the row kind each one selects.
+ *
+ * FIVE SINCE THE CONSTITUTION BECAME THREE TIERS, in constitutional order between the two
+ * entity sections and after them — `ontology`, `laws`, `doctrines` read as one block. The
+ * order here is only the no-section filter's; the printed order is `tuiEntries`'.
+ *
+ * ⚠ THE SET IS DECLARED IN TWO FILES AND `tests/unit/catalog.test.mjs` TIES THEM. The verb's
+ * `section` positional takes its `choices` from `js/cli-table.json`, so a kind added here and
+ * not there is a section the endpoint serves and the front door refuses. `catalog` has no
+ * recorded help text and no golden cell, which is what makes the pair editable at all.
+ */
+export const CATALOG_KINDS = {
+  agents: 'agent', skills: 'skill', ontology: 'ontology', laws: 'law', doctrines: 'doctrine',
+};
 
 /**
  * The badge column: what the catalog endpoint carries beside the name that is not the
  * purpose. An agent has a lifecycle status, a skill has that and a category, a law has a
  * governance class and no status at all — which is the endpoint's shape, not a shortcut.
+ *
+ * A doctrine rule's badge is its PACK plus whether this install built it in. The pack is
+ * already the rule's class (there is no second taxonomy over a doctrine), and `off` is the
+ * one thing a reader cannot infer from the row: an inactive pack is listed, not hidden, so
+ * without the marker its rules read as binding. An ontology section has neither — it is a
+ * worldview, not a rule list — and an empty badge collapses its column.
  */
 function badgeFor(kind, data) {
+  if (kind === 'ontology') return '';
+  if (kind === 'doctrine') return `${data.klass ?? 'craft'}${data.active === false ? ' (off)' : ''}`;
   if (kind === 'law') return data.klass ?? 'craft';
   if (kind === 'skill') return `${data.klass ?? 'build'}/${data.status ?? 'unknown'}`;
   return data.status ?? 'unknown';
@@ -98,11 +119,15 @@ export function catalogLines(inv, section, width, showSource = false) {
  * validator here, and the entry point's `exitCode` arm carries the refusal out.
  */
 export function cmdCatalog(args) {
-  const theme = args.theme || installedDefaults().theme || defaultTheme();
+  const inst = installedDefaults();
+  const theme = args.theme || inst.theme || defaultTheme();
+  // The install's own pack selection, so an inactive pack's rules are listed and MARKED
+  // rather than listed as though they bind. `null` — no carrier said — reads as every pack.
   // `helpWidth()` is `COLUMNS`, else the terminal, else 80 — minus the two columns argparse
   // subtracts for its own layout. This listing wants the whole terminal, so it adds them
   // back rather than owning a second copy of that precedence chain.
-  const lines = catalogLines(tuiInventory(theme), args.section, helpWidth() + 2, args.source);
+  const lines = catalogLines(tuiInventory(theme, inst.doctrines), args.section,
+    helpWidth() + 2, args.source);
   if (!lines.length) {
     pyPrint(`[catalog] nothing to list${args.section ? ` under ${args.section}` : ''}.\n`);
     return 1;

package/js/checkout.mjs

@@ -66,14 +66,36 @@ export function discoverNames(dir, first) {
   return names.length ? names : [first];
 }
 
+/**
+ * The doctrine packs, in the order they are rendered into AGENT.md — the ONE owner.
+ *
+ * DELIBERATELY NOT `discoverNames('doctrines', 'craft')`. That helper `.sort()`s, so it
+ * answers `craft, ops, process, rigor`; the constitution's order is a reading order —
+ * write it (craft), prove it (rigor), run it (ops), ship it (process) — and no sort
+ * produces it. Discovery still runs, but as a GATE rather than as the order: `js/render.mjs`
+ * refuses to build when a pack file exists under `src/doctrines/` that is missing from this
+ * array, so a fifth pack cannot be silently dropped from every install.
+ *
+ * It lives here, beside `makeCfg` and `discoverNames`, because every consumer (the cfg
+ * default, the render loop, the `Active packs:` marker, the CLI flag, the wizard, the
+ * doctor) already imports this module and this module imports nothing of theirs — the one
+ * placement that cannot introduce a cycle.
+ */
+export const PACK_ORDER = ['craft', 'rigor', 'ops', 'process'];
+
 /**
  * `_build_core.js_cfg()`, originated rather than received.
  *
  * `posture` and `mode` are `_build_core`'s module defaults (`peer` / `direct`) unless a
  * caller overrides them. `build.py`'s `main()` sets them from its flags; `rituals/harness.py`
  * never touches them, so every harness verb that renders renders at the defaults.
+ *
+ * `doctrines` is the third register and the first that is a SET rather than a scalar: all
+ * four packs unless a caller narrows it. Copied, never aliased — `cfg.doctrines` is handed
+ * out to renderers and a caller that sorted or spliced it in place would rewrite
+ * `PACK_ORDER` for the whole process.
  */
-export function makeCfg({ posture = 'peer', mode = 'direct' } = {}) {
+export function makeCfg({ posture = 'peer', mode = 'direct', doctrines = PACK_ORDER } = {}) {
   return {
     root: ROOT,
     src: SRC,
@@ -84,5 +106,6 @@ export function makeCfg({ posture = 'peer', mode = 'direct' } = {}) {
     workflowSrc: WORKFLOW_SRC,
     posture,
     mode,
+    doctrines: Array.isArray(doctrines) ? [...doctrines] : [...PACK_ORDER],
   };
 }

package/js/cli-table.json

@@ -78,18 +78,20 @@
     },
     {
       "name": "catalog",
-      "help": "list what this harness ships: every agent, skill and law, with its one-line purpose and lifecycle status",
+      "help": "list what this harness ships: every agent, skill and constitutional rule, with its one-line purpose and lifecycle status",
       "description": "",
       "positionals": [
         {
           "names": [],
           "dest": "section",
           "metavar": null,
-          "help": "limit the listing to one section (default: all three)",
+          "help": "limit the listing to one section (default: all five)",
           "choices": [
             "agents",
             "skills",
-            "laws"
+            "ontology",
+            "laws",
+            "doctrines"
           ],
           "default": null,
           "required": false,
@@ -135,7 +137,7 @@
     },
     {
       "name": "context",
-      "help": "print context.json eager entries for a SessionStart hook (Rule XVIII)",
+      "help": "print context.json eager entries for a SessionStart hook",
       "description": "",
       "positionals": [],
       "options": [
@@ -336,7 +338,7 @@
     },
     {
       "name": "git-gate",
-      "help": "PreToolUse hook: force an ASK before every git commit/push (Law XX backstop)",
+      "help": "PreToolUse hook: force an ASK before every git commit/push (process 5 backstop)",
       "description": "",
       "positionals": [],
       "options": [
@@ -584,7 +586,7 @@
     },
     {
       "name": "rule-gate",
-      "help": "PreToolUse hook: force an ASK before any write to user-rules.md or memory (Law VI backstop)",
+      "help": "PreToolUse hook: force an ASK before any write to user-rules.md or memory (process 1 backstop)",
       "description": "",
       "positionals": [],
       "options": [

package/js/diff.mjs

@@ -41,8 +41,8 @@ import path from 'node:path';
 import { emitGlobalInto } from '../bin/geneseed.mjs';
 import { GLOBAL_MANIFEST, VERSION_MARKER, expanduser, opencodeConfigDir } from './hosts.mjs';
 import {
-  EMIT_HOST_SCOPE, defaultTheme, footprintOfDir, modeOfDir, postureOfDir, readJsonMaybe,
-  readMaybe, themeOfDir,
+  EMIT_HOST_SCOPE, defaultTheme, doctrinesForBuild, footprintOfDir, modeOfDir, postureOfDir,
+  readJsonMaybe, readMaybe, themeOfDir,
 } from './installs.mjs';
 import { unifiedDiff, pySplitLines } from './lib/udiff.mjs';
 import { pyPathStr, pyPrint, pyPrintErr, readText, writeText } from './lib/fs.mjs';
@@ -166,7 +166,12 @@ export function diffCollect({ target = null, theme = null, emit = null, footprin
     const expected = path.join(tmp, 'expected');
     withStdoutSwallowed(() => emitGlobalInto(host, {
       theme: themeName, out: path.join(tmp, 'bundle'), cfgDir: expected, footprint: fp,
-      posture: postureOfDir(dir), mode: modeOfDir(dir),
+      // The third register read off the deployment, for the same reason as the other two: an
+      // install built with `--doctrines craft` compared against an `expected` rendered at all
+      // four reports its entire doctrines section — and its `Active packs:` line — as drift.
+      // `null` (no marker) means unknown and renders at all four, which `doctrinesForBuild`
+      // makes explicit rather than leaving to `makeCfg`'s parameter default two layers down.
+      posture: postureOfDir(dir), mode: modeOfDir(dir), doctrines: doctrinesForBuild(dir),
     }));
     const rels = [...new Set([...ownedSet(dir), ...ownedSet(expected)])].sort();
     for (const rel of rels) {