docs: ratify PRD rev1 — consolidated bundle, permanent shim, rev0 archived

Ratifies the Mosaic Stack PRD rev1 (Jason Woltje, 2026-09-01) as project
source of truth and installs the GOV.1 lifecycle model:

- docs/PRD.md becomes a permanent shim (kind: shim, current_rev ->
  docs/PRDs/2026-08-31_PRD_rev1/). Its path never changes again.
- docs/PRDs/2026-08-26_PRD_rev0/PRD.md archives the 2026-08-26 North Star
  verbatim (sha256 60cc2f98...36afdf unchanged). Archive, never delete.
- docs/PRDs/2026-08-31_PRD_rev1/ is the frozen rev1 bundle: 18 sectioned
  documents (VIS, DATA, AUTHN, AUTHZ, SEAT, ROLE, HARN, PROV, SESS, UI, CLI,
  GOV.1-5) consolidating rev0 D1-D15, the fleet north star, the agent-runtime
  L1/L2 contracts and the control-plane-surfaces lane findings, with a single
  decision map (GOV.3) and a closed open-questions frontier (GOV.5, grill
  rounds 1-8). Drafting inputs (_source-* snapshots) are not shipped.

Consequences of the ratified rulings carried in the same change:

- Q-T1 (ruling B, "shipped but frozen"): D3 amended in GOV.3/VIS.1;
  federation M1-M3 acknowledged as shipped behind tier === 'federated',
  excluded from the v1 bar and frozen, with a security re-audit gate before
  any resumption. docs/MISSION-MANIFEST.md, docs/federation/MISSION-MANIFEST.md
  and docs/scratchpads/mvp-20260312.md get status: superseded + banners
  (content preserved verbatim); docs/guides/deployment.md gains a
  "Relationship to the PRD (D15)" section. NORTH_STAR.yaml adds dormant
  workstream M (projects no goals by design); NORTH_STAR.md regenerated.
- Q-G2 (distinct registry prefixes): every citation of the operator
  DECISION-REGISTER in the bundle reads OD-nn; the stack registry stays
  D1-D15; L1-Dnn/L2-Dnn untouched. Prefix rule recorded in GOV.1.

Follow-ups (not in this PR): CI parity drift-gate witness (Q-C1); brain-side
DECISION-REGISTER rename to OD- with redirect table on its next touch.

docs/guides/deployment.md

@@ -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.