geneseed 3.6.0 → 3.8.0

package/CHANGELOG.md

@@ -10,6 +10,80 @@ label. For the capability ↔ spec map, see [SHIPPED.md](SHIPPED.md).
 
 _Nothing yet._
 
+## [3.8.0] — 2026-09-30
+
+**Upgrading:** re-emit (or `geneseed rebuild-all`) after installing, so each install carries the
+rewritten `geneseed` skill.
+
+### Added
+- `geneseed status` lists every install with its theme, footprint, posture/mode, doctrine packs
+  and excluded rules; `geneseed status --json` prints the same payload plus, per install, the
+  `geneseed build` command that rebuilds it unchanged — a global install's command names its
+  config dir with `--config-dir`, so it rebuilds in place even from a shell without the env
+  override that located it.
+- `geneseed build` forwards the generator's flags (`--emit`, `--footprint`, `--posture`, `--mode`,
+  `--doctrines`, `--exclude-rules`, `--out`, `--root`, `--config-dir`); the dry run is
+  `geneseed validate`.
+
+### Fixed
+- `setup`'s non-interactive hint (`geneseed build --emit … --theme …`) was a usage error.
+- The `geneseed` skill named `geneseed learn` and `geneseed context`, which are hook verbs the CLI
+  refuses; it now reads `status --json` and changes an install by one flag of its rebuild command.
+- README and SETUP claimed `geneseed-build --validate-only` dry-runs a build; the generator refuses
+  that flag, and both now name `geneseed validate`.
+- A `-global` emit ignored `--out` and always wrote the live config dir, so a global install could
+  not be previewed anywhere else; `--config-dir <dir>` now redirects it, and a per-repo emit
+  refuses the flag rather than ignoring it (#156).
+
+## [3.7.0] — 2026-09-28
+
+**Upgrading:** re-emit (or `geneseed rebuild-all`) after installing. An install built before
+this change keeps the reference-codes rule: see *Address migration* below.
+
+### Added — doctrines
+
+- **A fifth doctrine pack, `comms` — how answers are presented.** On by default, rendered last
+  (craft → rigor → ops → process → comms), toggleable like every pack. It holds two rules:
+  - `comms 1` — *Codes That Persist*: the reference-codes rule (`D`/`O`/`F`/`R`/`Q`/`A`),
+    moved out of process unchanged, themed titles included.
+  - `comms 2` — *Structure Beside Prose*: beside the prose, pick a diagram or a table, rarely
+    both. Draw a boxes-and-arrows diagram only when the arrows carry meaning (flow,
+    dependencies, topology, a spatial subject, four or more linked elements, or on request);
+    classifications and comparisons take a table or list; three steps or fewer stay inline.
+    ASCII in a terminal, Mermaid where markdown renders it; a richer rendered page is offered
+    in one line, never built unasked. Strictly additive to `comms 1`: a diagram or table may
+    tag a coded item, never absorb, merge or renumber it.
+
+### Changed — address migration
+
+Anyone citing a doctrine rule by address must remap two of them:
+
+| Old address | New address | Rule |
+|---|---|---|
+| `process 7` | `comms 1` | Codes That Persist (reference codes) |
+| `process 8` | `process 7` | One Writer Per File |
+
+`process 1`–`6` are unchanged. Every citation inside `src/` was remapped in this change. An
+existing install is migrated when it is next rebuilt: if its carrier was rendered before the
+comms pack existed (it names `process 8`, as a heading or in its `Excluded rules:` line) and its
+`Active packs:` marker names `process`, `comms` is added so the codes rule is not lost; its
+excluded rules are re-addressed by the table above. An install built after this change that has
+comms switched off stays off.
+
+### Added — hosts
+
+- **OpenClaude as a fifth host** (`--emit openclaude` / `--emit openclaude-global`).
+  [OpenClaude](https://openclaude.gitlawb.com/) is an any-model CLI forked from Claude Code, so
+  it rides the Claude engine and hook dialect verbatim. Only the paths differ:
+  `~/.openclaude` (`$OPENCLAUDE_CONFIG_DIR`, OpenClaude's own variable) globally, and
+  `.openclaude/` per repo. The per-repo preamble is `.openclaude/CLAUDE.md` rather than a root
+  file, because OpenClaude skips a root `CLAUDE.md` whenever `AGENTS.md` exists. MCP config goes
+  in `.openclaude.json` / `.mcp.json`. The host is wired through setup (appended after `files`,
+  so scripted menu answers keep their numbers), uninstall, disable/enable, excludes, status,
+  doctor, the web console's Harness page and Deploy form, and the `token-report` skill. The
+  golden matrix gains 56 cells, plus 2 deletion cells. Unverified live: no OpenClaude install
+  on the authoring machine. See `adapters/openclaude/README.md`.
+
 ## [3.6.0] — 2026-09-27
 
 **Upgrading:** re-emit (or `geneseed rebuild-all`) after installing. The root file changed, and

package/DESIGN.md

@@ -44,8 +44,8 @@ vault or a specific tool's hooks.
      and the prose words the docs use: the core nouns `LAW(S)`/`DOCTRINE(S)`/`ONTOLOGY`/
      `AGENT(S)`/`SKILL(S)`/`MEMORY`/`NOTEBOOK`/`VAULT`/`WIKI`, plus `TAGLINE`,
      `LOADED_SIGIL`, `EPI_*`, `BENEDICTION`, `DESC_*`, `ROAST_PERSONA`, the invariant
-     titles `LEX_I`..`LEX_XI`, the 27 doctrine-rule titles `DOC_<PACK>_<n>`, the four pack
-     names `PACK_CRAFT`/`PACK_RIGOR`/`PACK_OPS`/`PACK_PROCESS`, and the section intros
+     titles `LEX_I`..`LEX_XI`, the 28 doctrine-rule titles `DOC_<PACK>_<n>`, the five pack
+     names `PACK_CRAFT`/`PACK_RIGOR`/`PACK_OPS`/`PACK_PROCESS`/`PACK_COMMS`, and the section intros
      `INTRO_*`. Each theme defines its own nouns; **neutral keeps the plain words** (Rule,
      Doctrine, Agent, Skill, Memory, Workspace), so neutral output is unchanged.
      `{{LAW}}` and `{{DOCTRINE}}` must each be a **single word** — both heading parsers
@@ -101,9 +101,9 @@ vault or a specific tool's hooks.
    - **Invariants** (`src/laws/universal.md`) — *what is never traded*. Eleven numbered
      Rules, `I`..`XI`, nine in force — IX and XI are retired in place, their numbers kept so
      existing citations resolve — headed `### {{LAW}} <roman> — {{LEX_<roman>}}`.
-   - **Doctrines** (`src/doctrines/{craft,rigor,ops,process}.md`) — *how work is done
+   - **Doctrines** (`src/doctrines/{craft,rigor,ops,process,comms}.md`) — *how work is done
      here*. Practice rules addressed by pack and number, cited as `Doctrine process 5`.
-     `PACK_ORDER` (`js/build/source.mjs`) fixes the order craft → rigor → ops → process, which
+     `PACK_ORDER` (`js/build/source.mjs`) fixes the order craft → rigor → ops → process → comms, which
      is narrative and deliberately not alphabetical.
 
    **The Ontology and the Invariants are never toggleable** — every build carries both,
@@ -197,7 +197,7 @@ theme file defines a `DIR_*` key, so `laws/` is `laws/` in all fourteen voices.
 | Themes | `themes/*.json` | — | token → label maps; `themes/opencode/` is a separate colour system |
 | Release label | `harness.config.json` | `.geneseed-version` | the theme and the human-readable version the driver reads; the canonical identity is the source fingerprint, not this string |
 | Lifecycle | `registry.json` | — | maintainer-side status/version/owner per agent and skill; never rendered into a bundle |
-| Generator | `bin/build-driver.mjs` (`geneseed-build`) | — | substitution + `<!-- INCLUDE: -->` inlining, and the nine `--emit` targets |
+| Generator | `bin/build-driver.mjs` (`geneseed-build`) | — | substitution + `<!-- INCLUDE: -->` inlining, and the eleven `--emit` targets |
 | CLI, as data | `js/cli-table.json` | — | the owned document the entry point parses its own argv from |
 | Automation | `bin/geneseed-cli.mjs` (`geneseed`) | — | 25 verbs — `build` / `doctor` / `status` / `prompt` / `diff` / `setup` / `web` / `upgrade` / … |
 | Hooks | `bin/geneseed-hook.mjs` (`geneseed-hook`) | — | the five verbs an emitted hook config invokes: `context` / `git-gate` / `rule-gate` / `tool-gate` / `learn` |
@@ -225,7 +225,7 @@ theme file defines a `DIR_*` key, so `laws/` is `laws/` in all fourteen voices.
   stuck. WIRE must precede MANIFEST because wiring is what fills the `managed` record the
   manifest stores, and no RENDER may follow a WIRE because a render writes wholesale a file
   a wire has just reconciled. `tests/unit/emit_phase_order.test.mjs` fails the build if any of
-  the nine emits drifts out of that order, or if a new file-mutating routine in
+  the eleven emits drifts out of that order, or if a new file-mutating routine in
   `js/hosts/settings.mjs` is called from an emit without being classified. RENDER and WIRE now run
   in the *same process* — the seam that once spawned a second runtime per emit is gone — so
   the render and wire dispatchers stay two separate functions and two separate statements on

package/QUICKSTART.md

@@ -43,7 +43,7 @@ or a login item it did not create. Your clone keeps working meanwhile.
 
 ## Everything else
 
-Claude Code, Bob and plain-`AGENT.md` installs, per-repo mode, MCP servers, all
+Claude Code, Bob, Copilot, OpenClaude and plain-`AGENT.md` installs, per-repo mode, MCP servers, all
 environment knobs, and troubleshooting live in the full **[Setup guide](SETUP.md)**.
 
 Once installed, point the agent at your repo's own docs with a tiny

package/README.md

@@ -14,7 +14,7 @@
 [![Agents](https://img.shields.io/badge/agents-18-orange)](src/agents/)
 [![Laws](https://img.shields.io/badge/laws-11-critical)](src/laws/universal.md)
 [![Plugins](https://img.shields.io/badge/plugins-7-teal)](adapters/opencode/plugins/)
-[![OpenCode · Claude Code · Bob · Copilot · AGENT.md](https://img.shields.io/badge/works%20with-OpenCode%20·%20Claude%20Code%20·%20Bob%20·%20Copilot%20·%20AGENT.md-1f6feb)](#-supported-harnesses)
+[![OpenCode · Claude Code · Bob · Copilot · OpenClaude · AGENT.md](https://img.shields.io/badge/works%20with-OpenCode%20·%20Claude%20Code%20·%20Bob%20·%20Copilot%20·%20OpenClaude%20·%20AGENT.md-1f6feb)](#-supported-harnesses)
 
 [**Why**](#-1--why-geneseed) · [**Setup**](#-2--setup) · [**Web & terminal**](#-3--web--terminal) · [**What you get**](#-4--what-you-get)
 
@@ -24,7 +24,7 @@
 
 <p align="center"><img src="docs/assets/demo.svg" alt="geneseed setup, then two laws catching a force-push and a credential at the tool boundary" width="760"></p>
 
-**Geneseed compiles your agent's rules instead of asking you to write them.** One source in `src/` renders into a ready-made harness for OpenCode, Claude Code, Bob, Copilot, or any `AGENT.md` tool: a constitution of laws and doctrines, a roster of capability agents, native skills, a memory convention — and, wherever the host has a hook surface, gates that *enforce* the laws at the tool boundary instead of hoping the model remembers them.
+**Geneseed compiles your agent's rules instead of asking you to write them.** One source in `src/` renders into a ready-made harness for OpenCode, Claude Code, Bob, Copilot, OpenClaude, or any `AGENT.md` tool: a constitution of laws and doctrines, a roster of capability agents, native skills, a memory convention — and, wherever the host has a hook surface, gates that *enforce* the laws at the tool boundary instead of hoping the model remembers them.
 
 ```bash
 npx geneseed setup
@@ -36,8 +36,8 @@ Want to read what it leaves behind before installing anything? [**geneseed-demo*
 
 A hand-written instructions file is prose the model may or may not honour, copied into every repo and drifting in each one. Geneseed is a build, and that changes four things:
 
-- **Laws are enforced, not suggested.** A force-push, a `reset --hard`, or a credential written into a tracked file is caught by a hook *before* the tool runs, in the host's own dialect — a prompt on Claude Code and Copilot, a hard block on OpenCode, exit 2 on Bob. The gates fail closed, and every catch is one line in a ledger that `geneseed status` counts.
-- **One source, five targets.** Skills are byte-identical on every host; only the wiring differs. Every commit renders all 261 emit configurations, and a second emit into the same tree must change nothing.
+- **Laws are enforced, not suggested.** A force-push, a `reset --hard`, or a credential written into a tracked file is caught by a hook *before* the tool runs, in the host's own dialect — a prompt on Claude Code, Copilot and OpenClaude, a hard block on OpenCode, exit 2 on Bob. The gates fail closed, and every catch is one line in a ledger that `geneseed status` counts.
+- **One source, six targets.** Skills are byte-identical on every host; only the wiring differs. Every commit renders all 317 emit configurations, and a second emit into the same tree must change nothing.
 - **Costs are measured, not guessed.** Zero runtime dependencies. The hook path loads in about 14 ms per tool call. The default *lean* footprint keeps the always-on context small and puts the full rationale one read away — the numbers are in [docs/token-footprint.md](docs/token-footprint.md).
 - **It follows you.** Install once, globally; every repo inherits it. One `git pull` or `npm install -g geneseed@latest` rebuilds every active install.
 
@@ -164,7 +164,7 @@ The harness ships as a small set of layers, and the web console's rail is the sa
 | --- | --- |
 | **🧭 Ethos** (`ontology/`) | the mind the rules govern, in four prose sections — **Telos** (the Pact: three ranked laws — protect the user, serve their intent, keep your own honesty), **Evidence** (every claim graded by how it was obtained), **Decisions** (classify and tier by reversibility, show the real forks), **Conduct** (answer what was asked, once). Always in force, never toggleable |
 | **🛡️ Rules** (`laws/`) | 11 universal laws, nine of them in force — always, never toggleable: sealed-secrets, one-intent-one-act, verify-before-assert, deletion-is-deliberate, surface-failures, data-not-orders, least-privilege, root-cause, echo-the-intent. Laws IX and XI are retired, their numbers kept so old references resolve |
-| **📐 Doctrines** (`doctrines/`) | practice packs, chosen per install at build time: **craft** (how code is written), **rigor** (how work is proven), **ops** (how the machine is operated), **process** (how a task is run). A doctrine rule may tighten a Rule, never repeal one, and the user's own `user-rules.md` outranks it. Pick with `geneseed-build --doctrines craft,rigor` (or `none`), a single rule with `--exclude-rules "process 7"`, in the setup wizard, or through the switches on the console's Constitution page; all four pack files ship on disk either way, so a citation into a pack you left out still resolves |
+| **📐 Doctrines** (`doctrines/`) | practice packs, chosen per install at build time: **craft** (how code is written), **rigor** (how work is proven), **ops** (how the machine is operated), **process** (how a task is run), **comms** (how answers are presented). A doctrine rule may tighten a Rule, never repeal one, and the user's own `user-rules.md` outranks it. Pick with `geneseed-build --doctrines craft,rigor` (or `none`), a single rule with `--exclude-rules "process 7"`, in the setup wizard, or through the switches on the console's Constitution page; all five pack files ship on disk either way, so a citation into a pack you left out still resolves |
 | **🤖 Agents** (18) | capability specialists: `reviewer`, `tester`, `architect`, `docs`, `security`, `explorer`, `researcher`, `developer` — plus a debate **council** the `council` skill convenes: `advocate`, `skeptic`, `pragmatist`, `steward`, `visionary`, `user-advocate`, `framer`, `empiricist`, `operator`, `historian` |
 | **🛠 Skills** (52) | repeatable workflows: brainstorm · plan · **codebase-design** · **domain-modeling** · **wayfinder** · **tickets** · **develop** · **worktree** · debug · **prototype** · refactor · **ponytail** · **forge-mcp** · **bruno-collection-generator** · **bruno-test-writer** · geneseed-code-review · **fresh-eyes** · **security-audit** · **ci-fix** · **deps-audit** · **review-response** · commit · **ship** · **release** · **migrate** · **git-archaeology** · **git-rescue** · repo-map · document-project · **frontend-design** · **prose** · **ingest** · **research** · **teach** · **quiz** · handoff · roast-me · **council** · parallel-agents · **workflow** · **wiki** · **geneseed** · **rule** · **profile** · **consolidate-memory** · **skill-forge** · **opencode-theme** · **herdr** · **pipeline** · **daydream** · **react-view-transitions** · **token-report** |
 | **🔌 Plugins** (OpenCode) | `geneseed-context` injects project docs *and your machine wiki* every session (and across compaction); `geneseed-learn` distils memory at session end; `geneseed-guard` enforces the safety Laws and protected wiki folders at the tool boundary; `geneseed-workflow` registers the `workflow` tool that runs saved orchestration scripts; `geneseed-notify` sends a native OS notification when a long run finishes; `geneseed-ponytail` holds a minimal-code mode (`/ponytail lite\|full\|ultra\|off`), opt-in, injecting the laziest-that-works ruleset every turn so it doesn't drift; `geneseed-activity` streams what each session is doing to the web console's Activity view |
@@ -210,49 +210,49 @@ A second per-install dial, **footprint**, sets how much of the constitution `AGE
 
 **Lean is authored, not cut.** The Ethos, every Rule and every doctrine rule carry a hand-written lean form beside their full text (`LEAN` blocks in `src/`), so a rule's lean footprint is decided by its author and not by where its first full stop happens to fall — the earlier first-sentence cut shipped Rule II as one 36-character line and dropped its stop-and-ask mechanism, and shipped a doctrine rule like *Change as little as the task requires.* as six words with no verb to act on.
 
-Both footprints put the full text on disk beside `AGENT.md`: `laws/`, `ontology/` and `doctrines/` all ship in the bundle at **full** text whatever the footprint, and **all four pack files ship whether or not the pack was built in** — which is what lets a citation into an inactive pack resolve. So lean is a context/token optimization, **not** a rules cut.
+Both footprints put the full text on disk beside `AGENT.md`: `laws/`, `ontology/` and `doctrines/` all ship in the bundle at **full** text whatever the footprint, and **all five pack files ship whether or not the pack was built in** — which is what lets a citation into an inactive pack resolve. So lean is a context/token optimization, **not** a rules cut.
 
 Lean is the default: the rationale is one read away and the context it frees is paid back on every turn. Switch to **full** when token cost is a non-issue or you run a smaller model, which leans harder on always-present rationale. Set it with `--footprint lean|full`, the Settings toggle, the per-harness dropdown in the Harnesses tab, or the setup wizard. It's remembered in a `.geneseed-footprint` marker and preserved across rebuilds, on every host (OpenCode, Claude Code, Bob, Copilot).
 
 Either way the harness is otherwise identical — same files, Rules, capabilities, and guards; lean only relocates the *reasoning* to on-demand (and adds the standalone law, ontology and doctrine files to global/Claude/Bob installs). The one behavioural edge: with the rationale always in context, **full** applies a rule's nuance more reliably on subtle edge cases — or with a weaker model that may not reach for the pointer.
 
-Want to check a build before it touches anything real? `geneseed-build --validate-only --theme NAME --emit MODE --out TARGET` renders and validates into a throwaway sandbox — nothing under `--out`/`--root` is written — and exits non-zero on any problem. Details: [SETUP.md](SETUP.md#dry-run-a-build-validate).
+Want to check a build before it touches anything real? `geneseed validate --theme NAME --emit MODE --out TARGET` renders and validates into a throwaway sandbox — nothing under `--out`/`--root` is written — and exits non-zero on any problem. Details: [SETUP.md](SETUP.md#dry-run-a-build-validate).
 
 ---
 
 ## 🔌 Supported harnesses
 
-One source, five emit targets. Geneseed builds into whichever host you point it
+One source, six emit targets. Geneseed builds into whichever host you point it
 at — each with a per-repo and a global (`-global`) variant — plus a portable
 `files` bundle any `AGENT.md`-aware tool can read. **OpenCode** runs its own
-engine (JS plugins, colour themes, LSP); **Claude Code**, **Bob**, and
-**Copilot** share one Claude-shaped engine that diverges only by host dialect.
+engine (JS plugins, colour themes, LSP); **Claude Code**, **Bob**, **Copilot**
+and **OpenClaude** share one Claude-shaped engine that diverges only by host dialect.
 
 The harness — its Rules, Agents, Skills, Memory convention, and preamble voice —
 is **identical on every host**. What differs is how much of it the host can
 *automate* for you (via plugins or hooks) versus carry as preamble discipline.
 
-| Capability | OpenCode | Claude Code | Bob | Copilot |
-| --- | :---: | :---: | :---: | :---: |
-| **Instructions file** | `AGENT.md` + `opencode.json` | `CLAUDE.md` | `AGENTS.md` + `rules/geneseed.md` | `AGENTS.md` / `copilot-instructions.md` |
-| **Agents** (capability specialists) | ✅ native | ✅ | ✅ | ✅ `.agent.md` |
-| **Skills** (byte-identical) | ✅ | ✅ | ✅ | ✅ |
-| **Memory & Notebook** | ✅ | ✅ | ✅ | ✅ |
-| **Context injection** | ⚙️ plugin | 🪝 hook | 🪝 hook¹ | 🪝 hook³ |
-| **Memory write-back** (learn) | ⚙️ plugin | 🪝 hook | 🪝 hook¹ | 🪝 hook³ |
-| **Git-gate consent** (process 5) | ⚙️ plugin | 🪝 hook | 🪝 hook¹ (warn) | 🪝 hook³ |
-| **Rule-gate consent** (process 1) | ⚙️ plugin² | 🪝 hook | 🪝 hook¹ (warn) | 🪝 hook³ |
-| **Laws I / IV at the boundary** | ⚙️ plugin (block) | 🪝 hook (ask) | 🪝 hook¹ (exit 2) | 🪝 hook³ (ask) |
-| **Sovereign-repo excludes** | ⚙️ plugin | ✅ `claudeMdExcludes` | ✅ rules-shadow | ➖ none |
-| **MCP server wiring** | ✅ `mcp` | ✅ `mcpServers` | ✅ `mcp.json` | ✅ `mcp-config.json` |
-| **Colour themes** | ✅ full palette | ➖ | ➖ | ➖ |
-| **LSP · workflow runner · primary-agent · `/`-commands** | ✅ | ➖ | ➖ | ➖ |
-
-<sub>✅ native support · ⚙️ OpenCode plugin · 🪝 `settings.json` hook · 📄 carried by preamble prose only · ➖ no host mechanism (harness discipline still applies) · ¹ Bob's own hook contract: global hooks in `~/.bob/settings/settings.json`, Claude's event names but stdout ignored on `PreToolUse` — a refusal is **exit code 2**. So Laws I/IV exit 2, the consent rules are a stderr line, `SessionStart` context is plain stdout, `Stop` runs learn; `SubagentStop`/`PreCompact` are not Bob events and are not written. Unverified live (no Bob install on the authoring machine); the harness still holds via the rules preamble. · ² OpenCode's `tool.execute.before` can only allow or throw, with no "ask the user" tier, so the rule gate is a one-shot speed bump there rather than a prompt. · ³ Copilot's `~/.copilot/settings.json` hooks (`sessionStart`, `preToolUse`, `agentStop`, `preCompact`) wired by the **global** emit only; `preToolUse` has an ask tier, so every rule asks as on Claude Code. Unverified live (no Copilot CLI on the authoring machine).</sub>
+| Capability | OpenCode | Claude Code | Bob | Copilot | OpenClaude |
+| --- | :---: | :---: | :---: | :---: | :---: |
+| **Instructions file** | `AGENT.md` + `opencode.json` | `CLAUDE.md` | `AGENTS.md` + `rules/geneseed.md` | `AGENTS.md` / `copilot-instructions.md` | `CLAUDE.md` (in `.openclaude/` per repo) |
+| **Agents** (capability specialists) | ✅ native | ✅ | ✅ | ✅ `.agent.md` | ✅ |
+| **Skills** (byte-identical) | ✅ | ✅ | ✅ | ✅ | ✅ |
+| **Memory & Notebook** | ✅ | ✅ | ✅ | ✅ | ✅ |
+| **Context injection** | ⚙️ plugin | 🪝 hook | 🪝 hook¹ | 🪝 hook³ | 🪝 hook⁴ |
+| **Memory write-back** (learn) | ⚙️ plugin | 🪝 hook | 🪝 hook¹ | 🪝 hook³ | 🪝 hook⁴ |
+| **Git-gate consent** (process 5) | ⚙️ plugin | 🪝 hook | 🪝 hook¹ (warn) | 🪝 hook³ | 🪝 hook⁴ |
+| **Rule-gate consent** (process 1) | ⚙️ plugin² | 🪝 hook | 🪝 hook¹ (warn) | 🪝 hook³ | 🪝 hook⁴ |
+| **Laws I / IV at the boundary** | ⚙️ plugin (block) | 🪝 hook (ask) | 🪝 hook¹ (exit 2) | 🪝 hook³ (ask) | 🪝 hook⁴ (ask) |
+| **Sovereign-repo excludes** | ⚙️ plugin | ✅ `claudeMdExcludes` | ✅ rules-shadow | ➖ none | ✅ `claudeMdExcludes` |
+| **MCP server wiring** | ✅ `mcp` | ✅ `mcpServers` | ✅ `mcp.json` | ✅ `mcp-config.json` | ✅ `mcpServers` |
+| **Colour themes** | ✅ full palette | ➖ | ➖ | ➖ | ➖ |
+| **LSP · workflow runner · primary-agent · `/`-commands** | ✅ | ➖ | ➖ | ➖ | ➖ |
+
+<sub>✅ native support · ⚙️ OpenCode plugin · 🪝 `settings.json` hook · 📄 carried by preamble prose only · ➖ no host mechanism (harness discipline still applies) · ¹ Bob's own hook contract: global hooks in `~/.bob/settings/settings.json`, Claude's event names but stdout ignored on `PreToolUse` — a refusal is **exit code 2**. So Laws I/IV exit 2, the consent rules are a stderr line, `SessionStart` context is plain stdout, `Stop` runs learn; `SubagentStop`/`PreCompact` are not Bob events and are not written. Unverified live (no Bob install on the authoring machine); the harness still holds via the rules preamble. · ² OpenCode's `tool.execute.before` can only allow or throw, with no "ask the user" tier, so the rule gate is a one-shot speed bump there rather than a prompt. · ³ Copilot's `~/.copilot/settings.json` hooks (`sessionStart`, `preToolUse`, `agentStop`, `preCompact`) wired by the **global** emit only; `preToolUse` has an ask tier, so every rule asks as on Claude Code. Unverified live (no Copilot CLI on the authoring machine). · ⁴ OpenClaude is a Claude Code fork: Claude's hook groups and verdicts verbatim, in `~/.openclaude/settings.json` (global) or `.openclaude/settings.local.json` (per repo). Unverified live (no OpenClaude install on the authoring machine).</sub>
 
 **Reading the matrix.** Everything above the divider is at full parity — no host
 drops an Agent, Skill, or the memory convention. The asymmetry is entirely in
-*automation mechanism*: OpenCode's plugin surface and the Claude/Bob/Copilot hook
+*automation mechanism*: OpenCode's plugin surface and the Claude/Bob/Copilot/OpenClaude hook
 surfaces enforce a few Rules for you, each in the tier its host offers (a prompt on
 Claude Code, a hard block or a logged warning where the host has no prompt to
 give), and what no host can automate rides the preamble. The OpenCode-only extras (themes, LSP,
@@ -260,7 +260,8 @@ workflow runner, primary-agent) have no analogue on a Claude-shaped host.
 
 Per-host wiring in depth: **[OpenCode](adapters/opencode/README.md)** ·
 **[Claude Code](adapters/claude-code/README.md)** ·
-**[Bob](adapters/bob/README.md)** · **[Copilot](adapters/copilot/README.md)**.
+**[Bob](adapters/bob/README.md)** · **[Copilot](adapters/copilot/README.md)** ·
+**[OpenClaude](adapters/openclaude/README.md)**.
 Token cost per host: **[docs/token-footprint.md](docs/token-footprint.md)**.
 
 ## 🗂 Layout
@@ -281,7 +282,7 @@ Geneseed/
 │   ├── AGENT.md.tmpl     the entrypoint, rendered to AGENT.md
 │   ├── ontology/         how the agent thinks — Telos, Evidence, Decisions, Conduct
 │   ├── laws/             the universal invariants
-│   ├── doctrines/        the four practice packs (craft, rigor, ops, process)
+│   ├── doctrines/        the five practice packs (craft, rigor, ops, process, comms)
 │   ├── postures/         the relationship register, inlined into AGENT.md
 │   ├── modes/            the operating register, inlined into AGENT.md
 │   ├── agents/           capability specialists
@@ -293,7 +294,7 @@ Geneseed/
 ├── tests/                Node test suites, golden.mjs (every emit config) and mutate.mjs
 ├── docs/                 guides (web-ui, wiki, …) + docs/web/ (the console's Docs pages);
 │                         specs/, reviews/, superpowers/ are local working docs — git-ignored
-├── adapters/             per-host glue (opencode/, claude-code/, bob/, copilot/)
+├── adapters/             per-host glue (opencode/, claude-code/, bob/, copilot/, openclaude/)
 └── .github/workflows/    ci.yml (doctor + tests) · publish.yml (npm, OIDC, manual only)
 ```
 
@@ -345,6 +346,7 @@ Details and precedence rules: [SETUP.md → Upgrade](SETUP.md#upgrade).
 | **[adapters/claude-code/](adapters/claude-code/README.md)** | The Claude Code hook adapter |
 | **[adapters/bob/](adapters/bob/README.md)** | The IBM Bob adapter — Claude-shaped, rules-file preamble |
 | **[adapters/copilot/](adapters/copilot/README.md)** | The GitHub Copilot adapter — global hooks (`sessionStart`, `preToolUse`, `agentStop`, `preCompact`) |
+| **[adapters/openclaude/](adapters/openclaude/README.md)** | The OpenClaude adapter — the Claude engine under `~/.openclaude` / `.openclaude/` |
 | **[src/memory/README.md](src/memory/README.md)** | The memory convention |
 | **[src/notebook/README.md](src/notebook/README.md)** | The agent's own freeform-space convention |
 

package/SETUP.md

@@ -22,7 +22,7 @@ that matches your tool, then configure and verify. For the conceptual overview s
 
 - **Node ≥ 22.3** — the only hard requirement. Geneseed ships as an npm package with
   **zero dependencies**; `npx geneseed` needs nothing else.
-- **Your agent tool** — OpenCode (recommended), Claude Code, Bob, Copilot, or anything
+- **Your agent tool** — OpenCode (recommended), Claude Code, Bob, Copilot, OpenClaude, or anything
   that reads a root instructions file.
 - *Only for a git checkout:* **git**. Nothing else — a checkout runs the same Node
   entry points the npm package installs.
@@ -94,6 +94,7 @@ hand? Pick a path below.
 | [B — OpenCode, per-repo](#path-b--opencode-per-repo) | You want a committed `.opencode/` layer in one repository. |
 | [C — Claude Code](#path-c--claude-code) | You drive Claude Code and want the lifecycle hooks. |
 | [C′ — GitHub Copilot](#path-c--github-copilot) | You drive the Copilot CLI, coding agent, or VS Code agent mode. |
+| [C″ — OpenClaude](#path-c--openclaude) | You drive OpenClaude, the any-model Claude Code fork. |
 | [D — Any `AGENT.md` tool](#path-d--any-agentmd-tool) | Cursor, Aider, or any tool that reads a root instructions file. |
 | [E — No runtime on the target at all](#path-e--no-runtime-on-the-target-at-all) | The machine that *uses* the harness cannot run Node. |
 
@@ -214,7 +215,8 @@ Inside an excluded folder the global install is fully dormant: the context,
 learn and git-gate hooks exit silently (they check `<config dir>/excludes.json`
 on every call — edits take effect immediately, no re-emit), and the global
 preamble is suppressed natively (Claude: `claudeMdExcludes` written to the
-repo's own `.claude/settings.local.json`; Bob: the workspace rules shadow stub;
+repo's own `.claude/settings.local.json`, and OpenClaude's in `.openclaude/settings.local.json`;
+Bob: the workspace rules shadow stub;
 OpenCode: the plugins stand down). Everything is reversed by `exclude remove`.
 
 Limitations: GitHub Copilot has no per-repo suppression mechanism, so the global
@@ -255,6 +257,28 @@ shape). `$COPILOT_CONFIG_DIR` relocates the personal dir, mirroring
 `$BOB_CONFIG_DIR`. Note both carriers stack if you install globally *and* per-repo —
 the global emit warns when that's about to happen.
 
+### Path C″ — OpenClaude
+
+```
+geneseed-build --emit openclaude-global           # render into ~/.openclaude
+geneseed-build --emit openclaude --out . --root .  # per-repo: .openclaude/, committed
+```
+
+[OpenClaude](https://openclaude.gitlawb.com/) grew out of the Claude Code codebase, so this
+is Path C with another config dir: the same agents, skills, hook groups and `ask` verdicts.
+It never reads `~/.claude` or a project `.claude/`, so a Claude Code install does not reach
+it. Both installs can live side by side. Two differences:
+
+- **The per-repo preamble is `.openclaude/CLAUDE.md`**, not a root file. OpenClaude skips a
+  root `CLAUDE.md` whenever the repo has an `AGENTS.md`, and reads `.openclaude/CLAUDE.md`
+  always. Hooks go in `.openclaude/settings.local.json` (gitignored) with a
+  `claudeMdExcludes` for the global preamble, as on Claude Code.
+- **`$OPENCLAUDE_CONFIG_DIR` relocates the global dir.** It is OpenClaude's own variable.
+  MCP servers go in `~/.openclaude.json`, or in `.openclaude.json` inside that dir when it is
+  set. Per repo they go in `.mcp.json`.
+
+Details in [adapters/openclaude/](adapters/openclaude/README.md).
+
 ### Path D — Any `AGENT.md` tool
 
 ```
@@ -323,7 +347,7 @@ case where a `0` would have meant "in sync" without having checked anything.
 The constitution is three tiers, and only one of them is a choice. The **Ontology** (how the
 agent thinks — Telos, Evidence, Decisions, Conduct) and the nine **Rules** (what it never
 trades away) are always on and cannot be switched off. The **Doctrines** are practices rather
-than principles, and they ship as four packs:
+than principles, and they ship as five packs:
 
 | Pack | What it governs |
 | --- | --- |
@@ -331,17 +355,18 @@ than principles, and they ship as four packs:
 | **rigor** | how work is proven — idempotence, honest tests, cover-and-verify, gates that can actually fail |
 | **ops** | how the machine is driven — tool discovery, commands that return, complete teardowns, restart is not reload |
 | **process** | how a session runs — planning, context economy, docs first, bounded loops, and the consent gate on every commit and push |
+| **comms** | how answers are presented — stable reference codes on tracked items, a diagram or a table only where it earns its place |
 
 They are picked **at build time**, once, on the generator — there is no runtime toggle — and
-the default is all four:
+the default is all five:
 
     geneseed-build --doctrines craft,rigor   # two packs
     geneseed-build --doctrines none          # ontology and the nine Rules only
-    geneseed-build                           # all four (the default)
+    geneseed-build                           # all five (the default)
 
 `harness.config.json`'s `doctrines` array sets this checkout's own default, and `doctor`
 refuses one that names a pack the checkout does not ship. Order is fixed by the harness
-(craft → rigor → ops → process) regardless of the order you type.
+(craft → rigor → ops → process → comms) regardless of the order you type.
 
 ### One rule at a time
 
@@ -428,7 +453,7 @@ you run a smaller model.
 **Same harness, either way.** Footprint changes neither what the harness *is* nor what it
 can *do*: lean and full emit identical files (same agents, skills, plugins, commands, memory,
 notebook, hooks) and every Rule is present and binding. The only structural difference is
-that a lean install on a global / Claude / Bob / Copilot target also ships the standalone
+that a lean install on a global / Claude / Bob / Copilot / OpenClaude target also ships the standalone
 `laws/universal.md` and `ontology/` (project bundles already carry them, and `doctrines/`
 ships at both footprints on every target); the only behavioural difference is that the
 reasoning loads on demand instead of every turn. Lean is the default; full, with the rationale
@@ -438,7 +463,7 @@ with a weaker model, and is one flag away.
 Set it with `--footprint lean|full` (alongside any `--emit`), the **Footprint** toggle in
 the web Settings, the per-harness dropdown in the Harnesses tab, or the setup wizard. It is
 remembered in a `.geneseed-footprint` marker and preserved across every rebuild, on every
-host (OpenCode, Claude Code, Bob, Copilot).
+host (OpenCode, Claude Code, Bob, Copilot, OpenClaude).
 
 ### Dry-run a build (`validate`)
 
@@ -447,8 +472,8 @@ geneseed validate --theme imperial --emit opencode --out /path/to/repo/Harness
 ```
 
 (It is a verb on the CLI rather than a flag on the generator because it runs `doctor`, and
-the generator is deliberately unable to start a process. `geneseed-build --validate-only
-…` is the same tool with the same flags.)
+the generator is deliberately unable to start a process — `geneseed-build` refuses
+`--validate-only` outright.)
 
 Renders and emits the requested `--theme`/`--emit`/`--out`/`--root`/`--footprint`
 combination into a throwaway sandbox — nothing under the real `--out`/`--root` is
@@ -917,6 +942,7 @@ not connected, walk these in order:
 | `GENESEED_NO_WEB` | `home` | `1` disables the web-first default of bare `geneseed` — it prints the command list instead |
 | `GENESEED_STACK_GLOBAL` | context hook | `1` disables project-bypasses-global: a project install of the same host no longer makes the global install's hook stand down, so both inject |
 | `OPENCODE_CONFIG_DIR` / `XDG_CONFIG_HOME` | global emit | where the global install is written |
+| `OPENCLAUDE_CONFIG_DIR` | `openclaude-global` emit | OpenClaude's own config dir variable (default `~/.openclaude`); also moves `.openclaude.json` |
 | `OPENCODE_DISABLE_LSP_DOWNLOAD` | OpenCode (LSP) | `true` stops OpenCode auto-downloading built-in language servers (typescript, pyright, jdtls) — set it on air-gapped machines and pre-install each server yourself |
 
 ---

package/SHIPPED.md

@@ -20,7 +20,7 @@ historical references, not files distributed with the repo.
 > **On version numbers.** [`harness.config.json`](harness.config.json)'s `version` is a
 > human-readable label only. The canonical identity of an installed harness is the
 > **source fingerprint** stamped in `.geneseed-version` (see `geneseed version`), not the
-> string. Current label: **3.6.0**.
+> string. Current label: **3.8.0**.
 
 ## Capabilities
 
@@ -30,14 +30,14 @@ Every row below is present in the tree today; "Spec" names the design record.
 | --- | --- | --- |
 | **Themed generator** | One neutral `src/` → 14 themed bundles via `geneseed-build` (zero dependencies); structure stays theme-independent | [DESIGN.md](DESIGN.md) |
 | **Laws / Agents / Skills / Memory / Notebook** | 11 laws, 18 agents, 52 skills, the memory convention, and the agent's sovereign notebook | `2026-06-11-notebook-sovereign-space` · `2026-06-10-notebook-agent-own-space` |
-| **Three-tier constitution** | The governance surface splits into an always-on **Ontology** (Telos, Evidence, Decisions, Conduct — the Pact absorbed into Telos), the eleven always-on **Invariants** (IX and XI retired in place — folded into rigor 5 and Law III, numbers kept), and four toggleable **Doctrine** packs (craft, rigor, ops, process) addressed `<pack> <n>`. Packs are chosen at build time with `--doctrines` or the setup wizard; the whole catalogue ships on disk either way, so a citation into an inactive pack still resolves. Precedence, in order: Ontology + Invariants, then the user's `user-rules.md`, then the active Doctrines, then `PROFILE.md`. `doctor`'s `constitutionProblems` gates pack numbering, the per-rule Principle column, every `{{DOCTRINE}}` citation in `src/`, and the rule that an always-on tier may never cite a toggleable one | `2026-08-19-three-tier-constitution-design` |
+| **Three-tier constitution** | The governance surface splits into an always-on **Ontology** (Telos, Evidence, Decisions, Conduct — the Pact absorbed into Telos), the eleven always-on **Invariants** (IX and XI retired in place — folded into rigor 5 and Law III, numbers kept), and five toggleable **Doctrine** packs (craft, rigor, ops, process, comms) addressed `<pack> <n>`. Packs are chosen at build time with `--doctrines` or the setup wizard; the whole catalogue ships on disk either way, so a citation into an inactive pack still resolves. Precedence, in order: Ontology + Invariants, then the user's `user-rules.md`, then the active Doctrines, then `PROFILE.md`. `doctor`'s `constitutionProblems` gates pack numbering, the per-rule Principle column, every `{{DOCTRINE}}` citation in `src/`, and the rule that an always-on tier may never cite a toggleable one | `2026-08-19-three-tier-constitution-design` |
 | **`doctor`** | One check: unresolved tokens, dead/non-hermetic links, theme-key parity, authoring gates, rendered-bundle drift | `2026-06-07-theme-aware-doctor-diff` |
 | **`diff` + improvements export** | Deployed-vs-source drift report; export an `improvements.md` back-port | `2026-06-12-improvements-export` |
 | **`status` / `version`** | Headless dashboard + fingerprint verdict (no TUI needed) | `2026-06-07-status-command` · `2026-06-07-version-and-uninstall` |
 | **Terminal rendering** | There is no full-screen control panel: `tui` and `menu` are verbs that say so and print the command list. The display-width and glyph layer ships on, behind `status` and the install animation | `2026-06-07-tui-refactor-polish` · `2026-06-08-tui-modern-refresh` · `2026-06-11-windows-tui` |
 | **Web console** | Local browser UI (Dashboard; Codex: Constitution, Rules, Profile, Skills, Agents, Library, Docs; Care: Activity, Changes, Doctor; Setup: Harness, Settings), auto-build, in-app docs menu | `2026-06-12-web-ui-v2` · `2026-06-12-web-auto-build` · `2026-06-13-docs-menu` |
 | **OpenCode adapter** | Native agents/skills mapping + plugins (context, learn, guard, workflow, notify, ponytail, activity); global-emit link integrity; JSONC config target | `2026-06-07-opencode-adapter-features` · `2026-06-07-global-emit-link-integrity` · `2026-06-12-opencode-jsonc-target` · `2026-06-16-ponytail-minimal-code-mode` |
-| **Host hooks, per dialect** | Every host gets the hook surface its runtime offers, spoken in that runtime's own verdict dialect via `--host`: Claude Code asks (`permissionDecision`), Copilot asks as Claude does (`sessionStart`, `preToolUse`, `agentStop`, `preCompact` in `~/.copilot/settings.json`, global scope only), Bob refuses by exit code 2 (five Claude-named events, nested `~/.bob/settings/settings.json`, no subagent event), OpenCode's guard throws. Laws I/IV are the hard tier everywhere; the consent rules ask where a host can ask and warn where it cannot. `tool-gate` fuses the two gates for hosts that run one command per event; `PreCompact` runs `learn` before Claude compacts; every block or ask lands in `notebook/gates.jsonl` on every host | [copilot](adapters/copilot/README.md) · [bob](adapters/bob/README.md) · [claude-code](adapters/claude-code/README.md) · [candidate hosts](docs/candidate-hosts.md) |
+| **Host hooks, per dialect** | Every host gets the hook surface its runtime offers, spoken in that runtime's own verdict dialect via `--host`: Claude Code asks (`permissionDecision`), OpenClaude asks exactly as Claude does (a Claude Code fork, under `~/.openclaude` / `.openclaude/`), Copilot asks as Claude does (`sessionStart`, `preToolUse`, `agentStop`, `preCompact` in `~/.copilot/settings.json`, global scope only), Bob refuses by exit code 2 (five Claude-named events, nested `~/.bob/settings/settings.json`, no subagent event), OpenCode's guard throws. Laws I/IV are the hard tier everywhere; the consent rules ask where a host can ask and warn where it cannot. `tool-gate` fuses the two gates for hosts that run one command per event; `PreCompact` runs `learn` before Claude compacts; every block or ask lands in `notebook/gates.jsonl` on every host | [copilot](adapters/copilot/README.md) · [bob](adapters/bob/README.md) · [claude-code](adapters/claude-code/README.md) · [candidate hosts](docs/candidate-hosts.md) |
 | **Workflow primitive** | Saved, code-driven subagent orchestration (`workflow` tool + runtime); shipped scripts include `dispatch` — decompose a goal, route each subtask to its owning agent, converge | `2026-06-09-opencode-workflow-primitive` |
 | **Per-agent memory** | Each capability agent keeps durable lessons in `memory/agents/<name>.md`: read at dispatch, written back mechanically by `learn` on session/subagent end (OpenCode plugin + Claude `SubagentStop`; Bob has no subagent event); `learn --consolidate` rebuilds the index | `2026-07-04-orchestration-memory-upgrade` |
 | **Wiki integration** | Machine-wide knowledge base (`wiki.jsonc`): eager/lazy loading, conventions, protected folders enforced at the tool boundary | `2026-06-11-wiki-knowledge-base` |

package/adapters/claude-code/skills/geneseed/SKILL.md

@@ -21,7 +21,7 @@ If none resolve, the user does not have Geneseed deployed here — say so and st
 
 A live harness root contains: `AGENT.md`, `ontology/universal.md`, `laws/universal.md`, `doctrines/<pack>.md`, `agents/<name>.md`, `skills/<name>/SKILL.md`, `memory/MEMORY.md`, `notebook/NOTEBOOK.md`, `themes/`, and (on OpenCode) `plugins/`, `workflows/`, `opencode.jsonc`, `wiki.jsonc`.
 
-The constitution is **three tiers**: an always-on **Ontology** (four prose sections — Telos, Evidence, Decisions, Conduct), nine always-on **Rules** numbered I–IX, and the **Doctrines** — practice packs (`craft`, `rigor`, `ops`, `process`) chosen per install at build time. `AGENT.md` carries all three inline (whole at the `full` footprint, heading-plus-first-line at `lean`), *and* the complete text ships as files beside it. All four pack files ship even when a pack was not built in, so a citation into an inactive pack still resolves on disk — which is why a question about a rule is answered from the tier file, never only from `AGENT.md`.
+The constitution is **three tiers**: an always-on **Ontology** (four prose sections — Telos, Evidence, Decisions, Conduct), nine always-on **Rules** numbered I–IX, and the **Doctrines** — practice packs (`craft`, `rigor`, `ops`, `process`, `comms`) chosen per install at build time. `AGENT.md` carries all three inline (whole at the `full` footprint, heading-plus-first-line at `lean`), *and* the complete text ships as files beside it. All five pack files ship even when a pack was not built in, so a citation into an inactive pack still resolves on disk — which is why a question about a rule is answered from the tier file, never only from `AGENT.md`.
 
 ## Read-only verbs (safe, no confirmation needed)
 

package/adapters/openclaude/README.md

@@ -0,0 +1,64 @@
+# 🦀 OpenClaude adapter
+
+> [← Back to README](../../README.md) · [Setup guide](../../SETUP.md) · [Claude Code adapter](../claude-code/README.md) · [OpenCode adapter](../opencode/README.md)
+
+[OpenClaude](https://openclaude.gitlawb.com/) (`@gitlawb/openclaude`, binary
+`openclaude`) is an open-source coding-agent CLI that "originated from the Claude
+Code codebase" and talks to any model provider. Its config surfaces are Claude
+Code's (`settings.json` hooks, `agents/*.md`, `skills/<name>/SKILL.md`,
+`CLAUDE.md`, `claudeMdExcludes`), so the emit **reuses the Claude engine and the
+Claude hook dialect verbatim**. What changes is where OpenClaude keeps its config.
+There is nothing to install by hand: `geneseed setup` (or `geneseed-build --emit
+openclaude` / `--emit openclaude-global`) writes everything.
+
+**OpenClaude never reads `~/.claude`, a project `.claude/`, or `$CLAUDE_CONFIG_DIR`.**
+A Claude Code install is invisible to it, so it gets its own. The two coexist on one
+machine and in one repo without touching each other.
+
+## What the emit writes
+
+### Per-repo (`--emit openclaude`)
+
+Everything lives under **`.openclaude/`**. Nothing is written at the repo root.
+
+- `CLAUDE.md`: the harness preamble as a delimited **managed block**. OpenClaude
+  loads the root `AGENTS.md`, or the root `CLAUDE.md` only when `AGENTS.md` is
+  absent, but it **always** reads `.openclaude/CLAUDE.md`. Writing there means the
+  preamble loads in every repo, and a root `CLAUDE.md` owned by a Claude Code install
+  (or by you) is left alone.
+- `agents/<name>.md` in the Claude subagent dialect, and `skills/<name>/SKILL.md`,
+  byte-identical to every other host.
+- `settings.local.json`: Geneseed's hooks, plus a `claudeMdExcludes` entry for the
+  global `~/.openclaude/CLAUDE.md` (project-bypasses-global, as on Claude).
+  Gitignored by the emit's `.openclaude/.gitignore`, because the hook commands name
+  this machine's paths.
+- `memory/`, `notebook/` stores and their indices.
+- MCP servers you wire with `geneseed mcp` or the web console go in the repo's
+  `.mcp.json`, as on Claude.
+
+### Global (`--emit openclaude-global` → `~/.openclaude`, or `$OPENCLAUDE_CONFIG_DIR`)
+
+The same layout under the config dir, with `CLAUDE.md` (auto-loaded as user
+memory) and `settings.json`. `$OPENCLAUDE_CONFIG_DIR` is OpenClaude's own
+documented variable, so Geneseed honours it. Claude's `$CLAUDE_CONFIG_DIR` is
+ignored, as OpenClaude ignores it. MCP servers go in `~/.openclaude.json`, or in
+`$OPENCLAUDE_CONFIG_DIR/.openclaude.json` when the variable is set: OpenClaude's
+global config file.
+
+## Hooks
+
+The Claude group set, unchanged: `PreToolUse` (git gate on `Bash`, rule gate on
+writes), `SessionStart` (context on `startup|clear` and `resume|compact`), `Stop`,
+`SubagentStop` and `PreCompact` (learn). OpenClaude reads Claude's
+`hookSpecificOutput.permissionDecision`, so the gates **ask** where Claude asks.
+The context hook carries `--host openclaude` for one reason. It tells the hook
+which root file OpenClaude already loads (`AGENTS.md` when present, else
+`CLAUDE.md`), so that file is not injected a second time.
+
+## Not supported
+
+- **Workflows.** OpenClaude ships its `WorkflowTool` disabled, so the `workflow`
+  skill falls back to parallel agents, as on Bob and Copilot.
+- **Live verification.** The emit follows OpenClaude's source (`src/utils/envUtils.ts`,
+  `src/utils/claudemd.ts`, `src/utils/config.ts`, `src/types/hooks.ts`) as of
+  2026-09. It has not been run against an installed OpenClaude yet.

package/adapters/opencode/plugins/geneseed-workflow.js

@@ -89,7 +89,7 @@ function summarize(name, result, stats, tracePath) {
 }
 
 // Kept worktrees are work awaiting review, and an overlap is a conflict awaiting ONE
-// merger (process 8) — both are said out loud, never left for the trace to hold.
+// merger (process 7) — both are said out loud, never left for the trace to hold.
 function isolationReport(stats) {
   const kept = stats.worktrees || []
   if (!kept.length) return ""

package/adapters/opencode/workflows/_runtime.js

@@ -182,7 +182,7 @@ async function runChildSession(client, { prompt, agent, model, title, directory
 
 // ---- worktree isolation ------------------------------------------------------
 // `agent(prompt, { isolation: "worktree" })` — the same option Claude Code's Workflow
-// takes. Parallel editors in one tree lose each other's writes (process 8, one writer per
+// takes. Parallel editors in one tree lose each other's writes (process 7, one writer per
 // file), so each isolated agent gets its own branch + worktree off the root's HEAD, and
 // the files it changed are recorded for `overlaps()`. A worktree with no change is
 // removed with its branch; one with changes is KEPT for the parent to review and merge —

package/docs/extending.md

@@ -119,7 +119,7 @@ Notes that matter:
   from the seven commands; the container one is reachable locally through
   `tests/helpers/no-python-container.sh` with a docker daemon.
 - **Two assertions in `tests/unit/claude.test.mjs` silently stand down** on any machine where an
-  ancestor of the temp sandbox is a `.claude`/`.bob` install — which is every developer machine
+  ancestor of the temp sandbox is a `.claude`/`.bob`/`.openclaude` install — which is every developer machine
   with Claude Code installed under `~`. They are replaced by a `t.diagnostic`, so the TAP
   `# skipped` count does **not** move, and a local run shows no sign of it.
 
@@ -280,7 +280,7 @@ of nine emit modes in order and themed, under both footprints, with a `CEILING`
 (half the ceiling) on the rendered size. Its docblock carries the current measurement against
 the largest carrier — the host-agnostic `files` bundle; no figure is repeated here, because a
 typed headroom is stale by the next rule. Read that docblock before adding text to any tier; it is
-re-measured, never nudged, and the ceiling is measured **with all four packs active**, which is
+re-measured, never nudged, and the ceiling is measured **with all five packs active**, which is
 the only configuration it can speak for.
 
 ### 2d — Adding a whole PACK
@@ -291,15 +291,27 @@ Rare, and mechanical. On top of §2a for each rule the pack carries:
    file `PACK_ORDER` names but cannot read, or one carrying no `### {{DOCTRINE}} <pack> <n>`
    heading at all, is a refusal.
 2. `PACK_ORDER` in `js/build/source.mjs` — the registration, and the render order. It is **narrative,
-   not alphabetical** (craft → rigor → ops → process); discovery sorts alphabetically and the
+   not alphabetical** (craft → rigor → ops → process → comms); discovery sorts alphabetically and the
    renderer refuses a `.md` under `src/doctrines/` that `PACK_ORDER` does not name, rather than
    skipping it.
 3. `PACK_<NAME>` in `themes/_TEMPLATE.json` and all fourteen voices. Unlike `DOC_*`, this family is
    held only by `themeParityProblems` — presence, across the voices, template excluded.
 4. `DOCTRINE_BLURBS` in `js/maintain/setup.mjs` — the one-line description an installer sees in the wizard,
    and the only place a pack is ever explained to them. Missing entries fall back to the bare name.
-5. `harness.config.json` if the pack should be on by default; `constitutionProblems` refuses a
-   `doctrines` array naming a pack this checkout does not ship.
+5. `harness.config.json` only if this checkout's default must be *narrower* than every pack. The
+   shipped file carries no `doctrines` key, and an absent key means all of `PACK_ORDER`, so
+   step 2 already makes a new pack default-on. `constitutionProblems` refuses a `doctrines`
+   array naming a pack this checkout does not ship.
+6. The written-out **pack lists** in `tests/` — not only the rule totals of §2a. The full set is
+   spelled out, in `PACK_ORDER`, in `emit_smoke`, `generate`, `harness`, `setup`, `web_api`,
+   `web_jobs` and `wizard`, and the wizard cells also feed one y/n answer per pack on stdin.
+   Grep `tests/` for `'process']` and `ops,process` before trusting this list.
+7. **Existing installs.** An install's pack set is read back off its carrier's `Active packs:`
+   marker (§9), which names only the packs that existed when it was built, so a new pack reaches
+   an existing install only if that install is re-emitted *and* the reader adds it. A pack that
+   merely adds rules can stay off for old installs. A pack that *moves* a rule out of another
+   pack cannot, or the moved rule disappears on the next rebuild: `comms` (2026-09-27) is the
+   worked example — see `legacyProcessCarrier` in `js/hosts/installs.mjs`.
 
 ---
 
@@ -682,7 +694,7 @@ rows, nor `web/package.json`.
 |---|---|---|
 | git checkout | `geneseed upgrade` | export improvements → preflight → ff-only pull → `doctor` on the pulled tree → re-emit this bundle → bounce the web daemon → `rebuild-all` |
 | npm | `npm install -g geneseed@latest`, then `geneseed rebuild-all` | there is no `postinstall`; the two steps are manual |
-| any | `geneseed rebuild-all` | every **active** install, each re-read in its own five values (theme, emit, footprint, posture, mode) |
+| any | `geneseed rebuild-all` | every **active** install, each re-read in its own values: theme, emit, footprint, posture, mode, and the two doctrine axes (`Active packs:` and `Excluded rules:`, read back by `doctrinesForBuild` and `excludedRulesOfDir`) |
 
 **Which installs get missed:** project installs that were never registered; installs disabled via
 the `.geneseed-disabled` stash; registry rows whose directory is gone; and everything after the