docs/prd: address independent review findings 1-10 (fidelity, A1 record class + carve-out, roadmap completeness)

docs/PRD.md

@@ -139,8 +139,10 @@ custody rule in §7.
   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) keeps the same split for
-  forward-compatibility with the one-way Enterprise conversion (D3).
+- 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).
@@ -155,8 +157,9 @@ 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 the tool inventory and the
-webUI→tool mapping.
+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)
 
@@ -181,8 +184,11 @@ 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. A change that would put the two in
-conflict must amend one of them explicitly, never fork a third document.
+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
 
@@ -201,7 +207,7 @@ conflict must amend one of them explicitly, never fork a third document.
 | 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; frozen INPUTS baseline in the audit lane)                     |
+| 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                                                |
@@ -213,6 +219,23 @@ conflict must amend one of them explicitly, never fork a third document.
 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)