docs: PRD rev1 re-review — repoint PRD heading anchors to GOV.4, complete archive line cites

Addresses CPS-PRD-REV1-REREVIEW findings on PR #1491 head 13968e9a: F1 (blocker; the CI test failure): docs/PRD.md is now the permanent shim, so heading-fragment links into the former PRD body no longer resolve — fleet-documentation.spec.ts failed on docs/fleet/README.md's FCM anchor. The Part II workstream contracts live in docs/PRDs/2026-08-31_PRD_rev1/GOV.4-workstream-contracts.md; all five anchored links in the tree are repointed there (fleet/README.md, TASKS.md, release-integrity/TASKS.md, ADMIN-GUIDE mos-connector-lease-operations.md, DEVELOPER-GUIDE mos-runtime-portability-m1.md). Each anchor verified against the GOV.4 headings with the spec's slug rule. Bundle content unchanged. F2 (minor): the rev0 archive README's ./ROADMAP.md row now cites all three source lines (18, 177, 249).
docs: PRD rev1 review Q90 — Prettier-format the bundle, add rev0 archive README
2026-09-02 10:15:21 -05:00 · 2026-09-02 09:40:46 -05:00 · 2026-09-01 18:32:14 -05:00
32 changed files with 3694 additions and 932 deletions
@@ -81,4 +81,4 @@ The page may be promoted to an operative runbook only after deny-all is intentio
 ## Related contract

 - [M1 logical identity and fencing decision](../../DEVELOPER-GUIDE/architecture/decisions/mos-runtime-portability-m1.md)
- [MOS-PORT requirements](../../PRD.md#mos-runtime-portability-workstream-mos-port)
+- [MOS-PORT requirements](../../PRDs/2026-08-31_PRD_rev1/GOV.4-workstream-contracts.md#mos-runtime-portability-workstream-mos-port)
@@ -98,4 +98,4 @@ A valid lease or grant is therefore not a claim of exactly-once delivery, produc
 ## Related contract

 - [M1 connector lease operations — held/non-operative](../../../ADMIN-GUIDE/operations/mos-connector-lease-operations.md)
- [MOS-PORT requirements](../../../PRD.md#mos-runtime-portability-workstream-mos-port)
+- [MOS-PORT requirements](../../../PRDs/2026-08-31_PRD_rev1/GOV.4-workstream-contracts.md#mos-runtime-portability-workstream-mos-port)
@@ -1,8 +1,10 @@
 ---
 kind: tracking
-status: active
+status: superseded
 ---

+> **Superseded (2026-09-01, PRD rev1 ratification).** This document's federated-tier-as-canonical-MVP-deployment-topology and Federation-v1-as-top-priority framing is historical. Federation M1–M3 are shipped but **frozen** (dormant since 2026-06-25, excluded from the v1 bar, security re-audit gate before any resumption); the canonical v1 deployment topology is the compose standalone tier (PRD rev1, D15). Authority: `docs/PRD.md` → `docs/PRDs/2026-08-31_PRD_rev1/` (decision D3 as amended, GOV.5 Q-T1). Tracking: `docs/fleet/NORTH_STAR.yaml` (dormant federation workstream). Content below is preserved verbatim as a record — do not edit it.
+
 # Mission Manifest — MVP

 > Top-level rollup tracking Mosaic Stack MVP execution.
@@ -1,910 +1,24 @@
 ---
-kind: spec
+kind: shim
 status: active
 source_of_truth: true
+current_rev: docs/PRDs/2026-08-31_PRD_rev1/
 ---

-# PRD: Mosaic Stack — North Star
-
-This document is the product source of truth for Mosaic Stack.
-
- **Part I** defines the product north star. It is written from the ratified
-  decision set D1–D14 (operator decision session, 2026-08-25; decision owner
-  Jason Woltje). Each section cites the decisions it implements.
- **Part II** preserves the active workstream contracts unchanged. Open issues
-  bind to them; this rewrite does not alter a single normative word in them.
- The previous v0.1.0 beta PRD body is archived verbatim at
-  [docs/archive/PRD-v0.1.md](./archive/PRD-v0.1.md) and is no longer authority.
- The delivery roadmap lives in [docs/ROADMAP.md](./ROADMAP.md). Per D11, every
-  planned phase appears there from day one, even as a placeholder.
-
-## Metadata
-
- **Owner / decision authority:** Jason Woltje
- **Status:** active (supersedes the v0.1.0 PRD as product authority)
- **Date:** 2026-08-26
- **Decision registry:** D1–D14, recorded in Part I §12
- **SSOT rule:** this repository's `docs/` tree is the product source of truth
-  (D5). Estate brains hold operational records, not product canon; only
-  product-relevant material migrates here (D6).
-
---
-
-## Part I — Product north star
-
-### 1. What Mosaic Stack is (D1)
-
-Mosaic Stack is an **open-source, AI-first platform for people who want a
-self-hosted environment for agentic management and a life operating system.**
-It serves personal, business, and employee needs from one deployment, and the
-work is offered freely.
-
-"AI-first" means agents are first-class operators of the system, not a bolted-on
-chat box: the platform exists to let humans direct fleets of agents over their
-projects, tasks, communications, and infrastructure, with the same tools and
-the same guarantees whether a human or an agent is acting.
-
-### 2. Who it is for (D1, D9)
-
-The operator of a deployment is its user. Mosaic Stack is **not a hosted
-business**: running the system as a service for external customers is outside
-the north star. Multi-tenancy exists WITHIN a deployment so that one operator
-can separate their world — for example, several LLCs plus a personal domain —
-while every deployment is self-hosted by its own operator.
-
-"Company" in the hierarchy is organizational separation for one operator's
-world, not a customer account.
-
-### 3. Deployment modes (D3)
-
-Two modes, chosen at install time:
-
-|                     | Standalone / personal                  | Enterprise                                            |
-| ------------------- | -------------------------------------- | ----------------------------------------------------- |
-| Brains              | one mosaic-brain (system + user files) | system brain for config + one brain per user          |
-| User-data isolation | single user                            | no user-data leakage between users; sharing is opt-in |
-| Secrets             | OpenBao/Vault or flat files            | OpenBao/Vault REQUIRED                                |
-| Conversion          | Standalone → Enterprise, **one-way**   | terminal state                                        |
-
-Brains are configurable as external git repositories (recommended, not
-required); git tracking is always on locally.
-
-**Federation** (connecting deployments: system-level config, assigned users,
-rights and data-access control, trusts with boundaries, exfiltration
-monitoring) is intentionally not fully designed. It is deferred, appears on the
-roadmap as a placeholder phase per D11, and nothing in v1 may foreclose it.
-
-### 4. Structure and tenancy (D2, D9, D13)
-
-The hierarchy:
-
-```
-company/organization  (N per deployment)
-└─ estate             (each in exactly one company)
-   └─ project         (each in exactly one estate)
-      └─ workspace    (project-specific; carries the Kanban)
-```
-
-Rules:
-
- Users can create N companies, N estates, N projects.
- Tasks bubble UP the hierarchy so whole-system status is visible at every
-  level. Bubble-up is **read-only aggregation**, never a cross-workspace write.
- Granular RBAC: admins restrict access per company, estate, and project;
-  grants are evaluated down the chain. Assets are transferable subject to the
-  structure.
- **`workspace_id` remains the hard mechanical isolation unit** exactly as
-  ratified in
-  [docs/requirements/native-kanban-sot.md](./requirements/native-kanban-sot.md)
-  (#751): PostgreSQL sole writable SOT, cross-workspace relationships rejected,
-  fail-closed mutations. The hierarchy is parent structure ABOVE workspaces,
-  used for RBAC evaluation and read-only roll-ups. The kanban SOT carries this
-  as Amendment A1, added by reviewed PR — an amendment, not a rewrite (D13).
-
-### 5. Identity (D10)
-
-Built-in auth (better-auth) is the **account system of record**. Authentik and
-other external IdPs federate in via OIDC as login methods; they never become
-the system of record. Perimeter shims (forward-auth in front of a web host) are
-deployment workarounds, not the design.
-
-### 6. Onboarding (D4)
-
-Onboarding is a **wizard that differs by mode, is re-runnable (no lock-in), and
-is extensible** — new wizards attach as tabs.
-
-Standalone flow captures: system and company name; component choices (Mosaic
-Comms/Matrix vs external; Mosaic SSO/Authentik vs external; Mosaic
-DB/PostgreSQL vs external; vector DB); the initial user
-(email/password/name/SSO); comms setup (Matrix/Discord/Slack); agent enrollment
-(harness choice and install, OAuth or API-key login, multi-account, model
-choice with recommendation, agent name and persona, account assignment,
-optional comms auto-enroll); a user onboarding profile (disabilities including
-ADHD/autism/PDA/vision, professional background, education, desired agent
-communication style, optional voice-matching interview, family/pets/friends/
-hobbies/likes-dislikes); email and drive connectors (Gmail/IMAP, Google
-Drive/OneDrive/Dropbox) with granular agentic-access consent; SSO/OIDC
-configuration; an initial estate, an initial project, and seeded example data.
-
-Enterprise uses the same skeleton with personal data optional; the focus moves
-to business structure, org chart, RBAC, M365 and external systems, immediate
-OIDC, SSO prominent.
-
-Profile answers feed `USER.md` and/or the user's data store subject to the
-custody rule in §7.
-
-### 7. Data custody (D6, D14)
-
- **Sensitive profile categories** (disabilities, family, communication style,
-  and similar) live in the **user's own brain ONLY**. PostgreSQL holds
-  structural data, consent records, and pointers — never the content. "User
-  data does not leak" is enforced by architecture, not policy (D14).
- Standalone (one user, one brain) **may** keep the same split — D14 makes it
-  optional in Standalone, not required. Keeping it is the recommended default
-  because it preserves forward-compatibility with the one-way Enterprise
-  conversion (D3).
- Estate brains hold operational records. Only product-relevant material
-  migrates into this repository's docs; operational records stay in their
-  brains and are linked (D6).
-
-### 8. Architecture gate — the webUI sits OVER official tooling (D8, D12)
-
-**HARD RULE:** every webUI operation goes through the Gateway API backed by the
-same official framework tooling the CLI uses. The CLI remains the primary
-execution method; the webUI uses the tools to operate and configure the
-system. The webUI never bypasses tooling to reach the database or filesystem
-directly.
-
-Consequence for planning: when a desired webUI operation has no backing tool,
-the gap is scored **"blocked on tooling"** and the tool is built first. The
-product baseline therefore always includes all three D8 inputs: the tool
-inventory (what exists and what is missing), the webUI→tool mapping, and the
-measured current state of the `next` branch.
-
-### 9. v1 slice (D11)
-
-v1 is deliberately small:
-
-1. **Standalone onboarding wizard** — system/company name, component choices,
-   initial user, initial estate + project, seeded examples, re-runnable.
-2. **Hierarchy core** — company → estate → project → workspace → kanban, with
-   read-only task bubble-up.
-3. **Basic RBAC** on the hierarchy.
-4. **Minimal agent enrollment** — one harness, API key, name/persona.
-
-Deferred beyond v1: connectors, comms integrations, voice-matching, M365,
-Enterprise conversion, federation. Every deferred item appears in
-[docs/ROADMAP.md](./ROADMAP.md) per the D11 rule: nothing exists only in heads.
-
-### 10. Relationship to the fleet north star
-
-[docs/fleet/NORTH_STAR.md](./fleet/NORTH_STAR.md) (generated from
-`docs/fleet/NORTH_STAR.yaml`) is the **delivery-fleet** north star: how the
-agent fleet that builds and operates the system should run (NS-1..NS-10,
-workstreams A–L). This PRD is the **product** north star. They are not
-competitors: the fleet north star is subordinate product-wise — its workstream
-J ("Web control plane") is one consumer of this PRD's D8/D12 gate — and this
-PRD does not redefine fleet invariants. The subordination rule is ratified in
-the frozen audit-input baseline (T2 operator freeze, 2026-08-25: "the PRD must
-cite and subordinate it, never fork it"). A change that would put the two in
-conflict must amend one of them explicitly, never fork a third document
-(drafting addition — see §12.1).
-
-### 11. Explicit non-goals
-
- Hosted/SaaS operation for external customers (D9).
- A webUI that writes to the database or filesystem around the tooling (D12).
- A second writable task store beside PostgreSQL (native-kanban-sot invariants).
- Fully-designed federation in v1 (D3 — roadmap placeholder only).
-
-### D15 — Tiered containerized deployment (2026-08-30, containerization lane)
-
-The stack ships a tiered deployment target, additive to the architecture
-gate (D8): (1) Standalone tier — docker compose is the canonical
-single-host deployment: postgres, valkey, openbao, gateway, appservice
-and the served webUI in one composition, with migrations, health checks,
-and a documented install/upgrade path; the registry (CI-published
-images) is the only deployment source. (2) Enterprise tier — Kubernetes
-manifests for the same service set, phase-gated on the standalone tier
-holding its acceptance bar. The v1 acceptance bar for the standalone
-tier: compose-up healthy; webUI hosts agent chat; an in-stack agent can
-open a PR to this repo; CI validates it; the running deployment adopts
-the merged change (pull + restart). Federation (D3 clause) remains
-deferred and unforeclosed. Implementation plan:
-docs/plans/2026-08-30_containerization.md.
-
-## 12. Decision registry
-
-| ID  | Decision (short form)                                                                                                                      |
-| --- | ------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------- |
-| D1  | Open-source, AI-first, self-hosted platform for agentic management + life OS                                                               |
-| D2  | Hierarchy company→estate→project→workspace→kanban; bubble-up; granular RBAC                                                                |
-| D3  | Standalone vs Enterprise; one-way conversion; per-user brains + Vault required in Enterprise; federation deferred                          |
-| D4  | Re-runnable, extensible, per-mode onboarding wizards                                                                                       |
-| D5  | North star = this rewrite of docs/PRD.md; stack docs/ = product SSOT                                                                       |
-| D6  | Only product-relevant material migrates from brains; operational records stay and link                                                     |
-| D7  | Spec-inventory sweep launched immediately (executed; INPUTS baseline frozen by operator ruling T2, 2026-08-25)                             |
-| D8  | webUI sits over official framework tooling; CLI primary                                                                                    |
-| D9  | Not a hosted business; company = organizational separation for one operator                                                                |
-| D10 | better-auth is the account system of record; external IdPs via OIDC                                                                        |
-| D11 | Small v1 slice; ALL phases on the documented roadmap from day one                                                                          |
-| D12 | HARD RULE: webUI never bypasses tooling; missing tool ⇒ build the tool first                                                               |
-| D13 | workspace_id stays the hard isolation unit; hierarchy is parent structure above; kanban SOT amended, not rewritten                         |
-| D14 | Sensitive profile data in the user's own brain only; postgres holds structure/consent/pointers                                             |
-| D15 | Tiered containerized deployment: compose standalone tier (five-point v1 bar) + phase-gated k8s enterprise tier; registry-only image source | 2026-08-30 containerization lane; plan docs/plans/2026-08-30_containerization.md |
-
-The full decision texts are recorded in the operator decision log (USC estate
-brain, webui-audit lane, `GRILL.md`).
-
-### 12.1 Drafting additions beyond D1–D14
-
-Independent review of this rewrite identified rules in this document that are
-not present in the D1–D14 record or the frozen T2 baseline. They are listed
-here so their ratification is explicit: approval of the PR that introduces
-this document, by the decision owner, ratifies them. If any is rejected it is
-removed, not silently kept.
-
-1. **Federation forward-compatibility gate:** "nothing in v1 may foreclose
-   federation" (§3), and scoping federation later requires its own PRD plus
-   threat model ([ROADMAP](./ROADMAP.md) P5). D3 defers federation; these
-   protective gates are additions.
-2. **North-star amendment rule:** a product/fleet north-star conflict must be
-   resolved by amending one of the two documents explicitly, never by forking
-   a third (§10). The subordination itself is T2-ratified; this amendment
-   procedure is an addition.
-
---
-
-## Part II — Active workstream contracts (preserved unchanged)
-
-The sections below are normative, in-flight workstream contracts carried over
-verbatim from the previous revision of this file. Open issues bind to them.
-This rewrite moved no text and changed no requirement in them; they are
-governed by their own issues and review gates, and they graduate out of this
-file individually when their workstreams close.
-
-## Current addendum: #1194 — Installed framework-tool drift detection
-
- Compare the framework tools shipped with the executing Mosaic package against the deployed `$MOSAIC_HOME/tools` tree by content hash.
- Treat every shipped `tools/**` file as framework-owned/required according to `framework-manifest.txt`, while excluding the explicit operator-owned credential carve-out and preserving installed-only operator/unknown files.
- Distinguish and count `IN_SYNC`, `STALE`, `NOT_INSTALLED`, and installed-only classifications; fail non-zero when shipped tools are stale or absent and refuse self-comparison that would make drift unobservable.
- Surface the observational check through `mosaic doctor`; do not refresh files, restart seats, or mutate live tooling.
- Document identity/messaging/gate behavior changes in the current stale set, the reviewed quiet-window keep-mode refresh command, and post-refresh probes against the installed path.
- Prove by construction that a stale and missing deployed tool are detected; that regression must fail before this checker exists.
-
-## Compaction Refresh Trust Lifecycle (M1, #827–#830)
-
-### Problem and objective
-
-Context compaction, session replacement, and same-PID runtime reloads can leave a previously VERIFIED runtime lease attached to stale directives. M1 must revoke that authority mechanically for Claude (including Claudex) and Pi without trusting caller-asserted identity or forking the external broker state machine.
-
-### Requirements
-
-1. `CR-REQ-01`: Claude `PreCompact` and `SessionStart` with matcher `compact`, plus Pi `session_before_compact` and the first post-`session_compact` `context`, SHALL independently revoke the active broker lease.
-2. `CR-REQ-02`: Runtime generation increases—including same-PID Pi reload/new/resume/fork and Claude resume/clear—SHALL monotonically replace the prior broker incarnation and inherit no VERIFIED lease.
-3. `CR-REQ-03`: A fired observer that cannot confirm broker revocation SHALL fail closed through lifecycle cancellation, a private local generation fence, and/or a runtime-local tool latch. The existing all-tools broker gate remains authoritative.
-4. `CR-REQ-04`: The lease TTL SHALL remain monotonic and capped at 300 seconds. If both observers are missed, within-TTL consequential actions remain allowed and after-TTL actions are denied. This named bounded residual stale window SHALL be documented without claiming a mutator-action bound inside the window.
-5. `CR-REQ-05`: Hook descendants SHALL use the broker-minted session and owner-only current-generation state inherited from register-before-exec. Caller-minted sessions and parallel lease state machines remain forbidden.
-
-### Acceptance criteria
-
-1. `AC-CR-01`: Real-socket tests prove each Claude observer revokes, Pi lifecycle tests prove both observer paths, and Claudex isolated settings preserve and install the mandatory hooks.
-2. `AC-CR-02`: A same-PID generation test proves the old generation is stale and the replacement generation is UNVERIFIED across reload/resume/fork-equivalent lifecycle events.
-3. `AC-CR-03`: RED-first T12b/T30 evidence explicitly reports dual-hook miss within TTL as **ALLOWED** and after TTL as **DENIED**.
-4. `AC-CR-04`: Attributable executable coverage is at least 85%, the full repository suite is green on deterministic main, and independent code/security review completes before merge.
-
---
-
-## Pi Persistent Goal Loop (#1150)
-
-### Problem and objective
-
-A Pi agent can stop after a plausible-looking answer even when the operator's broader objective is
-not complete, and ordinary compaction can weaken or omit the original objective. Mosaic needs an
-optional, operator-controlled goal loop that keeps a Pi session oriented, checks progress at native
-lifecycle boundaries, and resumes work until completion is verified or a bounded safety state is
-reached.
-
-The objective is a Mosaic-owned Pi extension deployed from the framework into
-`~/.config/mosaic/runtime/pi/`. It must not install into or depend on `~/.pi/agent/extensions/`.
-
-### Scope
-
-#### In scope
-
-1. `PGL-REQ-01`: The framework SHALL ship a dedicated Pi goal extension under
-   `packages/mosaic/framework/runtime/pi/`, seed it under `$MOSAIC_HOME/runtime/pi/`, and make
-   `mosaic pi` load it alongside the core Mosaic extension when present.
-2. `PGL-REQ-02`: `/goal` SHALL support setting a goal plus status, pause, resume, cancel, and help
-   operations without silently replacing an active goal.
-3. `PGL-REQ-03`: Active branch-specific goal state SHALL be persisted in Pi custom session entries,
-   restored on session start and tree navigation, and never rely on a compaction summary as its
-   source of truth.
-4. `PGL-REQ-04`: A hidden goal contract SHALL be injected through Pi's `context` event before every
-   model request so it remains effective across tool turns, retries, and post-compaction requests.
-5. `PGL-REQ-05`: The harness SHALL inspect every `turn_end` and successful `session_compact` event.
-   A structured terminating goal-report tool SHALL capture `continue`, evidence-bearing `achieved`,
-   or `blocked` status without requiring a redundant model turn.
-6. `PGL-REQ-06`: An achievement claim SHALL remain provisional until a second consecutive
-   evidence-bearing verification report. Any continuation report or successful compaction during
-   verification SHALL reset the verification sequence.
-7. `PGL-REQ-07`: Continuation SHALL be initiated at safe lifecycle boundaries, primarily
-   `agent_settled`; manual compaction and restored active sessions may schedule a deferred idle
-   continuation without re-entering compaction handlers.
-8. `PGL-REQ-08`: The loop SHALL have operator cancellation plus bounded turn and repeated-no-progress
-   limits. Exhausted or blocked goals pause rather than continuing indefinitely.
-9. `PGL-REQ-09`: Framework installation and update SHALL preserve normal manifest ownership: the
-   goal extension is framework-owned under `runtime/**`, while no goal extension or configuration
-   asset is created or modified under the operator's main Pi configuration. Pi remains the owner of
-   its native session files used by `appendEntry()`.
-
-#### Out of scope
-
-1. A mathematical guarantee that an arbitrary natural-language goal is semantically complete.
-2. Automatically executing user-supplied shell predicates or accepting executable validation code in
-   `/goal` arguments.
-3. Restarting Pi after process, host, or supervisor failure; the existing Mosaic fleet/runtime
-   supervisor owns process durability.
-4. Gateway, database, web UI, Discord, or cross-harness goal orchestration in this slice.
-
-### User and stakeholder requirements
-
- An operator can start a goal from Pi and see its current phase, evidence, limits, and latest report.
- The agent remains oriented after each turn and compaction until verified, paused, blocked,
-  exhausted, or cancelled.
- Local testing uses a file under `~/.config/mosaic/runtime/pi/`; the feature never writes an
-  extension asset to `~/.pi/agent/extensions/`.
- Framework updates deploy the same reviewed extension source through Mosaic's existing manifest
-  sync path.
-
-### Non-functional requirements
-
-1. **Safety:** bounded continuation, explicit cancellation, no arbitrary command execution, and no
-   completion without non-empty reported evidence.
-2. **Reliability:** serialized continuation scheduling, branch-aware restoration, compaction-safe
-   context injection, and stale-timer cancellation on session shutdown.
-3. **Performance:** no extra nested judge-model request on every turn; structured reporting uses the
-   active agent's final terminating tool call.
-4. **Observability:** Pi status/notifications expose phase and bounded counters without recording
-   credentials or hidden model reasoning.
-5. **Maintainability:** the state machine is deterministic and behavior-tested independently from Pi
-   provider/network access.
-
-### Acceptance criteria
-
-1. `AC-PGL-01`: A framework-sync fixture installs the extension at
-   `$MOSAIC_HOME/runtime/pi/goal-extension.ts`, and launcher tests prove both Mosaic Pi extensions are
-   emitted in deterministic order while absent optional files remain backward-compatible.
-2. `AC-PGL-02`: Command tests prove set/status/pause/resume/cancel behavior, active-goal replacement
-   refusal, and bounded input handling.
-3. `AC-PGL-03`: Lifecycle tests prove every turn is recorded, active context is injected on every
-   request, two evidence-bearing achievement reports are required, and `agent_settled` continues an
-   unmet goal without duplicate scheduling.
-4. `AC-PGL-04`: Compaction and restoration tests prove goal state survives, verification is reset and
-   rechecked after compaction, manual compaction continuation is deferred until idle, and tree/session
-   branch state is reconstructed correctly.
-5. `AC-PGL-05`: Limit tests prove max-turn and repeated-no-progress exhaustion stop autonomous
-   continuation, while pause/cancel/blocked states do not restart.
-6. `AC-PGL-06`: Focused tests, package typecheck/lint/test, repository quality gates, a local Pi load
-   smoke test from `~/.config/mosaic/runtime/pi/`, independent review, and terminal-green CI pass before
-   issue #1150 closes.
-
-### Constraints, risks, and assumptions
-
- Dependency: Pi's extension API must continue to provide `registerCommand`, `registerTool`,
-  `context`, `turn_end`, `agent_settled`, `session_compact`, session custom entries, and terminating
-  tool results.
- Risk: the working agent can overstate completion. Mitigation: structured evidence, a mandatory
-  second verification pass, explicit semantic limitations, and operator-visible reports.
- Risk: an impossible goal can consume unbounded resources. Mitigation: hard turn/no-progress bounds
-  and paused terminal states.
- Risk: automatic continuation can race compaction or session replacement. Mitigation: drive from
-  `agent_settled`, defer idle restarts, generation-check timers, and clear timers on shutdown.
- `ASSUMPTION:` Two consecutive evidence-bearing reports are the initial local verification policy;
-  rationale: it provides a real recheck without doubling every turn's model cost. Future policy may
-  add independent or deterministic validators.
- `ASSUMPTION:` Default limits are 40 turns and 6 repeated no-progress reports, configurable only by
-  bounded Mosaic environment settings; rationale: useful persistence with a finite autonomous budget.
- `ASSUMPTION:` Documentation remains canonical in-repo for this slice; no external docs publication
-  is requested.
-
-### Testing and delivery intent
-
-Use TDD for the deterministic controller and lifecycle invariants. Test with fake Pi lifecycle
-objects first, then run a local load/smoke test from the deployed Mosaic path. Deliver source, tests,
-launcher wiring, framework/runtime documentation, user/developer guides, and sitemap updates in one
-reviewed squash PR to `main` with terminal-green CI.
-
---
-
-## Fleet Declarative Configuration Management Workstream (FCM, #758)
-
-### Problem and objective
-
-The local Mosaic fleet has a roster, generated agent environment files, user-systemd units, tmux
-sessions, heartbeat files, examples, profiles, and separate gateway-backed agent records. These
-planes have drifted and are not one safe operator lifecycle. The objective is one **local fleet
-roster** as the desired-state SSOT, with generated environment, systemd, tmux, and heartbeat
-artifacts as rebuildable projections; it does not merge the local fleet control plane with the
-gateway-backed agent catalog.
-
-### Normative requirements
-
-| ID           | Requirement                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `FCM-REQ-01` | The roster SHALL be the sole writable desired-state source for local fleet membership, launch policy, and persisted lifecycle target. Generated environment files, systemd enablement, tmux sessions, and heartbeat state SHALL be non-authoritative projections.                                                                                                                                                                                                         |
-| `FCM-REQ-02` | The implementation SHALL provide one executable structural contract for YAML/JSON input and one shared semantic validator. Roster load, profile validation, provision, migration, and apply SHALL reuse the existing baseline-plus-`roles.local` profile/persona resolver; a parallel role resolver is forbidden.                                                                                                                                                         |
-| `FCM-REQ-03` | The local fleet CLI SHALL expose documented programmatic validate, show, plan, apply/reconcile, create, inspect, update, delete, start, stop, restart, status, verify, and doctor operations with stable JSON and exit-code behavior. Existing `fleet add/remove` compatibility aliases may remain during the stated deprecation window.                                                                                                                                  |
-| `FCM-REQ-04` | A fresh create SHALL persist `enabled:true` and `desired_state:stopped` unless an explicit persisted start is requested. The model SHALL distinguish enabled state, persisted desired state, and observed state. Migration, apply, reboot, and rollback SHALL not start an agent that was observed stopped before cutover.                                                                                                                                                |
-| `FCM-REQ-05` | The launch chain SHALL consume deterministic, digest-stamped generated input only. Optional local overrides SHALL be parsed as strict data, may not shadow authoritative generated keys, and may not contain arbitrary commands, credential values, channels, or unknown `MOSAIC_AGENT_*` keys. Forbidden legacy keys, including `MOSAIC_AGENT_COMMAND`, SHALL be privately quarantined before launch and reported only by key name and content hash.                     |
-| `FCM-REQ-06` | Mutations and apply SHALL validate before mutation, use an expected generation/lock, write projections atomically, produce a deterministic plan, and emit recovery information on partial failure. Reconciliation SHALL act only on local, enabled, roster-owned projections and SHALL not kill unmanaged tmux sessions by fuzzy name.                                                                                                                                    |
-| `FCM-REQ-07` | Canonical required classes are `code`, `review`, `validator`, `orchestrator`, `team-leader`, `enhancer`, and `interaction`. `validator` issues an independent final certificate but has no merge authority; `merge-gate` remains sole approve-to-land/merge authority. Team-leader capacity is bounded by an orchestrator-issued lease, and interaction is request/status only. Tess and Ultron are configurable instance/display names, not required machine identities. |
-| `FCM-REQ-08` | v1 migration SHALL be field-complete, reversible, and explicit about aliases, unresolved classes, lifecycle inference, generated-file regeneration, local override quarantine, schema-only remote/connector fields, and rollback. Every shipped example, profile, and service preset SHALL be migrated and executable, retained as an explicitly versioned v1 fixture, or retired with a replacement and deprecation note.                                                |
-| `FCM-REQ-09` | M1–M5 SHALL remain local tmux/systemd control-plane work. Remote/SSH reconciliation, connector mutation, secret references, arbitrary command/channel overrides, gateway/API convergence, and UI configuration storage are excluded and require a separate PRD/threat model.                                                                                                                                                                                              |
-| `FCM-REQ-10` | Documentation and examples are delivery gates. The M0 checklist at [docs/fleet/FLEET-CONFIG-DOCS-IA-CHECKLIST.md](./fleet/FLEET-CONFIG-DOCS-IA-CHECKLIST.md) and the baseline disposition inventory at [docs/fleet/LEGACY-EXAMPLE-PROFILE-DISPOSITION-INVENTORY.md](./fleet/LEGACY-EXAMPLE-PROFILE-DISPOSITION-INVENTORY.md) SHALL be maintained as acceptance evidence.                                                                                                  |
-
-### Acceptance criteria
-
-1. `AC-FCM-01`: A valid local v2 roster can be parsed from YAML or JSON, validated structurally and semantically through the shared resolver, and rendered canonically; invalid fields, duplicate names, unresolved classes, unsupported runtime/model combinations, socket ambiguity, and incompatible options fail closed.
-2. `AC-FCM-02`: `plan` reports deterministic desired-versus-observed differences for roster, generated environment, systemd enablement, tmux/session, heartbeat, installed-asset revision, and provable orphans without mutation; `apply --check` reports drift without mutation.
-3. `AC-FCM-03`: Local create/update/delete is generation-guarded, atomic, idempotent, and safe by default; it permits supported runtime/model/harness/effort/workdir/role changes without direct editing of generated environment files and does not start a newly created agent unless explicitly persisted.
-4. `AC-FCM-04`: The generated-env/local-override launch chain rejects generated-key shadowing, arbitrary command override, unknown keys, shell evaluation, and sensitive-value diagnostics before any agent starts; known-safe legacy input is regenerated or strictly relocated, and forbidden input is quarantined.
-5. `AC-FCM-05`: Local lifecycle reconciliation implements the persisted/transient start-stop rules, exact default/named tmux socket targeting, systemd/tmux status, stale generated state, unmanaged-session reporting, and rollback without surprise restarts or fuzzy destructive targeting.
-6. `AC-FCM-06`: A v1 roster migration previews field-by-field disposition, preserves observed stopped/running state, inventories rather than reconciles remote/schema-only entries, supports a canary and rollback, and classifies every shipped example, profile, and service preset according to the M0 inventory.
-7. `AC-FCM-07`: Required role authority is validated: validator certificate is consumed but does not merge, merge-gate is the sole merge authority, team-leader leases do not change roster/credentials/authority, and interaction/Tess cannot claim orchestration or merge powers.
-8. `AC-FCM-08`: Documentation, examples, migration, troubleshooting, operational recovery, package/update asset drift, schema/example/profile validation, independent code/security review, validator certificate, and terminal-green CI are complete before #758 closes.
-
-### M0 implementation gate
-
-No source, schema, role, example, profile, systemd, or live-fleet change is authorized before M0
-lands. M0 consists only of these normative requirements, the complete task DAG, the scoped
-documentation IA checklist, and the legacy example/profile disposition inventory. Subsequent cards
-are defined in [docs/TASKS.md](./TASKS.md) and must remain one card/one PR.
-
-### Fleet git identity launch propagation (#1043)
-
-#### Problem and objective
-
-A fleet seat can have a registered per-agent Git credential while its launched runtime process lacks
-`MOSAIC_GIT_IDENTITY`. The credential resolver then cannot select the seat identity reliably, which
-blocks repository operations on fail-closed estates and can fall through to an unrelated identity on
-estates where that refusal is not active. The objective is to make Git identity a deterministic,
-roster-derived part of the generated launch projection and prove it reaches the launched process.
-
-#### Normative requirements
-
-1. `FGI-REQ-01`: Every generated fleet agent projection SHALL declare
-   `MOSAIC_GIT_IDENTITY=<MOSAIC_AGENT_NAME>`; a differing or unsafe identity SHALL fail closed before
-   tmux launch.
-2. `FGI-REQ-02`: The clean `/usr/bin/env -i` pane boundary SHALL pass every variable declared by the
-   generated projection, including `MOSAIC_GIT_IDENTITY`, to the launched runtime process.
-3. `FGI-REQ-03`: A behavioral integration test SHALL set-compare the complete generated projection
-   against the launched process environment. Source-text/string-presence assertions are insufficient.
-4. `FGI-REQ-04`: Verification SHALL include RED-first evidence and a delete-the-subject mutation that
-   removes Git-identity pane propagation and makes the behavioral test fail.
-
-#### Acceptance criteria
-
-1. `AC-FGI-01`: A launched seat process contains every key/value pair declared by its generated
-   environment projection, including the roster-derived Git identity.
-2. `AC-FGI-02`: Missing, unsafe, or split Git identity is rejected before a tmux session is created.
-3. `AC-FGI-03`: Focused launcher and generated-environment tests, repository quality gates,
-   independent review, and the required RED/green/R7 evidence are recorded before push.
-
-### Framework shell assertion portability (#1098)
-
-#### Problem and objective
-
-The blocking framework-shell chain can report that a pane command omitted `/usr/bin/env -i` even when
-`-i` matched successfully. A short-circuiting `grep -q` under `set -o pipefail` may close its pipe after
-the match and cause an upstream producer to exit with SIGPIPE, turning a valid semantic result into a
-nonzero aggregate pipeline. The objective is to inspect the captured NUL-delimited argv directly and
-make failures carry the observed records needed for diagnosis.
-
-#### Normative requirements
-
-1. `FSP-REQ-01`: The pane-boundary test SHALL validate an adjacent `/usr/bin/env`, `-i` argv pair from
-   the authoritative NUL-delimited tmux capture without a short-circuit pipeline whose upstream status
-   can override a successful match.
-2. `FSP-REQ-02`: Missing, reversed, or non-adjacent boundary tokens SHALL fail, while valid boundaries
-   SHALL remain valid regardless of trailing argv size, pipe capacity, process scheduling, or host/CI
-   utility implementation.
-3. `FSP-REQ-03`: A failed boundary check SHALL print stable indexed, shell-escaped observed argv records
-   before exiting nonzero; the fixture SHALL continue to contain generated non-secret launch data only.
-4. `FSP-REQ-04`: Verification SHALL include RED-first large-payload evidence, negative token-order
-   controls, the complete focused launcher suite, canonical Woodpecker CI, and independent review.
-
-#### Acceptance criteria
-
-1. `AC-FSP-01`: A large captured argv with adjacent `/usr/bin/env`, `-i` passes even when the former
-   `grep -q` pipeline returns nonzero from an upstream SIGPIPE.
-2. `AC-FSP-02`: Missing executable, missing flag, and detached/reversed flag fixtures return nonzero and
-   emit the indexed observed argv.
-3. `AC-FSP-03`: The focused suite passes on the development host and CI image, and the merged-main
-   Woodpecker pipeline is terminal green before #1098 closes.
-
---
-
-## Exact Cross-Harness Fleet Communications Contract (#766)
-
-### Problem and objective
-
-Fleet runtime contracts currently combine exact peer rows with generic operational metavariables and
-independently parsed roster data. Non-Claude harnesses can mistake those metavariables for values to
-infer, producing incorrect host, session, socket, or helper targets. The objective is one
-roster-resolved communications contract that every supported harness receives unchanged.
-
-### Normative requirements
-
-1. `FCOM-REQ-01`: Fleet commands and runtime composition SHALL use one shared v1 roster structural
-   resolver. A second lenient communications parser is forbidden.
-2. `FCOM-REQ-02`: The composed contract SHALL render the local roster member's authoritative host,
-   exact agent/session name, resolved tmux socket, exact helper path, and deterministic communications
-   generation.
-3. `FCOM-REQ-03`: Every known peer SHALL have one exact executable command. Same-host commands SHALL
-   omit `-H`; cross-host commands SHALL use only that peer's explicit roster `ssh` target; the one
-   supported fleet-wide named socket SHALL use `-L` with its exact value. A per-agent socket declaration
-   must equal that fleet-wide value; unsupported independent sockets and missing cross-host SSH data SHALL
-   fail closed.
-4. `FCOM-REQ-04`: Operational fleet examples SHALL not contain unresolved host, session, socket, or
-   helper-path metavariables. Agents SHALL select an exact rendered peer row and SHALL NOT infer,
-   substitute, or fuzzy-match targeting values.
-5. `FCOM-REQ-05`: An unknown local member or requested peer SHALL fail closed with exact-name discovery
-   guidance. Runtime composition SHALL not silently omit a requested fleet member's communications
-   contract.
-6. `FCOM-REQ-06`: Claude Code, Codex, OpenCode, and Pi SHALL receive equivalent authoritative
-   communications data through the common runtime composer.
-7. `FCOM-REQ-07`: Tests SHALL prove the contract from framework-source `TOOLS.md`, through a fresh
-   installed `TOOLS.md`, to final runtime composition and helper executability. User-owned installed
-   `TOOLS.md` content SHALL remain preserved.
-8. `FCOM-REQ-08`: Stale installed or active composed context SHALL be reported with deterministic
-   generation/repair/relaunch guidance. Currency requires the expected source and installed contract
-   marker/version plus bounded byte equality. The supported current-version repair SHALL run independently
-   of package updates, preserve divergent `TOOLS.md` bytes in a digest-qualified no-clobber backup, restore
-   a regular executable helper without following symlinks, and be idempotent. Detection and reporting SHALL
-   NOT rewrite active context, restart a session, or mutate a live fleet.
-9. `FCOM-REQ-09`: The shared resolver SHALL preserve and strictly validate every schema-supported v1
-   connector kind (`tmux`, `discord`, and `matrix`) from YAML and JSON. Every accepted snake/camel alias
-   pair SHALL reject differing dual declarations and accept identical declarations. JSON roster fallback
-   SHALL occur only when `roster.yaml` is absent; all other YAML access failures SHALL fail closed.
-10. `FCOM-REQ-10`: The communications generation SHALL cover the complete canonical rendered semantic
-    contract, including identity, role/class, resolved host/socket/helper, peer metadata, and exact commands.
-    Installed helpers SHALL be validated with no-follow filesystem inspection as regular executable files.
-    Keep-mode reseed and relaunch discovery SHALL preserve and support both YAML and JSON rosters.
-
-### Acceptance criteria
-
-1. `AC-FCOM-01`: Contract fixtures contain no unresolved operational targeting metavariables; local
-   identity contains exact host/session/socket/helper values.
-2. `AC-FCOM-02`: Same-host, cross-host, named-socket, literal-default-socket, and missing-SSH tests prove
-   exact targeting and fail-closed behavior.
-3. `AC-FCOM-03`: Unknown identities and peers report known exact names plus an exact self-scoped
-   discovery command; no fuzzy session selection is emitted.
-4. `AC-FCOM-04`: Four-harness tests prove byte-equal authoritative communications sections.
-5. `AC-FCOM-05`: Source, fresh-install, preserved-custom-install, stale-installed, composed-generation,
-   helper executable, agent-send socket isolation, and exact-target tests pass.
-6. `AC-FCOM-06`: Documentation defines non-mutating stale-context detection and operator-authorized,
-   exact-agent relaunch; no implementation path performs automatic session mutation.
-7. `AC-FCOM-07`: YAML and JSON fixtures cover every connector kind; all snake/camel aliases cover
-   identical acceptance and conflicting rejection; non-`ENOENT` YAML failures do not fall back.
-8. `AC-FCOM-08`: Missing, directory, symlink, and non-executable installed helpers fail closed. Explicit
-   current-version repair proves partial-deletion recovery, digest-qualified backup collision safety,
-   symlink-target safety, and repeated-run idempotence.
-9. `AC-FCOM-09`: Markerless-equal and wrong-version source/installed contracts are stale, and a rendered
-   role/class change produces a different communications generation.
-
---
-
-## KBN-101 Database Runtime/Migration Role Split (#771)
-
-### Problem and objective
-
-PostgreSQL Gateway/storage currently uses one `DATABASE_URL` for runtime queries and migrations. That makes the deployed application identity an owner and prevents certification that KBN immutable event, artifact, checkpoint, and evidence relations reject runtime `UPDATE`/`DELETE`. KBN-101 freezes a least-privilege runtime/migration split before KBN-100 schema work.
-
-### Normative requirements
-
-1. `K101-REQ-01`: `DATABASE_URL` SHALL be the non-owner PostgreSQL runtime connection and `DATABASE_MIGRATION_URL` SHALL be the migration-only owner/migrator connection. They are required respectively for runtime and the dedicated `mosaic-db-migrator --run|--verify` phase in `standalone`/`federated`; local PGlite is the explicit exception. The published `@mosaicstack/db` bin maps exactly `mosaic-db-migrator` to `./dist/cli.js`, its image entrypoint is exactly `mosaic-db-migrator`, accepts no URL/SQL/schema/role argv, and returns stable sanitized exits. Every current/future PostgreSQL DDL entrypoint SHALL route to that runner or be denied, and SHALL reject `DATABASE_URL`-only execution before connection/DDL. Data migration may connect only after the runner prepares and verifies the PostgreSQL target, through dedicated non-DDL `mosaic_data_importer` and exactly `--target-url-file /run/secrets/mosaic-migrate-target-url`, its fixed paired authenticated provider-version file `/run/secrets/mosaic-migrate-target-version`, plus `--target-attestation-file /run/mosaic-attestations/migrate-target.v1.json`. KBN-101-05 obtains URL key `url` and version only from the same successful Vault KV-v2 response at `secret-{env}/mosaic-stack/database/importer` (`data.metadata.version`), renders them as one immutable generation into separate consumer copies, and never infers a provider version from DSN bytes. The trusted runner verifies TLS/identity/manifest, reads its fixed importer URL/version copies only for binding through safe no-follow fd checks, and signs a credential-free JCS/Ed25519 attestation using its runner-only fixed root-owned private-key file; no signing key reaches importer/runtime. The artifact binds secret version and SHA-256 of exact high-entropy credential-file bytes, canonical TLS host/port/database, CA/SPKI, PostgreSQL system identifier/database OID, importer role, manifest/schema fingerprints, producer invocation/build/image digest, issued/expires/nonce, and correlation. Before target connection the importer validates URL/version/attestation/public-key files, signature/key/expiry/replay/authenticated provider version/digest/generation/bindings and the importer-only CA at exact `DATABASE_TLS_CA_CERT_PATH`; after verified TLS and before DML it validates server/database/role/CA/schema identity, with same-fd/in-memory-byte TOCTOU protection, rotation/revocation, a privileged producer-only-to-importer-only artifact handoff controller that verifies/copies/fsyncs/atomically renames/seals before importer start, consumer isolation/no logging-oracle, and sanitized errors. Raw `--target-url`, `DATABASE_URL` fallback, runtime-owner use, missing/unsafe/substituted files, stale/replayed/tampered/wrong-key attestation, wrong binding, and DDL attempt fail before target connection/DDL; post-connect mismatch closes with zero DML/DDL. A reviewed finite classifier inventories executable current source/scripts/package bins, operator docs, deploy manifests, and exact normative contracts by path; active secure records pin both options/files, producer/key/bindings/tests, while normative contracts cannot mask instructions. Unknown active commands, duplicate-owner, ownerless, missing-path, and historical/status-only masking hits fail. `db:push` is forbidden outside an explicitly disposable local developer database and cannot accept a production-like URL.
-2. `K101-REQ-02`: Gateway runtime/replicas SHALL not execute migrations or DDL. The runner SHALL hold one `max:1` session and fixed two-int advisory namespace `1297044289` (`MOSA`), `1262636593` (`KBN1`) across preflight, reconciliation, migration, verification, and release. It SHALL compare the versioned canonical manifest v1 tuple (journal logical index/tag plus exact SQL-byte SHA-256) to the complete observed ledger mapping; count/set-only, timestamps, and physical insertion order are non-normative and insufficient.
-3. `K101-REQ-03`: PostgreSQL SHALL separate non-login platform database owner, non-login schema owner, dedicated `NOLOGIN SUPERUSER` `mosaic_extension_owner`, login migrator, dedicated login non-DDL data importer, non-login runtime capability, and login runtime roles. For PostgreSQL 17 + pgvector 0.8.2, `vector` is untrusted (`trusted` is absent and `relocatable=true`): only an externally controlled audited platform-bootstrap superuser session may `SET ROLE mosaic_extension_owner` for CREATE/UPDATE/SET SCHEMA, then `RESET ROLE`; the role has `rolcanlogin=false`, `rolsuper=true`, zero members, no runtime credential/Vault secret, and is never provided to app containers. It owns `mosaic_extensions`, fresh `vector`, and owner-bearing extension members, while `mosaic_schema_owner` receives only `USAGE` for type resolution and never ownership/`CREATE`/`ALTER`/`DROP`/member-change/default-privilege authority there. Superuser cannot be constrained by `GRANT`/`REVOKE`; this is identity/non-login/no-membership/external-control/audit isolation, not a false least-privilege claim. Extension operations require control-plane change, independent review, backup/rollback, maintenance window, and audit evidence. Managed targets that cannot establish this exact role are ineligible until an independently approved versioned provider-owned extension-owner profile exists; app/migrator ownership is never silently retained. Existing approved-owner extension relocation validates exact `pg_namespace.nspowner`, `pg_extension.extowner`, member ownership/schema/version, while legacy runtime-owned extension fails closed to a controlled shadow-database migration—never unsupported ownership alteration, catalog mutation, ownership adoption, or `DROP CASCADE`. Runtime, migrator, schema owner, importer, and all service roles must fail `SET ROLE`, catalog/direct `ALTER`/`UPDATE`/`DROP`/membership-change denial, role ownership, superuser/role-creation/schema-creation/TEMPORARY, unsafe membership, untrusted search path, missing grants, unauthenticated TLS, and immutable privilege drift checks. Application schema is fixed `mosaic` with exact `pg_catalog,mosaic` session path; historical public migrations remain byte-immutable legacy bootstrap only, every future Drizzle application declaration targets `mosaic`, and `vector` is explicitly qualified from non-writable `mosaic_extensions`. No config-derived SQL identifier is permitted.
-4. `K101-REQ-04`: `mosaicstack/stack` KBN-101-00 SHALL exclusively own `infra/pg-bootstrap/roles.sql`, `infra/pg-bootstrap/extensions.sql`, `infra/pg-bootstrap/README.md`, and bootstrap tests; KBN-101-05 SHALL exclusively own `tools/db/render-postgres-secrets.ts`, its tests, and current Compose/Portainer/two-gateway deployment declarations, consuming the versioned bootstrap interface without overlap. Environment IaC/Vault is named input and Mosaic deployment control plane/Jason is activation authority. Distinct runtime/migrator/importer URL, importer authenticated provider-version, DB-client CA, Gateway leaf, and PostgreSQL server key/certificate materials are provisioned before a production-like database starts. Importer and migrator have separate immutable URL/version copies at fixed `10002:10002`/`10003:10003` identities; runtime/unrelated containers receive neither importer material, attestation private key, or importer artifact. Runtime, migrator, and importer require their mounted CA plus `sslmode=verify-full`. Exact UID/GID/mode/rendering, service-DNS SANs, Vault/compose/Swarm consumer isolation, two-gateway pair ordering, server activation, pre-enforcement legacy-client drain and `hostssl` zero-plaintext-session proof, fresh/existing transition, CA-overlap rotation, TLS-only rollback, and standalone/federated/Swarm/two-gateway positive/negative TLS evidence are required. No application-generated production certificate or plaintext bootstrap exception is permitted.
-5. `K101-REQ-05`: KBN immutable relations SHALL permit the real runtime role INSERT/SELECT only and deny UPDATE/DELETE; parent retention remains RESTRICT/no-cascade. Role/password/Vault creation is external platform control, never application migration/source.
-6. `K101-REQ-06`: N-1 single-URL compatibility, rollout/rollback, Vault ownership/rotation/redaction, CI, installer, compose/Portainer, observability, and deployment handoffs SHALL be separately bounded one-card/one-PR work. Prepared slices remain inactive while current owner-runtime deployments stay N-1; Mosaic control plane/Jason alone authorizes one final atomic activation or rollback, with no force-on-red/bypass. KBN-101 planning itself SHALL not mutate production.
-7. `K101-REQ-07`: KBN-100 SHALL begin only after the KBN-101 foundation role/schema-boundary certificate; it SHALL rebase on that main head, restore generated Drizzle declaration/snapshot/journal consistency, and bound procedural immutable-table grant/trigger/backfill additions to its schema slice. KBN-101 real deployed-role immutable-operation certification SHALL complete after KBN-100 creates those relations and before KBN-105.
-
-### Acceptance criteria
-
-1. `AC-K101-01`: DTO/command-matrix tests prove required modes, PGlite exception, `mosaic-db-migrator --help|--run|--verify`/stable exits/argv refusal, public-import negative, every finite classified DDL/static-bypass inventory path and both harness pairs reject `DATABASE_URL`-only before connection/DDL, no migration-to-runtime fallback, and `db:push` refusal outside an allowlisted disposable DB. Before inventory, ownership, or status masking, the semantic fixture fails README's exact former commented code-fence generic-wrapper form and the user guide's exact former executable generic-wrapper form; source-consistency proves current `packages/storage/src/cli.ts` directly `execSync`s `pnpm --filter @mosaicstack/db db:migrate` and no `mosaic-db-migrator` bin exists, so runner-delegation documentation fails. The active `docs/guides/migrate-tier.md` route is inventoried to KBN-101-07 and proves runner-produced `--target-url-file /run/secrets/mosaic-migrate-target-url`, fixed paired provider-version file, and `--target-attestation-file /run/mosaic-attestations/migrate-target.v1.json`; runner-only signing/private-key isolation; Vault KV-v2 same-response version provenance, separate immutable generation mounts, importer CA, JCS/Ed25519 signature/key rotation/revocation, atomic artifact, expiry/replay, safe-fd secret-version/digest, canonical TLS/CA/server/database/role/manifest/schema bindings, dedicated non-DDL importer, consumer isolation/no log-oracle, and exact no-connection versus zero-DML rejection for missing/wrong/stale/replayed/tampered/wrong-key/substituted/generation-mismatched inputs. The full current non-normative docs inventory—including user guide, federation historical task/MILESTONES status, and non-operative SETUP—has an exact safe disposition. Scanner semantic checks reject automatic first-boot/startup extension/schema/migration wording, Compose-up-before-runner, init-script authority, production `.env`/monorepo auto-load/`EnvironmentFile=`/credential-export-or-argv/restart-as-secret-activation routes, and every unqualified operator-document `mosaic-db-migrator --run|--verify` hit regardless of named/normative/status classification. The exact former README/dev/deployment Compose-first sequences, former SETUP wording, exact former MILESTONES wording `pgvector extension installed + verified on startup`, former architecture-plan/PERFORMANCE/backlog runner routes, and any unqualified runner fixture fail before inventory masking. Only one `Held future procedure` Markdown section—bounded through the next equal-or-higher heading—may contain the explicit non-operative/no-current-command-authority form that names KBN-101-00/-03/-05 and preserves external bootstrap → TLS/roles → `mosaic-db-migrator --run` → `mosaic-db-migrator --verify` → Gateway/Compose readiness; every runner hit outside that section fails. The README assertion for the checked-in direct CI `pnpm --filter @mosaicstack/db run db:migrate` with `DATABASE_URL` passes only as active legacy N-1, uncertified, non-authorizing-as-an-operator-route status against an isolated disposable CI database pending KBN-101-06 removal—not as an ordinary operator or approved DDL-authority route. Only local PGlite data-layer work or non-PostgreSQL Compose is current (Gateway/Web local startup is held pending daemon/inherited/project-DSN rejection).
-2. `AC-K101-02`: Fixed namespace lock contention/crash/readiness/non-interference and exact manifest-v1 reconciliation tests prove no replica race/runtime auto-migration and fail closed on every missing/unknown/duplicate/ambiguous/corrupt/stale ledger state.
-3. `AC-K101-03`: Actual PostgreSQL 17 + pgvector 0.8.2 control-file, catalog, Drizzle-generation, vector-query/operator, fresh/approved-owner/legacy-shadow/partial/resume/rollback/N-1, and real deployed-role tests prove `trusted` absent/untrusted plus relocatability, external-superuser `SET ROLE` create/update/`RESET ROLE` audit, exact `rolcanlogin=false`/`rolsuper=true`/zero-membership/no-runtime-secret state, platform/schema/extension-owner/migrator/importer/runtime separation, `pg_extension.extowner` plus owner-bearing extension-member/schema/version assertions, and runtime/migrator/schema-owner/importer/all-service-role `SET ROLE`/ALTER/DROP/member-update denial. They also prove `pg_catalog,mosaic` per-session pool safety, `mosaic_extensions` qualification, identifier injection denial, ownership/membership/ledger-read/TEMP/default grants, and unsafe privilege denial.
-4. `AC-K101-04`: Disposable standalone, federated/Swarm, and two-gateway verified-TLS positives plus for both pairs missing CA/wrong CA/wrong SAN/sslmode downgrade, server/Gateway key mode, UID/GID, secret-consumer isolation, and legacy-drain/`hostssl` negatives prove server bootstrap, ordering, and readiness; PGlite is expressly excluded from this PostgreSQL evidence.
-5. `AC-K101-05`: Real runtime-role evidence proves INSERT/SELECT succeeds and UPDATE/DELETE fails for every frozen immutable KBN relation.
-6. `AC-K101-06`: N-1/atomic activation/rollback, Vault/CA-overlap rotation/redaction, health/operator behavior, CI/deployment handoff, independent exact-head security review, and terminal-green CI evidence the foundation before KBN-100; after KBN-100, the real deployed-role immutable-operation certificate and Ultron approval release KBN-105.
-
-**Normative implementation contract:** [`docs/native-kanban-sot/KBN-101-DB-ROLE-SPLIT.md`](./native-kanban-sot/KBN-101-DB-ROLE-SPLIT.md). `ASSUMPTION:` existing `standalone` and `federated` are all PostgreSQL production-like modes; any new PostgreSQL tier inherits these requirements until an explicit versioned amendment.
-
---
-
-## Tess Interaction Agent Workstream (TESS)
-
-### Problem and Objective
-
-Jason needs one durable, operator-facing Mosaic agent outside Hermes that is reachable through a dedicated Discord channel and CLI, can attach to and operate the Mosaic fleet and transitional Hermes agents, and preserves context across restarts and compaction. Mos remains the coding/general fleet orchestrator; Tess is the complementary human interaction, visibility, control, and migration agent.
-
-The objective is to ship **Tess** (from _tessera_, a piece of a mosaic) as a Pi-native, GPT-5.6 Sol agent with high reasoning. Tess must use Mosaic-owned contracts and plugins so Hermes can be replaced incrementally rather than becoming a permanent architectural dependency.
-
-### Scope
-
-#### In Scope
-
-1. `TESS-ARP-001`: A runtime-neutral `AgentRuntimeProvider` contract supporting `listSessions`, `streamSession`, `sendMessage`, `terminate`, `getSessionTree`, `attach`, health, capability discovery, and normalized events/errors.
-2. `TESS-PI-001`: A long-running Pi-native Tess agent profile/service pinned to GPT-5.6 Sol with high reasoning, explicit tool policy, lifecycle hooks, durable checkpoints, and restart recovery.
-3. `TESS-DSC-001`: Dedicated Discord channel binding to Tess through the Mosaic gateway, with allowlists/RBAC, thread/reply policy, streaming, attachments, approvals, and correlation IDs.
-4. `TESS-CLI-001`: `mosaic tess` CLI commands for chat, status, session listing, attach/detach, send/steer/stop, provider health, and recovery.
-5. `TESS-FLT-001`: Fleet plugin capabilities for roster/status/heartbeat inspection, message delivery, session hierarchy, safe attach, and controlled restart/recovery.
-6. `TESS-MOS-001`: Explicit Mos coordination boundary and tools: hand off orchestration requests, observe mission/task state, receive results, and never silently compete for orchestration authority.
-7. `TESS-HRM-001`: Transitional Hermes adapter for profiles/agents, sessions, streaming/messages, Kanban, skills, memory, tools, cron, and health, using capability negotiation and fail-closed unsupported operations.
-8. `TESS-MEM-001`: Unified memory/retrieval plugin with scoped search/recent/capture/stats, startup context injection, provenance, redaction, namespace isolation, and flat-file/project truth precedence.
-9. `TESS-STA-001`: Durable agent state, inbox, handoff, compaction-recovery, and resume reconstruction.
-10. `TESS-PLG-001`: Plugin/tool catalog covering runtime bootstrap, repository/PR workflow, fleet diagnostics, incident-safe read operations, Discord interaction, and extensible MCP/skill discovery.
-11. `TESS-TRN-001`: Replaceable transport providers: tmux/fleet now, Matrix/native Mosaic transport later, with no Discord/CLI business logic coupled to transport details.
-12. `TESS-SEC-001`: RBAC, per-operation authorization, explicit approval for destructive/privileged/customer-visible actions, audit events, secret/PII redaction, tenant isolation, and bounded command execution.
-13. `TESS-SEC-002`: Command execution SHALL enforce declared scope/role server-side; admin/system and destructive operations SHALL require policy-bound durable approval.
-14. `TESS-SEC-003`: Every session list/read/attach/send/terminate operation SHALL enforce server-derived owner and tenant scope; guessed or client-supplied IDs SHALL grant no authority.
-15. `TESS-SEC-004`: MCP tools SHALL derive actor/tenant from authenticated context and SHALL NOT accept caller-controlled identity fields.
-16. `TESS-SEC-005`: Discord plugin ingress SHALL authenticate service identity, enforce guild/channel/user allowlists, propagate correlation/message IDs, and reject replay.
-17. `TESS-SEC-006`: Secret/PII classification and redaction SHALL occur before persistence and before channel egress, including tool metadata and authentication flows.
-18. `TESS-SEC-007`: Approvals SHALL be one-time, expiring, actor/tenant-bound, and cryptographically bound to the exact structured action digest.
-19. `TESS-SEC-008`: Ingress, provider sends, tool side effects, and responses SHALL use durable inbox/outbox/checkpoints and idempotency records for restart-safe replay.
-20. `TESS-SEC-009`: Garbage collection and retention SHALL be session/tenant scoped unless executed as a separately authorized and audited system-wide job.
-21. `TESS-OBS-001`: Structured logs, traces, health/readiness, provider latency/errors, session lifecycle, tool audit, and actionable recovery diagnostics.
-22. `TESS-MIG-001`: Capability inventory and staged Hermes-to-Mosaic migration matrix with coexistence, cutover, rollback, and deprecation gates.
-
-#### Out of Scope
-
-1. Replacing Mos as coding/general fleet orchestrator.
-2. Making Hermes the Mosaic core or coupling Mosaic domain logic to Hermes schemas.
-3. Migrating every historical chat verbatim; only policy-compliant indexed summaries and user-selected sessions are migrated.
-4. Unrestricted shell execution from Discord.
-5. Full web UI parity in the first Tess operational milestone; gateway contracts must remain web-consumable.
-6. Replacing tmux before Matrix/native transport reaches operational parity.
-
-### Stakeholder and User Requirements
-
- Jason must be able to converse with the same Tess session from Discord and CLI.
- Jason must be able to see what is running, stale, blocked, or unhealthy without attaching manually to every session.
- Jason must be able to attach to Tess and authorized fleet sessions through supported CLI controls.
- Tess must collaborate with Mos and the fleet while preserving a single clear orchestration authority.
- The system must migrate useful Hermes/OpenClaw capabilities intentionally, with evidence, instead of copying implementations wholesale.
-
-### Non-Functional Requirements
-
-1. **Security:** default-deny provider/tool capabilities, least privilege, no secrets in logs/prompts/commits, Discord user/channel authorization, and auditable approvals.
-2. **Reliability:** durable inbox/checkpoints; idempotent message handling; reconnect with bounded backoff; no message loss or duplicate execution across gateway restart.
-3. **Performance:** first acknowledgement within 2 seconds when connected; streamed agent output begins within 5 seconds excluding model/provider delay; status reads return within 2 seconds under nominal local conditions.
-4. **Observability:** every ingress message and resulting provider/tool operation carries a correlation ID across Discord, gateway, Tess, provider, and audit events.
-5. **Maintainability:** channel, runtime, transport, memory, and external-agent integrations remain adapter-based with contract tests.
-6. **Privacy:** only scoped context enters external runtimes; persisted messages/memories follow retention and redaction policy.
-7. **Portability:** Tess runs through Pi/Mosaic contracts and does not require Hermes to start or serve native Mosaic operations.
-
-### Acceptance Criteria
-
-1. `AC-TESS-01`: A dedicated Discord channel and `mosaic tess chat` connect to one durable Tess session and stream responses bidirectionally.
-2. `AC-TESS-02`: `mosaic tess status|sessions|tree|attach|send|stop` operate against authorized provider capabilities with stable typed outputs and actionable errors.
-3. `AC-TESS-03`: Tess runs GPT-5.6 Sol at high reasoning and its effective runtime/model/tool policy is visible through status without exposing credentials.
-4. `AC-TESS-04`: Tess can inspect and message the Mosaic fleet, hand orchestration work to Mos, and demonstrate that Tess does not independently claim Mos-owned orchestration work.
-5. `AC-TESS-05`: Hermes adapter demonstrates session listing, streaming/message delivery, hierarchy mapping, and at least one approved capability in each of Kanban, skills, memory, tools, and cron—or reports unsupported capabilities fail-closed.
-6. `AC-TESS-06`: Restart/compaction test preserves session identity, pending inbox, last durable checkpoint, and a resumable handoff without duplicate side effects.
-7. `AC-TESS-07`: Unauthorized Discord users/channels, cross-tenant access, unsafe tool calls, forged approvals, and sensitive-output cases are denied and audited.
-8. `AC-TESS-08`: tmux/fleet and Matrix/native transport implementations pass the same provider contract suite; Matrix may remain non-default until readiness gates pass.
-9. `AC-TESS-09`: Baseline quality gates, unit/integration/contract tests, Discord+CLI E2E, restart/recovery tests, independent code review, and security review are green.
-10. `AC-TESS-10`: Migration matrix documents every audited Hermes/OpenClaw capability as native, adapted, deferred, or rejected, with cutover and rollback evidence.
-11. `AC-TESS-11`: User, admin, developer, API/OpenAPI, operations/recovery, and plugin-authoring documentation is current and linked from the sitemap.
-
-### Constraints, Dependencies, Risks, and Assumptions
-
- Dependency: Mosaic gateway remains the single API surface; Pi is the native runtime; Valkey/PostgreSQL provide canonical durable state where required.
- Dependency: Discord bot credentials and dedicated channel ID are deployment secrets provisioned outside source control.
- Risk: Tess could drift into a second orchestrator. Mitigation: explicit role policy, Mos handoff contract, authority checks, and E2E boundary tests.
- Risk: broad Hermes compatibility can freeze legacy semantics into Mosaic. Mitigation: Mosaic-owned normalized contracts and capability negotiation.
- Risk: Discord creates a privileged remote-control surface. Mitigation: pairing/allowlists, RBAC, approvals, rate limits, audit, and safe tool classes.
- Risk: transcript ingestion can violate privacy or overload memory. Mitigation: scoped opt-in import, redacted summaries, provenance, retention, and deduplication.
- Risk: current root filesystem has limited headroom. Mitigation: isolated worktrees, no duplicated dependency installation unless required, and cleanup only after active-lane verification.
- `ASSUMPTION:` The public name is **Tess**, because the user requested a name and the tessera/Mosaic relationship is distinctive; config must permit later display-name changes without renaming APIs or storage keys.
- `ASSUMPTION:` The dedicated Discord channel ID and final guild policy will be supplied/provisioned during deployment, so implementation uses explicit configuration and fail-fast startup validation.
- `ASSUMPTION:` tmux/fleet is the production transport for the first operational milestone; Matrix/native transport is implemented behind the same contract and promoted only after parity/reliability verification.
- `ASSUMPTION:` Project/task truth remains in canonical Mosaic/project stores; semantic memory systems are retrieval/mirror layers, not hidden authorities.
-
-### Testing and Delivery Intent
-
-Delivery uses five gated milestones: runtime contracts/security; Pi service/state; Discord/CLI; fleet/Hermes/plugin suite; migration/Matrix/recovery/qualification. Every source-code task requires tests, independent review, a PR to `main`, terminal-green CI, and issue/task closure. Production activation additionally requires a clean-host Pi launch, dedicated Discord channel smoke test, CLI attach test, restart/recovery drill, and rollback procedure.
-
---
-
-## Official Channel Plugin Workstream (#756)
-
-### Problem and Objective
-
-The Discord plugin currently couples Discord event handling, gateway bridging, and reply routing in one implementation and activates only on mentions. Mosaic needs an official channel adapter that behaves the same no matter whether the bound logical agent currently runs through Claude, Codex, Pi, OpenCode, or a future harness. The Discord connection and conversation address must remain stable while the gateway changes the runtime provider behind that logical session.
-
-The objective is to make Discord the first implementation of a transport-neutral official channel contract, with explicit authorization and deterministic channel/thread routing that future Matrix, Slack, and other adapters can share.
-
-### Scope
-
-#### In Scope
-
-1. `CHN-001`: Transport-neutral channel adapter, route, message, attachment, authorization-principal, response-target, and health contracts in `@mosaicstack/types`, including trusted per-binding logical-agent configuration selection.
-2. `CHN-002`: Stable channel conversation addresses based on logical agent plus channel/thread identity; harness, model, and runtime-provider IDs are forbidden from channel session keys.
-3. `DSC-001`: An authorized untagged message in a configured agent-bound channel routes to the agent and receives its response in that channel.
-4. `DSC-002`: A bot mention in a configured parent channel creates a Discord thread, or reuses the thread already attached to that same native message; the mentioned turn and subsequent thread turns route and respond in that thread.
-5. `DSC-003`: A message already inside an authorized thread inherits authorization from its configured parent and never attempts a nested thread.
-6. `DSC-004`: Guild, parent channel, user, pairing, and role authorization remains default-deny before thread creation or gateway dispatch.
-7. `DSC-005`: Discord service authentication, HMAC envelope integrity, replay protection, attachments, approvals, response chunking, and correlation behavior remain intact.
-8. `DSC-006`: The Discord adapter exposes lifecycle and health behavior through the shared channel contract without importing a harness SDK.
-
-#### Out of Scope
-
-1. The logical-agent lease, fencing epoch, execution grant, checkpoint, or cross-harness takeover implementation tracked by #754/#755.
-2. Dynamic Discord authorization administration in the web UI.
-3. Multi-guild tenant isolation, DMs, slash commands, voice, reactions, or production bot deployment.
-4. Implementing Matrix or Slack adapters in this slice.
-
-### Non-Functional Requirements
-
-1. **Security:** no thread or dispatch side effect occurs until guild, parent channel, user, pairing, role, and bounded per-user/channel rate checks pass; attachment metadata is shape- and size-bounded; credentials never enter source, messages, session keys, or logs.
-2. **Portability:** channel contracts and stable conversation IDs contain no Claude, Codex, Pi, OpenCode, model, process, or provider-specific field; each configuration-owned binding selects its trusted logical agent without changing the channel identity.
-3. **Reliability:** repeated messages for one channel/thread resolve the same conversation handle; reconnecting the adapter does not require a harness-specific rebinding.
-4. **Maintainability:** Discord-specific API translation stays in the Discord package; gateway and future adapters depend on transport-neutral contracts.
-5. **Observability:** thread creation or routing failure is reported without message content or credential material.
-
-### Acceptance Criteria
-
-1. `AC-CHN-01`: Contract and behavior tests prove the plugin route contains only logical agent plus channel/thread identity and produces the same stable conversation handle regardless of underlying harness selection.
-2. `AC-CHN-02`: A mentioned authorized parent-channel message creates a thread (or reuses its already-attached thread), dispatches to the thread conversation, and targets the response to that thread.
-3. `AC-CHN-03`: An untagged authorized parent-channel message dispatches to the parent conversation and targets the response to the parent channel.
-4. `AC-CHN-04`: Untagged follow-ups inside an authorized thread dispatch and respond in that same thread without creating a nested thread.
-5. `AC-CHN-05`: Unauthorized guilds, channels, users, unpaired users, insufficient roles, and rate-limited senders produce no thread and no gateway dispatch.
-6. `AC-CHN-06`: Shared channel contracts are exported from `@mosaicstack/types`, Discord implements the lifecycle/health seam, and no harness SDK is imported by the plugin.
-7. `AC-CHN-07`: Focused routing/auth tests, package tests, typecheck, lint, formatting, coverage, independent code/security review, and terminal-green CI pass.
-
-### Constraints, Risks, and Assumptions
-
- Dependency: Mosaic gateway remains the policy, durable-session, audit, and runtime-provider boundary.
- Constraint: This work must not modify orchestrator-to-Pi migration or #754/#755 lease/fencing files.
- Risk: accepting untagged messages could create noisy or unintended agent input. Mitigation: only explicitly configured channels and paired, role-authorized users are accepted, with bounded per-user/channel message and thread rates.
- Risk: Discord thread creation can fail because of channel permissions, archived state, or API rate limits. Mitigation: fail without dispatching a turn whose response destination cannot be honored, and emit sanitized diagnostics.
- `ASSUMPTION:` Configured channels are dedicated agent interaction surfaces, so authorized untagged human messages are intentional agent input.
- `ASSUMPTION:` Mention in a parent channel selects a public thread; messages already in a thread remain there because Discord has no nested threads.
- `ASSUMPTION:` One Discord bot may serve multiple configuration-owned logical-agent bindings.
- `ASSUMPTION:` Static allowlists and paired-user roles are the authorization administration surface for this slice.
-
-### Testing and Delivery Intent
-
-Use TDD for remote-ingress routing and permission boundaries. Required evidence includes parent-channel mention, untagged parent message, existing-thread follow-up, existing-thread mention, thread reuse, unauthorized side-effect denial, stable harness-neutral conversation identity, adapter health, and regression coverage for signed envelopes and approvals. Deliver through issue #756, a reviewed squash PR to `main`, terminal-green CI, and issue closure.
-
---
-
-## Mos Runtime Portability Workstream (MOS-PORT)
-
-### Problem and Objective
-
-Mos is currently identified partly by a harness-native session and communication process. Replacement/rebinding exists, but no gateway-enforced logical identity or fencing prevents a stale harness from continuing to reply or execute effects after takeover.
-
-The objective is to make Mos a server-derived logical Mosaic identity whose authority can move safely among runtime connectors. The gateway owns identity, lease, policy, and audit; harnesses remain replaceable adapters.
-
-### M1 Requirements
-
-1. `MOS-PORT-ID-001`: Define a normalized logical-agent identity independent of Claude Code, Pi, Codex, tmux, Matrix, and provider-native session IDs.
-2. `MOS-PORT-LEASE-001`: Persist one exclusive connector lease per tenant/logical-agent/binding with CAS acquisition, monotonic fencing epoch, TTL, heartbeat, explicit release, and takeover.
-3. `MOS-PORT-FENCE-001`: Bind every connector dispatch/execution grant to the current server-derived tenant, logical identity, binding, connector, scopes, expiry, and lease epoch.
-4. `MOS-PORT-FENCE-002`: Reject and audit stale, expired, forged, cross-tenant, cross-binding, and unauthorized grants before connector, channel, provider, or tool side effects.
-5. `MOS-PORT-OBS-001`: Emit credential-safe correlation/audit events for lease acquire, renew, takeover, reject, release, and expiry.
-6. `MOS-PORT-ARCH-001`: Runtime/provider adapters consume normalized lease context without adding harness-native schemas to Mosaic core.
-
-### M1 Acceptance Criteria
-
-1. `AC-MOS-PORT-01`: Two contenders for one binding cannot simultaneously hold current authority under concurrency.
-2. `AC-MOS-PORT-02`: Successful takeover increments the fencing epoch and every operation from the old epoch fails closed before side effects.
-3. `AC-MOS-PORT-03`: Gateway/database restart preserves lease and epoch state; expired leases can be recovered only through the authorized takeover path.
-4. `AC-MOS-PORT-04`: Cross-tenant, cross-agent, cross-binding, forged, and expired lease/grant cases are denied and audited.
-5. `AC-MOS-PORT-05`: Unit, migration, repository close/reopen, concurrency, abuse, gateway integration, independent security review, CI, and documentation gates pass.
-
-### Deferred to Later #754 Milestones
-
-Canonical checkpoint/handoff payloads, exactly-once connector receipts, concrete Claude/Pi/Codex adapters, channel cutover, and full cross-harness failover/rollback E2E are explicitly out of M1 scope.
-
---
-
-## Workspace placement guard hardening (#1174)
-
-### Problem and objective
-
-The Bash pre-tool guard must prevent Git checkouts and repository state from being placed under
-`$HOME` without refusing ordinary Git commands merely because a source, option value, branch name,
-or metadata mentions `$HOME`. A guard that over-blocks routine work is unsafe because operators
-will route around it.
-
-### Scope and requirements
-
-1. `WPG-REQ-01`: `git clone` and `git worktree add` placement SHALL be judged from their placement
-   operands, not from every HOME-shaped word in the command.
-2. `WPG-REQ-02`: Clone sources, references, templates, environment assignments, and non-placement
-   worktree metadata MAY resolve under HOME when all placement operands resolve elsewhere.
-3. `WPG-REQ-03`: Both attached and separate-value `--separate-git-dir` forms SHALL remain placement
-   operands and SHALL be refused when they resolve under HOME.
-4. `WPG-REQ-04`: Option classification SHALL account for Git's rule-generated boolean negations
-   without relying on an enumerable allowlist of flag spellings.
-5. `WPG-REQ-05`: Quote removal, escapes, shell command boundaries, redirections, and end-of-options
-   handling SHALL preserve existing fail-closed checkout coverage.
-6. `WPG-REQ-06`: Absolute placement aliases SHALL resolve shell-known HOME spellings, dot segments,
-   repeated separators, and existing symlink parents before the HOME boundary comparison.
-7. Relative targets whose effective path depends on the shell cwd are out of scope and tracked by
-   #1197.
-
-### Acceptance and verification
-
-1. Git's own option parser accepts each tested flag, including generated `--no-*` forms, while the
-   guard allows a HOME-valued source with an explicit safe destination.
-2. Equivalent clone and worktree fixtures cover rule-generated negations and remain discriminating
-   against the prior head where the defect existed.
-3. Real HOME destinations and both `--separate-git-dir` forms remain blocked, including placements
-   after shell command boundaries.
-4. The full hermetic guard suite, syntax/static checks, adversarial probes, independent review, and
-   terminal-green CI pass before merge.
-5. Any option-classification residual is documented with its deliberate failure direction.
-
-### Constraints, risks, and assumptions
-
- Security and usability are co-equal: neither a placement bypass nor routine over-block is an
-  acceptable repair.
- `ASSUMPTION:` The value-taking option surface exposed by the installed Git version is closed and
-  measurable through Git's own parser/help output; rationale: boolean flags are rule-generated,
-  while separate-value options have explicit grammar and must be classified as such.
- Risk: a future Git release may add a new value-taking placement option. Mitigation: document the
-  chosen residual direction and pin every currently supported placement option in behavior tests.
- Risk: a symlink can be replaced after pre-execution canonicalization. Mitigation: resolve every
-  existing parent physically and document the remaining inherent TOCTOU window; the worktree helper
-  remains the authoritative path-derivation mechanism, with atomic closure tracked by #1199.
-
---
-
-## Release Integrity Workstream (RI, #1275)
-
-### Problem and objective
-
-At `next` 476db12b (review of 2026-08-17), publication from `next` is not bound to the full verification pipeline for the same commit: the publish pipeline's publish steps depend on `build` only, while ordinary push CI excludes `next`. Public Forge/MACP paths contain false-success placeholders: a stub executor that reports `completed` with exit zero, planning/remediation gates that execute literal `true`, a review gate that echoes an approving verdict, and a gate runner that treats empty commands and unimplemented CI-provider gates as passing. Shipping UI surfaces can render a failed fetch as an empty, healthy collection.
-
-Objective: for alpha 0.0.50, the release cannot publish, report, or display work state that the repository has not actually verified. Decisions SDLC-D-033 through SDLC-D-038 (Jason, 2026-08-17) scope this floor; full decision text and required-behavior lists live in jarvis-brain `docs/plans/2026-08-16_mosaic-stack-sdlc-protocol.md` and `data/decisions/mosaic-stack-sdlc-protocol.json`. This section restates only the normative requirements.
-
-### Normative requirements
-
-1. **RI-N1 Exact-commit publication verification (SDLC-D-034).** One canonical terminal verification command performs self-contained re-verification in the publish pipeline against the job's checked-out commit before any external publication effect. The command contains or invokes the complete mandatory verification set (semantic parity with the PR merge gate, including sanitization, upgrade-guard, typecheck, lint, format check, tests, and build); CI and publication do not maintain separate semantic checklists. Every publish step depends on the verification step in the executable pipeline DAG. Provider commit identity and `git rev-parse HEAD` must identify the same commit. Missing, skipped, cancelled, stale, or inconclusive checks fail closed. Documentation-only runs may skip publication but cannot bypass verification when a publication effect will occur. A negative control must prove that a broken check blocks every publish step.
-
-2. **RI-N2 Fail-closed Forge/MACP with explicit simulation (SDLC-D-035).** Simulation requires explicit caller intent (e.g. `--simulate`) and produces a distinct typed `simulated` state that can never satisfy dependencies, acceptance criteria, gates, merge, or release. Normal execution exits nonzero with a typed capability failure when a required executor, reviewer, command, or CI provider is absent — no stub completion, no literal-`true` gates, no synthetic approvals, no empty-command passes. A manual gate with no automation enters a waiting state; it does not pass. Positive tests prove explicit simulation still works; negative controls prove simulation and every missing-provider case cannot advance lifecycle state.
-
-3. **RI-N3 One transitional PRD authority (SDLC-D-036).** `@mosaicstack/prdy` structured storage under `docs/prdy/`, driven by `mosaic mission --plan`, is the authoritative PRD representation for the alpha. `mosaic prdy` either routes through the same application service or operates only as an explicit, named Markdown import/export adapter; `docs/PRD.md` is not a peer authority. `mission --plan` must persist the mission↔PRD linkage (mission id/version, PRD id/version, selected requirements). Markdown output is a generated view carrying source identity; editing it cannot mutate authority silently. Import is explicit, validated, and conflict-aware (proposed successor, never overwrite). Structural validity is separate from approval.
-
-4. **RI-N4 One quality-rails evaluator (SDLC-D-037).** The TypeScript quality-rails package is the sole authoritative evaluator. A complete probe inventory maps every current TypeScript and shell check to one canonical check with disposition (preserve/strengthen/retire, each named). Effective shell enforcement probes are absorbed before their independent paths retire; expected-file presence alone is not parity. The evaluator returns typed results (`passed`/`failed`/`blocked`/`error`/`not-applicable`) with check version, subject, and reason; missing implementation, missing input, unknown check, process error, timeout, or malformed output can never become `passed` or an unqualified skip. Check definitions and policy are versioned and digested. Shell commands become thin adapters with no separate verdict logic. The canonical terminal verification command (RI-N1) invokes this evaluator rather than duplicating its logic. Contract, parity, and negative-control tests are required, plus independent review of probe equivalence.
-
-5. **RI-N5 Consequence-aware stale UI (SDLC-D-038).** Mission Control distinguishes typed freshness states (`current`, `stale`, `partial`, `unknown`, `unavailable`) rather than inferring from empty arrays or null. A failed fetch never renders as an empty healthy collection. Last-known data may display for situational awareness only with source identity, version, and age visibly labeled; any derived completion/assurance/release verdict whose inputs are stale becomes `unknown`; all state-changing actions are disabled until fresh state loads and is revalidated. With no verified snapshot, surfaces show an explicit unavailable state. Cache corruption, cross-workspace data, schema mismatch, and version regression invalidate the snapshot. Tests cover the failure matrix (network, auth, malformed, partial, corruption, stale age, schema mismatch, recovery, stale-action rejection) with negative controls proving no case yields a current green verdict or enabled mutation.
-
-### Acceptance criteria
-
- AC-RI-1: A push to `next` that fails any mandatory verification step publishes nothing (no npm package, no image), demonstrated by a checked-in negative control and by pipeline evidence on a real `next` publish run where the verification step is green and every publish step depends on it.
- AC-RI-2: With no executor/reviewer/CI provider wired, Forge and MACP normal runs exit nonzero with typed capability failures; with `--simulate`, runs complete but every result is typed `simulated` and cannot satisfy any gate, dependency, or completion state — proven by unit tests including negative controls.
- AC-RI-3: A PRD created or revised through either `mosaic mission --plan` or `mosaic prdy` resolves to one authority under `docs/prdy/` with stable identities and versions; the mission↔PRD linkage survives restart; a Markdown export is labeled as generated and cannot silently become a second writer; divergent legacy content blocks baseline claims until explicitly resolved — proven by contract tests.
- AC-RI-4: `quality-rails check` through any entry point (TS CLI, framework shell adapter) returns the same typed verdict for the same subject; the probe inventory names every legacy check's disposition; a deliberately broken probe fails closed — proven by contract/parity/negative-control tests and independent review of probe equivalence.
- AC-RI-5: No shipping surface renders a failed fetch as an empty healthy state; stale/partial/unavailable states are typed, labeled, and mutation-disabled — proven by the failure-matrix tests.
- AC-RI-6: All cards merged to `next` via squash PR with terminal-green CI; release evidence for 0.0.50 records commit, verification run, and published artifacts.
-
-### Out of scope
-
-The canonical dispatcher/control-plane vertical slice (work graph, execution attempts, fenced leases, typed check-in, independent verifier dispatch) is decided post-alpha (SDLC-D-033, option B). Multi-pipeline verification certificates (SDLC-D-034 option B) are post-alpha. Full AF-1..AF-4 objective matrices and Mission Control portfolio surfaces are post-alpha.
-
-## Official CLI Capability and Tool Migration Workstream (T78)
-
-Normative contract on integration trunk `next`:
-[docs/requirements/cli-capability-migration.md](./requirements/cli-capability-migration.md):
-migrates agent-facing operations from directly invoked scripts into documented, first-class
-`mosaic` CLI command groups, together with the central-registry resolver, capability catalog,
-adapter boundary, and phased legacy-tool-tree decommission the migration requires. The contract
-carries its own implementation hold and delivery stages.
+# PRD: Mosaic Stack
+
+This file is a permanent shim, not the PRD body (GOV.1 lifecycle rule). The
+project source of truth is the **current revision bundle**:
+
+**[docs/PRDs/2026-08-31_PRD_rev1/](./PRDs/2026-08-31_PRD_rev1/PRD.md)** —
+rev1, ratified 2026-09-01 (Jason Woltje). It consolidates the 2026-08-26 North
+Star (D1–D15), the fleet north star, the agent-runtime L1/L2 contracts, and the
+control-plane-surfaces findings into sectioned documents (AUTHN, AUTHZ, CLI,
+DATA, GOV.1–5, HARN, PROV, ROLE, SEAT, SESS, UI, VIS) with a single decision
+map and a closed open-questions list.
+
+Revision bundles are frozen at ratification and never deleted. The prior
+revision, rev0 (2026-08-26 North Star), is archived verbatim at
+[docs/PRDs/2026-08-26_PRD_rev0/PRD.md](./PRDs/2026-08-26_PRD_rev0/PRD.md).
+Updating the PRD means ratifying a new bundle under `docs/PRDs/` and repointing
+`current_rev:` here; this path never changes.
@@ -0,0 +1,910 @@
+---
+kind: spec
+status: active
+source_of_truth: true
+---
+
+# PRD: Mosaic Stack — North Star
+
+This document is the product source of truth for Mosaic Stack.
+
+- **Part I** defines the product north star. It is written from the ratified
+  decision set D1–D14 (operator decision session, 2026-08-25; decision owner
+  Jason Woltje). Each section cites the decisions it implements.
+- **Part II** preserves the active workstream contracts unchanged. Open issues
+  bind to them; this rewrite does not alter a single normative word in them.
+- The previous v0.1.0 beta PRD body is archived verbatim at
+  [docs/archive/PRD-v0.1.md](./archive/PRD-v0.1.md) and is no longer authority.
+- The delivery roadmap lives in [docs/ROADMAP.md](./ROADMAP.md). Per D11, every
+  planned phase appears there from day one, even as a placeholder.
+
+## Metadata
+
+- **Owner / decision authority:** Jason Woltje
+- **Status:** active (supersedes the v0.1.0 PRD as product authority)
+- **Date:** 2026-08-26
+- **Decision registry:** D1–D14, recorded in Part I §12
+- **SSOT rule:** this repository's `docs/` tree is the product source of truth
+  (D5). Estate brains hold operational records, not product canon; only
+  product-relevant material migrates here (D6).
+
+---
+
+## Part I — Product north star
+
+### 1. What Mosaic Stack is (D1)
+
+Mosaic Stack is an **open-source, AI-first platform for people who want a
+self-hosted environment for agentic management and a life operating system.**
+It serves personal, business, and employee needs from one deployment, and the
+work is offered freely.
+
+"AI-first" means agents are first-class operators of the system, not a bolted-on
+chat box: the platform exists to let humans direct fleets of agents over their
+projects, tasks, communications, and infrastructure, with the same tools and
+the same guarantees whether a human or an agent is acting.
+
+### 2. Who it is for (D1, D9)
+
+The operator of a deployment is its user. Mosaic Stack is **not a hosted
+business**: running the system as a service for external customers is outside
+the north star. Multi-tenancy exists WITHIN a deployment so that one operator
+can separate their world — for example, several LLCs plus a personal domain —
+while every deployment is self-hosted by its own operator.
+
+"Company" in the hierarchy is organizational separation for one operator's
+world, not a customer account.
+
+### 3. Deployment modes (D3)
+
+Two modes, chosen at install time:
+
+|                     | Standalone / personal                  | Enterprise                                            |
+| ------------------- | -------------------------------------- | ----------------------------------------------------- |
+| Brains              | one mosaic-brain (system + user files) | system brain for config + one brain per user          |
+| User-data isolation | single user                            | no user-data leakage between users; sharing is opt-in |
+| Secrets             | OpenBao/Vault or flat files            | OpenBao/Vault REQUIRED                                |
+| Conversion          | Standalone → Enterprise, **one-way**   | terminal state                                        |
+
+Brains are configurable as external git repositories (recommended, not
+required); git tracking is always on locally.
+
+**Federation** (connecting deployments: system-level config, assigned users,
+rights and data-access control, trusts with boundaries, exfiltration
+monitoring) is intentionally not fully designed. It is deferred, appears on the
+roadmap as a placeholder phase per D11, and nothing in v1 may foreclose it.
+
+### 4. Structure and tenancy (D2, D9, D13)
+
+The hierarchy:
+
+```
+company/organization  (N per deployment)
+└─ estate             (each in exactly one company)
+   └─ project         (each in exactly one estate)
+      └─ workspace    (project-specific; carries the Kanban)
+```
+
+Rules:
+
+- Users can create N companies, N estates, N projects.
+- Tasks bubble UP the hierarchy so whole-system status is visible at every
+  level. Bubble-up is **read-only aggregation**, never a cross-workspace write.
+- Granular RBAC: admins restrict access per company, estate, and project;
+  grants are evaluated down the chain. Assets are transferable subject to the
+  structure.
+- **`workspace_id` remains the hard mechanical isolation unit** exactly as
+  ratified in
+  [docs/requirements/native-kanban-sot.md](./requirements/native-kanban-sot.md)
+  (#751): PostgreSQL sole writable SOT, cross-workspace relationships rejected,
+  fail-closed mutations. The hierarchy is parent structure ABOVE workspaces,
+  used for RBAC evaluation and read-only roll-ups. The kanban SOT carries this
+  as Amendment A1, added by reviewed PR — an amendment, not a rewrite (D13).
+
+### 5. Identity (D10)
+
+Built-in auth (better-auth) is the **account system of record**. Authentik and
+other external IdPs federate in via OIDC as login methods; they never become
+the system of record. Perimeter shims (forward-auth in front of a web host) are
+deployment workarounds, not the design.
+
+### 6. Onboarding (D4)
+
+Onboarding is a **wizard that differs by mode, is re-runnable (no lock-in), and
+is extensible** — new wizards attach as tabs.
+
+Standalone flow captures: system and company name; component choices (Mosaic
+Comms/Matrix vs external; Mosaic SSO/Authentik vs external; Mosaic
+DB/PostgreSQL vs external; vector DB); the initial user
+(email/password/name/SSO); comms setup (Matrix/Discord/Slack); agent enrollment
+(harness choice and install, OAuth or API-key login, multi-account, model
+choice with recommendation, agent name and persona, account assignment,
+optional comms auto-enroll); a user onboarding profile (disabilities including
+ADHD/autism/PDA/vision, professional background, education, desired agent
+communication style, optional voice-matching interview, family/pets/friends/
+hobbies/likes-dislikes); email and drive connectors (Gmail/IMAP, Google
+Drive/OneDrive/Dropbox) with granular agentic-access consent; SSO/OIDC
+configuration; an initial estate, an initial project, and seeded example data.
+
+Enterprise uses the same skeleton with personal data optional; the focus moves
+to business structure, org chart, RBAC, M365 and external systems, immediate
+OIDC, SSO prominent.
+
+Profile answers feed `USER.md` and/or the user's data store subject to the
+custody rule in §7.
+
+### 7. Data custody (D6, D14)
+
+- **Sensitive profile categories** (disabilities, family, communication style,
+  and similar) live in the **user's own brain ONLY**. PostgreSQL holds
+  structural data, consent records, and pointers — never the content. "User
+  data does not leak" is enforced by architecture, not policy (D14).
+- Standalone (one user, one brain) **may** keep the same split — D14 makes it
+  optional in Standalone, not required. Keeping it is the recommended default
+  because it preserves forward-compatibility with the one-way Enterprise
+  conversion (D3).
+- Estate brains hold operational records. Only product-relevant material
+  migrates into this repository's docs; operational records stay in their
+  brains and are linked (D6).
+
+### 8. Architecture gate — the webUI sits OVER official tooling (D8, D12)
+
+**HARD RULE:** every webUI operation goes through the Gateway API backed by the
+same official framework tooling the CLI uses. The CLI remains the primary
+execution method; the webUI uses the tools to operate and configure the
+system. The webUI never bypasses tooling to reach the database or filesystem
+directly.
+
+Consequence for planning: when a desired webUI operation has no backing tool,
+the gap is scored **"blocked on tooling"** and the tool is built first. The
+product baseline therefore always includes all three D8 inputs: the tool
+inventory (what exists and what is missing), the webUI→tool mapping, and the
+measured current state of the `next` branch.
+
+### 9. v1 slice (D11)
+
+v1 is deliberately small:
+
+1. **Standalone onboarding wizard** — system/company name, component choices,
+   initial user, initial estate + project, seeded examples, re-runnable.
+2. **Hierarchy core** — company → estate → project → workspace → kanban, with
+   read-only task bubble-up.
+3. **Basic RBAC** on the hierarchy.
+4. **Minimal agent enrollment** — one harness, API key, name/persona.
+
+Deferred beyond v1: connectors, comms integrations, voice-matching, M365,
+Enterprise conversion, federation. Every deferred item appears in
+[docs/ROADMAP.md](./ROADMAP.md) per the D11 rule: nothing exists only in heads.
+
+### 10. Relationship to the fleet north star
+
+[docs/fleet/NORTH_STAR.md](./fleet/NORTH_STAR.md) (generated from
+`docs/fleet/NORTH_STAR.yaml`) is the **delivery-fleet** north star: how the
+agent fleet that builds and operates the system should run (NS-1..NS-10,
+workstreams A–L). This PRD is the **product** north star. They are not
+competitors: the fleet north star is subordinate product-wise — its workstream
+J ("Web control plane") is one consumer of this PRD's D8/D12 gate — and this
+PRD does not redefine fleet invariants. The subordination rule is ratified in
+the frozen audit-input baseline (T2 operator freeze, 2026-08-25: "the PRD must
+cite and subordinate it, never fork it"). A change that would put the two in
+conflict must amend one of them explicitly, never fork a third document
+(drafting addition — see §12.1).
+
+### 11. Explicit non-goals
+
+- Hosted/SaaS operation for external customers (D9).
+- A webUI that writes to the database or filesystem around the tooling (D12).
+- A second writable task store beside PostgreSQL (native-kanban-sot invariants).
+- Fully-designed federation in v1 (D3 — roadmap placeholder only).
+
+### D15 — Tiered containerized deployment (2026-08-30, containerization lane)
+
+The stack ships a tiered deployment target, additive to the architecture
+gate (D8): (1) Standalone tier — docker compose is the canonical
+single-host deployment: postgres, valkey, openbao, gateway, appservice
+and the served webUI in one composition, with migrations, health checks,
+and a documented install/upgrade path; the registry (CI-published
+images) is the only deployment source. (2) Enterprise tier — Kubernetes
+manifests for the same service set, phase-gated on the standalone tier
+holding its acceptance bar. The v1 acceptance bar for the standalone
+tier: compose-up healthy; webUI hosts agent chat; an in-stack agent can
+open a PR to this repo; CI validates it; the running deployment adopts
+the merged change (pull + restart). Federation (D3 clause) remains
+deferred and unforeclosed. Implementation plan:
+docs/plans/2026-08-30_containerization.md.
+
+## 12. Decision registry
+
+| ID  | Decision (short form)                                                                                                                      |
+| --- | ------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------- |
+| D1  | Open-source, AI-first, self-hosted platform for agentic management + life OS                                                               |
+| D2  | Hierarchy company→estate→project→workspace→kanban; bubble-up; granular RBAC                                                                |
+| D3  | Standalone vs Enterprise; one-way conversion; per-user brains + Vault required in Enterprise; federation deferred                          |
+| D4  | Re-runnable, extensible, per-mode onboarding wizards                                                                                       |
+| D5  | North star = this rewrite of docs/PRD.md; stack docs/ = product SSOT                                                                       |
+| D6  | Only product-relevant material migrates from brains; operational records stay and link                                                     |
+| D7  | Spec-inventory sweep launched immediately (executed; INPUTS baseline frozen by operator ruling T2, 2026-08-25)                             |
+| D8  | webUI sits over official framework tooling; CLI primary                                                                                    |
+| D9  | Not a hosted business; company = organizational separation for one operator                                                                |
+| D10 | better-auth is the account system of record; external IdPs via OIDC                                                                        |
+| D11 | Small v1 slice; ALL phases on the documented roadmap from day one                                                                          |
+| D12 | HARD RULE: webUI never bypasses tooling; missing tool ⇒ build the tool first                                                               |
+| D13 | workspace_id stays the hard isolation unit; hierarchy is parent structure above; kanban SOT amended, not rewritten                         |
+| D14 | Sensitive profile data in the user's own brain only; postgres holds structure/consent/pointers                                             |
+| D15 | Tiered containerized deployment: compose standalone tier (five-point v1 bar) + phase-gated k8s enterprise tier; registry-only image source | 2026-08-30 containerization lane; plan docs/plans/2026-08-30_containerization.md |
+
+The full decision texts are recorded in the operator decision log (USC estate
+brain, webui-audit lane, `GRILL.md`).
+
+### 12.1 Drafting additions beyond D1–D14
+
+Independent review of this rewrite identified rules in this document that are
+not present in the D1–D14 record or the frozen T2 baseline. They are listed
+here so their ratification is explicit: approval of the PR that introduces
+this document, by the decision owner, ratifies them. If any is rejected it is
+removed, not silently kept.
+
+1. **Federation forward-compatibility gate:** "nothing in v1 may foreclose
+   federation" (§3), and scoping federation later requires its own PRD plus
+   threat model ([ROADMAP](./ROADMAP.md) P5). D3 defers federation; these
+   protective gates are additions.
+2. **North-star amendment rule:** a product/fleet north-star conflict must be
+   resolved by amending one of the two documents explicitly, never by forking
+   a third (§10). The subordination itself is T2-ratified; this amendment
+   procedure is an addition.
+
+---
+
+## Part II — Active workstream contracts (preserved unchanged)
+
+The sections below are normative, in-flight workstream contracts carried over
+verbatim from the previous revision of this file. Open issues bind to them.
+This rewrite moved no text and changed no requirement in them; they are
+governed by their own issues and review gates, and they graduate out of this
+file individually when their workstreams close.
+
+## Current addendum: #1194 — Installed framework-tool drift detection
+
+- Compare the framework tools shipped with the executing Mosaic package against the deployed `$MOSAIC_HOME/tools` tree by content hash.
+- Treat every shipped `tools/**` file as framework-owned/required according to `framework-manifest.txt`, while excluding the explicit operator-owned credential carve-out and preserving installed-only operator/unknown files.
+- Distinguish and count `IN_SYNC`, `STALE`, `NOT_INSTALLED`, and installed-only classifications; fail non-zero when shipped tools are stale or absent and refuse self-comparison that would make drift unobservable.
+- Surface the observational check through `mosaic doctor`; do not refresh files, restart seats, or mutate live tooling.
+- Document identity/messaging/gate behavior changes in the current stale set, the reviewed quiet-window keep-mode refresh command, and post-refresh probes against the installed path.
+- Prove by construction that a stale and missing deployed tool are detected; that regression must fail before this checker exists.
+
+## Compaction Refresh Trust Lifecycle (M1, #827–#830)
+
+### Problem and objective
+
+Context compaction, session replacement, and same-PID runtime reloads can leave a previously VERIFIED runtime lease attached to stale directives. M1 must revoke that authority mechanically for Claude (including Claudex) and Pi without trusting caller-asserted identity or forking the external broker state machine.
+
+### Requirements
+
+1. `CR-REQ-01`: Claude `PreCompact` and `SessionStart` with matcher `compact`, plus Pi `session_before_compact` and the first post-`session_compact` `context`, SHALL independently revoke the active broker lease.
+2. `CR-REQ-02`: Runtime generation increases—including same-PID Pi reload/new/resume/fork and Claude resume/clear—SHALL monotonically replace the prior broker incarnation and inherit no VERIFIED lease.
+3. `CR-REQ-03`: A fired observer that cannot confirm broker revocation SHALL fail closed through lifecycle cancellation, a private local generation fence, and/or a runtime-local tool latch. The existing all-tools broker gate remains authoritative.
+4. `CR-REQ-04`: The lease TTL SHALL remain monotonic and capped at 300 seconds. If both observers are missed, within-TTL consequential actions remain allowed and after-TTL actions are denied. This named bounded residual stale window SHALL be documented without claiming a mutator-action bound inside the window.
+5. `CR-REQ-05`: Hook descendants SHALL use the broker-minted session and owner-only current-generation state inherited from register-before-exec. Caller-minted sessions and parallel lease state machines remain forbidden.
+
+### Acceptance criteria
+
+1. `AC-CR-01`: Real-socket tests prove each Claude observer revokes, Pi lifecycle tests prove both observer paths, and Claudex isolated settings preserve and install the mandatory hooks.
+2. `AC-CR-02`: A same-PID generation test proves the old generation is stale and the replacement generation is UNVERIFIED across reload/resume/fork-equivalent lifecycle events.
+3. `AC-CR-03`: RED-first T12b/T30 evidence explicitly reports dual-hook miss within TTL as **ALLOWED** and after TTL as **DENIED**.
+4. `AC-CR-04`: Attributable executable coverage is at least 85%, the full repository suite is green on deterministic main, and independent code/security review completes before merge.
+
+---
+
+## Pi Persistent Goal Loop (#1150)
+
+### Problem and objective
+
+A Pi agent can stop after a plausible-looking answer even when the operator's broader objective is
+not complete, and ordinary compaction can weaken or omit the original objective. Mosaic needs an
+optional, operator-controlled goal loop that keeps a Pi session oriented, checks progress at native
+lifecycle boundaries, and resumes work until completion is verified or a bounded safety state is
+reached.
+
+The objective is a Mosaic-owned Pi extension deployed from the framework into
+`~/.config/mosaic/runtime/pi/`. It must not install into or depend on `~/.pi/agent/extensions/`.
+
+### Scope
+
+#### In scope
+
+1. `PGL-REQ-01`: The framework SHALL ship a dedicated Pi goal extension under
+   `packages/mosaic/framework/runtime/pi/`, seed it under `$MOSAIC_HOME/runtime/pi/`, and make
+   `mosaic pi` load it alongside the core Mosaic extension when present.
+2. `PGL-REQ-02`: `/goal` SHALL support setting a goal plus status, pause, resume, cancel, and help
+   operations without silently replacing an active goal.
+3. `PGL-REQ-03`: Active branch-specific goal state SHALL be persisted in Pi custom session entries,
+   restored on session start and tree navigation, and never rely on a compaction summary as its
+   source of truth.
+4. `PGL-REQ-04`: A hidden goal contract SHALL be injected through Pi's `context` event before every
+   model request so it remains effective across tool turns, retries, and post-compaction requests.
+5. `PGL-REQ-05`: The harness SHALL inspect every `turn_end` and successful `session_compact` event.
+   A structured terminating goal-report tool SHALL capture `continue`, evidence-bearing `achieved`,
+   or `blocked` status without requiring a redundant model turn.
+6. `PGL-REQ-06`: An achievement claim SHALL remain provisional until a second consecutive
+   evidence-bearing verification report. Any continuation report or successful compaction during
+   verification SHALL reset the verification sequence.
+7. `PGL-REQ-07`: Continuation SHALL be initiated at safe lifecycle boundaries, primarily
+   `agent_settled`; manual compaction and restored active sessions may schedule a deferred idle
+   continuation without re-entering compaction handlers.
+8. `PGL-REQ-08`: The loop SHALL have operator cancellation plus bounded turn and repeated-no-progress
+   limits. Exhausted or blocked goals pause rather than continuing indefinitely.
+9. `PGL-REQ-09`: Framework installation and update SHALL preserve normal manifest ownership: the
+   goal extension is framework-owned under `runtime/**`, while no goal extension or configuration
+   asset is created or modified under the operator's main Pi configuration. Pi remains the owner of
+   its native session files used by `appendEntry()`.
+
+#### Out of scope
+
+1. A mathematical guarantee that an arbitrary natural-language goal is semantically complete.
+2. Automatically executing user-supplied shell predicates or accepting executable validation code in
+   `/goal` arguments.
+3. Restarting Pi after process, host, or supervisor failure; the existing Mosaic fleet/runtime
+   supervisor owns process durability.
+4. Gateway, database, web UI, Discord, or cross-harness goal orchestration in this slice.
+
+### User and stakeholder requirements
+
+- An operator can start a goal from Pi and see its current phase, evidence, limits, and latest report.
+- The agent remains oriented after each turn and compaction until verified, paused, blocked,
+  exhausted, or cancelled.
+- Local testing uses a file under `~/.config/mosaic/runtime/pi/`; the feature never writes an
+  extension asset to `~/.pi/agent/extensions/`.
+- Framework updates deploy the same reviewed extension source through Mosaic's existing manifest
+  sync path.
+
+### Non-functional requirements
+
+1. **Safety:** bounded continuation, explicit cancellation, no arbitrary command execution, and no
+   completion without non-empty reported evidence.
+2. **Reliability:** serialized continuation scheduling, branch-aware restoration, compaction-safe
+   context injection, and stale-timer cancellation on session shutdown.
+3. **Performance:** no extra nested judge-model request on every turn; structured reporting uses the
+   active agent's final terminating tool call.
+4. **Observability:** Pi status/notifications expose phase and bounded counters without recording
+   credentials or hidden model reasoning.
+5. **Maintainability:** the state machine is deterministic and behavior-tested independently from Pi
+   provider/network access.
+
+### Acceptance criteria
+
+1. `AC-PGL-01`: A framework-sync fixture installs the extension at
+   `$MOSAIC_HOME/runtime/pi/goal-extension.ts`, and launcher tests prove both Mosaic Pi extensions are
+   emitted in deterministic order while absent optional files remain backward-compatible.
+2. `AC-PGL-02`: Command tests prove set/status/pause/resume/cancel behavior, active-goal replacement
+   refusal, and bounded input handling.
+3. `AC-PGL-03`: Lifecycle tests prove every turn is recorded, active context is injected on every
+   request, two evidence-bearing achievement reports are required, and `agent_settled` continues an
+   unmet goal without duplicate scheduling.
+4. `AC-PGL-04`: Compaction and restoration tests prove goal state survives, verification is reset and
+   rechecked after compaction, manual compaction continuation is deferred until idle, and tree/session
+   branch state is reconstructed correctly.
+5. `AC-PGL-05`: Limit tests prove max-turn and repeated-no-progress exhaustion stop autonomous
+   continuation, while pause/cancel/blocked states do not restart.
+6. `AC-PGL-06`: Focused tests, package typecheck/lint/test, repository quality gates, a local Pi load
+   smoke test from `~/.config/mosaic/runtime/pi/`, independent review, and terminal-green CI pass before
+   issue #1150 closes.
+
+### Constraints, risks, and assumptions
+
+- Dependency: Pi's extension API must continue to provide `registerCommand`, `registerTool`,
+  `context`, `turn_end`, `agent_settled`, `session_compact`, session custom entries, and terminating
+  tool results.
+- Risk: the working agent can overstate completion. Mitigation: structured evidence, a mandatory
+  second verification pass, explicit semantic limitations, and operator-visible reports.
+- Risk: an impossible goal can consume unbounded resources. Mitigation: hard turn/no-progress bounds
+  and paused terminal states.
+- Risk: automatic continuation can race compaction or session replacement. Mitigation: drive from
+  `agent_settled`, defer idle restarts, generation-check timers, and clear timers on shutdown.
+- `ASSUMPTION:` Two consecutive evidence-bearing reports are the initial local verification policy;
+  rationale: it provides a real recheck without doubling every turn's model cost. Future policy may
+  add independent or deterministic validators.
+- `ASSUMPTION:` Default limits are 40 turns and 6 repeated no-progress reports, configurable only by
+  bounded Mosaic environment settings; rationale: useful persistence with a finite autonomous budget.
+- `ASSUMPTION:` Documentation remains canonical in-repo for this slice; no external docs publication
+  is requested.
+
+### Testing and delivery intent
+
+Use TDD for the deterministic controller and lifecycle invariants. Test with fake Pi lifecycle
+objects first, then run a local load/smoke test from the deployed Mosaic path. Deliver source, tests,
+launcher wiring, framework/runtime documentation, user/developer guides, and sitemap updates in one
+reviewed squash PR to `main` with terminal-green CI.
+
+---
+
+## Fleet Declarative Configuration Management Workstream (FCM, #758)
+
+### Problem and objective
+
+The local Mosaic fleet has a roster, generated agent environment files, user-systemd units, tmux
+sessions, heartbeat files, examples, profiles, and separate gateway-backed agent records. These
+planes have drifted and are not one safe operator lifecycle. The objective is one **local fleet
+roster** as the desired-state SSOT, with generated environment, systemd, tmux, and heartbeat
+artifacts as rebuildable projections; it does not merge the local fleet control plane with the
+gateway-backed agent catalog.
+
+### Normative requirements
+
+| ID           | Requirement                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `FCM-REQ-01` | The roster SHALL be the sole writable desired-state source for local fleet membership, launch policy, and persisted lifecycle target. Generated environment files, systemd enablement, tmux sessions, and heartbeat state SHALL be non-authoritative projections.                                                                                                                                                                                                         |
+| `FCM-REQ-02` | The implementation SHALL provide one executable structural contract for YAML/JSON input and one shared semantic validator. Roster load, profile validation, provision, migration, and apply SHALL reuse the existing baseline-plus-`roles.local` profile/persona resolver; a parallel role resolver is forbidden.                                                                                                                                                         |
+| `FCM-REQ-03` | The local fleet CLI SHALL expose documented programmatic validate, show, plan, apply/reconcile, create, inspect, update, delete, start, stop, restart, status, verify, and doctor operations with stable JSON and exit-code behavior. Existing `fleet add/remove` compatibility aliases may remain during the stated deprecation window.                                                                                                                                  |
+| `FCM-REQ-04` | A fresh create SHALL persist `enabled:true` and `desired_state:stopped` unless an explicit persisted start is requested. The model SHALL distinguish enabled state, persisted desired state, and observed state. Migration, apply, reboot, and rollback SHALL not start an agent that was observed stopped before cutover.                                                                                                                                                |
+| `FCM-REQ-05` | The launch chain SHALL consume deterministic, digest-stamped generated input only. Optional local overrides SHALL be parsed as strict data, may not shadow authoritative generated keys, and may not contain arbitrary commands, credential values, channels, or unknown `MOSAIC_AGENT_*` keys. Forbidden legacy keys, including `MOSAIC_AGENT_COMMAND`, SHALL be privately quarantined before launch and reported only by key name and content hash.                     |
+| `FCM-REQ-06` | Mutations and apply SHALL validate before mutation, use an expected generation/lock, write projections atomically, produce a deterministic plan, and emit recovery information on partial failure. Reconciliation SHALL act only on local, enabled, roster-owned projections and SHALL not kill unmanaged tmux sessions by fuzzy name.                                                                                                                                    |
+| `FCM-REQ-07` | Canonical required classes are `code`, `review`, `validator`, `orchestrator`, `team-leader`, `enhancer`, and `interaction`. `validator` issues an independent final certificate but has no merge authority; `merge-gate` remains sole approve-to-land/merge authority. Team-leader capacity is bounded by an orchestrator-issued lease, and interaction is request/status only. Tess and Ultron are configurable instance/display names, not required machine identities. |
+| `FCM-REQ-08` | v1 migration SHALL be field-complete, reversible, and explicit about aliases, unresolved classes, lifecycle inference, generated-file regeneration, local override quarantine, schema-only remote/connector fields, and rollback. Every shipped example, profile, and service preset SHALL be migrated and executable, retained as an explicitly versioned v1 fixture, or retired with a replacement and deprecation note.                                                |
+| `FCM-REQ-09` | M1–M5 SHALL remain local tmux/systemd control-plane work. Remote/SSH reconciliation, connector mutation, secret references, arbitrary command/channel overrides, gateway/API convergence, and UI configuration storage are excluded and require a separate PRD/threat model.                                                                                                                                                                                              |
+| `FCM-REQ-10` | Documentation and examples are delivery gates. The M0 checklist at [docs/fleet/FLEET-CONFIG-DOCS-IA-CHECKLIST.md](./fleet/FLEET-CONFIG-DOCS-IA-CHECKLIST.md) and the baseline disposition inventory at [docs/fleet/LEGACY-EXAMPLE-PROFILE-DISPOSITION-INVENTORY.md](./fleet/LEGACY-EXAMPLE-PROFILE-DISPOSITION-INVENTORY.md) SHALL be maintained as acceptance evidence.                                                                                                  |
+
+### Acceptance criteria
+
+1. `AC-FCM-01`: A valid local v2 roster can be parsed from YAML or JSON, validated structurally and semantically through the shared resolver, and rendered canonically; invalid fields, duplicate names, unresolved classes, unsupported runtime/model combinations, socket ambiguity, and incompatible options fail closed.
+2. `AC-FCM-02`: `plan` reports deterministic desired-versus-observed differences for roster, generated environment, systemd enablement, tmux/session, heartbeat, installed-asset revision, and provable orphans without mutation; `apply --check` reports drift without mutation.
+3. `AC-FCM-03`: Local create/update/delete is generation-guarded, atomic, idempotent, and safe by default; it permits supported runtime/model/harness/effort/workdir/role changes without direct editing of generated environment files and does not start a newly created agent unless explicitly persisted.
+4. `AC-FCM-04`: The generated-env/local-override launch chain rejects generated-key shadowing, arbitrary command override, unknown keys, shell evaluation, and sensitive-value diagnostics before any agent starts; known-safe legacy input is regenerated or strictly relocated, and forbidden input is quarantined.
+5. `AC-FCM-05`: Local lifecycle reconciliation implements the persisted/transient start-stop rules, exact default/named tmux socket targeting, systemd/tmux status, stale generated state, unmanaged-session reporting, and rollback without surprise restarts or fuzzy destructive targeting.
+6. `AC-FCM-06`: A v1 roster migration previews field-by-field disposition, preserves observed stopped/running state, inventories rather than reconciles remote/schema-only entries, supports a canary and rollback, and classifies every shipped example, profile, and service preset according to the M0 inventory.
+7. `AC-FCM-07`: Required role authority is validated: validator certificate is consumed but does not merge, merge-gate is the sole merge authority, team-leader leases do not change roster/credentials/authority, and interaction/Tess cannot claim orchestration or merge powers.
+8. `AC-FCM-08`: Documentation, examples, migration, troubleshooting, operational recovery, package/update asset drift, schema/example/profile validation, independent code/security review, validator certificate, and terminal-green CI are complete before #758 closes.
+
+### M0 implementation gate
+
+No source, schema, role, example, profile, systemd, or live-fleet change is authorized before M0
+lands. M0 consists only of these normative requirements, the complete task DAG, the scoped
+documentation IA checklist, and the legacy example/profile disposition inventory. Subsequent cards
+are defined in [docs/TASKS.md](./TASKS.md) and must remain one card/one PR.
+
+### Fleet git identity launch propagation (#1043)
+
+#### Problem and objective
+
+A fleet seat can have a registered per-agent Git credential while its launched runtime process lacks
+`MOSAIC_GIT_IDENTITY`. The credential resolver then cannot select the seat identity reliably, which
+blocks repository operations on fail-closed estates and can fall through to an unrelated identity on
+estates where that refusal is not active. The objective is to make Git identity a deterministic,
+roster-derived part of the generated launch projection and prove it reaches the launched process.
+
+#### Normative requirements
+
+1. `FGI-REQ-01`: Every generated fleet agent projection SHALL declare
+   `MOSAIC_GIT_IDENTITY=<MOSAIC_AGENT_NAME>`; a differing or unsafe identity SHALL fail closed before
+   tmux launch.
+2. `FGI-REQ-02`: The clean `/usr/bin/env -i` pane boundary SHALL pass every variable declared by the
+   generated projection, including `MOSAIC_GIT_IDENTITY`, to the launched runtime process.
+3. `FGI-REQ-03`: A behavioral integration test SHALL set-compare the complete generated projection
+   against the launched process environment. Source-text/string-presence assertions are insufficient.
+4. `FGI-REQ-04`: Verification SHALL include RED-first evidence and a delete-the-subject mutation that
+   removes Git-identity pane propagation and makes the behavioral test fail.
+
+#### Acceptance criteria
+
+1. `AC-FGI-01`: A launched seat process contains every key/value pair declared by its generated
+   environment projection, including the roster-derived Git identity.
+2. `AC-FGI-02`: Missing, unsafe, or split Git identity is rejected before a tmux session is created.
+3. `AC-FGI-03`: Focused launcher and generated-environment tests, repository quality gates,
+   independent review, and the required RED/green/R7 evidence are recorded before push.
+
+### Framework shell assertion portability (#1098)
+
+#### Problem and objective
+
+The blocking framework-shell chain can report that a pane command omitted `/usr/bin/env -i` even when
+`-i` matched successfully. A short-circuiting `grep -q` under `set -o pipefail` may close its pipe after
+the match and cause an upstream producer to exit with SIGPIPE, turning a valid semantic result into a
+nonzero aggregate pipeline. The objective is to inspect the captured NUL-delimited argv directly and
+make failures carry the observed records needed for diagnosis.
+
+#### Normative requirements
+
+1. `FSP-REQ-01`: The pane-boundary test SHALL validate an adjacent `/usr/bin/env`, `-i` argv pair from
+   the authoritative NUL-delimited tmux capture without a short-circuit pipeline whose upstream status
+   can override a successful match.
+2. `FSP-REQ-02`: Missing, reversed, or non-adjacent boundary tokens SHALL fail, while valid boundaries
+   SHALL remain valid regardless of trailing argv size, pipe capacity, process scheduling, or host/CI
+   utility implementation.
+3. `FSP-REQ-03`: A failed boundary check SHALL print stable indexed, shell-escaped observed argv records
+   before exiting nonzero; the fixture SHALL continue to contain generated non-secret launch data only.
+4. `FSP-REQ-04`: Verification SHALL include RED-first large-payload evidence, negative token-order
+   controls, the complete focused launcher suite, canonical Woodpecker CI, and independent review.
+
+#### Acceptance criteria
+
+1. `AC-FSP-01`: A large captured argv with adjacent `/usr/bin/env`, `-i` passes even when the former
+   `grep -q` pipeline returns nonzero from an upstream SIGPIPE.
+2. `AC-FSP-02`: Missing executable, missing flag, and detached/reversed flag fixtures return nonzero and
+   emit the indexed observed argv.
+3. `AC-FSP-03`: The focused suite passes on the development host and CI image, and the merged-main
+   Woodpecker pipeline is terminal green before #1098 closes.
+
+---
+
+## Exact Cross-Harness Fleet Communications Contract (#766)
+
+### Problem and objective
+
+Fleet runtime contracts currently combine exact peer rows with generic operational metavariables and
+independently parsed roster data. Non-Claude harnesses can mistake those metavariables for values to
+infer, producing incorrect host, session, socket, or helper targets. The objective is one
+roster-resolved communications contract that every supported harness receives unchanged.
+
+### Normative requirements
+
+1. `FCOM-REQ-01`: Fleet commands and runtime composition SHALL use one shared v1 roster structural
+   resolver. A second lenient communications parser is forbidden.
+2. `FCOM-REQ-02`: The composed contract SHALL render the local roster member's authoritative host,
+   exact agent/session name, resolved tmux socket, exact helper path, and deterministic communications
+   generation.
+3. `FCOM-REQ-03`: Every known peer SHALL have one exact executable command. Same-host commands SHALL
+   omit `-H`; cross-host commands SHALL use only that peer's explicit roster `ssh` target; the one
+   supported fleet-wide named socket SHALL use `-L` with its exact value. A per-agent socket declaration
+   must equal that fleet-wide value; unsupported independent sockets and missing cross-host SSH data SHALL
+   fail closed.
+4. `FCOM-REQ-04`: Operational fleet examples SHALL not contain unresolved host, session, socket, or
+   helper-path metavariables. Agents SHALL select an exact rendered peer row and SHALL NOT infer,
+   substitute, or fuzzy-match targeting values.
+5. `FCOM-REQ-05`: An unknown local member or requested peer SHALL fail closed with exact-name discovery
+   guidance. Runtime composition SHALL not silently omit a requested fleet member's communications
+   contract.
+6. `FCOM-REQ-06`: Claude Code, Codex, OpenCode, and Pi SHALL receive equivalent authoritative
+   communications data through the common runtime composer.
+7. `FCOM-REQ-07`: Tests SHALL prove the contract from framework-source `TOOLS.md`, through a fresh
+   installed `TOOLS.md`, to final runtime composition and helper executability. User-owned installed
+   `TOOLS.md` content SHALL remain preserved.
+8. `FCOM-REQ-08`: Stale installed or active composed context SHALL be reported with deterministic
+   generation/repair/relaunch guidance. Currency requires the expected source and installed contract
+   marker/version plus bounded byte equality. The supported current-version repair SHALL run independently
+   of package updates, preserve divergent `TOOLS.md` bytes in a digest-qualified no-clobber backup, restore
+   a regular executable helper without following symlinks, and be idempotent. Detection and reporting SHALL
+   NOT rewrite active context, restart a session, or mutate a live fleet.
+9. `FCOM-REQ-09`: The shared resolver SHALL preserve and strictly validate every schema-supported v1
+   connector kind (`tmux`, `discord`, and `matrix`) from YAML and JSON. Every accepted snake/camel alias
+   pair SHALL reject differing dual declarations and accept identical declarations. JSON roster fallback
+   SHALL occur only when `roster.yaml` is absent; all other YAML access failures SHALL fail closed.
+10. `FCOM-REQ-10`: The communications generation SHALL cover the complete canonical rendered semantic
+    contract, including identity, role/class, resolved host/socket/helper, peer metadata, and exact commands.
+    Installed helpers SHALL be validated with no-follow filesystem inspection as regular executable files.
+    Keep-mode reseed and relaunch discovery SHALL preserve and support both YAML and JSON rosters.
+
+### Acceptance criteria
+
+1. `AC-FCOM-01`: Contract fixtures contain no unresolved operational targeting metavariables; local
+   identity contains exact host/session/socket/helper values.
+2. `AC-FCOM-02`: Same-host, cross-host, named-socket, literal-default-socket, and missing-SSH tests prove
+   exact targeting and fail-closed behavior.
+3. `AC-FCOM-03`: Unknown identities and peers report known exact names plus an exact self-scoped
+   discovery command; no fuzzy session selection is emitted.
+4. `AC-FCOM-04`: Four-harness tests prove byte-equal authoritative communications sections.
+5. `AC-FCOM-05`: Source, fresh-install, preserved-custom-install, stale-installed, composed-generation,
+   helper executable, agent-send socket isolation, and exact-target tests pass.
+6. `AC-FCOM-06`: Documentation defines non-mutating stale-context detection and operator-authorized,
+   exact-agent relaunch; no implementation path performs automatic session mutation.
+7. `AC-FCOM-07`: YAML and JSON fixtures cover every connector kind; all snake/camel aliases cover
+   identical acceptance and conflicting rejection; non-`ENOENT` YAML failures do not fall back.
+8. `AC-FCOM-08`: Missing, directory, symlink, and non-executable installed helpers fail closed. Explicit
+   current-version repair proves partial-deletion recovery, digest-qualified backup collision safety,
+   symlink-target safety, and repeated-run idempotence.
+9. `AC-FCOM-09`: Markerless-equal and wrong-version source/installed contracts are stale, and a rendered
+   role/class change produces a different communications generation.
+
+---
+
+## KBN-101 Database Runtime/Migration Role Split (#771)
+
+### Problem and objective
+
+PostgreSQL Gateway/storage currently uses one `DATABASE_URL` for runtime queries and migrations. That makes the deployed application identity an owner and prevents certification that KBN immutable event, artifact, checkpoint, and evidence relations reject runtime `UPDATE`/`DELETE`. KBN-101 freezes a least-privilege runtime/migration split before KBN-100 schema work.
+
+### Normative requirements
+
+1. `K101-REQ-01`: `DATABASE_URL` SHALL be the non-owner PostgreSQL runtime connection and `DATABASE_MIGRATION_URL` SHALL be the migration-only owner/migrator connection. They are required respectively for runtime and the dedicated `mosaic-db-migrator --run|--verify` phase in `standalone`/`federated`; local PGlite is the explicit exception. The published `@mosaicstack/db` bin maps exactly `mosaic-db-migrator` to `./dist/cli.js`, its image entrypoint is exactly `mosaic-db-migrator`, accepts no URL/SQL/schema/role argv, and returns stable sanitized exits. Every current/future PostgreSQL DDL entrypoint SHALL route to that runner or be denied, and SHALL reject `DATABASE_URL`-only execution before connection/DDL. Data migration may connect only after the runner prepares and verifies the PostgreSQL target, through dedicated non-DDL `mosaic_data_importer` and exactly `--target-url-file /run/secrets/mosaic-migrate-target-url`, its fixed paired authenticated provider-version file `/run/secrets/mosaic-migrate-target-version`, plus `--target-attestation-file /run/mosaic-attestations/migrate-target.v1.json`. KBN-101-05 obtains URL key `url` and version only from the same successful Vault KV-v2 response at `secret-{env}/mosaic-stack/database/importer` (`data.metadata.version`), renders them as one immutable generation into separate consumer copies, and never infers a provider version from DSN bytes. The trusted runner verifies TLS/identity/manifest, reads its fixed importer URL/version copies only for binding through safe no-follow fd checks, and signs a credential-free JCS/Ed25519 attestation using its runner-only fixed root-owned private-key file; no signing key reaches importer/runtime. The artifact binds secret version and SHA-256 of exact high-entropy credential-file bytes, canonical TLS host/port/database, CA/SPKI, PostgreSQL system identifier/database OID, importer role, manifest/schema fingerprints, producer invocation/build/image digest, issued/expires/nonce, and correlation. Before target connection the importer validates URL/version/attestation/public-key files, signature/key/expiry/replay/authenticated provider version/digest/generation/bindings and the importer-only CA at exact `DATABASE_TLS_CA_CERT_PATH`; after verified TLS and before DML it validates server/database/role/CA/schema identity, with same-fd/in-memory-byte TOCTOU protection, rotation/revocation, a privileged producer-only-to-importer-only artifact handoff controller that verifies/copies/fsyncs/atomically renames/seals before importer start, consumer isolation/no logging-oracle, and sanitized errors. Raw `--target-url`, `DATABASE_URL` fallback, runtime-owner use, missing/unsafe/substituted files, stale/replayed/tampered/wrong-key attestation, wrong binding, and DDL attempt fail before target connection/DDL; post-connect mismatch closes with zero DML/DDL. A reviewed finite classifier inventories executable current source/scripts/package bins, operator docs, deploy manifests, and exact normative contracts by path; active secure records pin both options/files, producer/key/bindings/tests, while normative contracts cannot mask instructions. Unknown active commands, duplicate-owner, ownerless, missing-path, and historical/status-only masking hits fail. `db:push` is forbidden outside an explicitly disposable local developer database and cannot accept a production-like URL.
+2. `K101-REQ-02`: Gateway runtime/replicas SHALL not execute migrations or DDL. The runner SHALL hold one `max:1` session and fixed two-int advisory namespace `1297044289` (`MOSA`), `1262636593` (`KBN1`) across preflight, reconciliation, migration, verification, and release. It SHALL compare the versioned canonical manifest v1 tuple (journal logical index/tag plus exact SQL-byte SHA-256) to the complete observed ledger mapping; count/set-only, timestamps, and physical insertion order are non-normative and insufficient.
+3. `K101-REQ-03`: PostgreSQL SHALL separate non-login platform database owner, non-login schema owner, dedicated `NOLOGIN SUPERUSER` `mosaic_extension_owner`, login migrator, dedicated login non-DDL data importer, non-login runtime capability, and login runtime roles. For PostgreSQL 17 + pgvector 0.8.2, `vector` is untrusted (`trusted` is absent and `relocatable=true`): only an externally controlled audited platform-bootstrap superuser session may `SET ROLE mosaic_extension_owner` for CREATE/UPDATE/SET SCHEMA, then `RESET ROLE`; the role has `rolcanlogin=false`, `rolsuper=true`, zero members, no runtime credential/Vault secret, and is never provided to app containers. It owns `mosaic_extensions`, fresh `vector`, and owner-bearing extension members, while `mosaic_schema_owner` receives only `USAGE` for type resolution and never ownership/`CREATE`/`ALTER`/`DROP`/member-change/default-privilege authority there. Superuser cannot be constrained by `GRANT`/`REVOKE`; this is identity/non-login/no-membership/external-control/audit isolation, not a false least-privilege claim. Extension operations require control-plane change, independent review, backup/rollback, maintenance window, and audit evidence. Managed targets that cannot establish this exact role are ineligible until an independently approved versioned provider-owned extension-owner profile exists; app/migrator ownership is never silently retained. Existing approved-owner extension relocation validates exact `pg_namespace.nspowner`, `pg_extension.extowner`, member ownership/schema/version, while legacy runtime-owned extension fails closed to a controlled shadow-database migration—never unsupported ownership alteration, catalog mutation, ownership adoption, or `DROP CASCADE`. Runtime, migrator, schema owner, importer, and all service roles must fail `SET ROLE`, catalog/direct `ALTER`/`UPDATE`/`DROP`/membership-change denial, role ownership, superuser/role-creation/schema-creation/TEMPORARY, unsafe membership, untrusted search path, missing grants, unauthenticated TLS, and immutable privilege drift checks. Application schema is fixed `mosaic` with exact `pg_catalog,mosaic` session path; historical public migrations remain byte-immutable legacy bootstrap only, every future Drizzle application declaration targets `mosaic`, and `vector` is explicitly qualified from non-writable `mosaic_extensions`. No config-derived SQL identifier is permitted.
+4. `K101-REQ-04`: `mosaicstack/stack` KBN-101-00 SHALL exclusively own `infra/pg-bootstrap/roles.sql`, `infra/pg-bootstrap/extensions.sql`, `infra/pg-bootstrap/README.md`, and bootstrap tests; KBN-101-05 SHALL exclusively own `tools/db/render-postgres-secrets.ts`, its tests, and current Compose/Portainer/two-gateway deployment declarations, consuming the versioned bootstrap interface without overlap. Environment IaC/Vault is named input and Mosaic deployment control plane/Jason is activation authority. Distinct runtime/migrator/importer URL, importer authenticated provider-version, DB-client CA, Gateway leaf, and PostgreSQL server key/certificate materials are provisioned before a production-like database starts. Importer and migrator have separate immutable URL/version copies at fixed `10002:10002`/`10003:10003` identities; runtime/unrelated containers receive neither importer material, attestation private key, or importer artifact. Runtime, migrator, and importer require their mounted CA plus `sslmode=verify-full`. Exact UID/GID/mode/rendering, service-DNS SANs, Vault/compose/Swarm consumer isolation, two-gateway pair ordering, server activation, pre-enforcement legacy-client drain and `hostssl` zero-plaintext-session proof, fresh/existing transition, CA-overlap rotation, TLS-only rollback, and standalone/federated/Swarm/two-gateway positive/negative TLS evidence are required. No application-generated production certificate or plaintext bootstrap exception is permitted.
+5. `K101-REQ-05`: KBN immutable relations SHALL permit the real runtime role INSERT/SELECT only and deny UPDATE/DELETE; parent retention remains RESTRICT/no-cascade. Role/password/Vault creation is external platform control, never application migration/source.
+6. `K101-REQ-06`: N-1 single-URL compatibility, rollout/rollback, Vault ownership/rotation/redaction, CI, installer, compose/Portainer, observability, and deployment handoffs SHALL be separately bounded one-card/one-PR work. Prepared slices remain inactive while current owner-runtime deployments stay N-1; Mosaic control plane/Jason alone authorizes one final atomic activation or rollback, with no force-on-red/bypass. KBN-101 planning itself SHALL not mutate production.
+7. `K101-REQ-07`: KBN-100 SHALL begin only after the KBN-101 foundation role/schema-boundary certificate; it SHALL rebase on that main head, restore generated Drizzle declaration/snapshot/journal consistency, and bound procedural immutable-table grant/trigger/backfill additions to its schema slice. KBN-101 real deployed-role immutable-operation certification SHALL complete after KBN-100 creates those relations and before KBN-105.
+
+### Acceptance criteria
+
+1. `AC-K101-01`: DTO/command-matrix tests prove required modes, PGlite exception, `mosaic-db-migrator --help|--run|--verify`/stable exits/argv refusal, public-import negative, every finite classified DDL/static-bypass inventory path and both harness pairs reject `DATABASE_URL`-only before connection/DDL, no migration-to-runtime fallback, and `db:push` refusal outside an allowlisted disposable DB. Before inventory, ownership, or status masking, the semantic fixture fails README's exact former commented code-fence generic-wrapper form and the user guide's exact former executable generic-wrapper form; source-consistency proves current `packages/storage/src/cli.ts` directly `execSync`s `pnpm --filter @mosaicstack/db db:migrate` and no `mosaic-db-migrator` bin exists, so runner-delegation documentation fails. The active `docs/guides/migrate-tier.md` route is inventoried to KBN-101-07 and proves runner-produced `--target-url-file /run/secrets/mosaic-migrate-target-url`, fixed paired provider-version file, and `--target-attestation-file /run/mosaic-attestations/migrate-target.v1.json`; runner-only signing/private-key isolation; Vault KV-v2 same-response version provenance, separate immutable generation mounts, importer CA, JCS/Ed25519 signature/key rotation/revocation, atomic artifact, expiry/replay, safe-fd secret-version/digest, canonical TLS/CA/server/database/role/manifest/schema bindings, dedicated non-DDL importer, consumer isolation/no log-oracle, and exact no-connection versus zero-DML rejection for missing/wrong/stale/replayed/tampered/wrong-key/substituted/generation-mismatched inputs. The full current non-normative docs inventory—including user guide, federation historical task/MILESTONES status, and non-operative SETUP—has an exact safe disposition. Scanner semantic checks reject automatic first-boot/startup extension/schema/migration wording, Compose-up-before-runner, init-script authority, production `.env`/monorepo auto-load/`EnvironmentFile=`/credential-export-or-argv/restart-as-secret-activation routes, and every unqualified operator-document `mosaic-db-migrator --run|--verify` hit regardless of named/normative/status classification. The exact former README/dev/deployment Compose-first sequences, former SETUP wording, exact former MILESTONES wording `pgvector extension installed + verified on startup`, former architecture-plan/PERFORMANCE/backlog runner routes, and any unqualified runner fixture fail before inventory masking. Only one `Held future procedure` Markdown section—bounded through the next equal-or-higher heading—may contain the explicit non-operative/no-current-command-authority form that names KBN-101-00/-03/-05 and preserves external bootstrap → TLS/roles → `mosaic-db-migrator --run` → `mosaic-db-migrator --verify` → Gateway/Compose readiness; every runner hit outside that section fails. The README assertion for the checked-in direct CI `pnpm --filter @mosaicstack/db run db:migrate` with `DATABASE_URL` passes only as active legacy N-1, uncertified, non-authorizing-as-an-operator-route status against an isolated disposable CI database pending KBN-101-06 removal—not as an ordinary operator or approved DDL-authority route. Only local PGlite data-layer work or non-PostgreSQL Compose is current (Gateway/Web local startup is held pending daemon/inherited/project-DSN rejection).
+2. `AC-K101-02`: Fixed namespace lock contention/crash/readiness/non-interference and exact manifest-v1 reconciliation tests prove no replica race/runtime auto-migration and fail closed on every missing/unknown/duplicate/ambiguous/corrupt/stale ledger state.
+3. `AC-K101-03`: Actual PostgreSQL 17 + pgvector 0.8.2 control-file, catalog, Drizzle-generation, vector-query/operator, fresh/approved-owner/legacy-shadow/partial/resume/rollback/N-1, and real deployed-role tests prove `trusted` absent/untrusted plus relocatability, external-superuser `SET ROLE` create/update/`RESET ROLE` audit, exact `rolcanlogin=false`/`rolsuper=true`/zero-membership/no-runtime-secret state, platform/schema/extension-owner/migrator/importer/runtime separation, `pg_extension.extowner` plus owner-bearing extension-member/schema/version assertions, and runtime/migrator/schema-owner/importer/all-service-role `SET ROLE`/ALTER/DROP/member-update denial. They also prove `pg_catalog,mosaic` per-session pool safety, `mosaic_extensions` qualification, identifier injection denial, ownership/membership/ledger-read/TEMP/default grants, and unsafe privilege denial.
+4. `AC-K101-04`: Disposable standalone, federated/Swarm, and two-gateway verified-TLS positives plus for both pairs missing CA/wrong CA/wrong SAN/sslmode downgrade, server/Gateway key mode, UID/GID, secret-consumer isolation, and legacy-drain/`hostssl` negatives prove server bootstrap, ordering, and readiness; PGlite is expressly excluded from this PostgreSQL evidence.
+5. `AC-K101-05`: Real runtime-role evidence proves INSERT/SELECT succeeds and UPDATE/DELETE fails for every frozen immutable KBN relation.
+6. `AC-K101-06`: N-1/atomic activation/rollback, Vault/CA-overlap rotation/redaction, health/operator behavior, CI/deployment handoff, independent exact-head security review, and terminal-green CI evidence the foundation before KBN-100; after KBN-100, the real deployed-role immutable-operation certificate and Ultron approval release KBN-105.
+
+**Normative implementation contract:** [`docs/native-kanban-sot/KBN-101-DB-ROLE-SPLIT.md`](./native-kanban-sot/KBN-101-DB-ROLE-SPLIT.md). `ASSUMPTION:` existing `standalone` and `federated` are all PostgreSQL production-like modes; any new PostgreSQL tier inherits these requirements until an explicit versioned amendment.
+
+---
+
+## Tess Interaction Agent Workstream (TESS)
+
+### Problem and Objective
+
+Jason needs one durable, operator-facing Mosaic agent outside Hermes that is reachable through a dedicated Discord channel and CLI, can attach to and operate the Mosaic fleet and transitional Hermes agents, and preserves context across restarts and compaction. Mos remains the coding/general fleet orchestrator; Tess is the complementary human interaction, visibility, control, and migration agent.
+
+The objective is to ship **Tess** (from _tessera_, a piece of a mosaic) as a Pi-native, GPT-5.6 Sol agent with high reasoning. Tess must use Mosaic-owned contracts and plugins so Hermes can be replaced incrementally rather than becoming a permanent architectural dependency.
+
+### Scope
+
+#### In Scope
+
+1. `TESS-ARP-001`: A runtime-neutral `AgentRuntimeProvider` contract supporting `listSessions`, `streamSession`, `sendMessage`, `terminate`, `getSessionTree`, `attach`, health, capability discovery, and normalized events/errors.
+2. `TESS-PI-001`: A long-running Pi-native Tess agent profile/service pinned to GPT-5.6 Sol with high reasoning, explicit tool policy, lifecycle hooks, durable checkpoints, and restart recovery.
+3. `TESS-DSC-001`: Dedicated Discord channel binding to Tess through the Mosaic gateway, with allowlists/RBAC, thread/reply policy, streaming, attachments, approvals, and correlation IDs.
+4. `TESS-CLI-001`: `mosaic tess` CLI commands for chat, status, session listing, attach/detach, send/steer/stop, provider health, and recovery.
+5. `TESS-FLT-001`: Fleet plugin capabilities for roster/status/heartbeat inspection, message delivery, session hierarchy, safe attach, and controlled restart/recovery.
+6. `TESS-MOS-001`: Explicit Mos coordination boundary and tools: hand off orchestration requests, observe mission/task state, receive results, and never silently compete for orchestration authority.
+7. `TESS-HRM-001`: Transitional Hermes adapter for profiles/agents, sessions, streaming/messages, Kanban, skills, memory, tools, cron, and health, using capability negotiation and fail-closed unsupported operations.
+8. `TESS-MEM-001`: Unified memory/retrieval plugin with scoped search/recent/capture/stats, startup context injection, provenance, redaction, namespace isolation, and flat-file/project truth precedence.
+9. `TESS-STA-001`: Durable agent state, inbox, handoff, compaction-recovery, and resume reconstruction.
+10. `TESS-PLG-001`: Plugin/tool catalog covering runtime bootstrap, repository/PR workflow, fleet diagnostics, incident-safe read operations, Discord interaction, and extensible MCP/skill discovery.
+11. `TESS-TRN-001`: Replaceable transport providers: tmux/fleet now, Matrix/native Mosaic transport later, with no Discord/CLI business logic coupled to transport details.
+12. `TESS-SEC-001`: RBAC, per-operation authorization, explicit approval for destructive/privileged/customer-visible actions, audit events, secret/PII redaction, tenant isolation, and bounded command execution.
+13. `TESS-SEC-002`: Command execution SHALL enforce declared scope/role server-side; admin/system and destructive operations SHALL require policy-bound durable approval.
+14. `TESS-SEC-003`: Every session list/read/attach/send/terminate operation SHALL enforce server-derived owner and tenant scope; guessed or client-supplied IDs SHALL grant no authority.
+15. `TESS-SEC-004`: MCP tools SHALL derive actor/tenant from authenticated context and SHALL NOT accept caller-controlled identity fields.
+16. `TESS-SEC-005`: Discord plugin ingress SHALL authenticate service identity, enforce guild/channel/user allowlists, propagate correlation/message IDs, and reject replay.
+17. `TESS-SEC-006`: Secret/PII classification and redaction SHALL occur before persistence and before channel egress, including tool metadata and authentication flows.
+18. `TESS-SEC-007`: Approvals SHALL be one-time, expiring, actor/tenant-bound, and cryptographically bound to the exact structured action digest.
+19. `TESS-SEC-008`: Ingress, provider sends, tool side effects, and responses SHALL use durable inbox/outbox/checkpoints and idempotency records for restart-safe replay.
+20. `TESS-SEC-009`: Garbage collection and retention SHALL be session/tenant scoped unless executed as a separately authorized and audited system-wide job.
+21. `TESS-OBS-001`: Structured logs, traces, health/readiness, provider latency/errors, session lifecycle, tool audit, and actionable recovery diagnostics.
+22. `TESS-MIG-001`: Capability inventory and staged Hermes-to-Mosaic migration matrix with coexistence, cutover, rollback, and deprecation gates.
+
+#### Out of Scope
+
+1. Replacing Mos as coding/general fleet orchestrator.
+2. Making Hermes the Mosaic core or coupling Mosaic domain logic to Hermes schemas.
+3. Migrating every historical chat verbatim; only policy-compliant indexed summaries and user-selected sessions are migrated.
+4. Unrestricted shell execution from Discord.
+5. Full web UI parity in the first Tess operational milestone; gateway contracts must remain web-consumable.
+6. Replacing tmux before Matrix/native transport reaches operational parity.
+
+### Stakeholder and User Requirements
+
+- Jason must be able to converse with the same Tess session from Discord and CLI.
+- Jason must be able to see what is running, stale, blocked, or unhealthy without attaching manually to every session.
+- Jason must be able to attach to Tess and authorized fleet sessions through supported CLI controls.
+- Tess must collaborate with Mos and the fleet while preserving a single clear orchestration authority.
+- The system must migrate useful Hermes/OpenClaw capabilities intentionally, with evidence, instead of copying implementations wholesale.
+
+### Non-Functional Requirements
+
+1. **Security:** default-deny provider/tool capabilities, least privilege, no secrets in logs/prompts/commits, Discord user/channel authorization, and auditable approvals.
+2. **Reliability:** durable inbox/checkpoints; idempotent message handling; reconnect with bounded backoff; no message loss or duplicate execution across gateway restart.
+3. **Performance:** first acknowledgement within 2 seconds when connected; streamed agent output begins within 5 seconds excluding model/provider delay; status reads return within 2 seconds under nominal local conditions.
+4. **Observability:** every ingress message and resulting provider/tool operation carries a correlation ID across Discord, gateway, Tess, provider, and audit events.
+5. **Maintainability:** channel, runtime, transport, memory, and external-agent integrations remain adapter-based with contract tests.
+6. **Privacy:** only scoped context enters external runtimes; persisted messages/memories follow retention and redaction policy.
+7. **Portability:** Tess runs through Pi/Mosaic contracts and does not require Hermes to start or serve native Mosaic operations.
+
+### Acceptance Criteria
+
+1. `AC-TESS-01`: A dedicated Discord channel and `mosaic tess chat` connect to one durable Tess session and stream responses bidirectionally.
+2. `AC-TESS-02`: `mosaic tess status|sessions|tree|attach|send|stop` operate against authorized provider capabilities with stable typed outputs and actionable errors.
+3. `AC-TESS-03`: Tess runs GPT-5.6 Sol at high reasoning and its effective runtime/model/tool policy is visible through status without exposing credentials.
+4. `AC-TESS-04`: Tess can inspect and message the Mosaic fleet, hand orchestration work to Mos, and demonstrate that Tess does not independently claim Mos-owned orchestration work.
+5. `AC-TESS-05`: Hermes adapter demonstrates session listing, streaming/message delivery, hierarchy mapping, and at least one approved capability in each of Kanban, skills, memory, tools, and cron—or reports unsupported capabilities fail-closed.
+6. `AC-TESS-06`: Restart/compaction test preserves session identity, pending inbox, last durable checkpoint, and a resumable handoff without duplicate side effects.
+7. `AC-TESS-07`: Unauthorized Discord users/channels, cross-tenant access, unsafe tool calls, forged approvals, and sensitive-output cases are denied and audited.
+8. `AC-TESS-08`: tmux/fleet and Matrix/native transport implementations pass the same provider contract suite; Matrix may remain non-default until readiness gates pass.
+9. `AC-TESS-09`: Baseline quality gates, unit/integration/contract tests, Discord+CLI E2E, restart/recovery tests, independent code review, and security review are green.
+10. `AC-TESS-10`: Migration matrix documents every audited Hermes/OpenClaw capability as native, adapted, deferred, or rejected, with cutover and rollback evidence.
+11. `AC-TESS-11`: User, admin, developer, API/OpenAPI, operations/recovery, and plugin-authoring documentation is current and linked from the sitemap.
+
+### Constraints, Dependencies, Risks, and Assumptions
+
+- Dependency: Mosaic gateway remains the single API surface; Pi is the native runtime; Valkey/PostgreSQL provide canonical durable state where required.
+- Dependency: Discord bot credentials and dedicated channel ID are deployment secrets provisioned outside source control.
+- Risk: Tess could drift into a second orchestrator. Mitigation: explicit role policy, Mos handoff contract, authority checks, and E2E boundary tests.
+- Risk: broad Hermes compatibility can freeze legacy semantics into Mosaic. Mitigation: Mosaic-owned normalized contracts and capability negotiation.
+- Risk: Discord creates a privileged remote-control surface. Mitigation: pairing/allowlists, RBAC, approvals, rate limits, audit, and safe tool classes.
+- Risk: transcript ingestion can violate privacy or overload memory. Mitigation: scoped opt-in import, redacted summaries, provenance, retention, and deduplication.
+- Risk: current root filesystem has limited headroom. Mitigation: isolated worktrees, no duplicated dependency installation unless required, and cleanup only after active-lane verification.
+- `ASSUMPTION:` The public name is **Tess**, because the user requested a name and the tessera/Mosaic relationship is distinctive; config must permit later display-name changes without renaming APIs or storage keys.
+- `ASSUMPTION:` The dedicated Discord channel ID and final guild policy will be supplied/provisioned during deployment, so implementation uses explicit configuration and fail-fast startup validation.
+- `ASSUMPTION:` tmux/fleet is the production transport for the first operational milestone; Matrix/native transport is implemented behind the same contract and promoted only after parity/reliability verification.
+- `ASSUMPTION:` Project/task truth remains in canonical Mosaic/project stores; semantic memory systems are retrieval/mirror layers, not hidden authorities.
+
+### Testing and Delivery Intent
+
+Delivery uses five gated milestones: runtime contracts/security; Pi service/state; Discord/CLI; fleet/Hermes/plugin suite; migration/Matrix/recovery/qualification. Every source-code task requires tests, independent review, a PR to `main`, terminal-green CI, and issue/task closure. Production activation additionally requires a clean-host Pi launch, dedicated Discord channel smoke test, CLI attach test, restart/recovery drill, and rollback procedure.
+
+---
+
+## Official Channel Plugin Workstream (#756)
+
+### Problem and Objective
+
+The Discord plugin currently couples Discord event handling, gateway bridging, and reply routing in one implementation and activates only on mentions. Mosaic needs an official channel adapter that behaves the same no matter whether the bound logical agent currently runs through Claude, Codex, Pi, OpenCode, or a future harness. The Discord connection and conversation address must remain stable while the gateway changes the runtime provider behind that logical session.
+
+The objective is to make Discord the first implementation of a transport-neutral official channel contract, with explicit authorization and deterministic channel/thread routing that future Matrix, Slack, and other adapters can share.
+
+### Scope
+
+#### In Scope
+
+1. `CHN-001`: Transport-neutral channel adapter, route, message, attachment, authorization-principal, response-target, and health contracts in `@mosaicstack/types`, including trusted per-binding logical-agent configuration selection.
+2. `CHN-002`: Stable channel conversation addresses based on logical agent plus channel/thread identity; harness, model, and runtime-provider IDs are forbidden from channel session keys.
+3. `DSC-001`: An authorized untagged message in a configured agent-bound channel routes to the agent and receives its response in that channel.
+4. `DSC-002`: A bot mention in a configured parent channel creates a Discord thread, or reuses the thread already attached to that same native message; the mentioned turn and subsequent thread turns route and respond in that thread.
+5. `DSC-003`: A message already inside an authorized thread inherits authorization from its configured parent and never attempts a nested thread.
+6. `DSC-004`: Guild, parent channel, user, pairing, and role authorization remains default-deny before thread creation or gateway dispatch.
+7. `DSC-005`: Discord service authentication, HMAC envelope integrity, replay protection, attachments, approvals, response chunking, and correlation behavior remain intact.
+8. `DSC-006`: The Discord adapter exposes lifecycle and health behavior through the shared channel contract without importing a harness SDK.
+
+#### Out of Scope
+
+1. The logical-agent lease, fencing epoch, execution grant, checkpoint, or cross-harness takeover implementation tracked by #754/#755.
+2. Dynamic Discord authorization administration in the web UI.
+3. Multi-guild tenant isolation, DMs, slash commands, voice, reactions, or production bot deployment.
+4. Implementing Matrix or Slack adapters in this slice.
+
+### Non-Functional Requirements
+
+1. **Security:** no thread or dispatch side effect occurs until guild, parent channel, user, pairing, role, and bounded per-user/channel rate checks pass; attachment metadata is shape- and size-bounded; credentials never enter source, messages, session keys, or logs.
+2. **Portability:** channel contracts and stable conversation IDs contain no Claude, Codex, Pi, OpenCode, model, process, or provider-specific field; each configuration-owned binding selects its trusted logical agent without changing the channel identity.
+3. **Reliability:** repeated messages for one channel/thread resolve the same conversation handle; reconnecting the adapter does not require a harness-specific rebinding.
+4. **Maintainability:** Discord-specific API translation stays in the Discord package; gateway and future adapters depend on transport-neutral contracts.
+5. **Observability:** thread creation or routing failure is reported without message content or credential material.
+
+### Acceptance Criteria
+
+1. `AC-CHN-01`: Contract and behavior tests prove the plugin route contains only logical agent plus channel/thread identity and produces the same stable conversation handle regardless of underlying harness selection.
+2. `AC-CHN-02`: A mentioned authorized parent-channel message creates a thread (or reuses its already-attached thread), dispatches to the thread conversation, and targets the response to that thread.
+3. `AC-CHN-03`: An untagged authorized parent-channel message dispatches to the parent conversation and targets the response to the parent channel.
+4. `AC-CHN-04`: Untagged follow-ups inside an authorized thread dispatch and respond in that same thread without creating a nested thread.
+5. `AC-CHN-05`: Unauthorized guilds, channels, users, unpaired users, insufficient roles, and rate-limited senders produce no thread and no gateway dispatch.
+6. `AC-CHN-06`: Shared channel contracts are exported from `@mosaicstack/types`, Discord implements the lifecycle/health seam, and no harness SDK is imported by the plugin.
+7. `AC-CHN-07`: Focused routing/auth tests, package tests, typecheck, lint, formatting, coverage, independent code/security review, and terminal-green CI pass.
+
+### Constraints, Risks, and Assumptions
+
+- Dependency: Mosaic gateway remains the policy, durable-session, audit, and runtime-provider boundary.
+- Constraint: This work must not modify orchestrator-to-Pi migration or #754/#755 lease/fencing files.
+- Risk: accepting untagged messages could create noisy or unintended agent input. Mitigation: only explicitly configured channels and paired, role-authorized users are accepted, with bounded per-user/channel message and thread rates.
+- Risk: Discord thread creation can fail because of channel permissions, archived state, or API rate limits. Mitigation: fail without dispatching a turn whose response destination cannot be honored, and emit sanitized diagnostics.
+- `ASSUMPTION:` Configured channels are dedicated agent interaction surfaces, so authorized untagged human messages are intentional agent input.
+- `ASSUMPTION:` Mention in a parent channel selects a public thread; messages already in a thread remain there because Discord has no nested threads.
+- `ASSUMPTION:` One Discord bot may serve multiple configuration-owned logical-agent bindings.
+- `ASSUMPTION:` Static allowlists and paired-user roles are the authorization administration surface for this slice.
+
+### Testing and Delivery Intent
+
+Use TDD for remote-ingress routing and permission boundaries. Required evidence includes parent-channel mention, untagged parent message, existing-thread follow-up, existing-thread mention, thread reuse, unauthorized side-effect denial, stable harness-neutral conversation identity, adapter health, and regression coverage for signed envelopes and approvals. Deliver through issue #756, a reviewed squash PR to `main`, terminal-green CI, and issue closure.
+
+---
+
+## Mos Runtime Portability Workstream (MOS-PORT)
+
+### Problem and Objective
+
+Mos is currently identified partly by a harness-native session and communication process. Replacement/rebinding exists, but no gateway-enforced logical identity or fencing prevents a stale harness from continuing to reply or execute effects after takeover.
+
+The objective is to make Mos a server-derived logical Mosaic identity whose authority can move safely among runtime connectors. The gateway owns identity, lease, policy, and audit; harnesses remain replaceable adapters.
+
+### M1 Requirements
+
+1. `MOS-PORT-ID-001`: Define a normalized logical-agent identity independent of Claude Code, Pi, Codex, tmux, Matrix, and provider-native session IDs.
+2. `MOS-PORT-LEASE-001`: Persist one exclusive connector lease per tenant/logical-agent/binding with CAS acquisition, monotonic fencing epoch, TTL, heartbeat, explicit release, and takeover.
+3. `MOS-PORT-FENCE-001`: Bind every connector dispatch/execution grant to the current server-derived tenant, logical identity, binding, connector, scopes, expiry, and lease epoch.
+4. `MOS-PORT-FENCE-002`: Reject and audit stale, expired, forged, cross-tenant, cross-binding, and unauthorized grants before connector, channel, provider, or tool side effects.
+5. `MOS-PORT-OBS-001`: Emit credential-safe correlation/audit events for lease acquire, renew, takeover, reject, release, and expiry.
+6. `MOS-PORT-ARCH-001`: Runtime/provider adapters consume normalized lease context without adding harness-native schemas to Mosaic core.
+
+### M1 Acceptance Criteria
+
+1. `AC-MOS-PORT-01`: Two contenders for one binding cannot simultaneously hold current authority under concurrency.
+2. `AC-MOS-PORT-02`: Successful takeover increments the fencing epoch and every operation from the old epoch fails closed before side effects.
+3. `AC-MOS-PORT-03`: Gateway/database restart preserves lease and epoch state; expired leases can be recovered only through the authorized takeover path.
+4. `AC-MOS-PORT-04`: Cross-tenant, cross-agent, cross-binding, forged, and expired lease/grant cases are denied and audited.
+5. `AC-MOS-PORT-05`: Unit, migration, repository close/reopen, concurrency, abuse, gateway integration, independent security review, CI, and documentation gates pass.
+
+### Deferred to Later #754 Milestones
+
+Canonical checkpoint/handoff payloads, exactly-once connector receipts, concrete Claude/Pi/Codex adapters, channel cutover, and full cross-harness failover/rollback E2E are explicitly out of M1 scope.
+
+---
+
+## Workspace placement guard hardening (#1174)
+
+### Problem and objective
+
+The Bash pre-tool guard must prevent Git checkouts and repository state from being placed under
+`$HOME` without refusing ordinary Git commands merely because a source, option value, branch name,
+or metadata mentions `$HOME`. A guard that over-blocks routine work is unsafe because operators
+will route around it.
+
+### Scope and requirements
+
+1. `WPG-REQ-01`: `git clone` and `git worktree add` placement SHALL be judged from their placement
+   operands, not from every HOME-shaped word in the command.
+2. `WPG-REQ-02`: Clone sources, references, templates, environment assignments, and non-placement
+   worktree metadata MAY resolve under HOME when all placement operands resolve elsewhere.
+3. `WPG-REQ-03`: Both attached and separate-value `--separate-git-dir` forms SHALL remain placement
+   operands and SHALL be refused when they resolve under HOME.
+4. `WPG-REQ-04`: Option classification SHALL account for Git's rule-generated boolean negations
+   without relying on an enumerable allowlist of flag spellings.
+5. `WPG-REQ-05`: Quote removal, escapes, shell command boundaries, redirections, and end-of-options
+   handling SHALL preserve existing fail-closed checkout coverage.
+6. `WPG-REQ-06`: Absolute placement aliases SHALL resolve shell-known HOME spellings, dot segments,
+   repeated separators, and existing symlink parents before the HOME boundary comparison.
+7. Relative targets whose effective path depends on the shell cwd are out of scope and tracked by
+   #1197.
+
+### Acceptance and verification
+
+1. Git's own option parser accepts each tested flag, including generated `--no-*` forms, while the
+   guard allows a HOME-valued source with an explicit safe destination.
+2. Equivalent clone and worktree fixtures cover rule-generated negations and remain discriminating
+   against the prior head where the defect existed.
+3. Real HOME destinations and both `--separate-git-dir` forms remain blocked, including placements
+   after shell command boundaries.
+4. The full hermetic guard suite, syntax/static checks, adversarial probes, independent review, and
+   terminal-green CI pass before merge.
+5. Any option-classification residual is documented with its deliberate failure direction.
+
+### Constraints, risks, and assumptions
+
+- Security and usability are co-equal: neither a placement bypass nor routine over-block is an
+  acceptable repair.
+- `ASSUMPTION:` The value-taking option surface exposed by the installed Git version is closed and
+  measurable through Git's own parser/help output; rationale: boolean flags are rule-generated,
+  while separate-value options have explicit grammar and must be classified as such.
+- Risk: a future Git release may add a new value-taking placement option. Mitigation: document the
+  chosen residual direction and pin every currently supported placement option in behavior tests.
+- Risk: a symlink can be replaced after pre-execution canonicalization. Mitigation: resolve every
+  existing parent physically and document the remaining inherent TOCTOU window; the worktree helper
+  remains the authoritative path-derivation mechanism, with atomic closure tracked by #1199.
+
+---
+
+## Release Integrity Workstream (RI, #1275)
+
+### Problem and objective
+
+At `next` 476db12b (review of 2026-08-17), publication from `next` is not bound to the full verification pipeline for the same commit: the publish pipeline's publish steps depend on `build` only, while ordinary push CI excludes `next`. Public Forge/MACP paths contain false-success placeholders: a stub executor that reports `completed` with exit zero, planning/remediation gates that execute literal `true`, a review gate that echoes an approving verdict, and a gate runner that treats empty commands and unimplemented CI-provider gates as passing. Shipping UI surfaces can render a failed fetch as an empty, healthy collection.
+
+Objective: for alpha 0.0.50, the release cannot publish, report, or display work state that the repository has not actually verified. Decisions SDLC-D-033 through SDLC-D-038 (Jason, 2026-08-17) scope this floor; full decision text and required-behavior lists live in jarvis-brain `docs/plans/2026-08-16_mosaic-stack-sdlc-protocol.md` and `data/decisions/mosaic-stack-sdlc-protocol.json`. This section restates only the normative requirements.
+
+### Normative requirements
+
+1. **RI-N1 Exact-commit publication verification (SDLC-D-034).** One canonical terminal verification command performs self-contained re-verification in the publish pipeline against the job's checked-out commit before any external publication effect. The command contains or invokes the complete mandatory verification set (semantic parity with the PR merge gate, including sanitization, upgrade-guard, typecheck, lint, format check, tests, and build); CI and publication do not maintain separate semantic checklists. Every publish step depends on the verification step in the executable pipeline DAG. Provider commit identity and `git rev-parse HEAD` must identify the same commit. Missing, skipped, cancelled, stale, or inconclusive checks fail closed. Documentation-only runs may skip publication but cannot bypass verification when a publication effect will occur. A negative control must prove that a broken check blocks every publish step.
+
+2. **RI-N2 Fail-closed Forge/MACP with explicit simulation (SDLC-D-035).** Simulation requires explicit caller intent (e.g. `--simulate`) and produces a distinct typed `simulated` state that can never satisfy dependencies, acceptance criteria, gates, merge, or release. Normal execution exits nonzero with a typed capability failure when a required executor, reviewer, command, or CI provider is absent — no stub completion, no literal-`true` gates, no synthetic approvals, no empty-command passes. A manual gate with no automation enters a waiting state; it does not pass. Positive tests prove explicit simulation still works; negative controls prove simulation and every missing-provider case cannot advance lifecycle state.
+
+3. **RI-N3 One transitional PRD authority (SDLC-D-036).** `@mosaicstack/prdy` structured storage under `docs/prdy/`, driven by `mosaic mission --plan`, is the authoritative PRD representation for the alpha. `mosaic prdy` either routes through the same application service or operates only as an explicit, named Markdown import/export adapter; `docs/PRD.md` is not a peer authority. `mission --plan` must persist the mission↔PRD linkage (mission id/version, PRD id/version, selected requirements). Markdown output is a generated view carrying source identity; editing it cannot mutate authority silently. Import is explicit, validated, and conflict-aware (proposed successor, never overwrite). Structural validity is separate from approval.
+
+4. **RI-N4 One quality-rails evaluator (SDLC-D-037).** The TypeScript quality-rails package is the sole authoritative evaluator. A complete probe inventory maps every current TypeScript and shell check to one canonical check with disposition (preserve/strengthen/retire, each named). Effective shell enforcement probes are absorbed before their independent paths retire; expected-file presence alone is not parity. The evaluator returns typed results (`passed`/`failed`/`blocked`/`error`/`not-applicable`) with check version, subject, and reason; missing implementation, missing input, unknown check, process error, timeout, or malformed output can never become `passed` or an unqualified skip. Check definitions and policy are versioned and digested. Shell commands become thin adapters with no separate verdict logic. The canonical terminal verification command (RI-N1) invokes this evaluator rather than duplicating its logic. Contract, parity, and negative-control tests are required, plus independent review of probe equivalence.
+
+5. **RI-N5 Consequence-aware stale UI (SDLC-D-038).** Mission Control distinguishes typed freshness states (`current`, `stale`, `partial`, `unknown`, `unavailable`) rather than inferring from empty arrays or null. A failed fetch never renders as an empty healthy collection. Last-known data may display for situational awareness only with source identity, version, and age visibly labeled; any derived completion/assurance/release verdict whose inputs are stale becomes `unknown`; all state-changing actions are disabled until fresh state loads and is revalidated. With no verified snapshot, surfaces show an explicit unavailable state. Cache corruption, cross-workspace data, schema mismatch, and version regression invalidate the snapshot. Tests cover the failure matrix (network, auth, malformed, partial, corruption, stale age, schema mismatch, recovery, stale-action rejection) with negative controls proving no case yields a current green verdict or enabled mutation.
+
+### Acceptance criteria
+
+- AC-RI-1: A push to `next` that fails any mandatory verification step publishes nothing (no npm package, no image), demonstrated by a checked-in negative control and by pipeline evidence on a real `next` publish run where the verification step is green and every publish step depends on it.
+- AC-RI-2: With no executor/reviewer/CI provider wired, Forge and MACP normal runs exit nonzero with typed capability failures; with `--simulate`, runs complete but every result is typed `simulated` and cannot satisfy any gate, dependency, or completion state — proven by unit tests including negative controls.
+- AC-RI-3: A PRD created or revised through either `mosaic mission --plan` or `mosaic prdy` resolves to one authority under `docs/prdy/` with stable identities and versions; the mission↔PRD linkage survives restart; a Markdown export is labeled as generated and cannot silently become a second writer; divergent legacy content blocks baseline claims until explicitly resolved — proven by contract tests.
+- AC-RI-4: `quality-rails check` through any entry point (TS CLI, framework shell adapter) returns the same typed verdict for the same subject; the probe inventory names every legacy check's disposition; a deliberately broken probe fails closed — proven by contract/parity/negative-control tests and independent review of probe equivalence.
+- AC-RI-5: No shipping surface renders a failed fetch as an empty healthy state; stale/partial/unavailable states are typed, labeled, and mutation-disabled — proven by the failure-matrix tests.
+- AC-RI-6: All cards merged to `next` via squash PR with terminal-green CI; release evidence for 0.0.50 records commit, verification run, and published artifacts.
+
+### Out of scope
+
+The canonical dispatcher/control-plane vertical slice (work graph, execution attempts, fenced leases, typed check-in, independent verifier dispatch) is decided post-alpha (SDLC-D-033, option B). Multi-pipeline verification certificates (SDLC-D-034 option B) are post-alpha. Full AF-1..AF-4 objective matrices and Mission Control portfolio surfaces are post-alpha.
+
+## Official CLI Capability and Tool Migration Workstream (T78)
+
+Normative contract on integration trunk `next`:
+[docs/requirements/cli-capability-migration.md](./requirements/cli-capability-migration.md):
+migrates agent-facing operations from directly invoked scripts into documented, first-class
+`mosaic` CLI command groups, together with the central-registry resolver, capability catalog,
+adapter boundary, and phased legacy-tool-tree decommission the migration requires. The contract
+carries its own implementation hold and delivery stages.
@@ -0,0 +1,35 @@
+---
+kind: record
+status: superseded
+---
+
+# PRD rev0 — archive record
+
+`PRD.md` in this directory is the 2026-08-26 North Star PRD, archived **verbatim** at
+ratification of rev1 (2026-09-01). It is byte-identical to `origin/next:docs/PRD.md` at
+commit `9aa4983c` (SHA-256
+`60cc2f98697471850caa3440d79139d70f67eda585a2ee465fdcd517bc36afdf`). Per GOV.1 the archived
+bytes are never edited — not even to repair links — so the digest stays verifiable.
+
+**Its relative links were written for `docs/PRD.md` and do not resolve from this directory.**
+That is an accepted, intentional consequence of archive-never-edit (owner disposition: the
+control-plane-surfaces lane, 2026-09-02, review `CPS-PRD-REV1-REVIEW-Q90` F3). Resolve them
+with this table; every target still exists in the tree.
+
+| Link text in `PRD.md` (lines)                                   | Resolves to                                                                                                                |
+| --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `./archive/PRD-v0.1.md` (17)                                    | [../../archive/PRD-v0.1.md](../../archive/PRD-v0.1.md)                                                                     |
+| `./ROADMAP.md` (18, 177, 249)                                   | [../../ROADMAP.md](../../ROADMAP.md)                                                                                       |
+| `./requirements/native-kanban-sot.md` (98)                      | [../../requirements/native-kanban-sot.md](../../requirements/native-kanban-sot.md)                                         |
+| `./fleet/NORTH_STAR.md` (181)                                   | [../../fleet/NORTH_STAR.md](../../fleet/NORTH_STAR.md)                                                                     |
+| `./fleet/FLEET-CONFIG-DOCS-IA-CHECKLIST.md` (444)               | [../../fleet/FLEET-CONFIG-DOCS-IA-CHECKLIST.md](../../fleet/FLEET-CONFIG-DOCS-IA-CHECKLIST.md)                             |
+| `./fleet/LEGACY-EXAMPLE-PROFILE-DISPOSITION-INVENTORY.md` (444) | [../../fleet/LEGACY-EXAMPLE-PROFILE-DISPOSITION-INVENTORY.md](../../fleet/LEGACY-EXAMPLE-PROFILE-DISPOSITION-INVENTORY.md) |
+| `./TASKS.md` (462)                                              | [../../TASKS.md](../../TASKS.md)                                                                                           |
+| `./native-kanban-sot/KBN-101-DB-ROLE-SPLIT.md` (623)            | [../../native-kanban-sot/KBN-101-DB-ROLE-SPLIT.md](../../native-kanban-sot/KBN-101-DB-ROLE-SPLIT.md)                       |
+| `./requirements/cli-capability-migration.md` (906)              | [../../requirements/cli-capability-migration.md](../../requirements/cli-capability-migration.md)                           |
+
+Rule for future archives (recorded here; GOV.1 carries the general archive contract): every
+`docs/PRDs/<date>_PRD_revN/` archived from a different original location ships a `README.md`
+like this one — digest, original path, and a link-resolution table — instead of edited bytes.
+
+Current revision: see [`docs/PRD.md`](../../PRD.md).
@@ -0,0 +1,85 @@
+---
+id: AUTHN.1
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# AUTHN.1 — Authentication accounts
+
+Agent-side provider credentials: the accounts seats use to reach providers.
+(Human login identity is D10 territory — better-auth as system of record — and
+is out of this section's scope.)
+
+## Authentication configuration surface (WebUI page + CLI)
+
+| Control                        | Notes                                                                                                                    |
+| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
+| in-browser OAuth establishment | the OAuth flow runs in-browser; whether the backing terminal flow is tmux-bridged is open: [[GOV.5-open-questions]] Q-N1 |
+| configured accounts list       | provider, mode (OAuth/API), status, holder                                                                               |
+| force renew                    |                                                                                                                          |
+| deactivate                     | deactivated accounts drop out of every seat/harness selector                                                             |
+| allowed harnesses              | which harnesses may use this account                                                                                     |
+
+## Custody rules
+
+- Secrets live with the **credential broker** (OpenBao/Vault or flat files per
+  deployment mode — D3), never in the brain tree, never in manifests, never in
+  Postgres records. Enforced role manifests declare
+  `credentials: {store: none, providerTokens: denied}` — the enforced roles
+  hold no credentials at all; accounts are a launcher/broker concern.
+- Multi-account per provider is a requirement (onboarding D4 already captures
+  multi-account enrollment).
+- Account shape in the seat record (single account vs per-provider map) is
+  open: [[GOV.5-open-questions]] Q-D2.
+
+## Credential-broker custody rules (pulled 2026-08-31, generalized from the vault draft)
+
+- Reads require a token scoped to the needed paths; provisioning and writes go
+  through a declared channel with documented purpose. An ordinary role never
+  mints credentials or creates production paths.
+- Canonical secret path: `environment / service / component / secret-name`,
+  lowercase kebab-case, nothing sensitive encoded in the path; environments
+  never cross-reference each other's mounts. Standard field names
+  (`username`/`password`, `token`, `host`/`port`/`url`).
+- Only the needed field is extracted into the consuming process; values are
+  never echoed to logs or transcripts — read success is proven by field
+  presence and digest, never by printing the value.
+- Least privilege, short-lived tokens, no local copies, immediate rotation on
+  compromise; every access audited by the broker.
+
+## E2 inputs (triage 2026-08-31; see [[GOV.2-docs-inventory]])
+
+**Canonical ground truth**: `ADMIN-GUIDE/security/sso-providers.md` (D10 ground
+truth: better-auth + Authentik/WorkOS/Keycloak OIDC).
+**Pending pulls**: DRAFT S2 `identity-lifecycle.md` (D10 + the #1430 bootstrap
+fix) and `custody-schema.md`; brain `docs/guides/proposed/operations/vault.md`
+(credential-broker custody rules this section states without operational detail).
+
+## S2 contract feed (extraction 2026-08-31)
+
+Full extraction record: lane `S2-EXTRACTION-2026-08-31.md` (per-contract cores, dependency edges, ruling cross-checks). Pulls binding on this section (identity-lifecycle, contract 4, plus
+wizard AUTHN clauses):
+
+- better-auth tables are the **only** account system of record (D10); IdPs are
+  login methods only; account creation grants nothing.
+- `registration_mode` open/invite/closed, defaults **closed** post-bootstrap,
+  forced closed during the epoch, enforced at a better-auth hook.
+- Bootstrap/first-admin invariant (#1430): zero-to-one-admin exactly once per
+  epoch, one atomic transaction, durable fail-closed `bootstrap_state`,
+  re-runnable; first-admin-via-SSO runs as a bootstrap-writer transaction,
+  never JIT. **v1 first admin is password-only — a disclosed PRD deviation.**
+- JIT defaults OFF per-provider always; JIT users get `member`, never
+  elevated; **role/authorization attributes are never mapped from IdP
+  claims**. Linking keyed `(issuer, subject)`; explicit linking = step-up
+  reauth ≤10 min; automatic linking gated by off-by-default
+  `trusted_for_linking` + verified email.
+- Deactivation (ban) must bound all entry paths — **live defect: the
+  admin-bearer-token path does not check banned status**. Deletion deferred;
+  the existing hard-delete endpoint and `mosaic auth users delete` are
+  mandated for removal.
+
+## Seat auth shape ruling (Q-D2, Jason 2026-09-01)
+
+Per-provider map in `profile.json`, values are credential-broker references —
+never secret material. The broker custody rules above govern resolution;
+extraction stays field-scoped and digest-proven.
@@ -0,0 +1,146 @@
+---
+id: AUTHZ.1
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# AUTHZ.1 — Capability authority, enforcement, and accepted risk
+
+The agent-side authority model: what binds a seat, where it is enforced, what
+is closed by construction, and what is accepted as residual risk. Sources: the
+L2 authorization contracts, `mosaic-core` (measured 2026-08-31), and the lane's
+`AUTHORIZATION-GAPS.md`.
+
+## Glossary
+
+**Privilege escapation** _(Jason, 2026-08-31)_ — the outcome class in which an
+agent exercises authority it was never granted, regardless of mechanism.
+Deliberately collapses escalation and misdirection: the outcome is identical;
+the distinction matters only when choosing a control.
+
+## Authority composition is pure intersection
+
+```
+role capability ceiling
+  ∩ assignment scope ∩ lease scope ∩ workflow state
+  ∩ target policy ∩ trusted backend availability
+  = effective capability grant
+```
+
+No operation adds capability. Only an authenticated principal with
+role-management authority may create, edit, activate, bind, or roll back roles
+(L2-D13); agents cannot, ever. Orchestrators cannot deploy seats at all —
+coordination goes through `mosaic coord` requests to the coordinator service
+(register OD-08/OD-09). Cycle detection is unnecessary because no grant edge
+exists.
+
+## Enforcement point: `mosaic-core`
+
+A tracked, non-npm Pi extension loaded via role-scoped settings. Per seat, per
+launch: trusted-path manifest load
+(`<brainHome>/fleet/roles/<role>/mosaic-core.manifest.json` — committed,
+non-symlink, role cross-checked), fail-closed state machine
+(`not-applied | applied | fail-closed`), exact active-tool reconciliation,
+per-call interception with read containment (canonicalization + realpath +
+credential-path deny), per-incarnation append-only journal. Capabilities C1–C8
+are the authority; tools are their bound projections; `tools[]` must equal the
+bound bindings exactly. The capability map is closed and hardcoded in the
+canary phase (gap G7 — by design for now; L2-D21 is the end state).
+
+## The firewall rules
+
+1. **Agents never reach role-management surfaces** (L2-D13). A seat that can
+   invoke role management can self-grant, voiding the model.
+2. **The coordinator is a service, never a seat** (gap G4; register OD-08). A
+   coordinator-as-seat turns the intersection chain into a cycle.
+
+## Closed vs accepted
+
+**Closed by construction: escalation.** The intersection chain admits no
+capability-adding edge.
+
+**Accepted within reason: misdirection.** A rogue or colluding orchestrator can
+still _route work_ to a seat that already legitimately holds a capability. The
+authority is genuine, so no structural control can refuse it. Jason's ruling:
+escalation and misdirection are tiered **by outcome — identically**; locking
+down far enough to mechanically prevent misdirection cripples the system to
+inoperability. Mitigation posture: **audit and visibility, not prevention** —
+see the audit surface in [[UI.1-webui-surfaces]] and gap G3 below.
+
+## Role separation as the working mitigation
+
+Design intent (not yet enforced by any manifest — gap C3 in the lane ledger):
+
+| Role           | Must NOT                         |
+| -------------- | -------------------------------- |
+| coding agent   | create remote git repositories   |
+| gate agent     | code                             |
+| review agent   | code                             |
+| interact agent | code, create remote repositories |
+
+Breaking the monopoly means no single seat holds an exit path; escape requires
+inter-seat coordination, which is exactly what the audit exists to catch.
+Register OD-25–OD-34 (review/gate/arena families, independence rules) carry the
+role taxonomy this matrix projects onto.
+
+## Gap register (measured 2026-08-31)
+
+| ID  | Gap                                                                                                                           | Status                                      |
+| --- | ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------- |
+| G1  | No least-privilege language anywhere in L1/L2/NORTH-STAR (grep-verified)                                                      | **L2-D52 amendment drafted**                |
+| G2  | Assignment issuance criteria unspecified (renewal names criteria; issuance does not) — full-ceiling requests validate cleanly | **L2-D52 amendment drafted**                |
+| G3  | No misdirection audit exists — no tooling, agent, or surface                                                                  | open → [[UI.1-webui-surfaces]] §Audit       |
+| G4  | Coordinator-as-seat would collapse the model                                                                                  | firewall — never violate                    |
+| G5  | Seat config mixes authority classes (role binding beside a model dropdown)                                                    | open → [[SEAT.1-seat-profile]]              |
+| G6  | `role-harness-config/DESIGN.md` scope defect (unstated surface)                                                               | fix drafted (amendment in `proposed/docs/`) |
+| G7  | Capability map closed/hardcoded                                                                                               | by design (canary phase)                    |
+
+Amendments staged in `proposed/docs/` per the lane convention; ledger items
+A3/A4 track ratification. The auditor-identity question (an auditor agent is
+itself a seat, itself subject to misdirection) is on the grill:
+[[GOV.5-open-questions]] Q-A1.
+
+## E2 inputs (triage 2026-08-31; see [[GOV.2-docs-inventory]])
+
+**Canonical ground truth**: `DEVELOPER-GUIDE/architecture/mutator-class-gate.md`
+(the default-deny whole-class gate this section's language must match),
+`lease-broker-protocol.md` + `lease-broker-security.md` (incl. the named
+promote-lease-lost-ACK residual), `ADMIN-GUIDE/security/discord-ingress.md`
+(the one implemented admission/role model).
+**Pending pulls**: DRAFT S2 `rbac-grant-model.md` (granular RBAC per rev0 §4).
+
+## S2 contract feed (extraction 2026-08-31)
+
+Full extraction record: lane `S2-EXTRACTION-2026-08-31.md` (per-contract cores, dependency edges, ruling cross-checks). Pulls binding on this section:
+
+- **Three-layer authority (contract 2)**: platform role (member/admin,
+  instance administration only, **no implicit tenant access** — two live admin
+  bypass paths named non-conformant and scheduled for retirement:
+  `command-authorization.service.ts` admin short-circuit, `mcp.service.ts`
+  scope derivation); hierarchy grants (viewer/member/owner, deny-by-default,
+  down-chain, effective = max, live fail-closed); workspace membership
+  (its own mechanism, REQ-ID-001). The layers are non-substitutable.
+- **Agents are not a valid grant subject** — grant subject is exactly-one-of
+  user_id/team_id. Structural enforcement of the agents-never-reach-role-
+  surfaces ruling, stronger than policy.
+- **Consent ≠ authorization (contract 7 §5.7)**: consent records govern
+  agentic/feature data access, are distinct from hierarchy grants, and confer
+  no platform authorization; default-deny with **no platform-admin bypass**;
+  consent mutation is subject-only (admins refused at write time).
+- **Bounded revocation propagation**: next authz decision denies; open
+  Socket.IO connections re-evaluated within 30s or next inbound message.
+- **company-CRUD capability**: platform-scoped, admin-assigned, audited
+  delegation of exactly one visibility-mutation command (`platform_capabilities`
+  table) — the model's template for narrow capability delegation.
+- **Membership locality + no-existence-oracle (contract 8 §3)**:
+  member-readable workspaces contribute only at their own node, never promoted
+  upward; unreadable vs nonexistent are byte-equivalent.
+
+## Audit implementation ruling (Q-A1/Q-A2, Jason 2026-09-01)
+
+The authorization audit is **mechanical tooling**: deterministic checks over
+the grant/assignment record, witness-style (the S2 writer-coverage pattern),
+feeding the audit page read-only. Agents may consume audit output but never
+produce the verdict — prompt adherence is not an enforcement mechanism. Q-A2
+(who audits the auditor) dissolves: the auditor is code, audited by ordinary
+review and CI.
@@ -0,0 +1,158 @@
+---
+id: CLI.1
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# CLI.1 — CLI surface and parity obligation
+
+## The rule
+
+The CLI is the **primary execution method** (D8); the WebUI operates the same
+tooling over the Gateway API and never bypasses it (D12). Register OD-49 fixes
+`mosaic config` as the stable installation-configuration command family backed
+by one desired-state engine; register OD-53 makes every interface (CLI, TUI,
+WebUI, API, automation) a client of that same engine.
+
+Parity is therefore **structural, not aspirational**: a capability that exists
+in the CLI without a WebUI surface is an incomplete projection; a WebUI wish
+with no backing tool is **"blocked on tooling"** and the tool is built first
+(D8 consequence). Neither side ever grows private logic.
+
+## Parity matrix obligation
+
+The ratified bundle must carry (or cite, per D8's baseline inputs) three
+artifacts, kept current:
+
+1. **Tool inventory** — what official tooling exists and what is missing.
+2. **WebUI→tool mapping** — every page control mapped to the tool it calls
+   ([[UI.1-webui-surfaces]] page inventory is the row source).
+3. **Measured `next`-branch state** — what actually works today.
+
+All three artifacts were measured 2026-08-31 against `origin/next` commit
+`9aa4983c` and appear below. Grill: [[GOV.5-open-questions]] Q-C1 (matrix
+freshness ownership after ratification).
+
+## Artifact 1 — tool inventory (measured, `origin/next` @ `9aa4983c`)
+
+Registration root: `packages/mosaic/src/cli.ts` (commander); command modules
+under `packages/mosaic/src/commands/`; `coord`/`prdy`/`doctor`/runtime
+launchers dispatch to bash tools under `packages/mosaic/framework/tools/`
+(subcommand tables at `commands/launch.ts:1151–1255`); sibling packages
+(`brain`, `forge`, `macp`, `quality-rails`, `log`, `memory`, `queue`,
+`storage`) register their own families.
+
+Control-plane-relevant families, by rev1 domain:
+
+| Domain           | Families (measured)                                                                                                                                                                                                                                                                                          |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| SEAT             | `fleet` (init/install/systemd/lifecycle/roster/add/remove/verify/ps), `fleet` roster-v2 CRUD (`get/plan/create/update/delete`), `fleet apply`/`reconcile`/`doctor`/`regen`, `fleet provision`, `fleet migrate-v1 preview`, `agent` (configs + enroll + nested fleet-agent commands), `promote`, `comms send` |
+| ROLE             | `fleet persona` (`list/show/customize` — baseline ⊕ `roles.local/` overrides), `fleet profile` (`list/show` topology templates)                                                                                                                                                                              |
+| HARN             | `config` (framework config + hooks), `compose-contract <harness>`, `skill`, `seq`, `init`/`sync`/`bootstrap`, `doctor`, runtime launchers (`claude`/`codex`/`opencode`/`pi`, experimental `claudex`, `yolo`)                                                                                                 |
+| PROV             | `gateway config` (raw provider API-key env vars only), `wizard` (setup-time provider config)                                                                                                                                                                                                                 |
+| AUTHN            | `login`, `auth users {list,create,delete}`, `auth sso {list,test}` (stubbed — see gaps), `auth sessions list` (stubbed), `gateway` token lifecycle (`config rotate-token/recover-token`)                                                                                                                     |
+| SESS             | `tui`, `sessions {list,resume,destroy}`, `interaction` (durable-session surface: enroll/attach/send/chat/stop/recover), `coord`, `watch`, `mission`                                                                                                                                                          |
+| Governance/other | `prdy {init,update,validate,status}`, `federation {grant,peer}`, `macp tasks gate`, `telemetry`, `upgrade`/`update`/`restore`/`uninstall`, `q`, sibling-package families                                                                                                                                     |
+
+Notable structural facts: there is **no top-level `mosaic role` verb** — role
+management lives at `fleet persona`, three levels deep; and `doctor`/`status`
+exist twice (top-level framework-scoped vs `fleet`-scoped), shadowing by name.
+
+## Artifact 2 + 3 — WebUI→tool mapping with measured state
+
+Rows are the [[UI.1-webui-surfaces]] page domains; measured against
+`apps/web/src/spa/pages/` and the gateway controllers on the same commit.
+
+| Surface function                                     | WebUI today                                                                     | CLI today                                                               | Parity state                                                                                                                                                                                                                    |
+| ---------------------------------------------------- | ------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Seat lifecycle & roster (SEAT)                       | **no Seats page** (routes are only /admin, /settings, /projects, /tasks, /chat) | complete (`fleet`/`agent` families)                                     | CLI-ahead — page is D2's work, tooling exists                                                                                                                                                                                   |
+| Role/persona config (ROLE)                           | no page                                                                         | `fleet persona`                                                         | CLI-ahead; naming mismatch: no `mosaic role` verb for the ROLE page to mirror                                                                                                                                                   |
+| User role/ban (AUTHN)                                | admin UsersTab toggles role/ban via admin endpoints directly                    | `auth users` lacks `set-role`/`ban`/`unban`                             | **WebUI-only mutation — violates the D12 rule as implemented**                                                                                                                                                                  |
+| SSO admin (AUTHN)                                    | SsoProviderSection reads _public_ `/api/sso/providers` discovery                | `auth sso list/test` stubbed: "admin endpoint missing"                  | **blocked on gateway tooling**; CLI and WebUI don't even hit the same surface                                                                                                                                                   |
+| Auth-session admin (AUTHN)                           | —                                                                               | `auth sessions list` stubbed (no server endpoint)                       | blocked on gateway tooling                                                                                                                                                                                                      |
+| Provider list/test (PROV)                            | settings ProvidersTab: `GET /api/providers`, `POST /api/providers/test`         | none — only `gateway config` raw env-var writes                         | **WebUI-only read/test — no `mosaic provider` family exists**                                                                                                                                                                   |
+| Default harness/provider/model selection (HARN/SESS) | `GET/PUT /api/chat/preferences/selection` per user                              | none persists the stored preference (`tui --model` is per-session only) | WebUI-only mutation                                                                                                                                                                                                             |
+| Authorization hierarchy & grants (UI-audit)          | **no page**                                                                     | **no command**                                                          | **the largest D12 gap**: `hierarchy.controller.ts` exposes full CRUD (companies, estates, platform-projects, grants incl. `grants/:id/change`) with audit repository and grant evaluation behind it — reachable only by raw API |
+| Federation grants/peers                              | no page                                                                         | `federation grant/peer`                                                 | CLI-ahead (posture pending Q-T1)                                                                                                                                                                                                |
+
+**Consequences for the build order** (D8: tool first, then surface):
+`mosaic provider {list,test}`, `auth users {set-role,ban,unban}`, a stored
+harness-selection command, the missing gateway admin endpoints for SSO/session
+listing, and a CLI face for the hierarchy/grant surface all precede their
+pages. The two **WebUI-only mutations** (role/ban toggle, harness selection)
+are standing D12 violations to remediate, not precedents to extend. The
+hierarchy CRUD surface is the natural backing for [[UI.1-webui-surfaces]]'s
+authorization audit page — but it must get a CLI face and an audit read-path
+before the page ships.
+
+## Command families in scope for the control plane
+
+`mosaic config` (OD-49 desired-state engine), `mosaic coord` (agent coordination
+boundary — register OD-09), `mosaic prdy` (PRD creation/acceptance — register
+OD-22), role management (one canonical API, L2-D14), seat lifecycle
+(launch/relaunch per register OD-59), `mosaic doctor` (drift detection classes,
+e.g. the #1194 framework-tool drift addendum in [[GOV.4-workstream-contracts]]).
+
+## `mosaic config` v1 subset (pulled 2026-08-31 from the minimal-subset spec)
+
+The Q14 ruling (2026-08-29) fixes the current scope: shipped surface
+`edit/get/set/show/hooks/path` **plus exactly two new read-only verbs** —
+`mosaic config validate` and `mosaic config plan` (`--file` | `--preset`,
+mutually exclusive; `--format table|json`). `apply`, `add`, `restructure`,
+`migrate`, `remove`, `export` are **out of v1 pending a full-engine ruling**
+([[GOV.5-open-questions]] Q-D5) — the configuration-lifecycle draft's "stable
+namespace" table describing the full family is aspirational, not current state.
+
+Contract highlights: **valid** vs **conformant** are distinct verdicts with
+distinct exit codes (nonconformance is a diagnostic, not a parser failure);
+`plan` emits `create|update|blocked` operations with risk classes
+(`none|review-required|full-engine-required`), a SHA-256 `planId`, and
+`applySupported: false` always in v1; destructive/unsupported drift is
+`blocked`, never silently normalized; absolute no-mutation during
+validate/plan (no writes, no network, no credential calls); results ride the
+T78 `CapabilityResultV1` envelope (capability IDs
+`config.installation.validate`/`.plan`); inputs capped, YAML
+aliases/anchors/tags rejected, no secret-shaped fields accepted or echoed.
+
+## E2 inputs (triage 2026-08-31; see [[GOV.2-docs-inventory]])
+
+**Canonical ground truth**: `requirements/cli-capability-migration.md` (T78,
+`source_of_truth: true`), `fleet/reference/cli.md` (local fleet CLI vs
+gateway-backed catalog), `USER-GUIDE/getting-started/quickstart.md`.
+**Pending pulls**: DRAFT S2 `tool-gateway-mapping.md`; brain
+`docs/specs/2026-08-29_mosaic-config-minimal-subset.md` (`mosaic config
+validate/plan`, cites OD-49–OD-55) and
+`docs/guides/proposed/workflows/configuration-lifecycle.md` (the OD-49 engine
+family definition).
+
+## S2 contract feed (extraction 2026-08-31)
+
+Full extraction record: lane `S2-EXTRACTION-2026-08-31.md` (per-contract cores, dependency edges, ruling cross-checks). Pulls binding on this section:
+
+- **Contract 5 §4.5 is the parity clause this section's matrix enforces**:
+  CLI remains the primary execution method for every Gateway command; no
+  WebUI-only command exists; a Gateway command without CLI exposure is a
+  conformance gap tracked at the family's implementing issue. The
+  hierarchy/grants CRUD gap measured in this section is exactly such a
+  tracked conformance gap once contract 5 ratifies.
+- **Command envelope**: typed request/result DTOs (no `any`), closed
+  per-family error taxonomy, audit correlation id, fail-closed — aligns with
+  the T78 `CapabilityResultV1` direction already in this section.
+- **Contract 9 (api-artifacts)**: `ApiAuthClass` closed six-value enum
+  (`none`/`session`/`api-key`/`admin`/`federation`/`bootstrap`); OPENAPI.yaml
+  generated, CI byte-drift-gated, never hand-edited; hard ordering — nothing
+  under contract 9 lands before contract 5 (PR #1438) is on the trunk.
+- **Roll-up (contract 8)** ships as a query-only tool with no command
+  counterpart (A5 rank 5) — the taxonomy precedent for read-only surfaces in
+  the parity matrix.
+- **Mandated removals** the CLI inventory must track: `mosaic auth users
+delete` (with the hard-delete endpoint) is required to be disabled/removed
+  by contract 4.
+
+## Parity freshness ruling (Q-C1, Jason 2026-09-01)
+
+The parity matrix becomes a generated artifact with a CI drift-gate witness in
+the stack repo (the contract-9 pattern): CI regenerates the tool inventory and
+WebUI→tool mapping from code and fails on divergence from the committed
+matrix. No human cadence to forget. Building the witness is E6-return
+follow-up work.
@@ -0,0 +1,159 @@
+---
+id: DATA.1
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# DATA.1 — Record-class authority and the configuration data model
+
+Merges J1 (2026-08-23), operator register OD-13/OD-48/OD-49–OD-52, and the lane's
+`CONFIG-MODEL.md` findings into one authority table. See
+[[GOV.3-decision-map]] for registry identities.
+
+## The rule (J1)
+
+- **Git owns** reviewed governance and declarative definitions.
+- **PostgreSQL owns** runtime state and projections.
+- Flat files on disk are **generated projections**, never authority (L2-D19).
+
+## Authority table
+
+| Record                                              | Authority                                                         | Rationale                                                               |
+| --------------------------------------------------- | ----------------------------------------------------------------- | ----------------------------------------------------------------------- |
+| Role Definition / Role Revision                     | **Git**                                                           | reviewed governance; revisions immutable and digested                   |
+| `mosaic-core.manifest.json`                         | **Git**                                                           | committed, non-symlink, trusted-path — the loader refuses anything else |
+| PRD revision bundles (`docs/PRDs/`)                 | **Git**                                                           | immutable accepted versions (register OD-17)                            |
+| Portable config blueprint                           | **Git** (`fleet/configuration/installation.yaml`, register OD-50) | declarative desired state                                               |
+| Host bindings                                       | ignored `config/installation.local.yaml` (OD-50)                  | host-local, never authority over roles/gates (OD-52)                    |
+| Role Binding (seat → revision)                      | **Postgres**                                                      | runtime state; control-plane mutable                                    |
+| Seat record (harness, model, workdir, auth account) | **Postgres**, projected to flat files                             | runtime state                                                           |
+| Leases, checkpoints, session/incarnation state      | **Postgres** / coordinator (register OD-57–OD-60)                 | runtime state with fencing                                              |
+| `settings.json`, `launch.env`                       | **generated projection**                                          | L2-D19; no writer may treat them as source                              |
+
+Transition rule: the WebUI may edit flat files during the transition, but the
+end state is exactly the table above — every flat file regenerated from Git or
+Postgres, never authored directly.
+
+## Seat file consolidation (lane Q1 — proposed, not ratified)
+
+Current flat-file state (measured 2026-08-31):
+
+| File                                           | Carries                                                        |
+| ---------------------------------------------- | -------------------------------------------------------------- |
+| `fleet/agents/<seat>/launch.env`               | model, workdir, reasoning level (hand-maintained, git-ignored) |
+| `fleet/agents/<seat>/profile.json`             | role — read by `mosaic-core`'s trusted-path loader             |
+| `fleet/roles/<role>/.pi/agent/settings.json`   | provider, model, extensions, skills paths                      |
+| `fleet/roles/<role>/mosaic-core.manifest.json` | capability/tool authority (schema v3)                          |
+
+Proposal: one `profile.json` rules seat information (role, harness, model,
+reasoning, workdir, overlay, authentication account); `launch.sh` reads it
+instead of `launch.env`. Register OD-48 already ratifies `profile.json` as the
+seat's **structured identity** file, which this consolidation completes.
+
+**Blocking consideration:** `mosaic-core` reads `profile.json` at every
+`session_start` to resolve the role. Widening the file widens the read surface
+of a trusted-path load. The loader must keep ignoring unknown keys (it reads
+only `.role` and already does); the file must stay non-symlink and committed.
+Verify `lib/loader.ts seatRole()` before landing. Open on the grill list:
+[[GOV.5-open-questions]] Q-D1.
+
+## Multi-provider authentication shape (lane Q2 — open)
+
+`profile.json` must name the authentication account a seat uses, across
+providers (Claude, OpenAI, ZAI, N others; OAuth or API key; local providers).
+Unresolved: one account vs a per-provider map, and the credential-broker
+relationship. The enforced role manifests hold **no** credentials
+(`store: none, providerTokens: denied`) — this is a launcher/broker concern,
+never a manifest concern. Grill: [[GOV.5-open-questions]] Q-D2. See
+[[AUTHN.1-auth-accounts]] for the account model itself.
+
+## Reconciliation obligation (lane Q4)
+
+Every change made through CLI or WebUI automatically configures authentication,
+`settings.json`, and required symlinks — the user never touches a file. Two
+directions with different timing (L2-D17): capability **removal** denies
+centrally and immediately; capability **addition** waits for runtime
+reconciliation and attestation.
+
+**Hazard to settle first:** Pi settings ownership is ambiguous today
+(`launch-seat.sh:259–261` symlinks `.pi/agent/settings.json` under
+`MOSAIC_SEAT_HOME=1` while the `MOSAIC_SEAT_CONFIG=1` seed fires on `! -s`,
+which the symlink satisfies). Settle ownership before the WebUI becomes a third
+writer. Grill: [[GOV.5-open-questions]] Q-D3.
+
+## Configuration file authority (pulled 2026-08-31 from the mosaic-config v1 spec)
+
+Four config records with fixed authority (brain spec `2026-08-29_mosaic-config-minimal-subset.md`, register OD-49–OD-55):
+
+| Record             | Path                                                | Authority                                           |
+| ------------------ | --------------------------------------------------- | --------------------------------------------------- |
+| Central registry   | `~/.config/mosaic/config.json`                      | resolves brainHome/socket/paths                     |
+| Portable blueprint | `<brainHome>/fleet/configuration/installation.yaml` | tracked, secret-free desired state                  |
+| Host bindings      | `<brainHome>/config/installation.local.yaml`        | git-ignored; **runtime and working directory only** |
+| Packaged presets   | immutable, versioned (`bootstrap-minimal@1`)        | never `latest`                                      |
+
+Precedence, high to low: constitution/safety (deny-wins, OD-51) → framework
+schema/profile/role/roster contracts → blueprint/preset → host bindings →
+framework binding defaults → observed state (**compared, never authoritative**).
+Host bindings can never change profile, seat selection, roles, authority,
+reviews, gates, or safety (OD-52) — the data-model enforcement of the
+[[AUTHZ.1-capability-authority]] intersection chain. Validation distinguishes
+**valid** (structurally sound) from **conformant** (observed == desired) with
+distinct exit codes.
+
+_Triage note:_ the intended-state reconciler spec was judged **operator
+host-ops tooling** on full read (systemd/tmux monitoring of the operator
+estate) — not product scope; its conformance idea is already covered by the
+validate/plan model above. E2-inputs pull downgraded to SKIP.
+
+## E2 inputs (triage 2026-08-31; see [[GOV.2-docs-inventory]])
+
+**Canonical ground truth**: `requirements/native-kanban-sot.md` (ratified, the
+D13 base), `native-kanban-sot/KBN-101-DB-ROLE-SPLIT.md` + `KBN-101-ENVELOPE-A.md`
+
+- `SHARED-CONTRACT.md` (frozen contracts), `ADMIN-GUIDE/operations/upgrade-safety-and-recovery.md`
+  (PGlite tier support boundary), `fleet/reference/roster-v2-fields.md`.
+  **Pending pulls**: DRAFT S2 contracts `hierarchy-schema.md`, `custody-schema.md`,
+  `rollup-projection.md`, `mode-conversion.md` (**predates D15 — reconcile first**,
+  Q-T4); brain `docs/specs/2026-08-28_intended-state-reconciler.md` (reconciler spec).
+  **Conflicts on the grill**: deployment/federation posture, Q-T1.
+
+## S2 contract feed (extraction 2026-08-31)
+
+Full extraction record: lane `S2-EXTRACTION-2026-08-31.md` (per-contract cores, dependency edges, ruling cross-checks). Pulls binding on this section:
+
+- **Hierarchy schema (contract 1)**: five tables, single-parent FK chains, no
+  parentage edge tables, **no `owner_id` column** — ownership only via grants.
+  All mutations through the sole-writable-SOT audited Gateway command path;
+  three-prong writer-coverage CI witness.
+- **Custody schema (contract 7)**: sensitive content only in the user's
+  git-tracked brain; Postgres holds pointers/consent/registry only ("not as
+  text, not as excerpts, not as embeddings"); content-first-then-pointer write
+  protocol with brain fence; HMAC content hashes (no oracle); mode-independent
+  schemas with a `custody_config` singleton.
+- **Roll-up (contract 8)**: the corpus's strongest projection-never-authority
+  statement — non-authoritative, recomputable, never gates work, enforced by
+  read-only DB transactions (mechanical, not conventional). Direct precedent
+  for this section's record-authority chain.
+- **Route metadata records (contract 9)**: metadata as _registration input_ —
+  auth guard derived from the record makes record-vs-code divergence on those
+  fields structurally impossible; generated OPENAPI.yaml is committed and
+  PR-reviewed yet strictly non-authoritative ("generation documents the code;
+  it does not ratify it") — drafting precedent: "generated" ≠ "uncommitted".
+- **Authoritative DB settings rows** — ruled (Q-T5, Jason 2026-09-01):
+  generated settings _files_ are projections of the active Role Revision,
+  never authority (L2-D19); DB settings records written through audited
+  Gateway commands (`platform_mode`, `registration_mode`, `custody_config`,
+  `bootstrap.seed-company-name`, and successors) are records of authority
+  like any other SOT row.
+
+## Seat-record rulings (Jason 2026-09-01)
+
+- **Q-D1 — one seat record**: `launch.env` folds into `profile.json`; loader
+  tolerance verified (`seatRole()` reads only `role` from a generic record).
+- **Q-D2 — per-provider auth map**: `profile.json` carries a per-provider map
+  of credential-broker references (`environment/service/component/secret-name`),
+  never secrets; one seat, N providers, zero secrets in the brain tree.
+- **Q-D3 — one settings writer**: the role-projection engine is the sole
+  writer of seat settings files; the launcher invokes the projector rather
+  than seeding; hand edits are drift flagged by `validate` (L2-D19 + Q-T5).
@@ -0,0 +1,107 @@
+---
+id: GOV.1
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# GOV.1 — PRD lifecycle: SOT, shim, revisions, archival
+
+Ratified structurally by Jason, 2026-08-31 (this lane's grill session). Applies
+to the Mosaic Stack PRD in `mosaicstack/stack` (integration trunk `next`).
+
+## The PRD is the project SOT
+
+The PRD is the source of truth for the entire project, independent of any
+mission. It is not linked to a current mission and is never overwritten by
+milestone work — the pre-2026-08-26 pattern of repurposing `docs/PRD.md` per
+milestone is retired. Mission documents are separate: they **reference** the
+PRD; they never usurp it. This maintains alignment over time.
+
+## Shim
+
+`docs/PRD.md` is a permanent shim, not the PRD body:
+
+- Frontmatter: `kind: shim`, `current_rev:` pointing at the live revision
+  bundle.
+- Body: one-paragraph summary and a link into `docs/PRDs/`.
+- Updating the PRD means ratifying a new revision bundle and repointing the
+  shim. The shim's path never changes, so every external reference to
+  `docs/PRD.md` stays valid forever.
+
+## Revision bundles
+
+Each ratified revision is a **frozen bundle directory**:
+
+```
+docs/PRDs/YYYY-MM-DD_PRD_revN/
+  PRD.md              # the assembled PRD for this revision
+  PRD.0-index.md      # order authority + domain registry as of this revision
+  <DOMAIN>.<n>-*.md   # every section document, frozen with the PRD
+```
+
+The PRD and its supporting sections freeze **as a set** — a revision whose
+sections keep moving underneath it is not a revision. Live editing never
+happens in `docs/PRDs/`; the next revision is drafted in a lane
+(class‑2 draft-natives per the lane's `proposed/README.md`) and lands as a new
+bundle.
+
+## Archival, never deletion
+
+A superseded revision is never deleted and never edited. Versioning is
+maintained: every revision that was ever current remains in `docs/PRDs/`
+verbatim. Supersession is expressed only from outside the bundle: the shim
+points elsewhere, and the dated directory names plus the shim's git history are
+the supersession record. The frozen bundle itself is never touched — not even
+to add a `superseded_by:` marker.
+
+## Immutability is convention, not enforcement
+
+No hook or CI guard protects `docs/PRDs/` today. If teeth are wanted later, a
+CI check that files under `docs/PRDs/` never change after merge is cheap; that
+is a separate, future decision.
+
+## Lineage
+
+- rev0 = the 2026-08-26 "North Star" PRD currently at `origin/next:docs/PRD.md`
+  (commit `9aa4983c`, sha256 `60cc2f98…36afdf`; lane snapshot
+  [rev0 PRD](../2026-08-26_PRD_rev0/PRD.md)). On ratification of rev1 it archives as
+  `docs/PRDs/2026-08-26_PRD_rev0/PRD.md` — a one-file bundle, so every revision
+  has the same shape.
+- rev1 = this lane's draft bundle (`proposed/docs/PRDs/2026-08-31_PRD_rev1/`),
+  combining rev0 with the control-plane-surfaces and agent-runtime-ng lane
+  findings and the reconciled docs corpus.
+
+Related: [[PRD.0-index]] for naming and ordering; the lane `proposed/README.md`
+for draft-stage conventions.
+
+## Registry mechanics (pulled 2026-08-31 from the prd-registry draft)
+
+The operator draft `operations/prd-registry.md` independently specifies the
+same lifecycle and adds mechanics this doc adopts:
+
+- **The registry, not the shim, is authoritative.** The shim is generated,
+  regenerated on every acceptance and amendment; a missing or ambiguous shim
+  entry is a generation defect, never an authority question.
+- Registered versions carry: stable PRD ID, canonical filename/slug, version +
+  status, acceptance timestamp **and actor**, lineage, content digest,
+  requirement IDs. Anonymous or inferred acceptance is invalid.
+- Missions pin PRD ID + version + digest + in-scope requirement IDs; a digest
+  mismatch between pin and artifact **blocks the readiness transition** (both
+  digests shown as evidence).
+- Amendment creates a new immutable version; superseded versions remain
+  queryable as lineage; **requirement IDs are never reused**.
+- Agents read and resolve; they never register versions, rewrite artifacts, or
+  select an implicit latest.
+
+## Registry prefixes (Q-G2, 2026-09-01)
+
+Every decision-bearing document declares a unique registry prefix; file-local
+bare D-numbering is prohibited. Three registries are live: the stack PRD
+registry (**D1–D15**, and successors **Dn** as new stack decisions ratify),
+the operator DECISION-REGISTER (**OD-01…OD-65**, renamed from its former
+zero-padded `D01`–`D65` form per this ruling), and the agent-runtime-ng
+contract decisions (**L1-Dnn**/**L2-Dnn**) — three distinct namespaces that
+must never be conflated. Any new decision-bearing document must declare its
+own unique prefix in its header before citing decisions. In text written
+before 2026-09-01, a zero-padded bare `Dnn` reads as the operator register's
+`OD-nn`.
@@ -0,0 +1,151 @@
+---
+id: GOV.2
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# GOV.2 — Documentation inventory & supersession triage
+
+E2 record and, at ratification, the PRD's answer to mandate item 4 (no central
+location; drift and naming confusion). Verdict vocabulary, per document:
+**canonical** | **superseded-by <ref>** | **conflict-with <ref>** |
+**working-notes** | **dead** | **operator-only** (brain corpora: correct home is
+the operator estate; nothing migrates).
+
+Full per-file verdict tables live in the lane evidence record
+`fleet/lanes/control-plane-surfaces/TRIAGE-2026-08-31_e2-verdicts.md`
+(point-in-time; this section carries the durable conclusions).
+
+## Corpora
+
+| #   | Corpus                                                                  | Files | Scanned at                                                                                                 |
+| --- | ----------------------------------------------------------------------- | ----- | ---------------------------------------------------------------------------------------------------------- |
+| 1   | `mosaicstack/stack` `origin/next:docs/`                                 | 346   | commit `9aa4983c`, triaged 2026-08-31 (141 live files per-file; archive dirs swept for orphaned decisions) |
+| 2   | `~/.mosaic/docs/` (excl. guides/proposed)                               | ~76   | triaged 2026-08-31                                                                                         |
+| 3   | `~/.mosaic/docs/guides/proposed/`                                       | 79    | triaged 2026-08-31                                                                                         |
+| 4   | `fleet/lanes/agent-runtime-ng/` + `fleet/lanes/control-plane-surfaces/` | —     | live lanes, canonical by definition for their scope                                                        |
+
+## Corpus 1 — stack `origin/next:docs/` — conclusions
+
+195 of 346 files (56%) were pre-triaged by the repo's own archive structure
+(`archive/` 135, `_old_structure/` 60). The 141 live files triaged per-file:
+
+**The healthy core.** The five guide trees (DEVELOPER-GUIDE, ADMIN-GUIDE,
+USER-GUIDE), `fleet/` (concepts/how-to/reference/operations/migration),
+`native-kanban-sot/`, `webui/`, `API/`, `tess/`, `release-integrity/`, and the
+root atlas docs (README, ROADMAP, SITEMAP) are overwhelmingly **canonical** and
+internally consistent. Load-bearing canonical anchors for this PRD:
+`requirements/native-kanban-sot.md` (ratified, D13), `KBN-101-DB-ROLE-SPLIT.md`
+(frozen), `requirements/cli-capability-migration.md` (T78),
+`fleet/NORTH_STAR.md` + `FLEET-DOCTRINE.md`, `mutator-class-gate.md` and the
+lease-broker pair (AUTHZ ground truth), `compaction-revocation.md` (SESS ground
+truth), `sso-providers.md` (D10/AUTHN ground truth),
+`mos-runtime-portability-m1.md` (the only current PROV identity ADR),
+`web-dashboard.md` (UI route-by-route ground truth).
+
+**The prime successor material.** The nine DRAFT "webui-audit S2" contracts in
+`requirements/` (hierarchy-schema, rbac-grant-model, onboarding-wizard,
+identity-lifecycle, tool-gateway-mapping, mode-conversion, custody-schema,
+rollup-projection, api-artifacts) are unratified but decision-traceable per
+clause to rev0 D-numbers — the most direct feed for DATA/AUTHZ/AUTHN/UI/CLI.
+`mode-conversion.md` predates D15 and needs reconciliation before it ratifies
+([[GOV.5-open-questions]] Q-T4). Per-contract extraction completed 2026-08-31
+(lane `S2-EXTRACTION-2026-08-31.md`): normative cores, dependency edges, and
+ruling cross-checks pulled into the DATA/AUTHZ/AUTHN/UI/CLI sections; two
+reconciliation questions raised (Q-T4 sharpened — no S2 file references D15;
+Q-T5 — projection-rule scope vs authoritative DB settings records).
+
+**Conflicts requiring a ruling** (all carried in [[GOV.5-open-questions]] Q-T1):
+
+| Document                                      | Conflict                                                                                                                                           |
+| --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| root `MISSION-MANIFEST.md` (2026-07-14)       | makes federated-tier the "canonical MVP deployment topology", Federation v1 top-priority — vs D3 (deferred) and D15 (compose standalone canonical) |
+| `federation/MISSION-MANIFEST.md` (2026-04-21) | Federation v1 as active in-progress M3 — vs D3 and ROADMAP P5 "deliberately undesigned"                                                            |
+| `guides/deployment.md`                        | blocks Compose activation pending KBN-101 gates — vs D15's `docker compose up` v1 bar                                                              |
+| `scratchpads/mvp-20260312.md`                 | records a _completed_ Federation M2 milestone (peer certs, grants, ScopeService, Step-CA) — vs D3's "deferred" framing                             |
+
+Code reality, verified 2026-08-31 at `9aa4983c` (dossier: lane
+`FEDERATION-DOSSIER-2026-08-31.md`): federation M1–M3 are shipped and wired
+behind a `tier === 'federated'` gate — M3 landed 2026-06-24/25, beyond what any
+doc records — M4–M7 absent, dormant since 2026-06-25, absent from the canonical
+`docker-compose.yml` (so code topology is consistent with D15), and tracked
+nowhere since the TASKS.md → NORTH_STAR.yaml supersession. The three stale docs'
+claims date to 2026-04 by true content edits. **Ruled B ("shipped but
+frozen"), Jason 2026-09-01** — see [[GOV.5-open-questions]] Q-T1 for the
+amendment consequences the E6 return carries.
+
+**Superseded set** (all with explicit in-file or index-level signals): root
+`TASKS.md`, `fleet/TASKS.md`, `federation/TASKS.md` (→ `fleet/NORTH_STAR.yaml`);
+`fleet/PRD.md` and `fleet/PRD-fleet-suite.md` (→ root `PRD.md`, per
+`fleet/README.md`); `native-kanban-sot` initial NO-GO review (→ GO re-review).
+`plans/`, `reports/`, `scratchpads/` are working-notes/evidence, never spec —
+consistent with their own README disclaimers.
+
+**Orphaned decisions found in the archive sweep** (ratified once, absent from
+D1–D15 and every live doc; disposition on the grill, Q-T2):
+
+1. "No Python" monorepo ruling (`archive/planning/monorepo-consolidation/board-review.md:742`).
+2. Matrix/MACP "exactly three supported modes" install-topology ruling, Mode A
+   split-domain primary; its DNS/domain prerequisite ruling still open
+   (`archive/planning/matrix-macp/rfc-002:133`, `rfc-001:428`).
+3. OpenBrain cut from WP1/WP2 consolidation scope (`board-review.md:611`).
+
+## Corpora 2 + 3 — `~/.mosaic/docs/` — conclusions
+
+The overwhelming majority is **operator-only**: generic engineering standards,
+fleet role playbooks, SDLC gates, ops pages, fleet Q&A rulings, incident
+methods, host-specific plans. Correct home is the brain; nothing migrates.
+Notable verdicts:
+
+- `docs/PRD.md` — **trap confirmed** (N1): it is the pi `/goal` extension PRD.
+  Superseded in substance by [[GOV.4-workstream-contracts]] §Pi Persistent Goal
+  Loop (#1150).
+- `docs/guides/proposed/workflows/prd-lifecycle.md` — superseded by
+  [[GOV.1-prd-lifecycle]] (the draft lifecycle this bundle ratified).
+- `docs/plans/2026-08-25_unified-roadmap.md` (T72 consolidation charter) —
+  superseded by this rev1 consolidation, its successor.
+- `docs/MOSAIC-CANON.md` vs `docs/STRUCTURE-CANON.md` — mutual conflict: both
+  claim to be "the canonical definition of a mosaic-brain" (653 vs 127 lines,
+  divergent sections); STRUCTURE-CANON is the copy everything links to.
+  Operator-side ruling needed (Q-T3).
+- Dead: `plans/2026-08-22_config-json-schema.md` (delivered as stack#1382), two
+  closed questions.
+
+**Migration candidates** — nine working-notes whose product content should feed
+rev1 sections during refinement (full list with rationale in the lane evidence
+record): `specs/2026-08-29_mosaic-config-minimal-subset.md` → CLI;
+`specs/2026-08-28_intended-state-reconciler.md` → DATA;
+`operations/seat-identity.md` → SEAT; `operations/vault.md` → AUTHN;
+`runtime/adapter-contract.md` → HARN; `SPECIALIZATION-MODEL.md` → ROLE;
+`workflows/session-lifecycle.md` → SESS; `operations/prd-registry.md` → GOV;
+`workflows/configuration-lifecycle.md` → CLI/GOV.
+
+`COORDINATION-CONTROL-PLANE.md` and `workflows/coordination-lifecycle.md` are
+product-adjacent but belong to the `agent-runtime-ng` lane's L1/L2 scope, not
+this bundle (corpus-4 boundary).
+
+## Corpus 4 — the two lanes
+
+Canonical for their scope by definition (they are the drafting record).
+`agent-runtime-ng` owns L1/L2 contract text; `control-plane-surfaces` owns
+surface/config findings and this bundle. One-way dependency: surfaces cite
+contracts, never the reverse.
+
+## Naming defects register (mandate item 4)
+
+| #   | Defect                                                                                                                                                                                                                                                                          | Fix proposed                                                                                                        |
+| --- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
+| N1  | `~/.mosaic/docs/PRD.md` is the pi goal-extension PRD wearing the project-PRD name (confirmed 2026-08-31)                                                                                                                                                                        | rename to a goal-extension-scoped name during return                                                                |
+| N2  | Stack local `main` is a divergent unpushed fork that shadows `next`                                                                                                                                                                                                             | already a lane convention; PRD states trunk identity explicitly                                                     |
+| N3  | Pre-2026-08-26 pattern: `docs/PRD.md` overwritten per milestone                                                                                                                                                                                                                 | retired by [[GOV.1-prd-lifecycle]] shim model                                                                       |
+| N4  | Two decision registries share the D-prefix ID space (stack D1–D15 vs operator D01–D65); "D8" is ambiguous without registry name                                                                                                                                                 | OD- prefix applied in rev1 (Q-G2 ruled 2026-09-01); collision rule in [[GOV.3-decision-map]]                        |
+| N5  | Triple "PRD" collision in the stack tree: root `PRD.md` vs superseded `fleet/PRD.md` and `fleet/PRD-fleet-suite.md`, with no local supersession signal on the latter two                                                                                                        | supersession banner in-file; long-term, the GOV.1 rule that the bare name `PRD.md` is reserved for the shim         |
+| N6  | "Tess" and "Ultron" each name two different things: non-authoritative roster-class display aliases (fleet how-tos) vs the named product agent / validator identity (TESS workstream, native-kanban-sot)                                                                         | rev1 text always qualifies which sense is meant; flag for upstream rename of the aliases                            |
+| N7  | Six stack `TASKS.md` files under three authority regimes (banner-superseded / explicitly-not-superseded / silently active) — the filename signals nothing                                                                                                                       | uniform status frontmatter on every TASKS.md; superseded ones point at NORTH_STAR.yaml                              |
+| N8  | Duplicate basenames across stack dirs: `gateway-security-20260313.md` (qa vs code-review, different content), `2026-08-10-docs-catalog-audit.md` (plan vs report), `1099-pipefail-sweep.md` (report vs scratchpad copy)                                                         | disambiguate on next touch; prune the unpromoted scratchpad copy                                                    |
+| N9  | `guides/` is outside the canonical tree per `docs/README.md` yet "protected current authority" per `SITEMAP.md` — contract and sitemap disagree                                                                                                                                 | reconcile the documentation contract; likely fold the four guides into the guide trees                              |
+| N10 | Two live front-matter schemas (`type`/`status: current…` per docs/README.md vs the newer `kind`/`status: active…` used by most files) — collision documented in the w4 worklist, unresolved                                                                                     | settle the schema in the documentation contract as part of E6 return                                                |
+| N11 | Three uncross-referenced descriptions of the `/goal` capability: brain `docs/PRD.md`, `operations/goals.md`, and GOV.4 §#1150                                                                                                                                                   | reconcile under the #1150 identity; brain docs cite it                                                              |
+| N12 | Brain-side: `MOSAIC-CANON.md` vs `STRUCTURE-CANON.md` both claim canon status                                                                                                                                                                                                   | operator ruling (Q-T3); retire or fold the unreferenced copy                                                        |
+| N13 | Forward-looking: rev0 Part II (RI-N3) rules `docs/PRD.md` "not a peer authority" once `docs/prdy/` lands — a third contender in "which PRD is real"                                                                                                                             | GOV.1 disambiguation: prdy is tooling-facing storage; the shim + bundle remain the human-facing SOT chain           |
+| N14 | Commit `a480ee83` (2026-08-21) mass-stamped `status: active` frontmatter across stack docs without content review — status metadata rubber-stamps stale docs as current (root MISSION-MANIFEST's "Last Updated: 2026-07-14" is likewise cosmetic; true content edit 2026-04-19) | status/date frontmatter changes only alongside content review; triage dates by git content edits, never frontmatter |
@@ -0,0 +1,121 @@
+---
+id: GOV.3
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# GOV.3 — Consolidated decision map
+
+Every ratified decision set that binds this PRD, in one place, with the
+collisions between their numbering spaces made explicit. This section exists
+because the estate carried at least four independent decision registries whose
+IDs overlap — a reader seeing "D8" could not know which law was meant.
+
+## The registries
+
+| Registry                   | IDs                                                                                                                                           | Ratified                   | Where                                                                                                                                                                      | Scope                                                          |
+| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
+| Stack PRD registry         | **D1–D15**                                                                                                                                    | 2026-08-25/30              | rev0 §12 → [[GOV.3-decision-map]] (this file, below)                                                                                                                       | product north star                                             |
+| Operator decision register | **OD-01–OD-65** (renamed from D01–D65 per Q-G2, 2026-09-01; the brain-side source doc renames on its next touch and carries a redirect table) | 2026-08-28 (Q1–Q92 review) | the operator DECISION-REGISTER (estate brain `docs/guides/proposed/DECISION-REGISTER.md`, snapshot 2026-08-28, sha256 `2cc81be1…aabec`; operator-only corpus, not shipped) | roles, coordination, PRD lifecycle, configuration, checkpoints |
+| L2 authorization decisions | **L2-D01–L2-D51** (+ proposed **L2-D52**)                                                                                                     | rolling                    | `fleet/lanes/agent-runtime-ng/MECHANICAL-AGENT-RUNTIME-L2-AUTHORIZATION.md`                                                                                                | mechanical agent-runtime authorization                         |
+| Control-plane rulings      | **J1–J5**                                                                                                                                     | 2026-08-23                 | `fleet/lanes/docs/mosaic-control-plane/rulings-J1-J5.md`                                                                                                                   | record-class authority                                         |
+| PRD structural rulings     | (unnumbered, 8 rulings)                                                                                                                       | 2026-08-31                 | [[PRD.0-index]] §Structural rulings                                                                                                                                        | this bundle's lifecycle                                        |
+
+**Collision rule:** zero-padded `D01`-form IDs = operator register; bare `D1`-form
+= stack PRD registry; `L2-D` = L2; `J` = control-plane rulings. Writing a bare
+"D8"-style reference without its registry name is a defect (naming register
+[[GOV.2-docs-inventory]] N4).
+
+## Stack PRD registry D1–D15 (carried from rev0 §12)
+
+| ID  | Decision (short form)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| --- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| D1  | Open-source, AI-first, self-hosted platform for agentic management + life OS                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| D2  | Hierarchy company→estate→project→workspace→kanban; bubble-up; granular RBAC                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| D3  | Standalone vs Enterprise; one-way conversion; per-user brains + Vault required in Enterprise; federation deferred. **Amended 2026-09-01 (Q-T1 ruling B, "shipped but frozen")**: federation M1–M3 exist in code behind `tier === 'federated'` (M3 landed 2026-06-24/25), are excluded from the v1 bar and frozen; tracked as a dormant workstream in `docs/fleet/NORTH_STAR.yaml`; the frozen cert/auth code carries a security re-audit gate before any resumption; the design itself stays deferred and unforeclosed |
+| D4  | Re-runnable, extensible, per-mode onboarding wizards                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| D5  | North star = docs/PRD.md rewrite; stack docs/ = product SSOT                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| D6  | Only product-relevant material migrates from brains; operational records stay and link                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| D7  | Spec-inventory sweep (executed; T2 baseline frozen 2026-08-25)                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| D8  | webUI sits over official framework tooling; CLI primary                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| D9  | Not a hosted business; company = organizational separation for one operator                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| D10 | better-auth is the account system of record; external IdPs via OIDC                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| D11 | Small v1 slice; ALL phases on the documented roadmap from day one                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| D12 | HARD RULE: webUI never bypasses tooling; missing tool ⇒ build the tool first                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| D13 | workspace_id stays the hard isolation unit; kanban SOT amended, not rewritten                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| D14 | Sensitive profile data in the user's own brain only                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| D15 | Tiered containerized deployment: compose standalone + phase-gated k8s                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+
+Full texts: rev0 §12 and the operator decision log (USC estate brain,
+webui-audit lane, `GRILL.md`).
+
+## Operator register decisions this PRD leans on hardest
+
+Full set: the operator DECISION-REGISTER (estate brain `docs/guides/proposed/DECISION-REGISTER.md`, snapshot 2026-08-28, sha256 `2cc81be1…aabec`; operator-only corpus, not shipped). Load-bearing here:
+
+| ID          | Ruling (short)                                                                                                                                                             | Consumed by                                                                                                                      |
+| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| OD-02/OD-03 | one role per seat; role change = clean session, ephemeral context discarded                                                                                                | [[SEAT.1-seat-profile]], [[SESS.1-session-continuity]]                                                                           |
+| OD-08/OD-09 | coordinator service owns leases/deployment; orchestrators never deploy seats directly                                                                                      | [[AUTHZ.1-capability-authority]]                                                                                                 |
+| OD-16–OD-23 | PRD owns requirements; immutable accepted versions; `docs/PRD.md` = generated pointer under `docs/PRDs/`; missions pin PRD version+digest; `mosaic prdy` owns PRD creation | [[GOV.1-prd-lifecycle]] — **independently re-derived in the 2026-08-31 grill before this register was consulted; the two agree** |
+| OD-48       | instance contract: `profile.json` structured identity, `overlay.json` generated composition                                                                                | [[SEAT.1-seat-profile]]                                                                                                          |
+| OD-49–OD-53 | `mosaic config` desired-state engine; blueprint + host-binding split; precedence chain; **all interfaces (CLI/TUI/WebUI/API) share one CLI-backed engine**                 | [[DATA.1-record-authority]], [[CLI.1-parity]], [[UI.1-webui-surfaces]]                                                           |
+| OD-54       | WebUI drafts are revisioned server-side desired-state; no effect until planned and applied                                                                                 | [[UI.1-webui-surfaces]]                                                                                                          |
+| OD-57–OD-61 | checkpoints tied to incarnation+lease; coordinator-run relaunch (checkpoint→stop→apply→clean incarnation→restore); fencing; full restart recovery                          | [[SESS.1-session-continuity]] — **this is the ratified mechanism for mid-stream harness/model/provider switching**               |
+| OD-62–OD-65 | watchdog, outage fail-closed, failure isolation/reporting                                                                                                                  | [[AUTHZ.1-capability-authority]], [[UI.1-webui-surfaces]] (audit/alerts)                                                         |
+
+## Reconciliation notes
+
+- Register OD-13 (repository-backed mission state canonical first, DB later behind
+  the same interface) and J1 (Git owns governance, PostgreSQL owns runtime
+  state) are compatible: OD-13 governs _mission_ state migration order; J1 governs
+  steady-state record classes. [[DATA.1-record-authority]] carries the merged
+  table.
+- Register OD-18's "generated pointer" is stricter than the 2026-08-31 grill's
+  hand-maintained shim: **adopted** — the shim should be generated by tooling,
+  not hand-edited ([[GOV.1-prd-lifecycle]] inherits this).
+- Proposed, not yet ratified: **L2-D52** (least-privilege Assignment issuance),
+  staged at `proposed/docs/MECHANICAL-AGENT-RUNTIME-L2-AUTHORIZATION--least-privilege-issuance.md`.
+
+## Extraction cross-check notes (2026-08-31)
+
+- Five highly product-normative operator drafts carry **no decision-register
+  citations at all** (seat-identity, vault, adapter-contract,
+  SPECIALIZATION-MODEL, prd-registry). Their rules were pulled into sections on
+  their merits; before E6 they must be cross-checked against the register
+  rather than assumed pre-vetted.
+- The intended-state-reconciler spec uses a **file-local D1–D6 numbering** that
+  is neither the stack registry nor the operator register — a live instance of
+  the N4 prefix-collision defect. Do not conflate when compiling
+  cross-references.
+- The session-lifecycle draft is the densest register consumer (OD-03/OD-04/OD-08,
+  OD-56–OD-65) and is likely the canonical drafting source for OD-56–OD-65; its
+  one-relaunch-path gap is Q-S4.
+
+## Re-ratified orphaned decisions (Q-T2, Jason 2026-09-01)
+
+Ratified once in archived planning docs, absent from every live document until
+this map; re-ratified as live constraints:
+
+- **No Python in the monorepo** (source:
+  `archive/planning/monorepo-consolidation/board-review.md:742`).
+- **Matrix/MACP: exactly three supported install modes, Mode A (split-domain)
+  primary** (source: `archive/planning/matrix-macp/rfc-002:133`). Its
+  DNS/domain prerequisite ruling remains open — [[GOV.5-open-questions]] Q-T6
+  blocks Matrix install work, not this map.
+- **OpenBrain excluded from WP1/WP2 consolidation scope** (source:
+  `board-review.md:611`).
+
+## Registry prefix ruling (Q-G2, Jason 2026-09-01)
+
+Distinct prefixes at source: stack keeps **D1–D15**; the operator
+DECISION-REGISTER renames to **OD-01…OD-65** with a redirect table in the
+source doc. Applied in this bundle: every stack-side citation of the operator
+register now reads **OD-nn**; the brain-side source doc itself still carries
+its old zero-padded `D01`–`D65` numbering and renames (with the redirect
+table) on its next touch. File-local D-numbering in drafts (the live N4
+instance: the reconciler spec's D1–D6) is prohibited — every decision doc
+declares a unique registry prefix. For any text predating 2026-09-01 not yet
+swept into this bundle, the old reading rule still applies: a zero-padded bare
+`Dnn` is the operator register (now read as `OD-nn`); a bare `Dn`/`Dnn` in the
+1–15 range without a zero pad is the stack registry.
@@ -0,0 +1,671 @@
+---
+id: GOV.4
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# GOV.4 — Active workstream contracts (preserved unchanged)
+
+Carried verbatim from rev0 ([rev0 PRD](../2026-08-26_PRD_rev0/PRD.md) lines
+258–910) under rev0's own rule: open issues bind to these contracts; this
+revision moves no text and changes no requirement in them. They graduate out
+individually when their workstreams close.
+
+The sections below are normative, in-flight workstream contracts carried over
+verbatim from the previous revision of this file. Open issues bind to them.
+This rewrite moved no text and changed no requirement in them; they are
+governed by their own issues and review gates, and they graduate out of this
+file individually when their workstreams close.
+
+## Current addendum: #1194 — Installed framework-tool drift detection
+
+- Compare the framework tools shipped with the executing Mosaic package against the deployed `$MOSAIC_HOME/tools` tree by content hash.
+- Treat every shipped `tools/**` file as framework-owned/required according to `framework-manifest.txt`, while excluding the explicit operator-owned credential carve-out and preserving installed-only operator/unknown files.
+- Distinguish and count `IN_SYNC`, `STALE`, `NOT_INSTALLED`, and installed-only classifications; fail non-zero when shipped tools are stale or absent and refuse self-comparison that would make drift unobservable.
+- Surface the observational check through `mosaic doctor`; do not refresh files, restart seats, or mutate live tooling.
+- Document identity/messaging/gate behavior changes in the current stale set, the reviewed quiet-window keep-mode refresh command, and post-refresh probes against the installed path.
+- Prove by construction that a stale and missing deployed tool are detected; that regression must fail before this checker exists.
+
+## Compaction Refresh Trust Lifecycle (M1, #827–#830)
+
+### Problem and objective
+
+Context compaction, session replacement, and same-PID runtime reloads can leave a previously VERIFIED runtime lease attached to stale directives. M1 must revoke that authority mechanically for Claude (including Claudex) and Pi without trusting caller-asserted identity or forking the external broker state machine.
+
+### Requirements
+
+1. `CR-REQ-01`: Claude `PreCompact` and `SessionStart` with matcher `compact`, plus Pi `session_before_compact` and the first post-`session_compact` `context`, SHALL independently revoke the active broker lease.
+2. `CR-REQ-02`: Runtime generation increases—including same-PID Pi reload/new/resume/fork and Claude resume/clear—SHALL monotonically replace the prior broker incarnation and inherit no VERIFIED lease.
+3. `CR-REQ-03`: A fired observer that cannot confirm broker revocation SHALL fail closed through lifecycle cancellation, a private local generation fence, and/or a runtime-local tool latch. The existing all-tools broker gate remains authoritative.
+4. `CR-REQ-04`: The lease TTL SHALL remain monotonic and capped at 300 seconds. If both observers are missed, within-TTL consequential actions remain allowed and after-TTL actions are denied. This named bounded residual stale window SHALL be documented without claiming a mutator-action bound inside the window.
+5. `CR-REQ-05`: Hook descendants SHALL use the broker-minted session and owner-only current-generation state inherited from register-before-exec. Caller-minted sessions and parallel lease state machines remain forbidden.
+
+### Acceptance criteria
+
+1. `AC-CR-01`: Real-socket tests prove each Claude observer revokes, Pi lifecycle tests prove both observer paths, and Claudex isolated settings preserve and install the mandatory hooks.
+2. `AC-CR-02`: A same-PID generation test proves the old generation is stale and the replacement generation is UNVERIFIED across reload/resume/fork-equivalent lifecycle events.
+3. `AC-CR-03`: RED-first T12b/T30 evidence explicitly reports dual-hook miss within TTL as **ALLOWED** and after TTL as **DENIED**.
+4. `AC-CR-04`: Attributable executable coverage is at least 85%, the full repository suite is green on deterministic main, and independent code/security review completes before merge.
+
+---
+
+## Pi Persistent Goal Loop (#1150)
+
+### Problem and objective
+
+A Pi agent can stop after a plausible-looking answer even when the operator's broader objective is
+not complete, and ordinary compaction can weaken or omit the original objective. Mosaic needs an
+optional, operator-controlled goal loop that keeps a Pi session oriented, checks progress at native
+lifecycle boundaries, and resumes work until completion is verified or a bounded safety state is
+reached.
+
+The objective is a Mosaic-owned Pi extension deployed from the framework into
+`~/.config/mosaic/runtime/pi/`. It must not install into or depend on `~/.pi/agent/extensions/`.
+
+### Scope
+
+#### In scope
+
+1. `PGL-REQ-01`: The framework SHALL ship a dedicated Pi goal extension under
+   `packages/mosaic/framework/runtime/pi/`, seed it under `$MOSAIC_HOME/runtime/pi/`, and make
+   `mosaic pi` load it alongside the core Mosaic extension when present.
+2. `PGL-REQ-02`: `/goal` SHALL support setting a goal plus status, pause, resume, cancel, and help
+   operations without silently replacing an active goal.
+3. `PGL-REQ-03`: Active branch-specific goal state SHALL be persisted in Pi custom session entries,
+   restored on session start and tree navigation, and never rely on a compaction summary as its
+   source of truth.
+4. `PGL-REQ-04`: A hidden goal contract SHALL be injected through Pi's `context` event before every
+   model request so it remains effective across tool turns, retries, and post-compaction requests.
+5. `PGL-REQ-05`: The harness SHALL inspect every `turn_end` and successful `session_compact` event.
+   A structured terminating goal-report tool SHALL capture `continue`, evidence-bearing `achieved`,
+   or `blocked` status without requiring a redundant model turn.
+6. `PGL-REQ-06`: An achievement claim SHALL remain provisional until a second consecutive
+   evidence-bearing verification report. Any continuation report or successful compaction during
+   verification SHALL reset the verification sequence.
+7. `PGL-REQ-07`: Continuation SHALL be initiated at safe lifecycle boundaries, primarily
+   `agent_settled`; manual compaction and restored active sessions may schedule a deferred idle
+   continuation without re-entering compaction handlers.
+8. `PGL-REQ-08`: The loop SHALL have operator cancellation plus bounded turn and repeated-no-progress
+   limits. Exhausted or blocked goals pause rather than continuing indefinitely.
+9. `PGL-REQ-09`: Framework installation and update SHALL preserve normal manifest ownership: the
+   goal extension is framework-owned under `runtime/**`, while no goal extension or configuration
+   asset is created or modified under the operator's main Pi configuration. Pi remains the owner of
+   its native session files used by `appendEntry()`.
+
+#### Out of scope
+
+1. A mathematical guarantee that an arbitrary natural-language goal is semantically complete.
+2. Automatically executing user-supplied shell predicates or accepting executable validation code in
+   `/goal` arguments.
+3. Restarting Pi after process, host, or supervisor failure; the existing Mosaic fleet/runtime
+   supervisor owns process durability.
+4. Gateway, database, web UI, Discord, or cross-harness goal orchestration in this slice.
+
+### User and stakeholder requirements
+
+- An operator can start a goal from Pi and see its current phase, evidence, limits, and latest report.
+- The agent remains oriented after each turn and compaction until verified, paused, blocked,
+  exhausted, or cancelled.
+- Local testing uses a file under `~/.config/mosaic/runtime/pi/`; the feature never writes an
+  extension asset to `~/.pi/agent/extensions/`.
+- Framework updates deploy the same reviewed extension source through Mosaic's existing manifest
+  sync path.
+
+### Non-functional requirements
+
+1. **Safety:** bounded continuation, explicit cancellation, no arbitrary command execution, and no
+   completion without non-empty reported evidence.
+2. **Reliability:** serialized continuation scheduling, branch-aware restoration, compaction-safe
+   context injection, and stale-timer cancellation on session shutdown.
+3. **Performance:** no extra nested judge-model request on every turn; structured reporting uses the
+   active agent's final terminating tool call.
+4. **Observability:** Pi status/notifications expose phase and bounded counters without recording
+   credentials or hidden model reasoning.
+5. **Maintainability:** the state machine is deterministic and behavior-tested independently from Pi
+   provider/network access.
+
+### Acceptance criteria
+
+1. `AC-PGL-01`: A framework-sync fixture installs the extension at
+   `$MOSAIC_HOME/runtime/pi/goal-extension.ts`, and launcher tests prove both Mosaic Pi extensions are
+   emitted in deterministic order while absent optional files remain backward-compatible.
+2. `AC-PGL-02`: Command tests prove set/status/pause/resume/cancel behavior, active-goal replacement
+   refusal, and bounded input handling.
+3. `AC-PGL-03`: Lifecycle tests prove every turn is recorded, active context is injected on every
+   request, two evidence-bearing achievement reports are required, and `agent_settled` continues an
+   unmet goal without duplicate scheduling.
+4. `AC-PGL-04`: Compaction and restoration tests prove goal state survives, verification is reset and
+   rechecked after compaction, manual compaction continuation is deferred until idle, and tree/session
+   branch state is reconstructed correctly.
+5. `AC-PGL-05`: Limit tests prove max-turn and repeated-no-progress exhaustion stop autonomous
+   continuation, while pause/cancel/blocked states do not restart.
+6. `AC-PGL-06`: Focused tests, package typecheck/lint/test, repository quality gates, a local Pi load
+   smoke test from `~/.config/mosaic/runtime/pi/`, independent review, and terminal-green CI pass before
+   issue #1150 closes.
+
+### Constraints, risks, and assumptions
+
+- Dependency: Pi's extension API must continue to provide `registerCommand`, `registerTool`,
+  `context`, `turn_end`, `agent_settled`, `session_compact`, session custom entries, and terminating
+  tool results.
+- Risk: the working agent can overstate completion. Mitigation: structured evidence, a mandatory
+  second verification pass, explicit semantic limitations, and operator-visible reports.
+- Risk: an impossible goal can consume unbounded resources. Mitigation: hard turn/no-progress bounds
+  and paused terminal states.
+- Risk: automatic continuation can race compaction or session replacement. Mitigation: drive from
+  `agent_settled`, defer idle restarts, generation-check timers, and clear timers on shutdown.
+- `ASSUMPTION:` Two consecutive evidence-bearing reports are the initial local verification policy;
+  rationale: it provides a real recheck without doubling every turn's model cost. Future policy may
+  add independent or deterministic validators.
+- `ASSUMPTION:` Default limits are 40 turns and 6 repeated no-progress reports, configurable only by
+  bounded Mosaic environment settings; rationale: useful persistence with a finite autonomous budget.
+- `ASSUMPTION:` Documentation remains canonical in-repo for this slice; no external docs publication
+  is requested.
+
+### Testing and delivery intent
+
+Use TDD for the deterministic controller and lifecycle invariants. Test with fake Pi lifecycle
+objects first, then run a local load/smoke test from the deployed Mosaic path. Deliver source, tests,
+launcher wiring, framework/runtime documentation, user/developer guides, and sitemap updates in one
+reviewed squash PR to `main` with terminal-green CI.
+
+---
+
+## Fleet Declarative Configuration Management Workstream (FCM, #758)
+
+### Problem and objective
+
+The local Mosaic fleet has a roster, generated agent environment files, user-systemd units, tmux
+sessions, heartbeat files, examples, profiles, and separate gateway-backed agent records. These
+planes have drifted and are not one safe operator lifecycle. The objective is one **local fleet
+roster** as the desired-state SSOT, with generated environment, systemd, tmux, and heartbeat
+artifacts as rebuildable projections; it does not merge the local fleet control plane with the
+gateway-backed agent catalog.
+
+### Normative requirements
+
+| ID           | Requirement                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `FCM-REQ-01` | The roster SHALL be the sole writable desired-state source for local fleet membership, launch policy, and persisted lifecycle target. Generated environment files, systemd enablement, tmux sessions, and heartbeat state SHALL be non-authoritative projections.                                                                                                                                                                                                         |
+| `FCM-REQ-02` | The implementation SHALL provide one executable structural contract for YAML/JSON input and one shared semantic validator. Roster load, profile validation, provision, migration, and apply SHALL reuse the existing baseline-plus-`roles.local` profile/persona resolver; a parallel role resolver is forbidden.                                                                                                                                                         |
+| `FCM-REQ-03` | The local fleet CLI SHALL expose documented programmatic validate, show, plan, apply/reconcile, create, inspect, update, delete, start, stop, restart, status, verify, and doctor operations with stable JSON and exit-code behavior. Existing `fleet add/remove` compatibility aliases may remain during the stated deprecation window.                                                                                                                                  |
+| `FCM-REQ-04` | A fresh create SHALL persist `enabled:true` and `desired_state:stopped` unless an explicit persisted start is requested. The model SHALL distinguish enabled state, persisted desired state, and observed state. Migration, apply, reboot, and rollback SHALL not start an agent that was observed stopped before cutover.                                                                                                                                                |
+| `FCM-REQ-05` | The launch chain SHALL consume deterministic, digest-stamped generated input only. Optional local overrides SHALL be parsed as strict data, may not shadow authoritative generated keys, and may not contain arbitrary commands, credential values, channels, or unknown `MOSAIC_AGENT_*` keys. Forbidden legacy keys, including `MOSAIC_AGENT_COMMAND`, SHALL be privately quarantined before launch and reported only by key name and content hash.                     |
+| `FCM-REQ-06` | Mutations and apply SHALL validate before mutation, use an expected generation/lock, write projections atomically, produce a deterministic plan, and emit recovery information on partial failure. Reconciliation SHALL act only on local, enabled, roster-owned projections and SHALL not kill unmanaged tmux sessions by fuzzy name.                                                                                                                                    |
+| `FCM-REQ-07` | Canonical required classes are `code`, `review`, `validator`, `orchestrator`, `team-leader`, `enhancer`, and `interaction`. `validator` issues an independent final certificate but has no merge authority; `merge-gate` remains sole approve-to-land/merge authority. Team-leader capacity is bounded by an orchestrator-issued lease, and interaction is request/status only. Tess and Ultron are configurable instance/display names, not required machine identities. |
+| `FCM-REQ-08` | v1 migration SHALL be field-complete, reversible, and explicit about aliases, unresolved classes, lifecycle inference, generated-file regeneration, local override quarantine, schema-only remote/connector fields, and rollback. Every shipped example, profile, and service preset SHALL be migrated and executable, retained as an explicitly versioned v1 fixture, or retired with a replacement and deprecation note.                                                |
+| `FCM-REQ-09` | M1–M5 SHALL remain local tmux/systemd control-plane work. Remote/SSH reconciliation, connector mutation, secret references, arbitrary command/channel overrides, gateway/API convergence, and UI configuration storage are excluded and require a separate PRD/threat model.                                                                                                                                                                                              |
+| `FCM-REQ-10` | Documentation and examples are delivery gates. The M0 checklist at [docs/fleet/FLEET-CONFIG-DOCS-IA-CHECKLIST.md](../../fleet/FLEET-CONFIG-DOCS-IA-CHECKLIST.md) and the baseline disposition inventory at [docs/fleet/LEGACY-EXAMPLE-PROFILE-DISPOSITION-INVENTORY.md](../../fleet/LEGACY-EXAMPLE-PROFILE-DISPOSITION-INVENTORY.md) SHALL be maintained as acceptance evidence.                                                                                          |
+
+### Acceptance criteria
+
+1. `AC-FCM-01`: A valid local v2 roster can be parsed from YAML or JSON, validated structurally and semantically through the shared resolver, and rendered canonically; invalid fields, duplicate names, unresolved classes, unsupported runtime/model combinations, socket ambiguity, and incompatible options fail closed.
+2. `AC-FCM-02`: `plan` reports deterministic desired-versus-observed differences for roster, generated environment, systemd enablement, tmux/session, heartbeat, installed-asset revision, and provable orphans without mutation; `apply --check` reports drift without mutation.
+3. `AC-FCM-03`: Local create/update/delete is generation-guarded, atomic, idempotent, and safe by default; it permits supported runtime/model/harness/effort/workdir/role changes without direct editing of generated environment files and does not start a newly created agent unless explicitly persisted.
+4. `AC-FCM-04`: The generated-env/local-override launch chain rejects generated-key shadowing, arbitrary command override, unknown keys, shell evaluation, and sensitive-value diagnostics before any agent starts; known-safe legacy input is regenerated or strictly relocated, and forbidden input is quarantined.
+5. `AC-FCM-05`: Local lifecycle reconciliation implements the persisted/transient start-stop rules, exact default/named tmux socket targeting, systemd/tmux status, stale generated state, unmanaged-session reporting, and rollback without surprise restarts or fuzzy destructive targeting.
+6. `AC-FCM-06`: A v1 roster migration previews field-by-field disposition, preserves observed stopped/running state, inventories rather than reconciles remote/schema-only entries, supports a canary and rollback, and classifies every shipped example, profile, and service preset according to the M0 inventory.
+7. `AC-FCM-07`: Required role authority is validated: validator certificate is consumed but does not merge, merge-gate is the sole merge authority, team-leader leases do not change roster/credentials/authority, and interaction/Tess cannot claim orchestration or merge powers.
+8. `AC-FCM-08`: Documentation, examples, migration, troubleshooting, operational recovery, package/update asset drift, schema/example/profile validation, independent code/security review, validator certificate, and terminal-green CI are complete before #758 closes.
+
+### M0 implementation gate
+
+No source, schema, role, example, profile, systemd, or live-fleet change is authorized before M0
+lands. M0 consists only of these normative requirements, the complete task DAG, the scoped
+documentation IA checklist, and the legacy example/profile disposition inventory. Subsequent cards
+are defined in [docs/TASKS.md](../../TASKS.md) and must remain one card/one PR.
+
+### Fleet git identity launch propagation (#1043)
+
+#### Problem and objective
+
+A fleet seat can have a registered per-agent Git credential while its launched runtime process lacks
+`MOSAIC_GIT_IDENTITY`. The credential resolver then cannot select the seat identity reliably, which
+blocks repository operations on fail-closed estates and can fall through to an unrelated identity on
+estates where that refusal is not active. The objective is to make Git identity a deterministic,
+roster-derived part of the generated launch projection and prove it reaches the launched process.
+
+#### Normative requirements
+
+1. `FGI-REQ-01`: Every generated fleet agent projection SHALL declare
+   `MOSAIC_GIT_IDENTITY=<MOSAIC_AGENT_NAME>`; a differing or unsafe identity SHALL fail closed before
+   tmux launch.
+2. `FGI-REQ-02`: The clean `/usr/bin/env -i` pane boundary SHALL pass every variable declared by the
+   generated projection, including `MOSAIC_GIT_IDENTITY`, to the launched runtime process.
+3. `FGI-REQ-03`: A behavioral integration test SHALL set-compare the complete generated projection
+   against the launched process environment. Source-text/string-presence assertions are insufficient.
+4. `FGI-REQ-04`: Verification SHALL include RED-first evidence and a delete-the-subject mutation that
+   removes Git-identity pane propagation and makes the behavioral test fail.
+
+#### Acceptance criteria
+
+1. `AC-FGI-01`: A launched seat process contains every key/value pair declared by its generated
+   environment projection, including the roster-derived Git identity.
+2. `AC-FGI-02`: Missing, unsafe, or split Git identity is rejected before a tmux session is created.
+3. `AC-FGI-03`: Focused launcher and generated-environment tests, repository quality gates,
+   independent review, and the required RED/green/R7 evidence are recorded before push.
+
+### Framework shell assertion portability (#1098)
+
+#### Problem and objective
+
+The blocking framework-shell chain can report that a pane command omitted `/usr/bin/env -i` even when
+`-i` matched successfully. A short-circuiting `grep -q` under `set -o pipefail` may close its pipe after
+the match and cause an upstream producer to exit with SIGPIPE, turning a valid semantic result into a
+nonzero aggregate pipeline. The objective is to inspect the captured NUL-delimited argv directly and
+make failures carry the observed records needed for diagnosis.
+
+#### Normative requirements
+
+1. `FSP-REQ-01`: The pane-boundary test SHALL validate an adjacent `/usr/bin/env`, `-i` argv pair from
+   the authoritative NUL-delimited tmux capture without a short-circuit pipeline whose upstream status
+   can override a successful match.
+2. `FSP-REQ-02`: Missing, reversed, or non-adjacent boundary tokens SHALL fail, while valid boundaries
+   SHALL remain valid regardless of trailing argv size, pipe capacity, process scheduling, or host/CI
+   utility implementation.
+3. `FSP-REQ-03`: A failed boundary check SHALL print stable indexed, shell-escaped observed argv records
+   before exiting nonzero; the fixture SHALL continue to contain generated non-secret launch data only.
+4. `FSP-REQ-04`: Verification SHALL include RED-first large-payload evidence, negative token-order
+   controls, the complete focused launcher suite, canonical Woodpecker CI, and independent review.
+
+#### Acceptance criteria
+
+1. `AC-FSP-01`: A large captured argv with adjacent `/usr/bin/env`, `-i` passes even when the former
+   `grep -q` pipeline returns nonzero from an upstream SIGPIPE.
+2. `AC-FSP-02`: Missing executable, missing flag, and detached/reversed flag fixtures return nonzero and
+   emit the indexed observed argv.
+3. `AC-FSP-03`: The focused suite passes on the development host and CI image, and the merged-main
+   Woodpecker pipeline is terminal green before #1098 closes.
+
+---
+
+## Exact Cross-Harness Fleet Communications Contract (#766)
+
+### Problem and objective
+
+Fleet runtime contracts currently combine exact peer rows with generic operational metavariables and
+independently parsed roster data. Non-Claude harnesses can mistake those metavariables for values to
+infer, producing incorrect host, session, socket, or helper targets. The objective is one
+roster-resolved communications contract that every supported harness receives unchanged.
+
+### Normative requirements
+
+1. `FCOM-REQ-01`: Fleet commands and runtime composition SHALL use one shared v1 roster structural
+   resolver. A second lenient communications parser is forbidden.
+2. `FCOM-REQ-02`: The composed contract SHALL render the local roster member's authoritative host,
+   exact agent/session name, resolved tmux socket, exact helper path, and deterministic communications
+   generation.
+3. `FCOM-REQ-03`: Every known peer SHALL have one exact executable command. Same-host commands SHALL
+   omit `-H`; cross-host commands SHALL use only that peer's explicit roster `ssh` target; the one
+   supported fleet-wide named socket SHALL use `-L` with its exact value. A per-agent socket declaration
+   must equal that fleet-wide value; unsupported independent sockets and missing cross-host SSH data SHALL
+   fail closed.
+4. `FCOM-REQ-04`: Operational fleet examples SHALL not contain unresolved host, session, socket, or
+   helper-path metavariables. Agents SHALL select an exact rendered peer row and SHALL NOT infer,
+   substitute, or fuzzy-match targeting values.
+5. `FCOM-REQ-05`: An unknown local member or requested peer SHALL fail closed with exact-name discovery
+   guidance. Runtime composition SHALL not silently omit a requested fleet member's communications
+   contract.
+6. `FCOM-REQ-06`: Claude Code, Codex, OpenCode, and Pi SHALL receive equivalent authoritative
+   communications data through the common runtime composer.
+7. `FCOM-REQ-07`: Tests SHALL prove the contract from framework-source `TOOLS.md`, through a fresh
+   installed `TOOLS.md`, to final runtime composition and helper executability. User-owned installed
+   `TOOLS.md` content SHALL remain preserved.
+8. `FCOM-REQ-08`: Stale installed or active composed context SHALL be reported with deterministic
+   generation/repair/relaunch guidance. Currency requires the expected source and installed contract
+   marker/version plus bounded byte equality. The supported current-version repair SHALL run independently
+   of package updates, preserve divergent `TOOLS.md` bytes in a digest-qualified no-clobber backup, restore
+   a regular executable helper without following symlinks, and be idempotent. Detection and reporting SHALL
+   NOT rewrite active context, restart a session, or mutate a live fleet.
+9. `FCOM-REQ-09`: The shared resolver SHALL preserve and strictly validate every schema-supported v1
+   connector kind (`tmux`, `discord`, and `matrix`) from YAML and JSON. Every accepted snake/camel alias
+   pair SHALL reject differing dual declarations and accept identical declarations. JSON roster fallback
+   SHALL occur only when `roster.yaml` is absent; all other YAML access failures SHALL fail closed.
+10. `FCOM-REQ-10`: The communications generation SHALL cover the complete canonical rendered semantic
+    contract, including identity, role/class, resolved host/socket/helper, peer metadata, and exact commands.
+    Installed helpers SHALL be validated with no-follow filesystem inspection as regular executable files.
+    Keep-mode reseed and relaunch discovery SHALL preserve and support both YAML and JSON rosters.
+
+### Acceptance criteria
+
+1. `AC-FCOM-01`: Contract fixtures contain no unresolved operational targeting metavariables; local
+   identity contains exact host/session/socket/helper values.
+2. `AC-FCOM-02`: Same-host, cross-host, named-socket, literal-default-socket, and missing-SSH tests prove
+   exact targeting and fail-closed behavior.
+3. `AC-FCOM-03`: Unknown identities and peers report known exact names plus an exact self-scoped
+   discovery command; no fuzzy session selection is emitted.
+4. `AC-FCOM-04`: Four-harness tests prove byte-equal authoritative communications sections.
+5. `AC-FCOM-05`: Source, fresh-install, preserved-custom-install, stale-installed, composed-generation,
+   helper executable, agent-send socket isolation, and exact-target tests pass.
+6. `AC-FCOM-06`: Documentation defines non-mutating stale-context detection and operator-authorized,
+   exact-agent relaunch; no implementation path performs automatic session mutation.
+7. `AC-FCOM-07`: YAML and JSON fixtures cover every connector kind; all snake/camel aliases cover
+   identical acceptance and conflicting rejection; non-`ENOENT` YAML failures do not fall back.
+8. `AC-FCOM-08`: Missing, directory, symlink, and non-executable installed helpers fail closed. Explicit
+   current-version repair proves partial-deletion recovery, digest-qualified backup collision safety,
+   symlink-target safety, and repeated-run idempotence.
+9. `AC-FCOM-09`: Markerless-equal and wrong-version source/installed contracts are stale, and a rendered
+   role/class change produces a different communications generation.
+
+---
+
+## KBN-101 Database Runtime/Migration Role Split (#771)
+
+### Problem and objective
+
+PostgreSQL Gateway/storage currently uses one `DATABASE_URL` for runtime queries and migrations. That makes the deployed application identity an owner and prevents certification that KBN immutable event, artifact, checkpoint, and evidence relations reject runtime `UPDATE`/`DELETE`. KBN-101 freezes a least-privilege runtime/migration split before KBN-100 schema work.
+
+### Normative requirements
+
+1. `K101-REQ-01`: `DATABASE_URL` SHALL be the non-owner PostgreSQL runtime connection and `DATABASE_MIGRATION_URL` SHALL be the migration-only owner/migrator connection. They are required respectively for runtime and the dedicated `mosaic-db-migrator --run|--verify` phase in `standalone`/`federated`; local PGlite is the explicit exception. The published `@mosaicstack/db` bin maps exactly `mosaic-db-migrator` to `./dist/cli.js`, its image entrypoint is exactly `mosaic-db-migrator`, accepts no URL/SQL/schema/role argv, and returns stable sanitized exits. Every current/future PostgreSQL DDL entrypoint SHALL route to that runner or be denied, and SHALL reject `DATABASE_URL`-only execution before connection/DDL. Data migration may connect only after the runner prepares and verifies the PostgreSQL target, through dedicated non-DDL `mosaic_data_importer` and exactly `--target-url-file /run/secrets/mosaic-migrate-target-url`, its fixed paired authenticated provider-version file `/run/secrets/mosaic-migrate-target-version`, plus `--target-attestation-file /run/mosaic-attestations/migrate-target.v1.json`. KBN-101-05 obtains URL key `url` and version only from the same successful Vault KV-v2 response at `secret-{env}/mosaic-stack/database/importer` (`data.metadata.version`), renders them as one immutable generation into separate consumer copies, and never infers a provider version from DSN bytes. The trusted runner verifies TLS/identity/manifest, reads its fixed importer URL/version copies only for binding through safe no-follow fd checks, and signs a credential-free JCS/Ed25519 attestation using its runner-only fixed root-owned private-key file; no signing key reaches importer/runtime. The artifact binds secret version and SHA-256 of exact high-entropy credential-file bytes, canonical TLS host/port/database, CA/SPKI, PostgreSQL system identifier/database OID, importer role, manifest/schema fingerprints, producer invocation/build/image digest, issued/expires/nonce, and correlation. Before target connection the importer validates URL/version/attestation/public-key files, signature/key/expiry/replay/authenticated provider version/digest/generation/bindings and the importer-only CA at exact `DATABASE_TLS_CA_CERT_PATH`; after verified TLS and before DML it validates server/database/role/CA/schema identity, with same-fd/in-memory-byte TOCTOU protection, rotation/revocation, a privileged producer-only-to-importer-only artifact handoff controller that verifies/copies/fsyncs/atomically renames/seals before importer start, consumer isolation/no logging-oracle, and sanitized errors. Raw `--target-url`, `DATABASE_URL` fallback, runtime-owner use, missing/unsafe/substituted files, stale/replayed/tampered/wrong-key attestation, wrong binding, and DDL attempt fail before target connection/DDL; post-connect mismatch closes with zero DML/DDL. A reviewed finite classifier inventories executable current source/scripts/package bins, operator docs, deploy manifests, and exact normative contracts by path; active secure records pin both options/files, producer/key/bindings/tests, while normative contracts cannot mask instructions. Unknown active commands, duplicate-owner, ownerless, missing-path, and historical/status-only masking hits fail. `db:push` is forbidden outside an explicitly disposable local developer database and cannot accept a production-like URL.
+2. `K101-REQ-02`: Gateway runtime/replicas SHALL not execute migrations or DDL. The runner SHALL hold one `max:1` session and fixed two-int advisory namespace `1297044289` (`MOSA`), `1262636593` (`KBN1`) across preflight, reconciliation, migration, verification, and release. It SHALL compare the versioned canonical manifest v1 tuple (journal logical index/tag plus exact SQL-byte SHA-256) to the complete observed ledger mapping; count/set-only, timestamps, and physical insertion order are non-normative and insufficient.
+3. `K101-REQ-03`: PostgreSQL SHALL separate non-login platform database owner, non-login schema owner, dedicated `NOLOGIN SUPERUSER` `mosaic_extension_owner`, login migrator, dedicated login non-DDL data importer, non-login runtime capability, and login runtime roles. For PostgreSQL 17 + pgvector 0.8.2, `vector` is untrusted (`trusted` is absent and `relocatable=true`): only an externally controlled audited platform-bootstrap superuser session may `SET ROLE mosaic_extension_owner` for CREATE/UPDATE/SET SCHEMA, then `RESET ROLE`; the role has `rolcanlogin=false`, `rolsuper=true`, zero members, no runtime credential/Vault secret, and is never provided to app containers. It owns `mosaic_extensions`, fresh `vector`, and owner-bearing extension members, while `mosaic_schema_owner` receives only `USAGE` for type resolution and never ownership/`CREATE`/`ALTER`/`DROP`/member-change/default-privilege authority there. Superuser cannot be constrained by `GRANT`/`REVOKE`; this is identity/non-login/no-membership/external-control/audit isolation, not a false least-privilege claim. Extension operations require control-plane change, independent review, backup/rollback, maintenance window, and audit evidence. Managed targets that cannot establish this exact role are ineligible until an independently approved versioned provider-owned extension-owner profile exists; app/migrator ownership is never silently retained. Existing approved-owner extension relocation validates exact `pg_namespace.nspowner`, `pg_extension.extowner`, member ownership/schema/version, while legacy runtime-owned extension fails closed to a controlled shadow-database migration—never unsupported ownership alteration, catalog mutation, ownership adoption, or `DROP CASCADE`. Runtime, migrator, schema owner, importer, and all service roles must fail `SET ROLE`, catalog/direct `ALTER`/`UPDATE`/`DROP`/membership-change denial, role ownership, superuser/role-creation/schema-creation/TEMPORARY, unsafe membership, untrusted search path, missing grants, unauthenticated TLS, and immutable privilege drift checks. Application schema is fixed `mosaic` with exact `pg_catalog,mosaic` session path; historical public migrations remain byte-immutable legacy bootstrap only, every future Drizzle application declaration targets `mosaic`, and `vector` is explicitly qualified from non-writable `mosaic_extensions`. No config-derived SQL identifier is permitted.
+4. `K101-REQ-04`: `mosaicstack/stack` KBN-101-00 SHALL exclusively own `infra/pg-bootstrap/roles.sql`, `infra/pg-bootstrap/extensions.sql`, `infra/pg-bootstrap/README.md`, and bootstrap tests; KBN-101-05 SHALL exclusively own `tools/db/render-postgres-secrets.ts`, its tests, and current Compose/Portainer/two-gateway deployment declarations, consuming the versioned bootstrap interface without overlap. Environment IaC/Vault is named input and Mosaic deployment control plane/Jason is activation authority. Distinct runtime/migrator/importer URL, importer authenticated provider-version, DB-client CA, Gateway leaf, and PostgreSQL server key/certificate materials are provisioned before a production-like database starts. Importer and migrator have separate immutable URL/version copies at fixed `10002:10002`/`10003:10003` identities; runtime/unrelated containers receive neither importer material, attestation private key, or importer artifact. Runtime, migrator, and importer require their mounted CA plus `sslmode=verify-full`. Exact UID/GID/mode/rendering, service-DNS SANs, Vault/compose/Swarm consumer isolation, two-gateway pair ordering, server activation, pre-enforcement legacy-client drain and `hostssl` zero-plaintext-session proof, fresh/existing transition, CA-overlap rotation, TLS-only rollback, and standalone/federated/Swarm/two-gateway positive/negative TLS evidence are required. No application-generated production certificate or plaintext bootstrap exception is permitted.
+5. `K101-REQ-05`: KBN immutable relations SHALL permit the real runtime role INSERT/SELECT only and deny UPDATE/DELETE; parent retention remains RESTRICT/no-cascade. Role/password/Vault creation is external platform control, never application migration/source.
+6. `K101-REQ-06`: N-1 single-URL compatibility, rollout/rollback, Vault ownership/rotation/redaction, CI, installer, compose/Portainer, observability, and deployment handoffs SHALL be separately bounded one-card/one-PR work. Prepared slices remain inactive while current owner-runtime deployments stay N-1; Mosaic control plane/Jason alone authorizes one final atomic activation or rollback, with no force-on-red/bypass. KBN-101 planning itself SHALL not mutate production.
+7. `K101-REQ-07`: KBN-100 SHALL begin only after the KBN-101 foundation role/schema-boundary certificate; it SHALL rebase on that main head, restore generated Drizzle declaration/snapshot/journal consistency, and bound procedural immutable-table grant/trigger/backfill additions to its schema slice. KBN-101 real deployed-role immutable-operation certification SHALL complete after KBN-100 creates those relations and before KBN-105.
+
+### Acceptance criteria
+
+1. `AC-K101-01`: DTO/command-matrix tests prove required modes, PGlite exception, `mosaic-db-migrator --help|--run|--verify`/stable exits/argv refusal, public-import negative, every finite classified DDL/static-bypass inventory path and both harness pairs reject `DATABASE_URL`-only before connection/DDL, no migration-to-runtime fallback, and `db:push` refusal outside an allowlisted disposable DB. Before inventory, ownership, or status masking, the semantic fixture fails README's exact former commented code-fence generic-wrapper form and the user guide's exact former executable generic-wrapper form; source-consistency proves current `packages/storage/src/cli.ts` directly `execSync`s `pnpm --filter @mosaicstack/db db:migrate` and no `mosaic-db-migrator` bin exists, so runner-delegation documentation fails. The active `docs/guides/migrate-tier.md` route is inventoried to KBN-101-07 and proves runner-produced `--target-url-file /run/secrets/mosaic-migrate-target-url`, fixed paired provider-version file, and `--target-attestation-file /run/mosaic-attestations/migrate-target.v1.json`; runner-only signing/private-key isolation; Vault KV-v2 same-response version provenance, separate immutable generation mounts, importer CA, JCS/Ed25519 signature/key rotation/revocation, atomic artifact, expiry/replay, safe-fd secret-version/digest, canonical TLS/CA/server/database/role/manifest/schema bindings, dedicated non-DDL importer, consumer isolation/no log-oracle, and exact no-connection versus zero-DML rejection for missing/wrong/stale/replayed/tampered/wrong-key/substituted/generation-mismatched inputs. The full current non-normative docs inventory—including user guide, federation historical task/MILESTONES status, and non-operative SETUP—has an exact safe disposition. Scanner semantic checks reject automatic first-boot/startup extension/schema/migration wording, Compose-up-before-runner, init-script authority, production `.env`/monorepo auto-load/`EnvironmentFile=`/credential-export-or-argv/restart-as-secret-activation routes, and every unqualified operator-document `mosaic-db-migrator --run|--verify` hit regardless of named/normative/status classification. The exact former README/dev/deployment Compose-first sequences, former SETUP wording, exact former MILESTONES wording `pgvector extension installed + verified on startup`, former architecture-plan/PERFORMANCE/backlog runner routes, and any unqualified runner fixture fail before inventory masking. Only one `Held future procedure` Markdown section—bounded through the next equal-or-higher heading—may contain the explicit non-operative/no-current-command-authority form that names KBN-101-00/-03/-05 and preserves external bootstrap → TLS/roles → `mosaic-db-migrator --run` → `mosaic-db-migrator --verify` → Gateway/Compose readiness; every runner hit outside that section fails. The README assertion for the checked-in direct CI `pnpm --filter @mosaicstack/db run db:migrate` with `DATABASE_URL` passes only as active legacy N-1, uncertified, non-authorizing-as-an-operator-route status against an isolated disposable CI database pending KBN-101-06 removal—not as an ordinary operator or approved DDL-authority route. Only local PGlite data-layer work or non-PostgreSQL Compose is current (Gateway/Web local startup is held pending daemon/inherited/project-DSN rejection).
+2. `AC-K101-02`: Fixed namespace lock contention/crash/readiness/non-interference and exact manifest-v1 reconciliation tests prove no replica race/runtime auto-migration and fail closed on every missing/unknown/duplicate/ambiguous/corrupt/stale ledger state.
+3. `AC-K101-03`: Actual PostgreSQL 17 + pgvector 0.8.2 control-file, catalog, Drizzle-generation, vector-query/operator, fresh/approved-owner/legacy-shadow/partial/resume/rollback/N-1, and real deployed-role tests prove `trusted` absent/untrusted plus relocatability, external-superuser `SET ROLE` create/update/`RESET ROLE` audit, exact `rolcanlogin=false`/`rolsuper=true`/zero-membership/no-runtime-secret state, platform/schema/extension-owner/migrator/importer/runtime separation, `pg_extension.extowner` plus owner-bearing extension-member/schema/version assertions, and runtime/migrator/schema-owner/importer/all-service-role `SET ROLE`/ALTER/DROP/member-update denial. They also prove `pg_catalog,mosaic` per-session pool safety, `mosaic_extensions` qualification, identifier injection denial, ownership/membership/ledger-read/TEMP/default grants, and unsafe privilege denial.
+4. `AC-K101-04`: Disposable standalone, federated/Swarm, and two-gateway verified-TLS positives plus for both pairs missing CA/wrong CA/wrong SAN/sslmode downgrade, server/Gateway key mode, UID/GID, secret-consumer isolation, and legacy-drain/`hostssl` negatives prove server bootstrap, ordering, and readiness; PGlite is expressly excluded from this PostgreSQL evidence.
+5. `AC-K101-05`: Real runtime-role evidence proves INSERT/SELECT succeeds and UPDATE/DELETE fails for every frozen immutable KBN relation.
+6. `AC-K101-06`: N-1/atomic activation/rollback, Vault/CA-overlap rotation/redaction, health/operator behavior, CI/deployment handoff, independent exact-head security review, and terminal-green CI evidence the foundation before KBN-100; after KBN-100, the real deployed-role immutable-operation certificate and Ultron approval release KBN-105.
+
+**Normative implementation contract:** [`docs/native-kanban-sot/KBN-101-DB-ROLE-SPLIT.md`](../../native-kanban-sot/KBN-101-DB-ROLE-SPLIT.md). `ASSUMPTION:` existing `standalone` and `federated` are all PostgreSQL production-like modes; any new PostgreSQL tier inherits these requirements until an explicit versioned amendment.
+
+---
+
+## Tess Interaction Agent Workstream (TESS)
+
+### Problem and Objective
+
+Jason needs one durable, operator-facing Mosaic agent outside Hermes that is reachable through a dedicated Discord channel and CLI, can attach to and operate the Mosaic fleet and transitional Hermes agents, and preserves context across restarts and compaction. Mos remains the coding/general fleet orchestrator; Tess is the complementary human interaction, visibility, control, and migration agent.
+
+The objective is to ship **Tess** (from _tessera_, a piece of a mosaic) as a Pi-native, GPT-5.6 Sol agent with high reasoning. Tess must use Mosaic-owned contracts and plugins so Hermes can be replaced incrementally rather than becoming a permanent architectural dependency.
+
+### Scope
+
+#### In Scope
+
+1. `TESS-ARP-001`: A runtime-neutral `AgentRuntimeProvider` contract supporting `listSessions`, `streamSession`, `sendMessage`, `terminate`, `getSessionTree`, `attach`, health, capability discovery, and normalized events/errors.
+2. `TESS-PI-001`: A long-running Pi-native Tess agent profile/service pinned to GPT-5.6 Sol with high reasoning, explicit tool policy, lifecycle hooks, durable checkpoints, and restart recovery.
+3. `TESS-DSC-001`: Dedicated Discord channel binding to Tess through the Mosaic gateway, with allowlists/RBAC, thread/reply policy, streaming, attachments, approvals, and correlation IDs.
+4. `TESS-CLI-001`: `mosaic tess` CLI commands for chat, status, session listing, attach/detach, send/steer/stop, provider health, and recovery.
+5. `TESS-FLT-001`: Fleet plugin capabilities for roster/status/heartbeat inspection, message delivery, session hierarchy, safe attach, and controlled restart/recovery.
+6. `TESS-MOS-001`: Explicit Mos coordination boundary and tools: hand off orchestration requests, observe mission/task state, receive results, and never silently compete for orchestration authority.
+7. `TESS-HRM-001`: Transitional Hermes adapter for profiles/agents, sessions, streaming/messages, Kanban, skills, memory, tools, cron, and health, using capability negotiation and fail-closed unsupported operations.
+8. `TESS-MEM-001`: Unified memory/retrieval plugin with scoped search/recent/capture/stats, startup context injection, provenance, redaction, namespace isolation, and flat-file/project truth precedence.
+9. `TESS-STA-001`: Durable agent state, inbox, handoff, compaction-recovery, and resume reconstruction.
+10. `TESS-PLG-001`: Plugin/tool catalog covering runtime bootstrap, repository/PR workflow, fleet diagnostics, incident-safe read operations, Discord interaction, and extensible MCP/skill discovery.
+11. `TESS-TRN-001`: Replaceable transport providers: tmux/fleet now, Matrix/native Mosaic transport later, with no Discord/CLI business logic coupled to transport details.
+12. `TESS-SEC-001`: RBAC, per-operation authorization, explicit approval for destructive/privileged/customer-visible actions, audit events, secret/PII redaction, tenant isolation, and bounded command execution.
+13. `TESS-SEC-002`: Command execution SHALL enforce declared scope/role server-side; admin/system and destructive operations SHALL require policy-bound durable approval.
+14. `TESS-SEC-003`: Every session list/read/attach/send/terminate operation SHALL enforce server-derived owner and tenant scope; guessed or client-supplied IDs SHALL grant no authority.
+15. `TESS-SEC-004`: MCP tools SHALL derive actor/tenant from authenticated context and SHALL NOT accept caller-controlled identity fields.
+16. `TESS-SEC-005`: Discord plugin ingress SHALL authenticate service identity, enforce guild/channel/user allowlists, propagate correlation/message IDs, and reject replay.
+17. `TESS-SEC-006`: Secret/PII classification and redaction SHALL occur before persistence and before channel egress, including tool metadata and authentication flows.
+18. `TESS-SEC-007`: Approvals SHALL be one-time, expiring, actor/tenant-bound, and cryptographically bound to the exact structured action digest.
+19. `TESS-SEC-008`: Ingress, provider sends, tool side effects, and responses SHALL use durable inbox/outbox/checkpoints and idempotency records for restart-safe replay.
+20. `TESS-SEC-009`: Garbage collection and retention SHALL be session/tenant scoped unless executed as a separately authorized and audited system-wide job.
+21. `TESS-OBS-001`: Structured logs, traces, health/readiness, provider latency/errors, session lifecycle, tool audit, and actionable recovery diagnostics.
+22. `TESS-MIG-001`: Capability inventory and staged Hermes-to-Mosaic migration matrix with coexistence, cutover, rollback, and deprecation gates.
+
+#### Out of Scope
+
+1. Replacing Mos as coding/general fleet orchestrator.
+2. Making Hermes the Mosaic core or coupling Mosaic domain logic to Hermes schemas.
+3. Migrating every historical chat verbatim; only policy-compliant indexed summaries and user-selected sessions are migrated.
+4. Unrestricted shell execution from Discord.
+5. Full web UI parity in the first Tess operational milestone; gateway contracts must remain web-consumable.
+6. Replacing tmux before Matrix/native transport reaches operational parity.
+
+### Stakeholder and User Requirements
+
+- Jason must be able to converse with the same Tess session from Discord and CLI.
+- Jason must be able to see what is running, stale, blocked, or unhealthy without attaching manually to every session.
+- Jason must be able to attach to Tess and authorized fleet sessions through supported CLI controls.
+- Tess must collaborate with Mos and the fleet while preserving a single clear orchestration authority.
+- The system must migrate useful Hermes/OpenClaw capabilities intentionally, with evidence, instead of copying implementations wholesale.
+
+### Non-Functional Requirements
+
+1. **Security:** default-deny provider/tool capabilities, least privilege, no secrets in logs/prompts/commits, Discord user/channel authorization, and auditable approvals.
+2. **Reliability:** durable inbox/checkpoints; idempotent message handling; reconnect with bounded backoff; no message loss or duplicate execution across gateway restart.
+3. **Performance:** first acknowledgement within 2 seconds when connected; streamed agent output begins within 5 seconds excluding model/provider delay; status reads return within 2 seconds under nominal local conditions.
+4. **Observability:** every ingress message and resulting provider/tool operation carries a correlation ID across Discord, gateway, Tess, provider, and audit events.
+5. **Maintainability:** channel, runtime, transport, memory, and external-agent integrations remain adapter-based with contract tests.
+6. **Privacy:** only scoped context enters external runtimes; persisted messages/memories follow retention and redaction policy.
+7. **Portability:** Tess runs through Pi/Mosaic contracts and does not require Hermes to start or serve native Mosaic operations.
+
+### Acceptance Criteria
+
+1. `AC-TESS-01`: A dedicated Discord channel and `mosaic tess chat` connect to one durable Tess session and stream responses bidirectionally.
+2. `AC-TESS-02`: `mosaic tess status|sessions|tree|attach|send|stop` operate against authorized provider capabilities with stable typed outputs and actionable errors.
+3. `AC-TESS-03`: Tess runs GPT-5.6 Sol at high reasoning and its effective runtime/model/tool policy is visible through status without exposing credentials.
+4. `AC-TESS-04`: Tess can inspect and message the Mosaic fleet, hand orchestration work to Mos, and demonstrate that Tess does not independently claim Mos-owned orchestration work.
+5. `AC-TESS-05`: Hermes adapter demonstrates session listing, streaming/message delivery, hierarchy mapping, and at least one approved capability in each of Kanban, skills, memory, tools, and cron—or reports unsupported capabilities fail-closed.
+6. `AC-TESS-06`: Restart/compaction test preserves session identity, pending inbox, last durable checkpoint, and a resumable handoff without duplicate side effects.
+7. `AC-TESS-07`: Unauthorized Discord users/channels, cross-tenant access, unsafe tool calls, forged approvals, and sensitive-output cases are denied and audited.
+8. `AC-TESS-08`: tmux/fleet and Matrix/native transport implementations pass the same provider contract suite; Matrix may remain non-default until readiness gates pass.
+9. `AC-TESS-09`: Baseline quality gates, unit/integration/contract tests, Discord+CLI E2E, restart/recovery tests, independent code review, and security review are green.
+10. `AC-TESS-10`: Migration matrix documents every audited Hermes/OpenClaw capability as native, adapted, deferred, or rejected, with cutover and rollback evidence.
+11. `AC-TESS-11`: User, admin, developer, API/OpenAPI, operations/recovery, and plugin-authoring documentation is current and linked from the sitemap.
+
+### Constraints, Dependencies, Risks, and Assumptions
+
+- Dependency: Mosaic gateway remains the single API surface; Pi is the native runtime; Valkey/PostgreSQL provide canonical durable state where required.
+- Dependency: Discord bot credentials and dedicated channel ID are deployment secrets provisioned outside source control.
+- Risk: Tess could drift into a second orchestrator. Mitigation: explicit role policy, Mos handoff contract, authority checks, and E2E boundary tests.
+- Risk: broad Hermes compatibility can freeze legacy semantics into Mosaic. Mitigation: Mosaic-owned normalized contracts and capability negotiation.
+- Risk: Discord creates a privileged remote-control surface. Mitigation: pairing/allowlists, RBAC, approvals, rate limits, audit, and safe tool classes.
+- Risk: transcript ingestion can violate privacy or overload memory. Mitigation: scoped opt-in import, redacted summaries, provenance, retention, and deduplication.
+- Risk: current root filesystem has limited headroom. Mitigation: isolated worktrees, no duplicated dependency installation unless required, and cleanup only after active-lane verification.
+- `ASSUMPTION:` The public name is **Tess**, because the user requested a name and the tessera/Mosaic relationship is distinctive; config must permit later display-name changes without renaming APIs or storage keys.
+- `ASSUMPTION:` The dedicated Discord channel ID and final guild policy will be supplied/provisioned during deployment, so implementation uses explicit configuration and fail-fast startup validation.
+- `ASSUMPTION:` tmux/fleet is the production transport for the first operational milestone; Matrix/native transport is implemented behind the same contract and promoted only after parity/reliability verification.
+- `ASSUMPTION:` Project/task truth remains in canonical Mosaic/project stores; semantic memory systems are retrieval/mirror layers, not hidden authorities.
+
+### Testing and Delivery Intent
+
+Delivery uses five gated milestones: runtime contracts/security; Pi service/state; Discord/CLI; fleet/Hermes/plugin suite; migration/Matrix/recovery/qualification. Every source-code task requires tests, independent review, a PR to `main`, terminal-green CI, and issue/task closure. Production activation additionally requires a clean-host Pi launch, dedicated Discord channel smoke test, CLI attach test, restart/recovery drill, and rollback procedure.
+
+---
+
+## Official Channel Plugin Workstream (#756)
+
+### Problem and Objective
+
+The Discord plugin currently couples Discord event handling, gateway bridging, and reply routing in one implementation and activates only on mentions. Mosaic needs an official channel adapter that behaves the same no matter whether the bound logical agent currently runs through Claude, Codex, Pi, OpenCode, or a future harness. The Discord connection and conversation address must remain stable while the gateway changes the runtime provider behind that logical session.
+
+The objective is to make Discord the first implementation of a transport-neutral official channel contract, with explicit authorization and deterministic channel/thread routing that future Matrix, Slack, and other adapters can share.
+
+### Scope
+
+#### In Scope
+
+1. `CHN-001`: Transport-neutral channel adapter, route, message, attachment, authorization-principal, response-target, and health contracts in `@mosaicstack/types`, including trusted per-binding logical-agent configuration selection.
+2. `CHN-002`: Stable channel conversation addresses based on logical agent plus channel/thread identity; harness, model, and runtime-provider IDs are forbidden from channel session keys.
+3. `DSC-001`: An authorized untagged message in a configured agent-bound channel routes to the agent and receives its response in that channel.
+4. `DSC-002`: A bot mention in a configured parent channel creates a Discord thread, or reuses the thread already attached to that same native message; the mentioned turn and subsequent thread turns route and respond in that thread.
+5. `DSC-003`: A message already inside an authorized thread inherits authorization from its configured parent and never attempts a nested thread.
+6. `DSC-004`: Guild, parent channel, user, pairing, and role authorization remains default-deny before thread creation or gateway dispatch.
+7. `DSC-005`: Discord service authentication, HMAC envelope integrity, replay protection, attachments, approvals, response chunking, and correlation behavior remain intact.
+8. `DSC-006`: The Discord adapter exposes lifecycle and health behavior through the shared channel contract without importing a harness SDK.
+
+#### Out of Scope
+
+1. The logical-agent lease, fencing epoch, execution grant, checkpoint, or cross-harness takeover implementation tracked by #754/#755.
+2. Dynamic Discord authorization administration in the web UI.
+3. Multi-guild tenant isolation, DMs, slash commands, voice, reactions, or production bot deployment.
+4. Implementing Matrix or Slack adapters in this slice.
+
+### Non-Functional Requirements
+
+1. **Security:** no thread or dispatch side effect occurs until guild, parent channel, user, pairing, role, and bounded per-user/channel rate checks pass; attachment metadata is shape- and size-bounded; credentials never enter source, messages, session keys, or logs.
+2. **Portability:** channel contracts and stable conversation IDs contain no Claude, Codex, Pi, OpenCode, model, process, or provider-specific field; each configuration-owned binding selects its trusted logical agent without changing the channel identity.
+3. **Reliability:** repeated messages for one channel/thread resolve the same conversation handle; reconnecting the adapter does not require a harness-specific rebinding.
+4. **Maintainability:** Discord-specific API translation stays in the Discord package; gateway and future adapters depend on transport-neutral contracts.
+5. **Observability:** thread creation or routing failure is reported without message content or credential material.
+
+### Acceptance Criteria
+
+1. `AC-CHN-01`: Contract and behavior tests prove the plugin route contains only logical agent plus channel/thread identity and produces the same stable conversation handle regardless of underlying harness selection.
+2. `AC-CHN-02`: A mentioned authorized parent-channel message creates a thread (or reuses its already-attached thread), dispatches to the thread conversation, and targets the response to that thread.
+3. `AC-CHN-03`: An untagged authorized parent-channel message dispatches to the parent conversation and targets the response to the parent channel.
+4. `AC-CHN-04`: Untagged follow-ups inside an authorized thread dispatch and respond in that same thread without creating a nested thread.
+5. `AC-CHN-05`: Unauthorized guilds, channels, users, unpaired users, insufficient roles, and rate-limited senders produce no thread and no gateway dispatch.
+6. `AC-CHN-06`: Shared channel contracts are exported from `@mosaicstack/types`, Discord implements the lifecycle/health seam, and no harness SDK is imported by the plugin.
+7. `AC-CHN-07`: Focused routing/auth tests, package tests, typecheck, lint, formatting, coverage, independent code/security review, and terminal-green CI pass.
+
+### Constraints, Risks, and Assumptions
+
+- Dependency: Mosaic gateway remains the policy, durable-session, audit, and runtime-provider boundary.
+- Constraint: This work must not modify orchestrator-to-Pi migration or #754/#755 lease/fencing files.
+- Risk: accepting untagged messages could create noisy or unintended agent input. Mitigation: only explicitly configured channels and paired, role-authorized users are accepted, with bounded per-user/channel message and thread rates.
+- Risk: Discord thread creation can fail because of channel permissions, archived state, or API rate limits. Mitigation: fail without dispatching a turn whose response destination cannot be honored, and emit sanitized diagnostics.
+- `ASSUMPTION:` Configured channels are dedicated agent interaction surfaces, so authorized untagged human messages are intentional agent input.
+- `ASSUMPTION:` Mention in a parent channel selects a public thread; messages already in a thread remain there because Discord has no nested threads.
+- `ASSUMPTION:` One Discord bot may serve multiple configuration-owned logical-agent bindings.
+- `ASSUMPTION:` Static allowlists and paired-user roles are the authorization administration surface for this slice.
+
+### Testing and Delivery Intent
+
+Use TDD for remote-ingress routing and permission boundaries. Required evidence includes parent-channel mention, untagged parent message, existing-thread follow-up, existing-thread mention, thread reuse, unauthorized side-effect denial, stable harness-neutral conversation identity, adapter health, and regression coverage for signed envelopes and approvals. Deliver through issue #756, a reviewed squash PR to `main`, terminal-green CI, and issue closure.
+
+---
+
+## Mos Runtime Portability Workstream (MOS-PORT)
+
+### Problem and Objective
+
+Mos is currently identified partly by a harness-native session and communication process. Replacement/rebinding exists, but no gateway-enforced logical identity or fencing prevents a stale harness from continuing to reply or execute effects after takeover.
+
+The objective is to make Mos a server-derived logical Mosaic identity whose authority can move safely among runtime connectors. The gateway owns identity, lease, policy, and audit; harnesses remain replaceable adapters.
+
+### M1 Requirements
+
+1. `MOS-PORT-ID-001`: Define a normalized logical-agent identity independent of Claude Code, Pi, Codex, tmux, Matrix, and provider-native session IDs.
+2. `MOS-PORT-LEASE-001`: Persist one exclusive connector lease per tenant/logical-agent/binding with CAS acquisition, monotonic fencing epoch, TTL, heartbeat, explicit release, and takeover.
+3. `MOS-PORT-FENCE-001`: Bind every connector dispatch/execution grant to the current server-derived tenant, logical identity, binding, connector, scopes, expiry, and lease epoch.
+4. `MOS-PORT-FENCE-002`: Reject and audit stale, expired, forged, cross-tenant, cross-binding, and unauthorized grants before connector, channel, provider, or tool side effects.
+5. `MOS-PORT-OBS-001`: Emit credential-safe correlation/audit events for lease acquire, renew, takeover, reject, release, and expiry.
+6. `MOS-PORT-ARCH-001`: Runtime/provider adapters consume normalized lease context without adding harness-native schemas to Mosaic core.
+
+### M1 Acceptance Criteria
+
+1. `AC-MOS-PORT-01`: Two contenders for one binding cannot simultaneously hold current authority under concurrency.
+2. `AC-MOS-PORT-02`: Successful takeover increments the fencing epoch and every operation from the old epoch fails closed before side effects.
+3. `AC-MOS-PORT-03`: Gateway/database restart preserves lease and epoch state; expired leases can be recovered only through the authorized takeover path.
+4. `AC-MOS-PORT-04`: Cross-tenant, cross-agent, cross-binding, forged, and expired lease/grant cases are denied and audited.
+5. `AC-MOS-PORT-05`: Unit, migration, repository close/reopen, concurrency, abuse, gateway integration, independent security review, CI, and documentation gates pass.
+
+### Deferred to Later #754 Milestones
+
+Canonical checkpoint/handoff payloads, exactly-once connector receipts, concrete Claude/Pi/Codex adapters, channel cutover, and full cross-harness failover/rollback E2E are explicitly out of M1 scope.
+
+---
+
+## Workspace placement guard hardening (#1174)
+
+### Problem and objective
+
+The Bash pre-tool guard must prevent Git checkouts and repository state from being placed under
+`$HOME` without refusing ordinary Git commands merely because a source, option value, branch name,
+or metadata mentions `$HOME`. A guard that over-blocks routine work is unsafe because operators
+will route around it.
+
+### Scope and requirements
+
+1. `WPG-REQ-01`: `git clone` and `git worktree add` placement SHALL be judged from their placement
+   operands, not from every HOME-shaped word in the command.
+2. `WPG-REQ-02`: Clone sources, references, templates, environment assignments, and non-placement
+   worktree metadata MAY resolve under HOME when all placement operands resolve elsewhere.
+3. `WPG-REQ-03`: Both attached and separate-value `--separate-git-dir` forms SHALL remain placement
+   operands and SHALL be refused when they resolve under HOME.
+4. `WPG-REQ-04`: Option classification SHALL account for Git's rule-generated boolean negations
+   without relying on an enumerable allowlist of flag spellings.
+5. `WPG-REQ-05`: Quote removal, escapes, shell command boundaries, redirections, and end-of-options
+   handling SHALL preserve existing fail-closed checkout coverage.
+6. `WPG-REQ-06`: Absolute placement aliases SHALL resolve shell-known HOME spellings, dot segments,
+   repeated separators, and existing symlink parents before the HOME boundary comparison.
+7. Relative targets whose effective path depends on the shell cwd are out of scope and tracked by
+   #1197.
+
+### Acceptance and verification
+
+1. Git's own option parser accepts each tested flag, including generated `--no-*` forms, while the
+   guard allows a HOME-valued source with an explicit safe destination.
+2. Equivalent clone and worktree fixtures cover rule-generated negations and remain discriminating
+   against the prior head where the defect existed.
+3. Real HOME destinations and both `--separate-git-dir` forms remain blocked, including placements
+   after shell command boundaries.
+4. The full hermetic guard suite, syntax/static checks, adversarial probes, independent review, and
+   terminal-green CI pass before merge.
+5. Any option-classification residual is documented with its deliberate failure direction.
+
+### Constraints, risks, and assumptions
+
+- Security and usability are co-equal: neither a placement bypass nor routine over-block is an
+  acceptable repair.
+- `ASSUMPTION:` The value-taking option surface exposed by the installed Git version is closed and
+  measurable through Git's own parser/help output; rationale: boolean flags are rule-generated,
+  while separate-value options have explicit grammar and must be classified as such.
+- Risk: a future Git release may add a new value-taking placement option. Mitigation: document the
+  chosen residual direction and pin every currently supported placement option in behavior tests.
+- Risk: a symlink can be replaced after pre-execution canonicalization. Mitigation: resolve every
+  existing parent physically and document the remaining inherent TOCTOU window; the worktree helper
+  remains the authoritative path-derivation mechanism, with atomic closure tracked by #1199.
+
+---
+
+## Release Integrity Workstream (RI, #1275)
+
+### Problem and objective
+
+At `next` 476db12b (review of 2026-08-17), publication from `next` is not bound to the full verification pipeline for the same commit: the publish pipeline's publish steps depend on `build` only, while ordinary push CI excludes `next`. Public Forge/MACP paths contain false-success placeholders: a stub executor that reports `completed` with exit zero, planning/remediation gates that execute literal `true`, a review gate that echoes an approving verdict, and a gate runner that treats empty commands and unimplemented CI-provider gates as passing. Shipping UI surfaces can render a failed fetch as an empty, healthy collection.
+
+Objective: for alpha 0.0.50, the release cannot publish, report, or display work state that the repository has not actually verified. Decisions SDLC-D-033 through SDLC-D-038 (Jason, 2026-08-17) scope this floor; full decision text and required-behavior lists live in jarvis-brain `docs/plans/2026-08-16_mosaic-stack-sdlc-protocol.md` and `data/decisions/mosaic-stack-sdlc-protocol.json`. This section restates only the normative requirements.
+
+### Normative requirements
+
+1. **RI-N1 Exact-commit publication verification (SDLC-D-034).** One canonical terminal verification command performs self-contained re-verification in the publish pipeline against the job's checked-out commit before any external publication effect. The command contains or invokes the complete mandatory verification set (semantic parity with the PR merge gate, including sanitization, upgrade-guard, typecheck, lint, format check, tests, and build); CI and publication do not maintain separate semantic checklists. Every publish step depends on the verification step in the executable pipeline DAG. Provider commit identity and `git rev-parse HEAD` must identify the same commit. Missing, skipped, cancelled, stale, or inconclusive checks fail closed. Documentation-only runs may skip publication but cannot bypass verification when a publication effect will occur. A negative control must prove that a broken check blocks every publish step.
+
+2. **RI-N2 Fail-closed Forge/MACP with explicit simulation (SDLC-D-035).** Simulation requires explicit caller intent (e.g. `--simulate`) and produces a distinct typed `simulated` state that can never satisfy dependencies, acceptance criteria, gates, merge, or release. Normal execution exits nonzero with a typed capability failure when a required executor, reviewer, command, or CI provider is absent — no stub completion, no literal-`true` gates, no synthetic approvals, no empty-command passes. A manual gate with no automation enters a waiting state; it does not pass. Positive tests prove explicit simulation still works; negative controls prove simulation and every missing-provider case cannot advance lifecycle state.
+
+3. **RI-N3 One transitional PRD authority (SDLC-D-036).** `@mosaicstack/prdy` structured storage under `docs/prdy/`, driven by `mosaic mission --plan`, is the authoritative PRD representation for the alpha. `mosaic prdy` either routes through the same application service or operates only as an explicit, named Markdown import/export adapter; `docs/PRD.md` is not a peer authority. `mission --plan` must persist the mission↔PRD linkage (mission id/version, PRD id/version, selected requirements). Markdown output is a generated view carrying source identity; editing it cannot mutate authority silently. Import is explicit, validated, and conflict-aware (proposed successor, never overwrite). Structural validity is separate from approval.
+
+4. **RI-N4 One quality-rails evaluator (SDLC-D-037).** The TypeScript quality-rails package is the sole authoritative evaluator. A complete probe inventory maps every current TypeScript and shell check to one canonical check with disposition (preserve/strengthen/retire, each named). Effective shell enforcement probes are absorbed before their independent paths retire; expected-file presence alone is not parity. The evaluator returns typed results (`passed`/`failed`/`blocked`/`error`/`not-applicable`) with check version, subject, and reason; missing implementation, missing input, unknown check, process error, timeout, or malformed output can never become `passed` or an unqualified skip. Check definitions and policy are versioned and digested. Shell commands become thin adapters with no separate verdict logic. The canonical terminal verification command (RI-N1) invokes this evaluator rather than duplicating its logic. Contract, parity, and negative-control tests are required, plus independent review of probe equivalence.
+
+5. **RI-N5 Consequence-aware stale UI (SDLC-D-038).** Mission Control distinguishes typed freshness states (`current`, `stale`, `partial`, `unknown`, `unavailable`) rather than inferring from empty arrays or null. A failed fetch never renders as an empty healthy collection. Last-known data may display for situational awareness only with source identity, version, and age visibly labeled; any derived completion/assurance/release verdict whose inputs are stale becomes `unknown`; all state-changing actions are disabled until fresh state loads and is revalidated. With no verified snapshot, surfaces show an explicit unavailable state. Cache corruption, cross-workspace data, schema mismatch, and version regression invalidate the snapshot. Tests cover the failure matrix (network, auth, malformed, partial, corruption, stale age, schema mismatch, recovery, stale-action rejection) with negative controls proving no case yields a current green verdict or enabled mutation.
+
+### Acceptance criteria
+
+- AC-RI-1: A push to `next` that fails any mandatory verification step publishes nothing (no npm package, no image), demonstrated by a checked-in negative control and by pipeline evidence on a real `next` publish run where the verification step is green and every publish step depends on it.
+- AC-RI-2: With no executor/reviewer/CI provider wired, Forge and MACP normal runs exit nonzero with typed capability failures; with `--simulate`, runs complete but every result is typed `simulated` and cannot satisfy any gate, dependency, or completion state — proven by unit tests including negative controls.
+- AC-RI-3: A PRD created or revised through either `mosaic mission --plan` or `mosaic prdy` resolves to one authority under `docs/prdy/` with stable identities and versions; the mission↔PRD linkage survives restart; a Markdown export is labeled as generated and cannot silently become a second writer; divergent legacy content blocks baseline claims until explicitly resolved — proven by contract tests.
+- AC-RI-4: `quality-rails check` through any entry point (TS CLI, framework shell adapter) returns the same typed verdict for the same subject; the probe inventory names every legacy check's disposition; a deliberately broken probe fails closed — proven by contract/parity/negative-control tests and independent review of probe equivalence.
+- AC-RI-5: No shipping surface renders a failed fetch as an empty healthy state; stale/partial/unavailable states are typed, labeled, and mutation-disabled — proven by the failure-matrix tests.
+- AC-RI-6: All cards merged to `next` via squash PR with terminal-green CI; release evidence for 0.0.50 records commit, verification run, and published artifacts.
+
+### Out of scope
+
+The canonical dispatcher/control-plane vertical slice (work graph, execution attempts, fenced leases, typed check-in, independent verifier dispatch) is decided post-alpha (SDLC-D-033, option B). Multi-pipeline verification certificates (SDLC-D-034 option B) are post-alpha. Full AF-1..AF-4 objective matrices and Mission Control portfolio surfaces are post-alpha.
+
+## Official CLI Capability and Tool Migration Workstream (T78)
+
+Normative contract on integration trunk `next`:
+[docs/requirements/cli-capability-migration.md](../../requirements/cli-capability-migration.md):
+migrates agent-facing operations from directly invoked scripts into documented, first-class
+`mosaic` CLI command groups, together with the central-registry resolver, capability catalog,
+adapter boundary, and phased legacy-tool-tree decommission the migration requires. The contract
+carries its own implementation hold and delivery stages.
+
+## Graduation ruling (Q-G3, Jason 2026-09-01)
+
+Graduation of a Part II workstream contract is a ratification act: Jason marks
+it (grill or direct ruling). The graduated contract text archives inside the
+then-current PRD revision bundle — this section gains a graduated-set record
+per revision — keeping the frozen-bundle model intact.
@@ -0,0 +1,171 @@
+---
+id: GOV.5
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# GOV.5 — Open questions (the grill list)
+
+Every question the corpus could not settle. This is the E5 ms-grill-me input;
+ratification is blocked until this list is empty or every remaining row is
+explicitly deferred with an owner. IDs are stable; answered questions get their
+ruling recorded here and flow into the owning section.
+
+**Frontier status (2026-09-01, grill rounds 3–8 complete): EMPTY.** Every row
+is ruled, dissolved, or deferred-with-owner. The operator-side Q-T3 canon
+coalescence closed in round 8 and was executed the same day (brain commit
+`59d43270`). E6 ratification executed 2026-09-01; this list is frozen with the
+bundle.
+
+## Data model
+
+- **Q-D1** — **RULED, Jason 2026-09-01: consolidate.** `launch.env` folds
+  into `profile.json` (one seat record). Precondition verified same day:
+  `mosaic-core/lib/loader.ts seatRole()` parses profile.json as a generic
+  record and reads only `role` — widened files tolerated by construction.
+  Migration staged as lane work (ledger B1).
+- **Q-D2** — **RULED, Jason 2026-09-01: per-provider map + broker refs.**
+  `profile.json` carries a per-provider map whose values are credential-broker
+  references (`environment/service/component/secret-name`), never secrets —
+  one seat, N providers, zero secrets in the brain tree. Flows to
+  [[DATA.1-record-authority]] and [[AUTHN.1-auth-accounts]].
+- **Q-D3** — **RULED, Jason 2026-09-01: the projection engine owns.** One
+  writer: the role-projection engine (`role apply` path). The launcher seeds
+  nothing itself — it invokes the projector; Pi and every harness get
+  regenerated files on each role/seat change; hand edits are drift, flagged by
+  `validate`. Consistent with L2-D19 + Q-T5. Unblocks the reconciliation
+  features (lane ledger B3 → D8).
+- **Q-D4** — **RULED, Jason 2026-09-01: role ceiling + seat choice.** The
+  Role Revision defines the allowed model set (policy ceiling); the seat
+  records preferences within it; effective models = intersection, consistent
+  with the L2-D39 intersection chain. Flows to [[HARN.1-harness-config]] and
+  role-harness-config DESIGN Q2 (same ruling, both doors).
+- **Q-D5** — **DEFERRED with owner (Jason 2026-09-01)**: the mutating
+  config-engine half gets its own ruling after v1 read-only `validate`/`plan`
+  ships; owner = the mosaic-config workstream. ([[CLI.1-parity]] §v1 subset)
+
+## Sessions
+
+- **Q-S1** — **DEFERRED with owner (Jason 2026-09-01)**: the
+  session-id ↔ incarnation-id contract is settled inside the session-lifecycle
+  draft before it lands (which now carries the Q-S4 two-path requirement);
+  owner = that draft's ratification. ([[SESS.1-session-continuity]])
+- **Q-S2** — **RULED, Jason 2026-09-01: step-up re-auth required.** Role
+  rebinding is an authority-changing act: fresh principal re-authentication
+  ≤10 minutes before the confirmation lands, matching the S2
+  identity-lifecycle linking precedent. Flows to [[SEAT.1-seat-profile]]
+  §role-binding and the UI.1 seat-page spec.
+- **Q-S3** — **DEFERRED with owner (Jason 2026-09-01)**: the measurable
+  continuity-degradation bar is settled inside the session-lifecycle draft
+  before it lands; owner = that draft's ratification.
+- **Q-S4** — **RULED, Jason 2026-09-01: two-path requirement ratified.** The
+  session-lifecycle draft may not land with one relaunch path. Role change →
+  clean-session path (new incarnation + fencing token, ephemeral context
+  discarded, OD-02/OD-03); harness/model/provider change → continuity path (same
+  Stack session id, checkpointed context restored, OD-57–OD-61, no noticeable
+  degradation). Binding requirement on the draft, recorded in
+  [[SESS.1-session-continuity]] §state machine.
+
+## Audit
+
+- **Q-A1** — **RULED, Jason 2026-09-01: mechanical tooling.** The audit is
+  deterministic tooling over the grant/assignment record (witness-style, per
+  the S2 writer-coverage pattern); its output feeds the audit page read-only.
+  Agents may consume audit output but never produce the verdict ("prompt
+  adherence is not an enforcement mechanism"). Flows to
+  [[AUTHZ.1-capability-authority]] and [[UI.1-webui-surfaces]] §audit.
+- **Q-A2** — **DISSOLVED by the Q-A1 ruling**: the auditor is code, audited by
+  ordinary review and CI witnesses, not a seat subject to misdirection.
+- **Q-A3** — **DEFERRED with owner (Jason 2026-09-01)**: the computable
+  misdirection metric is designed inside the mechanical audit tooling ruled by
+  Q-A1; owner = the audit-tooling workstream (lane ledger C2).
+
+## Surfaces
+
+- **Q-N1** — **DEFERRED with owner (Jason 2026-09-01)**: technical
+  investigation of the in-browser OAuth flow (tmux-bridged terminal vs
+  server-side) runs before the auth page builds; owner = the auth-page
+  workstream (lane ledger D6). ([[AUTHN.1-auth-accounts]])
+- **Q-C1** — **RULED, Jason 2026-09-01: CI witness in the stack repo.** The
+  parity matrix becomes a generated artifact with a drift-gate witness
+  (contract-9 pattern): CI regenerates the inventory from code and fails on
+  divergence from the committed matrix. Flows to [[CLI.1-parity]]; the
+  witness itself is E6-return follow-up work.
+
+## Governance
+
+- **Q-G1** — **RULED, Jason 2026-09-01: both ratified.** L2-D52
+  (least-privilege Assignment issuance, closes G1+G2) and the G6 WebUI
+  surface-scope fix applied per their return procedures after digest
+  re-verification; amendment files flipped to ratified; lane ledger A3/A4
+  closed.
+- **Q-G2** — **RULED, Jason 2026-09-01: distinct prefixes at source.**
+  Stack keeps D1–D15; the operator DECISION-REGISTER renames to **OD-01…OD-65**
+  with a redirect table at the source doc; file-local D-numbering in drafts is
+  prohibited going forward (each decision doc declares a unique registry
+  prefix, rule lands in [[GOV.1-prd-lifecycle]]). Applied at E6 return for
+  stack references; brain-side rename on next DECISION-REGISTER touch.
+- **Q-G3** — **RULED, Jason 2026-09-01: Jason marks; archive in bundle.**
+  Graduation is a ratification act — Jason marks it (grill or direct ruling);
+  the graduated contract text archives inside the then-current PRD revision
+  bundle ([[GOV.4-workstream-contracts]] gains a graduated-set section),
+  keeping the frozen-bundle model intact.
+
+## Triage-raised (E2 sweep, 2026-08-31)
+
+- **Q-T1** — **RULED B, Jason 2026-09-01: "shipped but frozen."** Amend D3 to
+  acknowledge federation M1–M3 exist (Step-CA, enrollment, grants, mTLS auth
+  guard, ScopeService, list/get/capabilities verbs; M3 landed 2026-06-24/25),
+  are excluded from the v1 bar, and are frozen; re-home tracking in
+  NORTH_STAR.yaml as a dormant workstream; frozen cert/auth code carries a
+  **security re-audit gate** before any resumption. Consequences at E6 return:
+  supersession/status banners on the three stale docs (root MISSION-MANIFEST,
+  federation/MISSION-MANIFEST, scratchpads/mvp-20260312), reconcile
+  guides/deployment.md with D15, NORTH_STAR.yaml dormant entry. The P5
+  scope ambiguity (governance-federation vs shipped mTLS-query federation)
+  stays open inside the future federation PRD, not rev1. Evidence: lane
+  `FEDERATION-DOSSIER-2026-08-31.md`.
+- **Q-T2** — **RULED, Jason 2026-09-01: all three re-ratified** into the
+  rev1 decision map ([[GOV.3-decision-map]] §re-ratified orphans): "No Python"
+  in the monorepo; Matrix/MACP exactly-three-install-modes with Mode A
+  (split-domain) primary; OpenBrain excluded from consolidation scope. The
+  Matrix ruling's open DNS/domain prerequisite gets its own row (Q-T6).
+- **Q-T3** — **RULED (partial), Jason 2026-09-01: coalesce under the
+  STRUCTURE-CANON name.** MOSAIC-CANON's more comprehensive content is
+  authoritative; `STRUCTURE-CANON.md` is the logical surviving document name;
+  the two coalesce into one. Conflict report delivered and all six
+  decision points ruled (grill round 8, 2026-09-01): per-seat credential
+  slots win; doc paths corrected to `fleet/auth/`/`fleet/memory/`;
+  ENTITY.md/README.md stay required with a 42-seat backfill task; merge
+  executed with the full reference sweep, MOSAIC-CANON reduced to a pointer
+  shim. Record: lane `CANON-COALESCENCE-2026-09-01.md`. Operator-side; not a
+  rev1 blocker.
+- **Q-T4** — **RULED, Jason 2026-09-01, two parts.**
+  **(a) Two independent axes**: "Standalone/Enterprise" in the S2 corpus is a
+  multi-tenancy/isolation _mode_ (`platform_mode`, D3/D11); D15's "compose
+  standalone tier" is deployment _packaging_. Orthogonal. rev1 text always
+  says "standalone mode" vs "compose tier"; mode-conversion.md needs a
+  terminology note only, not a rewrite.
+  **(b) Own track, rev1 cites**: rev1 ratifies citing the nine contracts as
+  DRAFT successor material with status noted; each contract ratifies on its
+  own PR when its family lands. Extraction record: lane
+  `S2-EXTRACTION-2026-08-31.md`.
+- **Q-T5** — **RULED, Jason 2026-09-01: scope to files.** Adopted wording:
+  "Generated settings _files_ are projections of the active Role Revision,
+  never authority (L2-D19). DB settings records written through audited
+  Gateway commands (`platform_mode`, `registration_mode`, `custody_config`,
+  `bootstrap.seed-company-name`, and their successors) are records of
+  authority like any other SOT row." No corpus conflict remains. Case law:
+  contract 1 §5.4, contract 8 §2.4, contract 9 §3.2.
+- **Q-T6** — **DEFERRED with owner (Jason 2026-09-01)**: the Matrix/MACP
+  Mode A DNS/domain prerequisite (`archive/planning/matrix-macp/rfc-001:428`)
+  rules before any Matrix install work resumes; owner = whoever reopens
+  Matrix. Until then Mode A is primary-on-paper only.
+
+## Deferred-by-scope (recorded, not blocking rev1)
+
+- Federation design (D3 — roadmap placeholder; nothing in v1 may foreclose it).
+  _Q-T1 ruled B (2026-09-01): D3 to be amended — M1–M3 acknowledged, frozen,
+  security re-audit gate before resumption; design itself stays deferred._
+- OS/kernel-level seat sandboxing (explicit lane non-goal; role-lane
+  discipline, not process containment).
@@ -0,0 +1,64 @@
+---
+id: HARN.1
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# HARN.1 — Harness configuration
+
+A harness is an installed agent runtime (claude, pi, codex, opencode, …).
+Shared contracts speak capability language; harness commands, model IDs,
+hooks, and settings live in runtime adapters (register OD-38).
+
+## Harness configuration surface (WebUI page + CLI)
+
+| Control                  | Notes                                                                                                                                                               |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| install harness          | single button push; installer runs server-side through official tooling                                                                                             |
+| enable / disable         | disabled harnesses are not selectable on any seat page                                                                                                              |
+| available models         | an **allowlist** a seat may select from — not a selection. Whether `enabledModels` is role policy or harness/seat preference is open: [[GOV.5-open-questions]] Q-H1 |
+| reasoning level defaults |                                                                                                                                                                     |
+| provider                 | which provider(s) back this harness ([[PROV.1-providers]])                                                                                                          |
+| linked auth accounts     | which accounts may drive this harness ([[AUTHN.1-auth-accounts]])                                                                                                   |
+
+Enable/disable and install are runtime state (Postgres-owned) projected into
+whatever flat state the launcher needs ([[DATA.1-record-authority]]).
+
+## Runtime adapter contract (pulled 2026-08-31 from adapter-contract draft)
+
+Every harness adapter binds a required capability set or **fails closed**:
+repository ops via wrapper capability, scoped file/command execution,
+structured reasoning, shared-memory capture/search/recall, inter-seat
+messaging/wake, checkpoint persistence + mechanical telemetry, a `mosaic coord`
+client that cannot mutate Kanban state or deploy seats directly, and credential
+resolution through the seat's own slot. Rules:
+
+- An unavailable capability is a **named blocker**, never silent degradation.
+  **"Prompt adherence is not an enforcement mechanism"** — a harness that
+  cannot persist checkpoints, emit telemetry, or honor fencing does not run
+  workflows that need them.
+- Each adapter publishes a capability→binding table (capability, binding
+  surface, config source, verification check) and proves its bindings at
+  session start; verification failure is a named blocker.
+- Adapters bind capabilities but **never redefine role authority, delivery
+  policy, gate outcomes, or review independence** — a harness whose native
+  workflow conflicts with shared policy keeps the shared policy and records the
+  conflict as an adapter limitation.
+
+## E2 inputs (triage 2026-08-31; see [[GOV.2-docs-inventory]])
+
+**Canonical ground truth**: the `fleet/` book — `concepts/desired-vs-observed-state.md`
+(roster-v2 sole writable authority), `concepts/generated-env-launch-chain.md` +
+`reference/generated-env-boundary.md`, `reference/roster-v2-fields.md`,
+`operations/reconcile-and-recover.md` (lock/generation semantics),
+`NORTH_STAR.md`/`FLEET-DOCTRINE.md` (delivery-fleet north star, subordinate to
+this PRD per rev0 §10).
+**Pending pulls**: brain `docs/guides/proposed/runtime/adapter-contract.md`
+(the register-OD-38 runtime-adapter capability contract this section cites).
+
+## enabledModels ruling (Q-D4, Jason 2026-09-01)
+
+The Role Revision defines the allowed model set — a policy ceiling. The seat
+records model preferences within that set. Effective models = the
+intersection, consistent with the L2-D39 authority-intersection chain. A seat
+preference outside the role ceiling is refused, not silently clamped.
@@ -0,0 +1,89 @@
+---
+id: PRD.0
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# PRD.0 — Index: naming standard, domain registry, reading order
+
+This file is the order authority for the PRD section documents. Lexical sort of
+the directory is **not** authoritative; this index is.
+
+## Naming standard (ratified 2026-08-31)
+
+`<DOMAIN>.<n[.n[.n]]>-<kebab-slug>.md` — e.g. `AUTHN.1.1-oidc.md`
+
+- **Domain code**: short uppercase code from the registry below. Codes are
+  append-only; a code is never reused or renamed.
+- **Number**: hierarchical, dotted, **append-only at every level**. A new
+  subtopic under `AUTHN.1` takes the next free number (`AUTHN.1.3`). Nothing
+  ever renumbers; depth absorbs insertions. Added topics augment, never
+  reshuffle.
+- **Slug**: kebab-case; names only what the number does not. The domain word is
+  never repeated in the slug (`AUTHN.1.1-oidc.md`, not
+  `AUTHN.1.1-authentication-oidc.md`).
+- **Separators**: dots between number levels only; one hyphen between number
+  and slug; hyphens inside the slug. No underscores, no spaces.
+- **ID in three places** that must agree: filename, frontmatter `id:`, H1.
+  Wikilinks use the basename, e.g. `[[AUTHN.1.1-oidc]]` (illustrative — no such section exists yet).
+- **Flat directory**: hierarchy lives in the number, not nested folders.
+
+## Domain registry (append-only)
+
+| Code  | Domain                                                                                          |
+| ----- | ----------------------------------------------------------------------------------------------- |
+| PRD   | The PRD assembly itself: index, preamble, revision log                                          |
+| GOV   | Governance: document lifecycle, decision registers, amendment process, ratification             |
+| VIS   | Vision / north star: what the Stack is, premises, non-goals                                     |
+| AUTHZ | Authorization & enforcement: capabilities, role policy, mosaic-core, L2 contracts, gap register |
+| AUTHN | Authentication: provider accounts, OAuth/API keys, renewal, deactivation, allowed harnesses     |
+| ROLE  | Roles: manifests, role config surfaces, role/seat separation                                    |
+| SEAT  | Seats: profiles, launch config, seat config surfaces, profile.json consolidation                |
+| HARN  | Harnesses: install/enable, model availability, reasoning, linked auth                           |
+| PROV  | Providers: supported providers, local providers (Ollama, LM Studio), provider config            |
+| SESS  | Sessions: Stack session identity, continuity, mid-stream harness/model/provider switching       |
+| UI    | WebUI: pages, page-scope rules, interaction patterns, audit surfaces                            |
+| CLI   | mosaic CLI: command surface, CLI↔WebUI parity                                                   |
+| DATA  | Record classes & storage: J1 git/DB authority split, flat-file vs DB, reconciliation            |
+
+New domains append below this line with a dated note.
+
+## Reading order
+
+Order is by lifecycle of understanding, not by code:
+
+1. [[PRD.0-index]] (this file)
+2. [[GOV.1-prd-lifecycle]]
+3. [[GOV.2-docs-inventory]]
+4. [[GOV.3-decision-map]]
+5. [[VIS.1-north-star]]
+6. [[DATA.1-record-authority]]
+7. [[AUTHZ.1-capability-authority]]
+8. [[ROLE.1-role-governance]] → [[SEAT.1-seat-profile]] (separation is load-bearing; role before seat)
+9. [[HARN.1-harness-config]] → [[PROV.1-providers]] → [[AUTHN.1-auth-accounts]]
+10. [[SESS.1-session-continuity]]
+11. [[UI.1-webui-surfaces]] → [[CLI.1-parity]] (surfaces last; they project everything above)
+12. [[GOV.4-workstream-contracts]] (preserved contracts; bind after the model is understood)
+13. [[GOV.5-open-questions]] (the grill list; ratification gate)
+
+Pulled sources (inputs, never ratified): [rev0 PRD](../2026-08-26_PRD_rev0/PRD.md),
+the operator DECISION-REGISTER (estate brain `docs/guides/proposed/DECISION-REGISTER.md`, snapshot 2026-08-28, sha256 `2cc81be1…aabec`; operator-only corpus, not shipped).
+
+Sections are added to this list as they are authored; an unlisted file is a
+defect.
+
+## Structural rulings (2026-08-31, Jason)
+
+- The finished PRD is the **project SOT**. `docs/PRD.md` in the stack repo
+  becomes a shim to the current dated revision. Missions reference the PRD,
+  never usurp it. See [[GOV.1-prd-lifecycle]].
+- The entire PRD lives in the **stack repo** (mosaicstack/stack, trunk `next`).
+  Brain documents are operator-instance documents that cite it.
+- This work is the **successor** to the 2026-08-26 "North Star" PRD on
+  `origin/next` (snapshot: [rev0 PRD](../2026-08-26_PRD_rev0/PRD.md)).
+- Revisions **archive, never delete**. Each ratified revision is a frozen
+  bundle directory — `docs/PRDs/YYYY-MM-DD_PRD_revN/` holding the PRD, this
+  index, and every section doc as a set (layout: [[GOV.1-prd-lifecycle]]
+  §Revision bundles).
+- Shim and revision immutability are **convention, not enforcement** (no hook
+  or CI guard yet).
@@ -0,0 +1,103 @@
+---
+kind: spec
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+succeeds: origin/next:docs/PRD.md (2026-08-26 North Star, commit 9aa4983c, sha256 60cc2f98697471850caa3440d79139d70f67eda585a2ee465fdcd517bc36afdf)
+---
+
+# PRD: Mosaic Stack — rev1
+
+The project source of truth, successor to the 2026-08-26 North Star PRD
+(rev0). Ratified 2026-09-01; this bundle is frozen — the next revision is
+drafted in a lane and lands as a new bundle ([[GOV.1-prd-lifecycle]]). This file assembles the section documents in this bundle; the
+sections own the detail. Order authority and naming: [[PRD.0-index]].
+Lifecycle (shim, frozen revision bundles, archival): [[GOV.1-prd-lifecycle]].
+
+The PRD is **mission-independent**: missions pin an accepted PRD version and
+reference it (register OD-16/OD-19); they never usurp it. rev0 ([rev0 PRD](../2026-08-26_PRD_rev0/PRD.md)) is archived verbatim beside this bundle;
+`docs/PRD.md` is the permanent shim pointing here.
+
+## Metadata
+
+- **Owner / decision authority:** Jason Woltje
+- **Status:** ratified 2026-09-01 (Jason Woltje). Drafted as a class-2 draft-native in lane `fleet/lanes/control-plane-surfaces` (estate brain); grill record in [[GOV.5-open-questions]]
+- **Base text:** rev0, pinned at `origin/next` commit `9aa4983c`
+- **Pulled sources (inputs, never ratified; not shipped in this bundle):** [rev0 PRD](../2026-08-26_PRD_rev0/PRD.md) and the operator DECISION-REGISTER (estate brain `docs/guides/proposed/DECISION-REGISTER.md`, snapshot 2026-08-28, sha256 `2cc81be1…aabec`; operator-only corpus, not shipped)
+
+## Revision log
+
+| Rev  | Date       | State                                                                              | Notes                                                                                                                                                                                     |
+| ---- | ---------- | ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| rev0 | 2026-08-26 | superseded 2026-09-01; archived verbatim as `docs/PRDs/2026-08-26_PRD_rev0/PRD.md` | North Star PRD (Part I product north star from D1–D14 + D15; Part II workstream contracts)                                                                                                |
+| rev1 | 2026-08-31 | **ratified 2026-09-01** (Jason; grill rounds 1–8 closed the GOV.5 frontier)        | rev0 + control-plane surfaces (seats, roles, harnesses, providers, authentication, sessions, WebUI/CLI), consolidated decision map, authorization gap register, docs-estate consolidation |
+
+## Mandate (2026-08-31 drafting directive)
+
+1. Combine the official PRD (rev0) with the `control-plane-surfaces` and
+   `agent-runtime-ng` lane findings.
+2. Ingest and reconcile the pertinent document corpus — stack `docs/` on
+   `origin/next`, `~/.mosaic/docs`, `~/.mosaic/docs/guides/proposed`
+   ([[GOV.2-docs-inventory]] is the audit trail).
+3. Specify all functions of the site and the north star in one place, with
+   full `mosaic` CLI ↔ WebUI parity.
+4. Remove the no-central-location ambiguity; clear up drift and naming issues;
+   clarify ambiguous structural language.
+5. Walk open questions via ms-grill-me before ratification
+   ([[GOV.5-open-questions]]).
+
+---
+
+## Part I — Product north star
+
+**[[VIS.1-north-star]]** — what Mosaic Stack is, who it is for, deployment
+modes, hierarchy and tenancy, identity, onboarding, data custody, the
+webUI-over-tooling architecture gate, the v1 slice, the fleet-north-star
+subordination, non-goals, and tiered containerized deployment. rev0 Part I
+preserved as base text with marked rev1 annotations.
+
+## Part II — Platform model (control plane)
+
+| Section                          | Owns                                                                                                                        |
+| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
+| [[DATA.1-record-authority]]      | record-class authority (J1), the configuration data model, seat-file consolidation, reconciliation obligation               |
+| [[AUTHZ.1-capability-authority]] | intersection authority model, `mosaic-core` enforcement, firewalls, privilege escapation, accepted risk, gap register G1–G7 |
+| [[ROLE.1-role-governance]]       | role definitions/revisions, manifest invariants, role surface, seat/role separation rule                                    |
+| [[SEAT.1-seat-profile]]          | instance contract, seat surface, the separated role-binding control (G5), OD-02/OD-03 semantics                             |
+| [[HARN.1-harness-config]]        | harness install/enable, model allowlists, adapter boundary (register OD-38)                                                 |
+| [[PROV.1-providers]]             | hosted and local providers, named instances, activation                                                                     |
+| [[AUTHN.1-auth-accounts]]        | agent-side provider accounts, OAuth/API, custody rules, broker boundary                                                     |
+| [[SESS.1-session-continuity]]    | Stack session id, incarnation layering, mid-stream switching via register OD-57–OD-61, the two-operations rule              |
+
+## Part III — Surfaces
+
+| Section                 | Owns                                                                                             |
+| ----------------------- | ------------------------------------------------------------------------------------------------ |
+| [[UI.1-webui-surfaces]] | governing rules and the complete page/function inventory, including the authorization-audit page |
+| [[CLI.1-parity]]        | CLI primacy, the one-engine rule (OD-53), the parity-matrix obligation, command families         |
+
+## Part IV — Governance
+
+| Section                  | Owns                                                                  |
+| ------------------------ | --------------------------------------------------------------------- |
+| [[GOV.1-prd-lifecycle]]  | SOT rule, shim, frozen revision bundles, archival                     |
+| [[GOV.2-docs-inventory]] | corpus inventory, supersession verdicts, naming-defects register      |
+| [[GOV.3-decision-map]]   | every binding decision registry, collision rule, reconciliation notes |
+| [[GOV.5-open-questions]] | the grill list; ratification gate                                     |
+
+## Part V — Active workstream contracts (preserved unchanged)
+
+**[[GOV.4-workstream-contracts]]** — rev0 Part II carried verbatim: #1194
+drift detection, Compaction Refresh Trust Lifecycle, Pi Persistent Goal Loop,
+FCM, cross-harness comms, KBN-101, TESS, channel plugins, MOS-PORT, workspace
+placement guard, Release Integrity, T78 CLI migration. Open issues bind to
+them; they graduate out individually as workstreams close.
+
+---
+
+## Ratification
+
+Per [[GOV.1-prd-lifecycle]]: this bundle freezes into
+`mosaicstack/stack docs/PRDs/` (branch off `origin/next`), rev0 archives as a
+one-file bundle, `docs/PRD.md` becomes the generated pointer (register OD-18).
+Gate: [[GOV.5-open-questions]] empty or explicitly deferred; then reviewed PR
+per stack delivery gates.
@@ -0,0 +1,34 @@
+---
+id: PROV.1
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# PROV.1 — Provider configuration
+
+A provider is a model-inference source: hosted (Claude, OpenAI, ZAI, N others)
+or local (Ollama, LM Studio, other).
+
+## Provider configuration surface (WebUI page + CLI)
+
+| Control               | Notes                                                                                  |
+| --------------------- | -------------------------------------------------------------------------------------- |
+| provider selection    | dropdown of supported providers                                                        |
+| name                  | user-chosen instance name (multiple named instances of one provider type are expected) |
+| auth mode             | OAuth or API key — the account itself lives in [[AUTHN.1-auth-accounts]]               |
+| local provider setup  | endpoint/port for Ollama, LM Studio, other local providers                             |
+| activate / deactivate | inactive providers are not selectable downstream                                       |
+
+Provider records are runtime state (Postgres-owned, projected). Credentials
+never enter provider records; they live with the credential broker
+([[AUTHN.1-auth-accounts]]).
+
+## E2 inputs (triage 2026-08-31; see [[GOV.2-docs-inventory]])
+
+**Canonical ground truth**: `DEVELOPER-GUIDE/architecture/decisions/mos-runtime-portability-m1.md`
+(the only current ADR for the logical-agent/connector-lease identity model);
+`ADMIN-GUIDE/operations/mos-connector-lease-operations.md` — connector
+activation is a **deliberate deny-all hold**; nothing in this section may imply
+it is live.
+**Drafts noted**: `rfcs/optional-ai-egress-gateways.md` (non-operative;
+separates `IProviderAdapter` from egress-gateway concerns).
@@ -0,0 +1,85 @@
+---
+id: ROLE.1
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# ROLE.1 — Role governance and configuration
+
+## What a role is
+
+A role is the reviewed, Git-owned capability ceiling for a class of seats:
+Role Definition → immutable, digested Role Revisions → the active revision
+projects `mosaic-core.manifest.json` and role-scoped settings. Authority table:
+[[DATA.1-record-authority]]. Enforcement: [[AUTHZ.1-capability-authority]].
+
+## The separation rule (Jason, 2026-08-31 — closes gap G6)
+
+- The **seat** configuration surface NEVER directly modifies role config.
+- The **role** configuration surface NEVER directly modifies seat config.
+- A seat page writes at most a per-seat **overlay**, never the role file.
+
+The original `role-harness-config/DESIGN.md` sentence constrained a surface it
+never named — both readings were faithful, and reviewer context decided the
+meaning. The staged amendment names the surface explicitly.
+
+## Role configuration surface (WebUI page + CLI)
+
+| Control             | Notes                                                                                                          |
+| ------------------- | -------------------------------------------------------------------------------------------------------------- |
+| manifest editing    | capability grants against the C1–C8 (later open) registry; schema-validated before commit                      |
+| revision management | create revision, diff against active, activate, roll back — every revision immutable and digested              |
+| role links          | which seats bind this role (read-only here; binding happens on the seat surface — see [[SEAT.1-seat-profile]]) |
+| projection status   | whether each bound seat's on-disk projection matches the active revision (`role check` class)                  |
+
+All writes go through the one canonical role-management API (L2-D14) shared
+with the CLI — the WebUI holds no separate role logic. Role management is
+**principal-only** (L2-D13): no agent identity may ever invoke these
+operations, and the API enforces that, not the page.
+
+## Manifest invariants (must survive any surface)
+
+- Committed, non-symlink, trusted-path — `mosaic-core`'s loader refuses
+  violations; no surface may "fix" that by writing a symlink.
+- Nothing env-overridable, nothing cwd-relative.
+- `tools[]` equals exactly the bound bindings of granted capabilities.
+- Role cross-checked against path at load.
+
+## Specialization model (pulled 2026-08-31 from SPECIALIZATION-MODEL draft)
+
+Four layers: **Role** (decision ownership and prohibited actions — few,
+stable) → **Seat** (durable identity performing the role) → **Specialization**
+(recurring domain/tools/behavior — open-ended, composable, never changes
+authority) → **Task** (current activity). Rules:
+
+- A seat has **exactly one role at a time**; never activate a second role
+  inside a session. If authority changes, `mosaic config` reconfigures the seat
+  and the coordinator starts a **clean session** — seat identity, history, and
+  authorship survive; the old lease is revoked and a new incarnation starts.
+  (Independent confirmation of register OD-02/OD-03 and the
+  [[SESS.1-session-continuity]] two-operations rule.)
+- Promotion to a new role only when decision ownership or prohibited actions
+  materially differ; otherwise a formal specialization profile. Promotion
+  triggers: different authority/external side effects, distinct
+  credential/identity/data boundaries, added compliance controls, stable
+  machine-readable I/O contract, required independence, deterministic gate
+  behavior, repeated cross-seat use.
+- Ad-hoc task-scoped specialization is valid only inside existing authority,
+  with no new credential/safety/independence boundary; it dies with the task
+  unless intentionally promoted.
+- Anti-patterns: per-topic role explosion; role-subtype hierarchies no workflow
+  consumes; model IDs or harness syntax inside specialization definitions;
+  using specialization to bypass role authority or gates.
+
+## E2 inputs (triage 2026-08-31; see [[GOV.2-docs-inventory]])
+
+**Canonical ground truth**: `fleet/reference/role-classes.md`,
+`fleet/concepts/role-authority-and-leases.md`, `fleet/how-to/customize-roles.md`
+(baseline + `roles.local` resolver), `fleet/migration/legacy-class-aliases.md`,
+`ADMIN-GUIDE/security/discord-ingress.md` (viewer/operator/admin precedent).
+**Pending pulls**: brain `docs/guides/proposed/SPECIALIZATION-MODEL.md`
+(Role/Seat/Specialization/Task layering — the conceptual basis of this
+section's separation rule); `plans/2026-08-29-agent-enrollment-command-design.md`
+(enrollment authority composed across three contracts — fragility to fix or document).
+**Naming hazard**: "Tess"/"Ultron" are roster-class display aliases in fleet
+how-tos and named product identities elsewhere (defect N6) — qualify every use.
@@ -0,0 +1,87 @@
+---
+id: SEAT.1
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# SEAT.1 — Seat identity, profile, and configuration
+
+## Instance contract (register OD-48)
+
+| File                   | Carries                                                                                                          |
+| ---------------------- | ---------------------------------------------------------------------------------------------------------------- |
+| `profile.json`         | structured identity — and, post-consolidation, the full seat record ([[DATA.1-record-authority]] §consolidation) |
+| `overlay.json`         | generated composition                                                                                            |
+| seat-local `AGENTS.md` | narrative specialization                                                                                         |
+| `SOUL.md`              | persona                                                                                                          |
+
+## Seat configuration surface (WebUI page + CLI)
+
+| Control                | Notes                                                                                 |
+| ---------------------- | ------------------------------------------------------------------------------------- |
+| harness                | from **enabled** harnesses only ([[HARN.1-harness-config]])                           |
+| model                  | constrained by the harness's available-models allowlist                               |
+| reasoning level        |                                                                                       |
+| work dir               |                                                                                       |
+| authentication account | from configured, active accounts allowed for that harness ([[AUTHN.1-auth-accounts]]) |
+| overlay                | per-seat overlay only — never the role file (ROLE separation rule)                    |
+| role binding           | **separated section — see below**                                                     |
+
+## The role-binding control (gap G5)
+
+Role Binding is the single highest-authority action in the system,
+principal-only under L2-D13. `model` is a preference. They must not share one
+undifferentiated form — a privilege grant must not inherit the ceremony of a
+dropdown. Requirements:
+
+- Visually and structurally separate section on the page.
+- Distinct confirmation step; re-authentication of the principal is under
+  consideration ([[GOV.5-open-questions]] Q-S2).
+- Register OD-02/OD-03 bind the semantics: a seat has exactly one role; an
+  **active session never switches roles**. A role change reconfigures the
+  existing seat, preserves identity and history, **discards ephemeral context,
+  and starts a clean session**. The surface must say so before confirming.
+- Role-transition history is recorded: old role, new role, reason, authorizer,
+  checkpoint, activation time (register OD-04).
+
+Role changes are therefore a _different operation_ from harness/model/provider
+changes ([[SESS.1-session-continuity]]) and must not share a code path.
+
+## Seat identity and credential rules (pulled 2026-08-31 from seat-identity draft)
+
+- **One seat = one identity = one token slot.** A second copy of a token
+  anywhere is drift and is removed without reading it.
+- Agents never mint their own tokens; provisioning, rotation, and scope changes
+  are operator authority. Credential refusal is _correct behavior_ — the fix is
+  the seat's identity, never another seat's or a shared credential.
+- Fail-closed everywhere: an empty/unreadable slot is a designed state reported
+  at launch; the credential helper refuses, records, notifies — never falls
+  back to a shared or owner credential.
+- Git identity resolution order: explicit environment identity → configured
+  identity → git's own answer. Identity is named on every invocation and never
+  persisted inside a shared clone/worktree config (silent attribution rewrite).
+  Commit author must identify the seat that did the work.
+- Tokens are compared by digest, never by value; scopes are verified from the
+  authority's own report, never transcription.
+
+## E2 inputs (triage 2026-08-31; see [[GOV.2-docs-inventory]])
+
+**Canonical ground truth**: `fleet/reference/agent-mutations.md`,
+`fleet/reference/lifecycle-transitions.md` (`enabled`/`desired_state` authority),
+`fleet/how-to/create-update-delete-agent.md`, `guides/fleet-local-canary.md`.
+**Pending pulls**: brain `docs/guides/proposed/operations/seat-identity.md`
+(credential-resolution mechanics under the OD-48 instance contract).
+
+## Role-binding step-up ruling (Q-S2, Jason 2026-09-01)
+
+Confirming a role-binding change requires fresh principal re-authentication no
+older than 10 minutes — the same step-up bar the S2 identity-lifecycle
+contract sets for account linking. An active session alone is insufficient;
+this closes the stolen-session → privilege-misdirection path through the seat
+surface.
+
+## Seat record consolidation ruling (Q-D1, Jason 2026-09-01)
+
+`launch.env` consolidates into `profile.json`: one seat record. Verified:
+`mosaic-core/lib/loader.ts seatRole()` reads only the `role` key from a
+generically-parsed record, so widened files are tolerated by construction.
@@ -0,0 +1,121 @@
+---
+id: SESS.1
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# SESS.1 — Session identity and mid-stream switching
+
+## Requirement (Jason, 2026-08-31)
+
+An agent session stays active on the system, tied to a **Stack session id**.
+Changing harness, model, or provider mid-stream preserves the session id and
+fully switches context from one provider/harness to another, with no user
+intervention and no noticeable performance degradation.
+
+## Two operations, two code paths — never merged
+
+|             | Harness / model / provider switch | Role switch                                             |
+| ----------- | --------------------------------- | ------------------------------------------------------- |
+| Session id  | preserved                         | seat identity preserved; session is **clean**           |
+| Context     | fully transferred                 | **ephemeral context discarded** (register OD-03)        |
+| Governed by | this section                      | [[SEAT.1-seat-profile]] §role-binding                   |
+| Why         | continuity requirement            | an active session never switches roles (register OD-02) |
+
+## The ratified mechanism already exists: register OD-57–OD-61
+
+The 2026-08-28 register confirms the machinery this requirement needs:
+
+- **OD-57 checkpoints** — atomic, schema-valid, revisioned seat checkpoints tied
+  to incarnation and lease; freshness enforced mechanically.
+- **OD-59 relaunch** — the coordinator requests and validates a checkpoint, stops
+  the session, applies configuration, starts a **clean incarnation**, restores
+  the assignment, verifies readiness.
+- **OD-60 fencing** — leases, epochs, incarnation IDs, fencing tokens prevent a
+  stale session from mutating state after the switch.
+- **OD-61 restart recovery** — the relaunched seat restores role, mission, task,
+  PRD pin, constraints, evidence, blockers, leases, dependencies, and next
+  action **without prior conversation**.
+
+A mid-stream harness switch is therefore an OD-59 relaunch keyed to a persistent
+Stack session id: checkpoint → stop → reconfigure → new incarnation →
+restore → resume. What OD-59 does not yet promise is the _experience_ bar — no
+user intervention, no noticeable degradation — which is this PRD's addition.
+
+## Identity layering
+
+`mosaic-core` mints a per-launch **incarnation id** and keys its journal on it,
+deliberately not on any session id. A harness switch is a new process → new
+incarnation → new journal, **while the Stack session id persists**. So:
+
+```
+Stack session id   (durable; user-facing continuity)
+  └─ incarnation id (per launch; enforcement journal, fencing per OD-60)
+```
+
+The precise contract between the two ids — minting, custody, what the
+coordinator records at each relaunch — must be specified before build:
+[[GOV.5-open-questions]] Q-S1.
+
+## Open hard problem
+
+Context-transfer fidelity between harnesses with different context formats,
+tool-call encodings, and system-prompt injection points. The checkpoint (OD-57)
+is the transfer vehicle; whether a checkpoint alone meets "no noticeable
+degradation" across harness families is unproven: [[GOV.5-open-questions]] Q-S3.
+
+## Session lifecycle state machine (pulled 2026-08-31 from the session-lifecycle draft — with one required extension)
+
+The operator draft (`workflows/session-lifecycle.md`, the densest
+decision-register consumer: OD-03/OD-04/OD-08, OD-56–OD-65) supplies the checkpoint/
+lease/fencing machinery this section's continuity requirement runs on:
+
+- **States**: Active → Relaunch-requested (triggers per OD-59: context
+  utilization, session age, milestone, drift, degraded health, role
+  reconfiguration, authorized request) → Checkpointing (atomic, revisioned,
+  bound to identity + incarnation + epoch + lease, OD-57) → Relaunching
+  (validated checkpoint, old lease revoked → **new incarnation, new fencing
+  token**, OD-59) → Restoring (readiness proof: role, task, PRD pin, blockers,
+  next action, OD-61) → Active/Degraded. Role change routes through
+  Reconfiguring first (old-role record, transition history, revoked lease,
+  OD-03/OD-04).
+- **Fencing**: a stale session cannot mutate after its replacement holds the
+  new token (OD-60); mutation authority is lease-gated and not renewed while the
+  checkpoint is stale. Coordinator outage fails closed for new
+  assignments/relaunches/renewals; existing leases run to expiry; read-only
+  work continues (OD-63).
+- **Checkpoint contents** (required fields): role, config version, mission,
+  outcome node, task, PRD pin, constraints, completed work with evidence refs,
+  blockers and failed attempts, active leases/external ops, next action with
+  required inputs. The checkpoint is an operational projection — mission truth
+  stays in the ledger (OD-58). Telemetry is append-only and never the resumable
+  checkpoint (OD-56).
+
+**Structural gap found at extraction (must be fixed before this machine
+ratifies):** the draft models exactly **one** relaunch mechanism — every
+trigger, without exception, mints a new incarnation and fencing token. There is
+no continuity-preserving path at all, and harness/model/provider switching does
+not appear among the triggers. This PRD's two-operations rule (above) requires
+**two code paths**: the state machine must gain a switch path that preserves
+the Stack session id and full context per OD-57–OD-61 while still rotating the
+fencing token safely. Adopting the draft's table verbatim would silently
+collapse the two operations back into one — the exact defect register OD-02/OD-03
+vs the continuity requirement exists to prevent.
+
+## E2 inputs (triage 2026-08-31; see [[GOV.2-docs-inventory]])
+
+**Canonical ground truth**: `DEVELOPER-GUIDE/architecture/compaction-revocation.md`
+(the only current continuity/revocation lifecycle — observer/generation-fencing,
+test-consumed), `channel-protocol.md`.
+**Pending pulls**: brain `docs/guides/proposed/workflows/session-lifecycle.md`
+(checkpoint/relaunch/recovery/role-reconfig — complements this section's
+switching focus; its role-reconfig path must respect the OD-02/OD-03 clean-session rule).
+
+## Two-path requirement ratified (Q-S4, Jason 2026-09-01)
+
+The state-machine gap flagged above is now a binding requirement: the
+session-lifecycle draft may not land with a single relaunch path. Role change
+→ clean-session path (new incarnation + fencing token, context discarded,
+OD-02/OD-03). Harness/model/provider change → continuity path (same Stack session
+id, OD-57 checkpoint restored under OD-61, no noticeable degradation). The two
+paths must not share a code path.
@@ -0,0 +1,108 @@
+---
+id: UI.1
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# UI.1 — WebUI control-plane surfaces (all functions of the site)
+
+The complete function inventory of the WebUI control plane. Every page obeys
+the governing rules; every control ultimately calls the same engine as the CLI.
+
+## Governing rules
+
+1. **Full CLI parity** — every aspect of the `mosaic` CLI surfaces in the WebUI
+   ([[CLI.1-parity]] carries the matrix obligation).
+2. **One canonical API** (L2-D14; register OD-53) — CLI, TUI, WebUI, API, and
+   automation share one CLI-backed schema, resolver, planner, authorization,
+   transaction, validation, and audit engine. The WebUI holds no separate
+   logic.
+3. **The webUI sits OVER official tooling** (D8/D12 hard rule) — no page ever
+   reaches the database or filesystem around the tooling; a missing tool means
+   the gap is "blocked on tooling" and the tool is built first.
+4. **Strict surface separation** — seat pages never modify role config; role
+   pages never modify seat config ([[ROLE.1-role-governance]]).
+5. **No direct settings-file authorship** — settings are generated projections
+   (L2-D19; [[DATA.1-record-authority]]).
+6. **Agents can never reach these surfaces** (L2-D13; the API refuses agent
+   identity — the enforcement is not the page's absence).
+7. **WebUI drafts** (register OD-54) — draft configuration is revisioned
+   server-side desired-state; drafts have no effect until planned and applied.
+
+## Interaction conventions
+
+Logically separated pages; dropdowns, activate/deactivate buttons, drag-drop
+actions performed on-page.
+
+## Page inventory
+
+| Page                   | Section doc                | Functions                                                                                                        |
+| ---------------------- | -------------------------- | ---------------------------------------------------------------------------------------------------------------- |
+| Seat configuration     | [[SEAT.1-seat-profile]]    | harness, model, reasoning, workdir, auth account, overlay; separated role-binding section                        |
+| Role configuration     | [[ROLE.1-role-governance]] | manifest editing, revision create/diff/activate/rollback, role links, projection status                          |
+| Harness configuration  | [[HARN.1-harness-config]]  | install (button), enable/disable, available-models allowlist, reasoning defaults, provider link, linked accounts |
+| Provider configuration | [[PROV.1-providers]]       | provider dropdown, named instances, OAuth/API mode, local providers, activate/deactivate                         |
+| Authentication         | [[AUTHN.1-auth-accounts]]  | in-browser OAuth establishment, account list, force renew, deactivate, allowed harnesses                         |
+| Authorization audit    | below                      | effective grants, escapation potential, drift                                                                    |
+
+## Page: Authorization audit (closes gap G3)
+
+Surfaces, per seat, to the user:
+
+- **Effective capability grant** — the live intersection
+  (role ∩ assignment ∩ lease ∩ workflow ∩ target policy ∩ backend).
+- **Misdirection potential** — which seats hold capabilities that would let
+  another seat's work be routed around its own role lane.
+- **Escalation potential** — any path that would add capability. Should be
+  provably empty; the audit's job is proving it _stays_ empty.
+- **Drift** — seats whose on-disk projection diverges from their active role
+  revision (`role check` class).
+- **Failure/blocked surfacing** (register OD-64) — the canonical alert stream's
+  WebUI adapter.
+
+Implementation choice (dedicated auditor agent vs mechanical tooling) and the
+auditor-identity problem are on the grill: [[GOV.5-open-questions]] Q-A1/Q-A2.
+
+## Cross-cutting requirement
+
+Every change made through these pages — or the CLI — automatically reconciles
+authentication, `settings.json`, and required symlinks
+([[DATA.1-record-authority]] §reconciliation; removal-fast / addition-attested
+per L2-D17). The user never touches a file.
+**Measured 2026-08-31** ([[CLI.1-parity]] Artifacts 2–3): the shipped WebUI
+already contains two D12 violations — the admin role/ban toggles and the stored
+harness/provider/model selection mutate state with no backing CLI command.
+Remediation, not precedent. The server-side hierarchy/grants CRUD surface
+(`hierarchy.controller.ts`) is the natural backing for the authorization audit
+page below, but needs a CLI face and an audit read-path first.
+
+## E2 inputs (triage 2026-08-31; see [[GOV.2-docs-inventory]])
+
+**Canonical ground truth**: `USER-GUIDE/product/web-dashboard.md` (route-by-route
+current state, incl. explicit gaps — no New Project/Task UI),
+`webui/PHASE-P-STRUCTURE.md` (Next→Vite SPA migration).
+**Pending pulls**: DRAFT S2 `onboarding-wizard.md` (D4/D11/D8),
+`tool-gateway-mapping.md` (the D8/D12 gate made concrete), `api-artifacts.md`.
+
+## S2 contract feed (extraction 2026-08-31)
+
+Full extraction record: lane `S2-EXTRACTION-2026-08-31.md` (per-contract cores, dependency edges, ruling cross-checks). Pulls binding on this section:
+
+- **Contract 5 verbatim-affirms the parity rule**: "The webUI is a Gateway
+  client only"; "No webUI-only command exists; a Gateway command without CLI
+  exposure is a conformance gap." "Blocked on tooling" closure is mandatory;
+  UI workarounds (direct DB/filesystem, legacy endpoints, domain logic in the
+  web app) are non-conformant. This is the ratifiable D8/D12 text this
+  section's violation findings measure against.
+- **Legacy non-substitutes** barred from backing any P1 surface, frozen for
+  new consumers: `/api/projects`, `/api/tasks` CRUD, `POST /api/workspaces`,
+  `/api/teams` reads, `POST /api/bootstrap/setup`, MCP `brain_*` mutations.
+- **Onboarding wizard (contract 3)** is the reference pattern for every config
+  page this section specifies: pure client-side composition of Gateway
+  commands, exactly one disclosed server-side composed transaction (bootstrap
+  finalize), wizard state always derived from canonical state — never a
+  persisted answer file that can drift.
+- **Company visibility** (`private` default vs `directory`) is a UI-facing
+  disclosure control with a bounded existence-only carve-out.
+- P1 build rank order (T10): hierarchy → hierarchy RBAC → typed kanban →
+  agent enrollment → authorized roll-up → onboarding orchestration.
@@ -0,0 +1,214 @@
+---
+id: VIS.1
+status: ratified
+ratified: 2026-09-01 (Jason Woltje; PRD rev1 ratification PR)
+---
+
+# VIS.1 — Product north star
+
+Successor text to rev0 Part I ([rev0 PRD](../2026-08-26_PRD_rev0/PRD.md) lines
+33–215, preserved there verbatim). Base text unchanged except marked **rev1**
+annotations; the decision registry moves to [[GOV.3-decision-map]].
+
+### 1. What Mosaic Stack is (D1)
+
+Mosaic Stack is an **open-source, AI-first platform for people who want a
+self-hosted environment for agentic management and a life operating system.**
+It serves personal, business, and employee needs from one deployment, and the
+work is offered freely.
+
+"AI-first" means agents are first-class operators of the system, not a bolted-on
+chat box: the platform exists to let humans direct fleets of agents over their
+projects, tasks, communications, and infrastructure, with the same tools and
+the same guarantees whether a human or an agent is acting.
+
+### 2. Who it is for (D1, D9)
+
+The operator of a deployment is its user. Mosaic Stack is **not a hosted
+business**: running the system as a service for external customers is outside
+the north star. Multi-tenancy exists WITHIN a deployment so that one operator
+can separate their world — for example, several LLCs plus a personal domain —
+while every deployment is self-hosted by its own operator.
+
+"Company" in the hierarchy is organizational separation for one operator's
+world, not a customer account.
+
+### 3. Deployment modes (D3)
+
+Two modes, chosen at install time:
+
+|                     | Standalone / personal                  | Enterprise                                            |
+| ------------------- | -------------------------------------- | ----------------------------------------------------- |
+| Brains              | one mosaic-brain (system + user files) | system brain for config + one brain per user          |
+| User-data isolation | single user                            | no user-data leakage between users; sharing is opt-in |
+| Secrets             | OpenBao/Vault or flat files            | OpenBao/Vault REQUIRED                                |
+| Conversion          | Standalone → Enterprise, **one-way**   | terminal state                                        |
+
+Brains are configurable as external git repositories (recommended, not
+required); git tracking is always on locally.
+
+**Federation** (connecting deployments: system-level config, assigned users,
+rights and data-access control, trusts with boundaries, exfiltration
+monitoring) is intentionally not fully designed. It is deferred, appears on the
+roadmap as a placeholder phase per D11, and nothing in v1 may foreclose it.
+_D3 as amended 2026-09-01 (Q-T1 ruling B):_ federation milestones M1–M3
+(Step-CA, enrollment, grants, mTLS auth guard, ScopeService, list/get/
+capabilities verbs) are **shipped but frozen** — present in code behind the
+`tier === 'federated'` gate, dormant since 2026-06-25, absent from the canonical
+compose topology (D15), excluded from the v1 bar, tracked as a dormant
+workstream in `docs/fleet/NORTH_STAR.yaml`, and gated on a security re-audit
+before any resumption. See [[GOV.5-open-questions]] Q-T1.
+
+### 4. Structure and tenancy (D2, D9, D13)
+
+The hierarchy:
+
+```
+company/organization  (N per deployment)
+└─ estate             (each in exactly one company)
+   └─ project         (each in exactly one estate)
+      └─ workspace    (project-specific; carries the Kanban)
+```
+
+Rules:
+
+- Users can create N companies, N estates, N projects.
+- Tasks bubble UP the hierarchy so whole-system status is visible at every
+  level. Bubble-up is **read-only aggregation**, never a cross-workspace write.
+- Granular RBAC: admins restrict access per company, estate, and project;
+  grants are evaluated down the chain. Assets are transferable subject to the
+  structure.
+- **`workspace_id` remains the hard mechanical isolation unit** exactly as
+  ratified in
+  [docs/requirements/native-kanban-sot.md](../../requirements/native-kanban-sot.md)
+  (#751): PostgreSQL sole writable SOT, cross-workspace relationships rejected,
+  fail-closed mutations. The hierarchy is parent structure ABOVE workspaces,
+  used for RBAC evaluation and read-only roll-ups. The kanban SOT carries this
+  as Amendment A1, added by reviewed PR — an amendment, not a rewrite (D13).
+
+### 5. Identity (D10)
+
+Built-in auth (better-auth) is the **account system of record**. Authentik and
+other external IdPs federate in via OIDC as login methods; they never become
+the system of record. Perimeter shims (forward-auth in front of a web host) are
+deployment workarounds, not the design.
+
+### 6. Onboarding (D4)
+
+Onboarding is a **wizard that differs by mode, is re-runnable (no lock-in), and
+is extensible** — new wizards attach as tabs.
+
+Standalone flow captures: system and company name; component choices (Mosaic
+Comms/Matrix vs external; Mosaic SSO/Authentik vs external; Mosaic
+DB/PostgreSQL vs external; vector DB); the initial user
+(email/password/name/SSO); comms setup (Matrix/Discord/Slack); agent enrollment
+(harness choice and install, OAuth or API-key login, multi-account, model
+choice with recommendation, agent name and persona, account assignment,
+optional comms auto-enroll); a user onboarding profile (disabilities including
+ADHD/autism/PDA/vision, professional background, education, desired agent
+communication style, optional voice-matching interview, family/pets/friends/
+hobbies/likes-dislikes); email and drive connectors (Gmail/IMAP, Google
+Drive/OneDrive/Dropbox) with granular agentic-access consent; SSO/OIDC
+configuration; an initial estate, an initial project, and seeded example data.
+
+Enterprise uses the same skeleton with personal data optional; the focus moves
+to business structure, org chart, RBAC, M365 and external systems, immediate
+OIDC, SSO prominent.
+
+Profile answers feed `USER.md` and/or the user's data store subject to the
+custody rule in §7.
+
+### 7. Data custody (D6, D14)
+
+- **Sensitive profile categories** (disabilities, family, communication style,
+  and similar) live in the **user's own brain ONLY**. PostgreSQL holds
+  structural data, consent records, and pointers — never the content. "User
+  data does not leak" is enforced by architecture, not policy (D14).
+- Standalone (one user, one brain) **may** keep the same split — D14 makes it
+  optional in Standalone, not required. Keeping it is the recommended default
+  because it preserves forward-compatibility with the one-way Enterprise
+  conversion (D3).
+- Estate brains hold operational records. Only product-relevant material
+  migrates into this repository's docs; operational records stay in their
+  brains and are linked (D6).
+
+### 8. Architecture gate — the webUI sits OVER official tooling (D8, D12)
+
+**HARD RULE:** every webUI operation goes through the Gateway API backed by the
+same official framework tooling the CLI uses. The CLI remains the primary
+execution method; the webUI uses the tools to operate and configure the
+system. The webUI never bypasses tooling to reach the database or filesystem
+directly.
+
+Consequence for planning: when a desired webUI operation has no backing tool,
+the gap is scored **"blocked on tooling"** and the tool is built first. The
+product baseline therefore always includes all three D8 inputs: the tool
+inventory (what exists and what is missing), the webUI→tool mapping, and the
+measured current state of the `next` branch.
+
+### 9. v1 slice (D11)
+
+v1 is deliberately small:
+
+1. **Standalone onboarding wizard** — system/company name, component choices,
+   initial user, initial estate + project, seeded examples, re-runnable.
+2. **Hierarchy core** — company → estate → project → workspace → kanban, with
+   read-only task bubble-up.
+3. **Basic RBAC** on the hierarchy.
+4. **Minimal agent enrollment** — one harness, API key, name/persona.
+
+Deferred beyond v1: connectors, comms integrations, voice-matching, M365,
+Enterprise conversion, federation. Every deferred item appears in
+[docs/ROADMAP.md](../../ROADMAP.md) per the D11 rule: nothing exists only in heads.
+
+### 10. Relationship to the fleet north star
+
+[docs/fleet/NORTH_STAR.md](../../fleet/NORTH_STAR.md) (generated from
+`docs/fleet/NORTH_STAR.yaml`) is the **delivery-fleet** north star: how the
+agent fleet that builds and operates the system should run (NS-1..NS-10,
+workstreams A–L). This PRD is the **product** north star. They are not
+competitors: the fleet north star is subordinate product-wise — its workstream
+J ("Web control plane") is one consumer of this PRD's D8/D12 gate — and this
+PRD does not redefine fleet invariants. The subordination rule is ratified in
+the frozen audit-input baseline (T2 operator freeze, 2026-08-25: "the PRD must
+cite and subordinate it, never fork it"). A change that would put the two in
+conflict must amend one of them explicitly, never fork a third document
+(drafting addition — see §12.1).
+
+### 11. Explicit non-goals
+
+- Hosted/SaaS operation for external customers (D9).
+- A webUI that writes to the database or filesystem around the tooling (D12).
+- A second writable task store beside PostgreSQL (native-kanban-sot invariants).
+- Fully-designed federation in v1 (D3 — roadmap placeholder only; the shipped M1–M3 code is frozen, not a v1 feature).
+
+### D15 — Tiered containerized deployment (2026-08-30, containerization lane)
+
+The stack ships a tiered deployment target, additive to the architecture
+gate (D8): (1) Standalone tier — docker compose is the canonical
+single-host deployment: postgres, valkey, openbao, gateway, appservice
+and the served webUI in one composition, with migrations, health checks,
+and a documented install/upgrade path; the registry (CI-published
+images) is the only deployment source. (2) Enterprise tier — Kubernetes
+manifests for the same service set, phase-gated on the standalone tier
+holding its acceptance bar. The v1 acceptance bar for the standalone
+tier: compose-up healthy; webUI hosts agent chat; an in-stack agent can
+open a PR to this repo; CI validates it; the running deployment adopts
+the merged change (pull + restart). Federation (D3 clause) remains
+deferred and unforeclosed. Implementation plan:
+docs/plans/2026-08-30_containerization.md.
+
+---
+
+## rev1 annotations (2026-08-31)
+
+- §8's architecture gate (webUI over official tooling, CLI primary) is
+  elaborated for the control plane by [[UI.1-webui-surfaces]] and
+  [[CLI.1-parity]]; register decision OD-53 confirms all interfaces share one
+  CLI-backed engine.
+- §4's RBAC and §5's identity are joined by the **agent-side** authority model
+  in [[AUTHZ.1-capability-authority]]: role capability ceilings enforced at the
+  harness by `mosaic-core`, composed by pure intersection.
+- The fleet north star subordination (§10) gains a control-plane consequence:
+  the WebUI workstream consumes this PRD's surface specifications
+  ([[UI.1-webui-surfaces]]) rather than defining its own.
@@ -59,7 +59,7 @@ Active workstream is **W1 — Federation v1**. Workers should:

 ## Fleet configuration management (#758) — M0–M5 implementation DAG

-> **PRD:** [Fleet declarative configuration management](./PRD.md#fleet-declarative-configuration-management-workstream-fcm-758) · **M0 acceptance:** [docs IA checklist](./fleet/FLEET-CONFIG-DOCS-IA-CHECKLIST.md) · **baseline dispositions:** [legacy example/profile inventory](./fleet/LEGACY-EXAMPLE-PROFILE-DISPOSITION-INVENTORY.md)
+> **PRD:** [Fleet declarative configuration management](./PRDs/2026-08-31_PRD_rev1/GOV.4-workstream-contracts.md#fleet-declarative-configuration-management-workstream-fcm-758) · **M0 acceptance:** [docs IA checklist](./fleet/FLEET-CONFIG-DOCS-IA-CHECKLIST.md) · **baseline dispositions:** [legacy example/profile inventory](./fleet/LEGACY-EXAMPLE-PROFILE-DISPOSITION-INVENTORY.md)
 >
 > Every row below is one independently reviewable card and **one PR**. `depends_on` is a
 > hard DAG edge; no card may silently absorb another card's scope. All source cards require
@@ -1,8 +1,10 @@
 ---
 kind: tracking
-status: active
+status: superseded
 ---

+> **Superseded (2026-09-01, PRD rev1 ratification).** This document's framing of Federation v1 as an active, in-progress mission (M3) is historical. Federation M1–M3 are shipped but **frozen** (dormant since 2026-06-25, excluded from the v1 bar, security re-audit gate before any resumption); the canonical v1 deployment topology is the compose standalone tier (PRD rev1, D15). Authority: `docs/PRD.md` → `docs/PRDs/2026-08-31_PRD_rev1/` (decision D3 as amended, GOV.5 Q-T1). Tracking: `docs/fleet/NORTH_STAR.yaml` (dormant federation workstream). Content below is preserved verbatim as a record — do not edit it.
+
 # Mission Manifest — Federation v1

 > Persistent document tracking full mission scope, status, and session history.
@@ -39,20 +39,21 @@ The Mosaic Backlog is the backlog of record + dispatch engine, built on Mosaic's

 ## Workstreams

-| id  | title                                                                                                       |
-| --- | ----------------------------------------------------------------------------------------------------------- |
-| A   | Substrate — Mosaic Backlog on native Postgres storage service                                               |
-| B   | Supervisor — movement guarantee, two-agent floor, dispatch/claim                                            |
-| C   | Planner — goal decomposition into independently-shippable cards                                             |
-| D   | Merge-gate — single approver, pr-merge.sh after CI wait                                                     |
-| E   | Meta-loop — session-review + enhancer improvement PRs                                                       |
-| F   | Safety-rails — TTL claims, advisory spend, PAUSE kill-switch                                                |
-| G   | Kill-switch — operator PAUSE honored before dispatch and merge                                              |
-| H   | Personas & system profiles — cross-domain library, system-type provisioning, update-surviving customization |
-| I   | Operator surface — launcher, fleet visibility, reliable steering (tier 0)                                   |
-| J   | Web control plane — browser surface over the gateway (tier 1)                                               |
-| K   | Clients — desktop and mobile over the same backend (tier 2)                                                 |
-| L   | Auth profiles — per-provider accounts, per-session selection (tier 2)                                       |
+| id  | title                                                                                                             |
+| --- | ----------------------------------------------------------------------------------------------------------------- |
+| A   | Substrate — Mosaic Backlog on native Postgres storage service                                                     |
+| B   | Supervisor — movement guarantee, two-agent floor, dispatch/claim                                                  |
+| C   | Planner — goal decomposition into independently-shippable cards                                                   |
+| D   | Merge-gate — single approver, pr-merge.sh after CI wait                                                           |
+| E   | Meta-loop — session-review + enhancer improvement PRs                                                             |
+| F   | Safety-rails — TTL claims, advisory spend, PAUSE kill-switch                                                      |
+| G   | Kill-switch — operator PAUSE honored before dispatch and merge                                                    |
+| H   | Personas & system profiles — cross-domain library, system-type provisioning, update-surviving customization       |
+| I   | Operator surface — launcher, fleet visibility, reliable steering (tier 0)                                         |
+| J   | Web control plane — browser surface over the gateway (tier 1)                                                     |
+| K   | Clients — desktop and mobile over the same backend (tier 2)                                                       |
+| L   | Auth profiles — per-provider accounts, per-session selection (tier 2)                                             |
+| M   | Federation — DORMANT; M1–M3 shipped and frozen (PRD rev1 D3 as amended; security re-audit gate before resumption) |

 ## Goals (backlog projection)

@@ -145,8 +145,15 @@ workstreams:
    title: Clients — desktop and mobile over the same backend (tier 2)
  - id: L
    title: Auth profiles — per-provider accounts, per-session selection (tier 2)
+  # M is DORMANT by ruling (PRD rev1, D3 as amended 2026-09-01, GOV.5 Q-T1
+  # ruling B). Federation M1–M3 exist in code behind `tier === 'federated'`
+  # (M3 landed 2026-06-24/25), are excluded from the v1 bar and frozen. It
+  # projects no goals on purpose: none may be added before a security
+  # re-audit of the frozen cert/auth code and a federation PRD revision.
+  - id: M
+    title: Federation — DORMANT; M1–M3 shipped and frozen (PRD rev1 D3 as amended; security re-audit gate before resumption)

-# NOTE: workstreams C, D, E and F are declared but currently project no goals.
+# NOTE: workstreams C, D, E, F and M are declared but currently project no goals.
 # That is planning debt, not an editing error: their goals have not been written
 # yet. The A5 validator below reports it rather than letting it stay invisible.

@@ -1,6 +1,6 @@
 # Fleet Configuration Management

-This book documents the local roster-v2 desired-state control plane delivered under issue #758. The normative requirements are the [FCM section of the repository PRD](../PRD.md#fleet-declarative-configuration-management-workstream-fcm-758), not the older fleet-suite or observability planning pages.
+This book documents the local roster-v2 desired-state control plane delivered under issue #758. The normative requirements are the [FCM section of the repository PRD](../PRDs/2026-08-31_PRD_rev1/GOV.4-workstream-contracts.md#fleet-declarative-configuration-management-workstream-fcm-758), not the older fleet-suite or observability planning pages.

 ## Authority boundary

@@ -5,12 +5,24 @@ status: active

 # Deployment Guide

-> **Status: non-operative for PostgreSQL, federated, and bare-metal production.** The checked-in
+> **Status: non-operative for PostgreSQL, federated (federation is frozen — PRD rev1 D3 as
+> amended; not a v1 route), and bare-metal production.** The checked-in
 > Compose PostgreSQL service mounts legacy initialization SQL and the KBN-101 bootstrap, runner,
 > secret-renderer, and process-exec interfaces do not exist yet. This page does not authorize a
 > production deployment, database initialization, manual DDL, secret provisioning, or service
 > activation.

+## Relationship to the PRD (D15)
+
+Per PRD rev1 Decision D15 (`docs/PRD.md`), the compose standalone tier — `docker compose up` — is
+the canonical v1 deployment topology; this guide describes the interim path to that bar, not a
+competing one. The KBN-101 holds documented below (bootstrap, runner, secret-renderer, process-exec)
+are operational gates on the road to the standalone-tier bar, not an alternative or federated
+topology. They remain fully binding: nothing in this guide authorizes PostgreSQL, federated, or
+bare-metal production activation until the named KBN-101-00/03/05 artifacts land, pass review, and
+satisfy the order specified below. Federation M1–M3 references elsewhere in this guide are
+historical/frozen (PRD rev1 D3 as amended) and do not describe a live or v1-bound route.
+
 ## Current safe local route

 Use PGlite only for current in-process data-layer work; it requires no PostgreSQL. A Gateway/Web
@@ -22,12 +34,14 @@ docker compose up -d valkey
 ```

 This command intentionally does not start PostgreSQL. Do not run a broad Compose start, use its
-PostgreSQL initialization mount, infer that current Compose is a production/federated route, or
+PostgreSQL initialization mount, infer that current Compose is a production/federated (federation
+is frozen — PRD rev1 D3 as amended; not a v1 route) route, or
 start Gateway/Web until KBN-101-02 supplies fail-closed local-tier/DSN isolation.

 ## Held future procedure

-PostgreSQL local, federated, Compose, and bare-metal production activation are held until these
+PostgreSQL local, federated (federation is frozen — PRD rev1 D3 as amended; not a v1 route),
+Compose, and bare-metal production activation are held until these
 artifacts land and pass their independent gates:

 1. **KBN-101-00** external privileged bootstrap artifact;
@@ -69,4 +83,5 @@ For local PGlite development, diagnose application behavior without introducing
 connection.

 Non-database local services may be inspected with their ordinary local health/log tools. Those
-checks do not certify PostgreSQL, federated deployment, or production readiness.
+checks do not certify PostgreSQL, federated (federation is frozen — PRD rev1 D3 as amended; not a
+v1 route) deployment, or production readiness.
@@ -8,7 +8,7 @@ status: active
 > Single-writer: the RI-050 orchestrator (jarvis, dragon-lin) only. Workers read but never modify.
 >
 > **Mission:** alpha 0.0.50 release-integrity floor (decisions SDLC-D-033..038).
-> **PRD:** [docs/PRD.md § Release Integrity Workstream](../PRD.md#release-integrity-workstream-ri-1275)
+> **PRD:** [PRD rev1 GOV.4 § Release Integrity Workstream](../PRDs/2026-08-31_PRD_rev1/GOV.4-workstream-contracts.md#release-integrity-workstream-ri-1275)
 > **Issue:** #1275 (remains open until RI-V-001 closes)
 > **Base branch:** `next` (all cards branch from `origin/next`, squash-merge via PR)
 >
@@ -1,8 +1,10 @@
 ---
 kind: record
-status: active
+status: superseded
 ---

+> **Superseded (2026-09-01, PRD rev1 ratification).** This document's record of a completed Federation M2 milestone is historical. Federation M1–M3 are shipped but **frozen** (dormant since 2026-06-25, excluded from the v1 bar, security re-audit gate before any resumption); the canonical v1 deployment topology is the compose standalone tier (PRD rev1, D15). Authority: `docs/PRD.md` → `docs/PRDs/2026-08-31_PRD_rev1/` (decision D3 as amended, GOV.5 Q-T1). Tracking: `docs/fleet/NORTH_STAR.yaml` (dormant federation workstream). Content below is preserved verbatim as a record — do not edit it.
+
 # Mission Scratchpad — MVP

 > Append-only log. NEVER delete entries. NEVER overwrite sections.