rcf-lite 0.28.4 → 0.30.0

package/rcf/code-nodes/cn-747.json

@@ -0,0 +1,18 @@
+{
+  "cnId": "CN-747",
+  "path": "src/view/readiness/po-layer.js",
+  "title": "Readiness PO layer: VerdictCards, QuestionCards grouped by source span, intent-complete empty state, For-engineers DocRow",
+  "description": "`renderReadinessPO(readiness, { persona, engineerBody })` emits the PO layer HTML: two equal-height VerdictCards (intent-complete and ready-to-build) with the chain term muted beside each plain label; one QuestionCard group per source span sourced from `toQuestions(readiness)`; a `data-rcf-empty=\"yes\"` block that renders the verbatim `formatVerdictLines(readiness).intentComplete` string when `questions[]` is empty and both levels are ok (AC-18002-2); the Requirements-that-still-need-work table; and the For-engineers DocRow that wraps the engineer rendering, closed under productOwner / unstated and open under engineer, with the data preserved in the DOM in every register (AC-18002-3). Stamps `data-rcf-source=\"readiness.questions\"` on the questions block when the real compute shape is live (AC-18002-1).",
+  "implementsAcIds": [
+    "AC-18002-1",
+    "AC-18002-2",
+    "AC-18002-3"
+  ],
+  "dependencies": [
+    "CN-746"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T09:30:00Z",
+  "updatedAt": "2026-10-03T09:30:00Z"
+}

package/rcf/code-nodes/cn-748.json

@@ -0,0 +1,16 @@
+{
+  "cnId": "CN-748",
+  "path": "src/view/readiness.js",
+  "title": "renderReadinessPanel wraps the PO layer around the engineer body and picks the register from profile.md",
+  "description": "`renderReadinessPanel(result, { profileText })` picks the register from `profile.md` (productOwner | engineer | unstated), renders the engineer body (the pre-PR-8 Readiness rendering: tree line, CLI verdict lines, next-action-per-persona, D1..D8 chips, PO + Engineer blocker groups, delta/diff) once, and hands it to `renderReadinessPO` as `engineerBody`. The engineer body is never removed from the DOM; `renderReadinessPO` is what folds it into the For-engineers DocRow and decides open/closed per register (AC-18002-3).",
+  "implementsAcIds": [
+    "AC-18002-3"
+  ],
+  "dependencies": [
+    "CN-747"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T09:30:00Z",
+  "updatedAt": "2026-10-03T09:30:00Z"
+}

package/rcf/code-nodes/cn-749.json

@@ -0,0 +1,16 @@
+{
+  "cnId": "CN-749",
+  "path": "src/view/index.js",
+  "title": "View bootstrap attaches computeQuestions output to readiness so the adapter feature-detects the real shape",
+  "description": "After `computeReadiness` returns, the view bootstrap calls `computeQuestions(readiness, { tree, ledgers, profileText, persona: 'productOwner' })` and merges the result's `questions`, `groups`, `optional` and `engineer` fields onto the readiness object before it reaches `renderPage`. `preferReadinessQuestions` then returns true and `fromReadinessQuestions` reads the real `computeQuestions` output rather than falling back to the blockers path (AC-18002-1). The phrasebook stays available as the per-field fallback when a question carries no `ask` / `hint` of its own.",
+  "implementsAcIds": [
+    "AC-18002-1"
+  ],
+  "dependencies": [
+    "CN-746"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T09:30:00Z",
+  "updatedAt": "2026-10-03T09:30:00Z"
+}

package/rcf/code-nodes/cn-750.json

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-750",
+  "path": "src/view/test-host/fixture.js",
+  "title": "Wespa host fixture page: 56px header, resizable sidebar, iframe mounted at ./?embed=1&theme=light with no inline script",
+  "description": "`renderTestHostPage()` returns the host-fixture HTML as a pure string: HTML5 doctype, lang='en-GB', a 56px wespa-header carrying the Light/Dark toggle buttons, a resizable sidebar shell (data-rcf-host-sidebar + drag handle) and a content pane carrying `<iframe id=\"rcf-test-host-iframe\" src=\"./?embed=1&amp;theme=light\">`. The fixture ships no inline `<script>` body (CSP-friendly, consistent with the PR 1 contract); its client-side wiring lives at /test-host.js (served via /test-host.js when the test-host route is enabled). The fixture does not persist theme or sidebar width to localStorage (ADR-4136): a passing run has to flip the iframe through the postMessage path, which is the invariant the fixture pins. Proves AC-206-1 (shell + iframe src + no inline script) and underwrites AC-206-6 (no outbound postMessage shape beyond the embed-client's single rcf-view-theme post).",
+  "implementsAcIds": [
+    "AC-206-1",
+    "AC-206-6"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T09:55:00Z",
+  "updatedAt": "2026-10-03T09:55:00Z"
+}

package/rcf/code-nodes/cn-751.json

@@ -0,0 +1,18 @@
+{
+  "cnId": "CN-751",
+  "path": "src/view/test-host/embed-client.js",
+  "title": "Wespa host fixture client: theme postMessage, sidebar drag + collapse/expand, same-origin message target",
+  "description": "Classic (non-module) browser script served at /test-host.js when the test-host route is on. Three fixture behaviours: (a) the theme toggle posts `{ type: 'rcf-view-theme', theme }` to `iframe.contentWindow`, targeting `window.location.origin` so a cross-origin receiver would refuse the message (underwrites AC-206-4 together with the viewer's own origin check in page-init.js); (b) the sidebar drag handle sets `--wespa-sidebar-width` on the <main> grid, clamped to 64..400 px live; (c) collapse/expand snaps the sidebar between 64 px and 200 px. Reads the iframe's `data-theme` attribute as evidence of the postMessage round-trip (AC-206-2). After the iframe's hash-only navigation, `data-embed` and the search string carry embed=1 and the theme, which the live-proof script captures (AC-206-3). The host does not read event.origin (the viewer does) and does not persist theme to localStorage (ADR-4136 invariant).",
+  "implementsAcIds": [
+    "AC-206-2",
+    "AC-206-3",
+    "AC-206-4"
+  ],
+  "dependencies": [
+    "CN-750"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T09:55:00Z",
+  "updatedAt": "2026-10-03T09:55:00Z"
+}

package/rcf/code-nodes/cn-752.json

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-752",
+  "path": "src/view/test-host/lints.js",
+  "title": "Three embedding lints: framing headers, target=_top, localStorage namespace",
+  "description": "Three pure assertions callable by any test harness; test/view/wespa-host-fixture.test.js is the suite caller. (1) `assertFramingHeaders(response)` refuses on `X-Frame-Options` or on CSP `frame-ancestors` forbidding same-origin, and accepts `frame-ancestors 'self'`. (2) `assertNoTargetTop(renderedHtml)` greps for `target=\"_top\"` / `target='_top'` / `target=_top` and refuses on any match; returns `{ ok, count }`. (3) `assertLocalStorageNamespace(sourceTreeRoot)` walks every .js file under `src/view/**` (excluding vendored and .min.js) and asserts every `localStorage.*` / `sessionStorage.*` / shared `storage.*` call site uses a key literal starting with `rcf-view:v1:` or a constant resolving to that prefix. Together they pin AC-206-5 against regressions.",
+  "implementsAcIds": [
+    "AC-206-5"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T09:55:00Z",
+  "updatedAt": "2026-10-03T09:55:00Z"
+}

package/rcf/code-nodes/cn-753.json

@@ -0,0 +1,19 @@
+{
+  "cnId": "CN-753",
+  "path": "src/query/gates.js",
+  "title": "DEFINE step 3 PR 5: D3 bite checks, parseInterfaceTemplate and ackable on the gates module",
+  "description": "src/query/gates.js grows the three D3 bite checks (shapes:templateMarkers over delta with per-kind marker presence on interfaces[].description; shapes:entityJoin over tree asserting every coreEntities[].name is named by exactly one recordShape with ids TAD.entity:<name>; shapes:pathsResolve over delta asserting any path:-like token resolves against the resolvedPaths map in the stage context or carries authoredAt: D3), the parseInterfaceTemplate(iface) helper that computes per-kind marker presence (exported for validate's step 6 notice), and the ackable(stage) helper that returns true for D3, D5 and D6. The CHECK_PERSONA, CHECK_QUESTION and STAGE_FALLBACK_PERSONA maps grow in step so every new check carries a persona and a question. Drafts are included in templateMarkers. The gate functions stay pure: readiness.js threads the resolvedPaths map through the stage context; the CLI resolves candidate paths on disk.",
+  "implementsAcIds": [
+    "AC-17404-1",
+    "AC-17404-2",
+    "AC-17404-3",
+    "AC-17404-4"
+  ],
+  "dependencies": [
+    "CN-725"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T10:50:00Z",
+  "updatedAt": "2026-10-03T10:50:00Z"
+}

package/rcf/code-nodes/cn-754.json

@@ -0,0 +1,17 @@
+{
+  "cnId": "CN-754",
+  "path": "src/cli/readiness.js",
+  "title": "DEFINE step 3 PR 5: --check shapes exit 4 policy and resolvedPaths resolve-on-disk",
+  "description": "src/cli/readiness.js grows a bite-aware --check policy: --check shapes exits 4 on an unacknowledged D3 failure and 0 when the freeze record acknowledges define.shapes at the current tree hash; the warn-with-ack branch is kept for D5 and D6 until PRs 6 and 7 bite them. Before invoking computeReadiness the CLI collects candidate path tokens from in-scope TAC interface descriptions and passes a resolvedPaths map (local resolve on disk) through the stage context so the pure gate function shapes:pathsResolve can decide path existence without I/O. The decideExitCode helper reads ackable(stage) and the freeze.gates[<gate>] record to pick between 0 (warn-with-ack unacked or acked bite) and 4 (bite unacked at the current hash).",
+  "implementsAcIds": [
+    "AC-17404-5"
+  ],
+  "dependencies": [
+    "CN-727",
+    "CN-753"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T10:50:00Z",
+  "updatedAt": "2026-10-03T10:50:00Z"
+}

package/rcf/code-nodes/cn-755.json

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-755",
+  "path": "src/cli/freeze.js",
+  "title": "DEFINE step 3 PR 5: freeze --ack on D1, D2, D4, D7 or D8 keeps exiting 2",
+  "description": "src/cli/freeze.js already refuses --ack on any gate outside D3, D5 and D6 with exit 2 and the usage line ADR-4124 pins. PR 5 confirms the invariant with AC-17404-6: ackable(stage) in gates.js is the single source of truth for the three ackable gates (freeze reads ACKABLE_GATES = STAGE_GATES.D3 | D5 | D6, which lines up with ackable()). No code change in this PR; this CN anchors the AC against the file that enforces the invariant so a future refactor cannot drop the exit-2 behaviour without flagging the AC.",
+  "implementsAcIds": [
+    "AC-17404-6"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T10:50:00Z",
+  "updatedAt": "2026-10-03T10:50:00Z"
+}

package/rcf/code-nodes/cn-756.json

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-756",
+  "path": "src/define/concern-catalogue.js",
+  "title": "DEFINE step 3 PR 6: the eight-concern applicability map keyed by REQ shape",
+  "description": "src/define/concern-catalogue.js lands as a new pure module beside ledgers.js. Exports CONCERN_KEYS (the eight concern names in canonical order), CONCERN_APPLICABILITY (the map { concern -> [req-shapes] } that spec section 4 row 'D5 catalogue' pins), and applicableConcernsFor(reqShape) which returns the concern keys that apply to a REQ shape. No I/O, no state. Keys shared with the baseline catalogue where names coincide (auth; the rest are new because the baseline-AC catalog does not name per-concern crosscut keys). Read by crosscut:catalogue in src/query/gates.js (PR 6) to enumerate the applicable (reqShape, concern) pairs for every REQ in scope.",
+  "implementsAcIds": [
+    "AC-17405-3",
+    "AC-17405-4"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T13:30:00Z",
+  "updatedAt": "2026-10-03T13:30:00Z"
+}

package/rcf/code-nodes/cn-757.json

@@ -0,0 +1,21 @@
+{
+  "cnId": "CN-757",
+  "path": "src/query/gates.js",
+  "title": "DEFINE step 3 PR 6: D4 closed-set and ownerRef findings, D5 catalogue, standards citation on the gates module",
+  "description": "src/query/gates.js grows four new engineer checks: stories:closedSets (over delta; AC description with an enumeration cue and no bracketed list or ownerRef fails, honouring the quoted-cue guard shared with D6); stories:ownerRefResolves (over delta plus tree for ownerRef targets; every ownerRef { tacId, field: interfaces[<name>] } on an AC resolves on that TAC, else fails with 'ownerRef does not resolve'); crosscut:catalogue (over tree; for every REQ in scope, every applicable (reqShape, concern) pair via src/define/concern-catalogue.js has a concern-ledger entry keyed <REQ>:<concern> with disposition applied or waived, else fails <REQ>:<concern>); skeleton:standardsCited (over tree; every manifest.standards[].slug is cited in a REQ rationale or an ADR, or waived by a concern-ledger entry keyed standards:<pack>, else fails standards:<pack> with 'uncited and unwaived'). The CHECK_PERSONA and CHECK_QUESTION maps grow in step. parseAcClass is already exported; closedSets re-uses the quoted-cue guard pattern.",
+  "implementsAcIds": [
+    "AC-17405-1",
+    "AC-17405-2",
+    "AC-17405-3",
+    "AC-17405-4",
+    "AC-17405-5"
+  ],
+  "dependencies": [
+    "CN-753",
+    "CN-756"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T13:30:00Z",
+  "updatedAt": "2026-10-03T13:30:00Z"
+}

package/rcf/code-nodes/cn-758.json

@@ -0,0 +1,16 @@
+{
+  "cnId": "CN-758",
+  "path": "src/cli/readiness.js",
+  "title": "DEFINE step 3 PR 6: --check crosscut rides the D3 --ack fold with exit 4 unacked and 0 acked",
+  "description": "src/cli/readiness.js lifts the hard-coded D3-only bite branch so --check crosscut (and --check D5) honours the same --ack fold as --check shapes: an unacknowledged D5 failure exits 4; a D5 failure acknowledged at the current tree hash exits 0. The decision defers to gates.js's ackable(stage) rather than naming D5 inline, so a future bite on D6 is a one-line change. --check consistency keeps the 0.29.0 warn-with-ack posture until PR 7 bites D6; D1, D2, D4, D7, D8 keep exit 4 on a failure as blocking stages already do.",
+  "implementsAcIds": [
+    "AC-17405-3"
+  ],
+  "dependencies": [
+    "CN-754"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T13:30:00Z",
+  "updatedAt": "2026-10-03T13:30:00Z"
+}

package/rcf/code-nodes/cn-759.json

@@ -0,0 +1,21 @@
+{
+  "cnId": "CN-759",
+  "path": "src/query/gates.js",
+  "title": "DEFINE step 3 PR 7: four D6 scans (consistency:contradictions/unsatisfiable/duplicates/orphanInterfaces)",
+  "description": "src/query/gates.js gains four new engineer checks on checkD6Consistency: contradictions (two ACs on one story sharing a when clause with a negated then, honouring the shared quoted-substring guard with D4), unsatisfiable (a then naming a field no recordShape defines; a field defined in a [draft] recordShape counts as defined), duplicates (identical AC descriptions across stories fail both ACs), and orphanInterfaces (an interface on any TAC that no AC ownerRef points at and that no REQ deliveredBy reaches fails). The four checks are registered in CHECK_PERSONA and CHECK_QUESTION; they ride the existing D6 ackable fold.",
+  "implementsAcIds": [
+    "AC-17406-1",
+    "AC-17406-2",
+    "AC-17406-3",
+    "AC-17406-4",
+    "AC-17406-5",
+    "AC-17406-6"
+  ],
+  "dependencies": [
+    "CN-757"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T16:10:00Z",
+  "updatedAt": "2026-10-03T16:10:00Z"
+}

package/rcf/code-nodes/cn-760.json

@@ -0,0 +1,19 @@
+{
+  "cnId": "CN-760",
+  "path": "src/query/readiness.js",
+  "title": "DEFINE step 3 PR 7: probeRunner seam, parseLitmusFlag and countLitmusReadersAtHash",
+  "description": "src/query/readiness.js accepts an injectable `probeRunner` ({ reqId, tree }) => findings[], default null; when set, computeReadiness calls it once per REQ in scope and merges the returned findings into ledgers.probes.probes[] as open probe entries so consistency:probeCount reports them. With no runner the result equals the 0.29.0 result on the same fixture (AC-17504-2). Also exports parseLitmusFlag (positive-integer validator) and countLitmusReadersAtHash (reads distinct <reader> ids from probe-ledger entries whose finding begins litmus:<reader>: and whose text includes the given hash). Pure.",
+  "implementsAcIds": [
+    "AC-17504-1",
+    "AC-17504-2",
+    "AC-17504-3",
+    "AC-17504-4"
+  ],
+  "dependencies": [
+    "CN-761"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T16:10:00Z",
+  "updatedAt": "2026-10-03T16:10:00Z"
+}

package/rcf/code-nodes/cn-761.json

@@ -0,0 +1,16 @@
+{
+  "cnId": "CN-761",
+  "path": "src/define/probe-runner.js",
+  "title": "DEFINE step 3 PR 7: probe-runner seam (no shipped runner)",
+  "description": "src/define/probe-runner.js is a seam only: it exports the ProbeRunner typedef, a NO_PROBE_RUNNER sentinel and an isProbeRunner guard. No runner ships. rcf-lite has no LLM at runtime and does not spawn processes or make network calls; the harness is the runner through `rcf define ledger probes add` or a test harness that passes a stub into computeReadiness. Keeps the extension point named rather than monkey-patched (ADR-4131 extended).",
+  "implementsAcIds": [
+    "AC-17504-1",
+    "AC-17504-2",
+    "AC-17504-5"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T16:10:00Z",
+  "updatedAt": "2026-10-03T16:10:00Z"
+}

package/rcf/code-nodes/cn-762.json

@@ -0,0 +1,18 @@
+{
+  "cnId": "CN-762",
+  "path": "src/cli/readiness.js",
+  "title": "DEFINE step 3 PR 7: --litmus <n> and D6 in the biting-stages set",
+  "description": "src/cli/readiness.js adds the --litmus <n> flag with usage help, parses it via parseLitmusFlag, counts distinct litmus readers at the current tree hash via countLitmusReadersAtHash, and exits 4 with a stderr warn line naming the shortfall when fewer than n have attested. D6 joins the BITING_STAGES set so --check consistency now exits 4 on an unacknowledged D6 failure and 0 when acked at the current hash. --help documents the new flag. No process is spawned and no network call is made.",
+  "implementsAcIds": [
+    "AC-17504-3",
+    "AC-17504-4",
+    "AC-17504-5"
+  ],
+  "dependencies": [
+    "CN-760"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T16:10:00Z",
+  "updatedAt": "2026-10-03T16:10:00Z"
+}

package/rcf/code-nodes/cn-763.json

@@ -0,0 +1,18 @@
+{
+  "cnId": "CN-763",
+  "path": "src/cli/freeze.js",
+  "title": "DEFINE step 3 PR 7: --litmus <n> on rcf define freeze",
+  "description": "src/cli/freeze.js adds the --litmus <n> flag with usage help, parses it via parseLitmusFlag, and after the gate check (and any --ack folding) refuses (exit 4) and writes nothing when fewer than n distinct litmus readings exist at the current tree hash. --litmus-attested remains the default attestation path and is unchanged.",
+  "implementsAcIds": [
+    "AC-17504-3",
+    "AC-17504-4",
+    "AC-17504-5"
+  ],
+  "dependencies": [
+    "CN-760"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T16:10:00Z",
+  "updatedAt": "2026-10-03T16:10:00Z"
+}

package/rcf/code-nodes/cn-764.json

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-764",
+  "path": "guidance/define-litmus.md",
+  "title": "DEFINE step 3 PR 7: rcf_define_litmus prompt content",
+  "description": "guidance/define-litmus.md: the argument-free markdown served as the rcf_define_litmus MCP prompt (spec section 6 row). Walks the harness through spawning n fresh-context readers at the current tree hash and landing their readings as probe-ledger entries whose finding begins litmus:<reader>: and whose text includes the hash. Registered through guidance/manifest.json. No new resource URI (the markdown is the prompt content itself, not a doc).",
+  "implementsAcIds": [
+    "AC-17504-3",
+    "AC-17504-4"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T16:10:00Z",
+  "updatedAt": "2026-10-03T16:10:00Z"
+}

package/rcf/code-nodes/cn-765.json

@@ -0,0 +1,23 @@
+{
+  "cnId": "CN-765",
+  "path": "src/cli/build.js",
+  "title": "DEFINE step 3 PR 8: rcf build bundle --next freeze gate, --override write and impacted-FBS skip",
+  "description": "src/cli/build.js grows the `--override <reason>` flag, the pre-emit freeze gate (`enforceBundleNextFreezeGate`) that loads the freeze record and the computed delta, writes `freeze.override { reason, by, at }` through `applyOverrideToFreezeRecord` when a non-empty reason is supplied, refuses with exit 4 naming `rcf define readiness` and the override channel when no freeze record exists and no override is given, and passes `impactedFbsIds` into `selectNext`. The next-item path reports every skipped FBS on stderr; when every actionable FBS is impacted and no override is given, the verb refuses with exit 4 and the same message.",
+  "implementsAcIds": [
+    "AC-17702-1",
+    "AC-17702-2",
+    "AC-17702-3",
+    "AC-17702-4",
+    "AC-17702-5",
+    "AC-17902-2",
+    "AC-17902-3"
+  ],
+  "dependencies": [
+    "CN-720",
+    "CN-721"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T18:30:00Z",
+  "updatedAt": "2026-10-03T18:30:00Z"
+}

package/rcf/code-nodes/cn-766.json

@@ -0,0 +1,17 @@
+{
+  "cnId": "CN-766",
+  "path": "src/define/freeze-record.js",
+  "title": "DEFINE step 3 PR 8: applyOverrideToFreezeRecord writer",
+  "description": "src/define/freeze-record.js grows `applyOverrideToFreezeRecord({ projectRoot, reason, by, at })` which loads or creates a freeze record (stamped `frozenAt=now`, `treeHash=currentTreeHash` of the live tree, `docHashes` empty when no prior freeze), sets `override: { reason, by, at }` and writes through saveFreezeRecord. Reuses the existing SHA256 schema and canonical-JSON contract so the output is identical in shape to a freeze-verb write.",
+  "implementsAcIds": [
+    "AC-17702-2",
+    "AC-17902-3"
+  ],
+  "dependencies": [
+    "CN-721"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T18:30:00Z",
+  "updatedAt": "2026-10-03T18:30:00Z"
+}

package/rcf/code-nodes/cn-767.json

@@ -0,0 +1,17 @@
+{
+  "cnId": "CN-767",
+  "path": "src/define/validate-findings.js",
+  "title": "DEFINE step 3 PR 8: collectDefineValidateFindings module",
+  "description": "src/define/validate-findings.js exports `collectDefineValidateFindings(tree)`: a pure walker-tree function returning walker-shaped error entries for an interface kind outside INTERFACE_KINDS, an AC description's leading bracketed prefix outside the five known classes, a `tacIds` naming a non-TAC, and an unresolving `ownerRef` or `deliveredBy`. Reuses INTERFACE_KINDS and parseAcClass from src/query/gates.js so the vocabularies cannot diverge. Absence of a bracketed prefix is not a finding (decision 10, kept).",
+  "implementsAcIds": [
+    "AC-17802-1",
+    "AC-17802-2",
+    "AC-17802-3",
+    "AC-17802-4"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T18:30:00Z",
+  "updatedAt": "2026-10-03T18:30:00Z"
+}

package/rcf/code-nodes/cn-768.json

@@ -0,0 +1,19 @@
+{
+  "cnId": "CN-768",
+  "path": "src/cli/validate.js",
+  "title": "DEFINE step 3 PR 8: rcf define validate folds in the PR 8 finding set",
+  "description": "src/cli/validate.js runs `collectDefineValidateFindings(tree)` after the Code Node resolution pass and the companions check, folds the returned entries into the `errors` array it already exits on (exit 3), and reports them in the same `--json` envelope. The clean-output notice is suppressed when any PR 8 finding fires. The HELP text and the OPTION_SPEC are unchanged (the findings are the shipped surface).",
+  "implementsAcIds": [
+    "AC-17802-1",
+    "AC-17802-2",
+    "AC-17802-3",
+    "AC-17802-4"
+  ],
+  "dependencies": [
+    "CN-767"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T18:30:00Z",
+  "updatedAt": "2026-10-03T18:30:00Z"
+}

package/rcf/code-nodes/cn-769.json

@@ -0,0 +1,17 @@
+{
+  "cnId": "CN-769",
+  "path": "src/ruleset/ruleset.json",
+  "title": "DEFINE step 3 PR 8: NV-DL-ADM-01..05 added with refuseByDefault:true and overrideChannel:recordedInChain",
+  "description": "packages/rcf-lite/src/ruleset/ruleset.json gains the NV-DL namespace: NV-DL-ADM-01 (bundle refuses without a freeze), NV-DL-ADM-02 (D4 stories floor is a finding), NV-DL-ADM-03 (D3 shapes bite is a finding), NV-DL-ADM-04 (validate finding set is a finding) and NV-DL-ADM-05 (bundle skips impacted FBS). Each carries refuseByDefault:true and overrideChannel:'recordedInChain'. The existing NV-BL rows and ruling-sheet item 1 pattern are untouched.",
+  "implementsAcIds": [
+    "AC-17902-1",
+    "AC-17902-2",
+    "AC-17902-3",
+    "AC-17902-4"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T18:30:00Z",
+  "updatedAt": "2026-10-03T18:30:00Z"
+}

package/rcf/code-nodes/cn-770.json

@@ -0,0 +1,18 @@
+{
+  "cnId": "CN-770",
+  "path": "src/query/refuse-on-admissibility.js",
+  "title": "DEFINE step 3 PR 8: NV-DL admissibility wrap recognises freeze.override as recordedInChain",
+  "description": "src/query/refuse-on-admissibility.js grows a thin helper `evaluateDefineAdmissibility({ tree, projectRoot })` that checks the freeze record and the delta for the NV-DL rules: without a freeze record and without `freeze.override` it returns a refusal citing NV-DL-ADM-01; when `freeze.override` is set it returns ok and names the override on the result. The existing enforceAdmissibility path over NV-BL rows is unchanged. readiness and other query-tool callers that pass through runWithAdmissibilityGate see the NV-DL refusal; the compute still runs (ADR-4123) when the refusal is informational.",
+  "implementsAcIds": [
+    "AC-17902-2",
+    "AC-17902-3",
+    "AC-17902-4"
+  ],
+  "dependencies": [
+    "CN-769"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-03T18:30:00Z",
+  "updatedAt": "2026-10-03T18:30:00Z"
+}

package/rcf/fbs/fbs-196.json

@@ -1,6 +1,6 @@
 {
   "createdAt": "2026-09-24T14:30:00Z",
-  "updatedAt": "2026-09-24T14:30:00Z",
+  "updatedAt": "2026-10-01T13:12:16Z",
   "acIds": [
     "AC-17401-1",
     "AC-17401-2",
@@ -9,7 +9,9 @@
     "AC-17401-5",
     "AC-17401-6",
     "AC-17401-7",
-    "AC-17401-8"
+    "AC-17401-8",
+    "AC-17401-9",
+    "AC-17401-10"
   ],
   "fbsId": "FBS-196",
   "prdId": "PRD-001",
@@ -18,11 +20,17 @@
   "executionStatus": "complete",
   "title": "DEFINE slice 2: stage gates D1..D8 pure check functions",
   "summary": "Ship src/query/gates.js exposing one check function per stage D1..D8 with the section 2.4 shape { stage, gate, state, checks[] }. Blocking stages (D1, D2, D4, D7, D8) enforce the floors listed in proposal section 3.2; warn-with-ack stages (D3, D5, D6) run only the cheap data-backed checks and are acknowledgeable via freeze.gates[<gate>] at the current tree hash. AC class parses off the bracketed prefix on AC description (decision 6); D4 per-class opt-outs read manifest.baselineAcOptOuts[] with baselineKey 'defineD4:failure' or 'defineD4:mustNot' per ADR-4122.",
-  "dependsOnFbsIds": ["FBS-195"],
+  "dependsOnFbsIds": [
+    "FBS-195"
+  ],
   "approach": "One file, eight exported functions plus the STAGE_ORDER, STAGE_GATES, STAGE_SHORT_NAMES and INTERFACE_KINDS constants. Every function follows the same shape: decide notApplicable per section 3.2; assemble a checks[] list of { name, ok, over, pass, total, failing }; fold to state, honouring the warn-with-ack acknowledgement window when the stage is D3/D5/D6. Ledger reads use the emptyLedger fallback so an absent ledger contributes no findings. AC class parsing is a static regex over the description string (leading '[failure]' / '[must-not]' / '[happy]' / '[edge]' / '[non-functional]', case-sensitive). Profile parsing is a light presence check on rcf/.identity/profile.md (surface and register markers).",
   "contextRequirements": {
-    "tacIds": ["TAC-4122-define-gates"],
-    "adrIds": ["ADR-4122-define-gates-blocking-and-optout"]
+    "tacIds": [
+      "TAC-4122-define-gates"
+    ],
+    "adrIds": [
+      "ADR-4122-define-gates-blocking-and-optout"
+    ]
   },
   "deliverables": [
     "src/query/gates.js: STAGE_ORDER, STAGE_GATES, STAGE_SHORT_NAMES, INTERFACE_KINDS, checkD1Brief..checkD8Freeze, plus foldState and parseAcClass helpers",

package/rcf/fbs/fbs-198.json

@@ -0,0 +1,42 @@
+{
+  "createdAt": "2026-09-24T16:33:15Z",
+  "updatedAt": "2026-09-24T16:33:15Z",
+  "acIds": [
+    "AC-17601-1",
+    "AC-17601-2",
+    "AC-17601-3",
+    "AC-17601-4",
+    "AC-17601-5",
+    "AC-17601-6",
+    "AC-17601-7",
+    "AC-17601-8"
+  ],
+  "fbsId": "FBS-198",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 198,
+  "executionStatus": "notStarted",
+  "title": "DEFINE slice 3: rcf define freeze CLI + freeze-record override + hygiene",
+  "summary": "Ship src/cli/freeze.js implementing 'rcf define freeze' as the only freeze-record writer, wire it into bin/rcf.js and src/cli/help.js, update src/define/freeze-record.js so override is a nullable-required field (loader defaults missing keys to null; validator refuses a body without the key), and replace the ' -- ' double-dash in the readiness CLI stage header and the CHANGELOG TODO-regex line with a colon.",
+  "dependsOnFbsIds": ["FBS-197"],
+  "approach": "One CLI module composing computeReadiness (REQ-175) and saveFreezeRecord (REQ-172). Ack parsing is a small helper walking --ack and --reason multi-valued arrays in parallel. Ack folding uses the same WARN_WITH_ACK rules gates.js applies at the current tree hash. Counts derivation reuses tree.kindById and parseAcClass; interface counts walk each TAC's interfaces[]. Version reading loads packages/rcf-lite/package.json, src/ruleset/ruleset.json and node_modules/@stravica-ai/rcf-schemas/package.json. --status is a read-only branch that never runs gates. Admissibility refusal is informational per ADR-4124. The freeze-record schema fix requires an override field (nullable): validator throws on missing key, loader defaults missing keys to null on read for backward compatibility, saveFreezeRecord's own validate step catches a caller that forgets to write override.",
+  "contextRequirements": {
+    "tacIds": ["TAC-4124-define-freeze"],
+    "adrIds": ["ADR-4124-define-freeze-verb"]
+  },
+  "deliverables": [
+    "src/cli/freeze.js: HELP, main; --ack (multiple) / --reason (multiple) / --note / --litmus-attested / --status / --json / --help flags; runWithAdmissibilityGate wrap; section 2.5 summary line and --json envelope; counts derivation",
+    "src/define/freeze-record.js: validateFreezeRecord requires override (nullable); loadFreezeRecord defaults missing override to null; saveFreezeRecord unchanged (still validates first, which now catches missing override)",
+    "src/cli/readiness.js: stage header line uses ': ' between stage / gate / state (no ' -- ')",
+    "CHANGELOG.md: TODO regex line rewritten to use ': ' instead of ' -- ', plus slice-3 entries under [Unreleased]",
+    "bin/rcf.js: GROUPS.define.freeze wired to freezeMain",
+    "src/cli/help.js: HELP as FREEZE_HELP imported; HELP_MAP.define.freeze wired; DEFINE_HELP listing extended",
+    "test/cli/freeze.test.js: CLI tests covering AC-17601-1..6 and AC-17601-8",
+    "test/define/freeze-record.test.js: extension test covering AC-17601-7 (override required, loader defaults)"
+  ],
+  "riskLevel": "low",
+  "domain": "defineDetection",
+  "estimatedSize": "medium",
+  "estimatedHours": 4,
+  "notes": "Depth-2 slice: no sub-agents. Chain first, code next, tests last. Dogfood is NOT frozen in the repo (a committed freeze.json would be a product decision); prove the verb on scratch trees and run --status on the dogfood chain as evidence."
+}

package/rcf/fbs/fbs-199.json

@@ -0,0 +1,59 @@
+{
+  "createdAt": "2026-10-01T14:30:00Z",
+  "updatedAt": "2026-10-01T14:30:00Z",
+  "acIds": [
+    "AC-17402-1",
+    "AC-17402-2",
+    "AC-17402-3",
+    "AC-17402-4",
+    "AC-17402-5",
+    "AC-17402-6",
+    "AC-17402-7",
+    "AC-17403-1",
+    "AC-17403-2",
+    "AC-17403-3",
+    "AC-17403-4",
+    "AC-17403-5",
+    "AC-17403-6",
+    "AC-17403-7",
+    "AC-17403-8",
+    "AC-17502-1",
+    "AC-17502-2",
+    "AC-17502-3",
+    "AC-17502-4",
+    "AC-17502-5",
+    "AC-17502-6",
+    "AC-17502-7",
+    "AC-17502-8"
+  ],
+  "fbsId": "FBS-199",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 199,
+  "executionStatus": "complete",
+  "title": "DEFINE step 2 (0.29.0) PR A: persona tags on every gate check and two readiness levels (ADR-4126)",
+  "summary": "Ship the compute layer for ADR-4126: CHECK_PERSONA / CHECK_QUESTION maps and persona + question on every stages[].checks[] entry; split skeleton:reqFields into skeleton:reqIntent + skeleton:reqShape and decisions:allAnswered into decisions:wellFormed + decisions:allAnswered; add the new D3 shapes:draftSettled check and the parseInterfaceDraft helper; fold levels (intentComplete, readyToBuild) and personas (productOwner, engineer) on the computeReadiness result; extend deriveNextAction with an optional persona filter; add formatVerdictLines shared by the CLI (PR B) and the Readiness tab (PR C). All additions are strictly additive; the 0.28.4 top-level shape is preserved and rcf define readiness default behaviour / exit codes are unchanged.",
+  "dependsOnFbsIds": ["FBS-197"],
+  "approach": "One pass through src/query/gates.js adds the persona + question maps and plumbs them through makeCheck; the two splits are per-REQ / per-entry loops that evaluate every item independently so one failure never masks another; the shapes:draftSettled check parses the leading bracket marker on interface descriptions (whitespace tolerated). src/query/readiness.js folds levels + personas from stages[].checks[] after the eight stage functions run; deriveNextAction gains an optional persona argument; formatVerdictLines builds the two shared verdict strings. The CLI flags (--level, --persona) and the viewer tab land in PRs B and C of the same train and are out of scope here.",
+  "contextRequirements": {
+    "tacIds": [
+      "TAC-4122-define-gates",
+      "TAC-4123-define-readiness"
+    ],
+    "adrIds": [
+      "ADR-4126-persona-tagged-blockers-two-levels"
+    ]
+  },
+  "deliverables": [
+    "src/query/gates.js: CHECK_PERSONA + CHECK_QUESTION + STAGE_FALLBACK_PERSONA maps; checkPersona / checkQuestion / parseInterfaceDraft helpers; split skeleton:reqIntent / skeleton:reqShape; new shapes:draftSettled; split decisions:wellFormed / decisions:allAnswered; makeCheck adds persona + question on every emitted check; D3 doc comment fix for TAD.dataArchitecture.coreEntities",
+    "src/query/readiness.js: levels (intentComplete, readyToBuild) and personas (productOwner, engineer) fold; deriveNextAction gains an optional persona argument; formatVerdictLines builds the two shared verdict strings",
+    "src/query/index.js: re-export the new helpers (CHECK_PERSONA / CHECK_QUESTION / STAGE_FALLBACK_PERSONA / parseInterfaceDraft / deriveLevels / derivePersonas / formatVerdictLines)",
+    "test/query/gates.test.js and test/query/readiness.test.js: new cases covering AC-17402-*, AC-17403-* and AC-17502-*",
+    "CHANGELOG [Unreleased] entry describing the additive compute changes"
+  ],
+  "riskLevel": "low",
+  "domain": "defineDetection",
+  "estimatedSize": "medium",
+  "estimatedHours": 4,
+  "notes": "PR B (CLI --level / --persona + text report) and PR C (Readiness viewer tab) are the remaining 0.29.0 step-2 PRs under REQ-175 / REQ-180 / REQ-181. No file under rcf/ is created or modified by any rcf define readiness invocation; the levels and personas folds are read-only derivations over stages[].checks[]."
+}