rcf-lite 0.29.0 → 0.30.0

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-202.json

@@ -1,6 +1,6 @@
 {
   "createdAt": "2026-10-02T16:40:00Z",
-  "updatedAt": "2026-10-03T00:00:00Z",
+  "updatedAt": "2026-10-03T20:30:00Z",
   "acIds": [
     "AC-17302-1",
     "AC-17302-2",
@@ -46,15 +46,55 @@
     "AC-18202-1",
     "AC-18202-2",
     "AC-18202-3",
-    "AC-18202-4"
+    "AC-18202-4",
+    "AC-17404-1",
+    "AC-17404-2",
+    "AC-17404-3",
+    "AC-17404-4",
+    "AC-17404-5",
+    "AC-17404-6",
+    "AC-17405-1",
+    "AC-17405-2",
+    "AC-17405-3",
+    "AC-17405-4",
+    "AC-17405-5",
+    "AC-17405-6",
+    "AC-17406-1",
+    "AC-17406-2",
+    "AC-17406-3",
+    "AC-17406-4",
+    "AC-17406-5",
+    "AC-17406-6",
+    "AC-17504-1",
+    "AC-17504-2",
+    "AC-17504-3",
+    "AC-17504-4",
+    "AC-17504-5",
+    "AC-17702-1",
+    "AC-17702-2",
+    "AC-17702-3",
+    "AC-17702-4",
+    "AC-17702-5",
+    "AC-17802-1",
+    "AC-17802-2",
+    "AC-17802-3",
+    "AC-17802-4",
+    "AC-17902-1",
+    "AC-17902-2",
+    "AC-17902-3",
+    "AC-17902-4",
+    "AC-17405-7",
+    "AC-17405-8",
+    "AC-17702-6",
+    "AC-17902-5"
   ],
   "fbsId": "FBS-202",
   "prdId": "PRD-001",
   "bsId": "BS-001",
   "buildOrder": 202,
   "executionStatus": "notStarted",
-  "title": "DEFINE step 3 PRs 1-3: intake markers, ledger update, resolvedBy grammar (PR 1); computeQuestions, questions verb and MCP tools (PR 2); draft-shape marker extension, DISCOVERY prototypes guidance and prompts (PR 3)",
-  "summary": "Carry the ACs for PRs 1, 2 and 3 of the DEFINE step 3 spec (2026-10-01). PR 1: statement-file markers in parseBriefFromFile ([kind] and (source: ...)), the brief add --scan / --no-scan / --findings / --dry-run / --json wiring, the new ledger <name> update <id> subverb, and the resolvedBy closed pointer grammar validated by D2 (title-hit fallback dropped). PR 2: computeQuestions pure compute over readiness per persona; `rcf define questions` verb; three MCP tools (rcf_define_questions, rcf_define_readiness, rcf_define_ledger); the define-intent guidance file and the rcf_define_intent + rcf_define_intake prompts; two new managed-block rules. PR 3: parseInterfaceDraft extended to TAC.purpose and coreEntities[].description, shapes:draftSettled reports all three id forms (<tacId>:<name>, <tacId>, TAD.entity:<name>); the two new argument-free prompts rcf_define_draft_shapes and rcf_discover_prototype plus guidance/discovery-prototypes.md (REQ-188 + REQ-182 amended, ADR-4132). Chain-first commits landed before the code in each PR. FBS stays notStarted until the CN axis mints Code Nodes against the ACs across the PRs. PR 1 tests ride TS-215; PR 2 tests ride TS-226; PR 3 tests ride TS-228 (renumbered from the cloud build's TS-227 after viewer PR 8 claimed TS-227 for US-18002).",
+  "title": "DEFINE step 3 PRs 1-3, PR 5, PR 6, PR 7 and PR 8: intake markers, ledger update, resolvedBy grammar (PR 1); computeQuestions, questions verb and MCP tools (PR 2); draft-shape marker extension, DISCOVERY prototypes guidance and prompts (PR 3); D3 bite checks, ackable, --check exit 4 policy (PR 5); D4 closed-set and ownerRef findings, D5 concern catalogue, standards citation (PR 6); D6 consistency scans, probe seam, --litmus and rcf_define_litmus (PR 7); bundle refuse/override/skip, validate findings and NV-DL enforced (PR 8)",
+  "summary": "Carry the ACs for PRs 1, 2, 3, 5 and 6 of the DEFINE step 3 spec (2026-10-01). PR 1: statement-file markers in parseBriefFromFile ([kind] and (source: ...)), the brief add --scan / --no-scan / --findings / --dry-run / --json wiring, the new ledger <name> update <id> subverb, and the resolvedBy closed pointer grammar validated by D2 (title-hit fallback dropped). PR 2: computeQuestions pure compute over readiness per persona; `rcf define questions` verb; three MCP tools (rcf_define_questions, rcf_define_readiness, rcf_define_ledger); the define-intent guidance file and the rcf_define_intent + rcf_define_intake prompts; two new managed-block rules. PR 3: parseInterfaceDraft extended to TAC.purpose and coreEntities[].description, shapes:draftSettled reports all three id forms (<tacId>:<name>, <tacId>, TAD.entity:<name>); the two new argument-free prompts rcf_define_draft_shapes and rcf_discover_prototype plus guidance/discovery-prototypes.md (REQ-188 + REQ-182 amended, ADR-4132). PR 5: the three D3 bite checks shapes:templateMarkers, shapes:entityJoin and shapes:pathsResolve on src/query/gates.js (parseInterfaceTemplate exported for validate); ackable(stage) companion to stagePolicy returning true for D3, D5, D6; readiness CLI --check shapes exits 4 on an unacknowledged D3 failure and 0 when acked at the current hash; cli-readiness.js resolves candidate paths on disk and passes resolvedPaths in the stage context so gates stay pure (REQ-174 amended, US-17404, TAC-4122 and TAC-4123 amended, ADR-4131). Chain-first commits landed before the code in each PR. FBS stays notStarted until the CN axis mints Code Nodes against the ACs across the PRs. PR 1 tests ride TS-215; PR 2 tests ride TS-226; PR 3 tests ride TS-228 (renumbered from the cloud build's TS-227 after viewer PR 8 claimed TS-227 for US-18002); PR 5 tests ride TS-230 (next free when expecting the viewer PR 9 to land TS-229; brief predicted TS-230). PR 6 tests ride TS-231 and anchor CN-756, CN-757 and CN-758.",
   "dependsOnFbsIds": [
     "FBS-195",
     "FBS-201"
@@ -66,12 +106,14 @@
       "TAC-4130-define-intake-brief",
       "TAC-4129-define-questions",
       "TAC-4128-define-guidance",
-      "TAC-4122-define-gates"
+      "TAC-4122-define-gates",
+      "TAC-4123-define-readiness"
     ],
     "adrIds": [
       "ADR-4129-questions-harness-driven-loop",
       "ADR-4130-intake-harness-split-tool-scanned",
-      "ADR-4132-prototypes-in-discovery-as-evidence"
+      "ADR-4132-prototypes-in-discovery-as-evidence",
+      "ADR-4131-gates-bite-ack-recorded-override"
     ]
   },
   "deliverables": [
@@ -100,11 +142,29 @@
     "src/query/gates.js: parseInterfaceDraft extended to TAC.purpose and coreEntities[].description; checkD3Shapes shapes:draftSettled enumerates all three homes (PR 3)",
     "guidance/define-draft-shapes.md, guidance/discover-prototype.md, guidance/discovery-prototypes.md and guidance/manifest.json entries for the two prompts and the two slugs (PR 3)",
     "guidance/managed/agent-instructions-block.md: the prototype rule from ADR-4132 (PR 3)",
-    "test/query/gates.test.js: extended for the three draft homes; test/guidance/manifest.test.js and test/guidance/register-scan.test.js: new slugs and five prompts, em-dash scan (PR 3)"
+    "test/query/gates.test.js: extended for the three draft homes; test/guidance/manifest.test.js and test/guidance/register-scan.test.js: new slugs and five prompts, em-dash scan (PR 3)",
+    "rcf/requirements/req-174.json (amended), rcf/user-stories/us-17404.json, rcf/tacs/tac-4122-define-gates.json (amended with the three D3 bite responsibilities, parseInterfaceTemplate and ackable interfaces), rcf/tacs/tac-4123-define-readiness.json (amended with the resolvedPaths context seam and the --check shapes exit 4 policy), rcf/adrs/adr-4131-gates-bite-ack-recorded-override.json, rcf/test-suites/ts-230.json (PR 5 chain)",
+    "src/query/gates.js: parseInterfaceTemplate(iface) exported; shapes:templateMarkers, shapes:entityJoin, shapes:pathsResolve added to checkD3Shapes; ackable(stage) exported (PR 5)",
+    "src/query/readiness.js: resolvedPaths threaded through the stage context when the caller supplies it (PR 5)",
+    "src/cli/readiness.js: resolve candidate paths on disk before computeReadiness and pass resolvedPaths in; --check shapes exits 4 on an unacknowledged D3 failure and 0 when acked at the current hash (PR 5)",
+    "test/query/gates.test.js: AC-17404-1..4 D3 bite cases; test/cli/readiness.test.js: AC-17404-5 exit 4/0 cases; test/cli/freeze.test.js: AC-17404-6 --ack-on-D1/D2/D4/D7/D8 exit 2 case (PR 5)",
+    "rcf/user-stories/us-17405.json, rcf/tacs/tac-4121-define-ledgers.json (amended with the concern-ledger applied/waived responsibility), rcf/tacs/tac-4122-define-gates.json (amended with the four new PR 6 responsibilities and the applicableConcernsFor interface), rcf/test-suites/ts-231.json, rcf/code-nodes/cn-756.json, cn-757.json, cn-758.json (PR 6 chain)",
+    "src/define/concern-catalogue.js: CONCERN_KEYS, CONCERN_APPLICABILITY and applicableConcernsFor exported (PR 6)",
+    "src/query/gates.js: stories:closedSets, stories:ownerRefResolves, crosscut:catalogue, skeleton:standardsCited; CHECK_PERSONA / CHECK_QUESTION extended (PR 6)",
+    "src/cli/readiness.js: --check crosscut and --check D5 ride the same --ack fold as D3 (PR 6)",
+    "test/query/gates.test.js, test/define/concern-catalogue.test.js, test/cli/readiness.test.js, test/cli/validate.test.js, test/query/questions-loop.test.js: PR 6 cases for AC-17405-1..6 and the loop-convergence row (PR 6)",
+    "rcf/requirements/req-175.json (amended with the probeRunner + --litmus paragraph), rcf/user-stories/us-17406.json (D6 bites), rcf/user-stories/us-17504.json (probe seam and litmus), rcf/tacs/tac-4122-define-gates.json (amended with the four D6 scan responsibilities), rcf/tacs/tac-4123-define-readiness.json (amended with the probeRunner, --litmus and D6 biting-stage responsibilities and four moduleApi interfaces), rcf/tacs/tac-4128-define-guidance.json (amended with the rcf_define_litmus responsibility and interface), rcf/test-suites/ts-232.json, rcf/code-nodes/cn-759.json..cn-764.json (PR 7 chain)",
+    "src/query/gates.js: consistency:contradictions, consistency:unsatisfiable, consistency:duplicates, consistency:orphanInterfaces added to checkD6Consistency; CHECK_PERSONA / CHECK_QUESTION extended (PR 7)",
+    "src/query/readiness.js: probeRunner seam merged into ledgers.probes.probes[]; parseLitmusFlag and countLitmusReadersAtHash exported (PR 7)",
+    "src/define/probe-runner.js: new seam-only module (ProbeRunner typedef, NO_PROBE_RUNNER, isProbeRunner); no shipped runner (PR 7)",
+    "src/cli/readiness.js: --litmus <n> flag with usage; D6 joins the BITING_STAGES set; --help carries the new flag (PR 7)",
+    "src/cli/freeze.js: --litmus <n> flag with usage; refuses (exit 4) and writes nothing on a shortfall (PR 7)",
+    "guidance/define-litmus.md and guidance/manifest.json entry for rcf_define_litmus (PR 7)",
+    "test/query/gates.test.js: AC-17406-1..6 D6 bite cases; test/query/readiness.test.js: AC-17504-1/2/5 probe-seam and litmus unit cases; test/cli/readiness.test.js: AC-17504-3/4 --litmus exit cases (PR 7)"
   ],
   "riskLevel": "low",
   "domain": "defineLedgers",
   "estimatedSize": "medium",
   "estimatedHours": 4,
-  "notes": "FBS-202 was reserved as 'next free' in the dispatch brief and allocated here to keep the dogfood no-orphan-AC invariant. executionStatus is 'notStarted' so the CN axis stays legitimately deferred for this PR (test additions ride existing test suites, no new CN per brief). Later DEFINE PRs promote this FBS to inProgress / complete as their deliveries land."
-}
+  "notes": "FBS-202 was reserved as 'next free' in the dispatch brief and allocated here to keep the dogfood no-orphan-AC invariant. executionStatus is 'notStarted' so the CN axis stays legitimately deferred for this PR (test additions ride existing test suites). PR 6 anchors three new CNs (CN-756, CN-757, CN-758) against src/define/concern-catalogue.js, src/query/gates.js and src/cli/readiness.js. Later DEFINE PRs promote this FBS to inProgress / complete as their deliveries land."
+}

package/rcf/requirements/req-174.json

@@ -1,10 +1,10 @@
 {
   "createdAt": "2026-09-24T14:30:00Z",
-  "updatedAt": "2026-10-01T14:13:27Z",
+  "updatedAt": "2026-10-03T10:50:00Z",
   "reqId": "REQ-174",
   "prdId": "PRD-001",
   "title": "DEFINE stage gates D1..D8 as pure check functions",
-  "description": "rcf-lite gains src/query/gates.js with one check function per stage D1..D8. Each function takes (tree, ledgers, profile, scope) and returns { stage, gate, state, checks[] } where every check is { name, ok, over: 'delta'|'tree', pass, total, failing: [{ id, why }] }. Stage state is 'passed' | 'failing' | 'acknowledged' (only for D3, D5, D6 and only when the freeze record acknowledges that gate at the current hash) | 'notApplicable' (the stage decides that itself from the scope per the proposal 2026-09-22 v3 section 3.2 rules and the summary table in section 2.7). Blocking in 0.29.0: D1 brief, D2 skeleton, D4 floors (every REQ in scope has a US; every US in scope has a testable AC, a failure AC and a must-not AC, or a reasoned opt-out per class; tacIds non-empty and resolving; no scaffold placeholder), D7 decisions, D8 freeze (prior gates passed or acknowledged at the current hash, every AC owned by exactly one FBS, queue head actionable and not a placeholder, validate clean; preflight and ui-baseline presence as the section 3.2 rules specify). Warn-with-ack in 0.29.0: D3, D5, D6 build only the cheap data-backed checks (D3: every TAC in scope has at least one interface and each interface kind is in the closed vocabulary of section 5.2; D5: TAD securityArchitecture present when any auth or httpApi REQ exists, operationalConcerns present when deployed-scope ACs exist, concern-ledger entries applied or waived where they exist; D6: validate clean tree-wide plus open probe-ledger count). The D3 template parser, entity join, D5 catalogue, D6 contradiction and unsatisfiable scans, and the probe runner are 0.30 and left as named seams. AC class is a bracketed prefix on AC description ('[failure] ...', '[must-not] ...', '[happy]', '[edge]', '[non-functional]', decision 6); opt-out per class reuses the existing manifest.baselineAcOptOuts[] array with a baselineKey of the shape 'defineD4:failure' or 'defineD4:mustNot' (recorded in ADR-4122). No storage state, no 'stale' state. ADR-4126 (0.29.0) amendment: every gate check declares an owning persona, `productOwner` or `engineer`, and a one-sentence `question` in that persona’s register. A check that would need both personas is split so every check is homogeneous: `skeleton:reqFields` becomes `skeleton:reqIntent` (productOwner: description + domain) + `skeleton:reqShape` (engineer: shapeClassification.shapes); `decisions:allAnswered` becomes `decisions:wellFormed` (productOwner: enumerated per #241 format) + `decisions:allAnswered` (engineer: zero open). A new D3 check `shapes:draftSettled` fails every interface whose description still carries the leading `[draft]` marker so an L1-pre-populated interface stays distinguishable from one the engineer has settled.",
+  "description": "rcf-lite gains src/query/gates.js with one check function per stage D1..D8. Each function takes (tree, ledgers, profile, scope) and returns { stage, gate, state, checks[] } where every check is { name, ok, over: 'delta'|'tree', pass, total, failing: [{ id, why }] }. Stage state is 'passed' | 'failing' | 'acknowledged' (only for D3, D5, D6 and only when the freeze record acknowledges that gate at the current hash) | 'notApplicable' (the stage decides that itself from the scope per the proposal 2026-09-22 v3 section 3.2 rules and the summary table in section 2.7). Blocking in 0.29.0: D1 brief, D2 skeleton, D4 floors (every REQ in scope has a US; every US in scope has a testable AC, a failure AC and a must-not AC, or a reasoned opt-out per class; tacIds non-empty and resolving; no scaffold placeholder), D7 decisions, D8 freeze (prior gates passed or acknowledged at the current hash, every AC owned by exactly one FBS, queue head actionable and not a placeholder, validate clean; preflight and ui-baseline presence as the section 3.2 rules specify). Warn-with-ack in 0.29.0: D3, D5, D6 build only the cheap data-backed checks (D3: every TAC in scope has at least one interface and each interface kind is in the closed vocabulary of section 5.2; D5: TAD securityArchitecture present when any auth or httpApi REQ exists, operationalConcerns present when deployed-scope ACs exist, concern-ledger entries applied or waived where they exist; D6: validate clean tree-wide plus open probe-ledger count). The D3 template parser, entity join, D5 catalogue, D6 contradiction and unsatisfiable scans, and the probe runner are 0.30 and left as named seams. AC class is a bracketed prefix on AC description ('[failure] ...', '[must-not] ...', '[happy]', '[edge]', '[non-functional]', decision 6); opt-out per class reuses the existing manifest.baselineAcOptOuts[] array with a baselineKey of the shape 'defineD4:failure' or 'defineD4:mustNot' (recorded in ADR-4122). No storage state, no 'stale' state. ADR-4126 (0.29.0) amendment: every gate check declares an owning persona, `productOwner` or `engineer`, and a one-sentence `question` in that persona’s register. A check that would need both personas is split so every check is homogeneous: `skeleton:reqFields` becomes `skeleton:reqIntent` (productOwner: description + domain) + `skeleton:reqShape` (engineer: shapeClassification.shapes); `decisions:allAnswered` becomes `decisions:wellFormed` (productOwner: enumerated per #241 format) + `decisions:allAnswered` (engineer: zero open). A new D3 check `shapes:draftSettled` fails every interface whose description still carries the leading `[draft]` marker so an L1-pre-populated interface stays distinguishable from one the engineer has settled. 0.30.0 PR 5 (ADR-4131) amendment: D3, D5 and D6 run the substantive checks of proposal 3.2 and exit 4 under `--check`; `--ack` remains their recorded override. D4 reports closed sets and `ownerRef` resolution as findings. D2 validates `resolvedBy` pointers and the standards citation. The three D3 bite checks land in this PR: `shapes:templateMarkers` (per-kind marker presence on `interfaces[].description`, over delta, ids `<tacId>:<name>`, why names the missing marker, drafts included), `shapes:entityJoin` (every `coreEntities[].name` named by exactly one `recordShape` tree-wide, ids `TAD.entity:<name>` with 'no record shape' or 'N record shapes'), `shapes:pathsResolve` (any `path:`-like token in an interface description resolves against `resolvedPaths` in the stage context or the description carries `authoredAt: D3`, over delta). The CLI readiness `--check shapes` exits 4 on an unacknowledged D3 failure and 0 when acked at the current hash; `ackable(stage)` returns true for D3, D5, D6 and false for D1, D2, D4, D7, D8; `--ack` on D1, D2, D4, D7 or D8 exits 2 unchanged.",
   "category": "functional",
   "domain": "defineDetection",
   "priority": "must",

package/rcf/requirements/req-175.json

@@ -1,10 +1,10 @@
 {
   "createdAt": "2026-09-24T14:30:00Z",
-  "updatedAt": "2026-10-01T14:13:27Z",
+  "updatedAt": "2026-10-03T16:10:00Z",
   "reqId": "REQ-175",
   "prdId": "PRD-001",
   "title": "computeReadiness and the rcf define readiness CLI verb",
-  "description": "rcf-lite gains src/query/readiness.js with computeReadiness(tree, { freeze, ledgers, profile, testPointers }) returning the exact section 2.4 shape { tree, delta, stages, nextAction, coverage, decisions, freezeable }. computeReadiness composes computeDelta (slice 1), calls computeImpact once per id in changed union added (the union is the fan-out; impacted names every id, impactedFbs names the re-execute subset), runs the gates D1..D8 over scope = changed union added union impacted ids, calls computeCoverage tree-wide plus per REQ ancestor of the delta (using the testPointers map the CLI produces exactly as src/cli/coverage.js builds it), lists open decisions (in the #241 numbered format from the decisions ledger), derives a nextAction { stage, check, ids, command } from the first failing gate, and reports freezeable when every stage state is passed, acknowledged or notApplicable. rcf-lite also gains src/cli/readiness.js implementing rcf define readiness [--json] [--check <stage>|all] (stage accepts D1..D8 or the gate short name: brief, skeleton, shapes, stories, crosscut, consistency, decisions, freeze). Text output: tree line, next action, stage chips, delta list, failing items. --check exits 0 green, 4 red (matching coverage refusal exit); warn-with-ack stages failing but unacknowledged exit 0 with a visible warning. The producer is wrapped with runWithAdmissibilityGate as the ruleset toolScope requires. loadAllLedgers (src/define/ledgers.js) is corrected so a project that never authored a ledger does not get ledger:<name> hashes in the docHashes map (slice-1 P3 resolution: code and JSDoc agree that absent ledger files contribute no docHash). ADR-4126 (0.29.0) amendment: the readiness object carries two computed levels on the one ladder. `levels.intentComplete.ok` is true when every `productOwner` check is ok across every stage (stage state ignored); `levels.readyToBuild.ok` equals `freezeable`. Neither is recorded. `personas.productOwner.blockers` deep-equals `levels.intentComplete.blockedBy`; `personas.engineer.blockers` is the failing engineer checks in failing stages. `deriveNextAction(stages, persona?)` gains an optional persona filter; the productOwner next-action command carries `--level intent`. `formatVerdictLines(result)` builds the two verdict strings the CLI (PR B) and the Readiness tab (PR C) share so they cannot disagree.",
+  "description": "rcf-lite gains src/query/readiness.js with computeReadiness(tree, { freeze, ledgers, profile, testPointers }) returning the exact section 2.4 shape { tree, delta, stages, nextAction, coverage, decisions, freezeable }. computeReadiness composes computeDelta (slice 1), calls computeImpact once per id in changed union added (the union is the fan-out; impacted names every id, impactedFbs names the re-execute subset), runs the gates D1..D8 over scope = changed union added union impacted ids, calls computeCoverage tree-wide plus per REQ ancestor of the delta (using the testPointers map the CLI produces exactly as src/cli/coverage.js builds it), lists open decisions (in the #241 numbered format from the decisions ledger), derives a nextAction { stage, check, ids, command } from the first failing gate, and reports freezeable when every stage state is passed, acknowledged or notApplicable. rcf-lite also gains src/cli/readiness.js implementing rcf define readiness [--json] [--check <stage>|all] (stage accepts D1..D8 or the gate short name: brief, skeleton, shapes, stories, crosscut, consistency, decisions, freeze). Text output: tree line, next action, stage chips, delta list, failing items. --check exits 0 green, 4 red (matching coverage refusal exit); warn-with-ack stages failing but unacknowledged exit 0 with a visible warning. The producer is wrapped with runWithAdmissibilityGate as the ruleset toolScope requires. loadAllLedgers (src/define/ledgers.js) is corrected so a project that never authored a ledger does not get ledger:<name> hashes in the docHashes map (slice-1 P3 resolution: code and JSDoc agree that absent ledger files contribute no docHash). ADR-4126 (0.29.0) amendment: the readiness object carries two computed levels on the one ladder. `levels.intentComplete.ok` is true when every `productOwner` check is ok across every stage (stage state ignored); `levels.readyToBuild.ok` equals `freezeable`. Neither is recorded. `personas.productOwner.blockers` deep-equals `levels.intentComplete.blockedBy`; `personas.engineer.blockers` is the failing engineer checks in failing stages. `deriveNextAction(stages, persona?)` gains an optional persona filter; the productOwner next-action command carries `--level intent`. `formatVerdictLines(result)` builds the two verdict strings the CLI (PR B) and the Readiness tab (PR C) share so they cannot disagree. 0.30.0 PR 7 (ADR-4131 extended; spec section 11.6): the compute accepts an injectable `probeRunner`; `--litmus <n>` requires n distinct litmus readings at the current LITMUS HASH (`tree.litmusHash`, R9 amended 2026-10-03 under w-2026-10-03-dave-011). The litmus hash is the tree hash computed with the probes ledger excluded; the probes ledger is inside `tree.currentTreeHash` by ADR-4120, so without this amendment a reader writing a litmus probe entry would shift the hash it just attested to and the --litmus check could never match deterministically. computeLitmusHash lives in src/query/readiness.js and reuses hashDocument / computeTreeHash from delta.js; writes to the probes ledger do not shift it, writes to the brief, decisions or concerns ledgers do.",
   "category": "functional",
   "domain": "defineDetection",
   "priority": "must",

package/rcf/requirements/req-177.json

@@ -0,0 +1,31 @@
+{
+  "createdAt": "2026-10-03T18:30:00Z",
+  "updatedAt": "2026-10-03T18:30:00Z",
+  "reqId": "REQ-177",
+  "prdId": "PRD-001",
+  "title": "rcf build bundle --next refuses without a freeze and skips impacted FBS",
+  "description": "rcf-lite's build dispatcher (`src/cli/build.js` with freeze-record support in `src/define/freeze-record.js`) tightens `rcf build bundle --next` against the detection-model freeze record: without a freeze record the verb refuses, with `--override` it writes an override and proceeds, and on a non-empty delta it skips impacted FBS. 0.30.0 PR 8 (DEFINE step 3 spec section 4 bundle row, section 11.7 US-17702 appended paragraph): `rcf build bundle --next` refuses without a freeze record and exits 4; `--override \"<reason>\"` writes `freeze.override { reason, by, at }` and proceeds; impacted FBS are skipped with the reason and the next unimpacted FBS is handed out; every impacted and no override is a refusal.",
+  "category": "functional",
+  "domain": "defineDetection",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "persistence"
+    ],
+    "reason": "keyword-scan",
+    "classifiedAt": "2026-10-03T18:30:00Z",
+    "signals": [
+      {
+        "source": "description",
+        "shape": "persistence",
+        "match": "record"
+      }
+    ]
+  },
+  "rationale": "Spec section 4 pins the gates-bite surface for `rcf build bundle --next`: the detection-model freeze record is the one source of truth that a change is closed; an unfrozen tree is the one condition under which the next-item compute cannot be answered without an operator decision, so the verb refuses rather than guessing. The override channel keeps the verb usable under a hotfix with a recorded reason, by whom and when, satisfying NV-DL-ADM-01's `recordedInChain` and leaving an audit trail; the impacted-skip is the mechanical consequence of the delta model (an FBS whose ACs changed cannot be bundled from the pre-change tree without a re-freeze). The verb's 0.29.0 shape on a frozen tree with an empty delta is unchanged (AC-17702-5), so operators whose work does not touch an impacted FBS see no regression.",
+  "tags": [
+    "capability:define-detection"
+  ]
+}

package/rcf/requirements/req-178.json

@@ -0,0 +1,31 @@
+{
+  "createdAt": "2026-10-03T18:30:00Z",
+  "updatedAt": "2026-10-03T18:30:00Z",
+  "reqId": "REQ-178",
+  "prdId": "PRD-001",
+  "title": "rcf define validate reports findings for interface kind, AC class prefix, tacIds and ownerRef or deliveredBy",
+  "description": "`rcf define validate` (`src/cli/validate.js`) grows four new findings over the walker's existing schema and broken-reference pass: an interface kind outside the closed vocabulary (`INTERFACE_KINDS` in `src/query/gates.js`), a bracketed AC prefix on an AC `description` outside the known classes (`[happy]`, `[edge]`, `[failure]`, `[must-not]`, `[non-functional]`), a `tacIds` naming a non-TAC, and an unresolving `ownerRef` or `deliveredBy`. 0.30.0 PR 8 (DEFINE step 3 spec section 4 validate row, section 11.7 US-17802 appended paragraph): `rcf define validate` reports findings for an interface kind outside the vocabulary, a bracketed AC prefix outside the known classes, a `tacIds` naming a non-TAC, and an unresolving `ownerRef` or `deliveredBy`; absence of a class marker on an AC is NOT a validate finding (that is D4's floor). Each finding exits non-zero (3) alongside the existing schema/broken-reference exit path.",
+  "category": "functional",
+  "domain": "defineDetection",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "persistence"
+    ],
+    "reason": "keyword-scan",
+    "classifiedAt": "2026-10-03T18:30:00Z",
+    "signals": [
+      {
+        "source": "description",
+        "shape": "persistence",
+        "match": "record"
+      }
+    ]
+  },
+  "rationale": "Spec section 4 pins the validate row's bite: notices on the four categories named here become findings because every legacy and dogfood tree can comply (the vocabularies are closed and small; the resolutions are mechanical). Decision 10 keeps absence of an AC class marker off validate because the dogfood tree and every legacy tree would fail CI on day one: an absence is already D4's finding and D4 is where the ladder for an AC-shape surfaces the gap. Routing bracketed-prefix misuse through validate lets the engineer and the author see the same signal without needing to re-run readiness; the four kinds all share one implementation path (walker already loaded the tree, finding emission is additive).",
+  "tags": [
+    "capability:define-detection"
+  ]
+}

package/rcf/requirements/req-179.json

@@ -0,0 +1,31 @@
+{
+  "createdAt": "2026-10-03T18:30:00Z",
+  "updatedAt": "2026-10-03T21:01:32Z",
+  "reqId": "REQ-179",
+  "prdId": "PRD-001",
+  "title": "NV-DL-ADM-01..05 refuse by default with overrideChannel recordedInChain",
+  "description": "The rcf-lite ruleset (`packages/rcf-lite/src/ruleset/ruleset.json`) gains five admissibility rules in the NV-DL (DefineLite) 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). All five carry `refuseByDefault: true` and `overrideChannel: recordedInChain`. 0.30.0 PR 8 (DEFINE step 3 spec section 4 NV-DL row, section 11.7 US-17902 appended paragraph): NV-DL-ADM-01..05 flip to `refuseByDefault`; ADM-01 and ADM-05 are the bundle refusal and skip; ADM-02..04 are D4 and D3 findings surfaced through the admissibility wrap; `overrideChannel: recordedInChain` is satisfied by `freeze.override` or an `--ack` reason. The admissibility wrap (`src/query/refuse-on-admissibility.js` plus the admissibility enforcer the chain-admissibility layer reads) surfaces ADM-02..04 as D4 and D3 findings; ADM-01 and ADM-05 are the bundle refusal and skip. readiness compute still runs and prints under refusal (0.29.0 informational posture unchanged for the compute). PR 9 enforcement locus (REQ-179 extension, spec section 17; ruling R12 2026-10-03): NV-DL-ADM-02 (D4 stories floor failing) and NV-DL-ADM-03 (D3 shapes bite failing) are surfaced through the admissibility wrap (`src/query/refuse-on-admissibility.js`, `evaluateDefineStageAdmissibility`), cited in the wrap's refusal envelope with their rule ids. For NV-DL-ADM-03 (D3 is ackable per decision 9) an `--ack <gate>=<reason>` recorded on freeze.gates at the current tree hash satisfies the recordedInChain override channel. For NV-DL-ADM-02 (D4 is NOT ackable; decision 9 keeps ackable to D3/D5/D6) the only recordedInChain override channel is `freeze.override` written by `rcf build bundle --next --override \"<reason>\"`; the normal path is to fix the failing D4 findings. NV-DL-ADM-04 (`rcf define validate` finding set) is surfaced through the wrap when callers pass `defineValidateErrors`; its override channel is a chain-document correction committed to git (per the ruleset note), not a gate ack. Readiness itself stays informational (AC-17902-4 unchanged); freeze keeps its own freezeableAfterAck gate.",
+  "category": "functional",
+  "domain": "defineDetection",
+  "priority": "must",
+  "version": "0.1.1",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "persistence"
+    ],
+    "reason": "keyword-scan",
+    "classifiedAt": "2026-10-03T18:30:00Z",
+    "signals": [
+      {
+        "source": "description",
+        "shape": "persistence",
+        "match": "record"
+      }
+    ]
+  },
+  "rationale": "Spec section 4 pins the NV-DL row to the ratified pattern of ruling-sheet item 1: an admissibility rule refuses by default and the override is recorded in the chain. 0.29.0 shipped the DEFINE compute and the CLI in an informational posture while PRs 5 to 7 built the biting checks; PR 8 flips the ruleset so the gate matches the checks' intent. The two override channels are the already-shipped `freeze.override` object (bundle --override) and the already-shipped `--ack` reasons recorded in freeze.gates (readiness / freeze), both of which land in the chain as part of the freeze record. Keeping readiness compute unchanged under refusal (AC-17902-4) matches ADR-4123 (refusal is informational on the compute; the gate surfaces it).",
+  "tags": [
+    "capability:define-detection"
+  ]
+}

package/rcf/tacs/tac-001.json

@@ -17,18 +17,18 @@
   "interfaces": [
     {
       "name": "loadDocument",
-      "kind": "function",
-      "description": "Resolve an id to a path, parse and validate, return the document or a structured error."
+      "kind": "other",
+      "description": "Resolve an id to a path, parse and validate, return the document or a structured error. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "saveDocument",
-      "kind": "function",
-      "description": "Validate then persist a document; refuse to write if validation fails."
+      "kind": "other",
+      "description": "Validate then persist a document; refuse to write if validation fails. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "walkTree",
-      "kind": "function",
-      "description": "From the manifest roots, resolve every child by id and return the full tree."
+      "kind": "other",
+      "description": "From the manifest roots, resolve every child by id and return the full tree. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     }
   ],
   "dependencies": [
@@ -41,5 +41,5 @@
   "tradeoffs": "Centralising all filesystem access in one component costs a small amount of indirection but guarantees that no consumer can write an unvalidated document or bypass the source-of-truth rule.",
   "notes": "The store is intentionally synchronous where possible; a local CLI does not benefit from streaming and synchronous code is easier for contributors to follow.",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-10-03T18:30:00Z"
 }

package/rcf/tacs/tac-002.json

@@ -16,58 +16,58 @@
   "interfaces": [
     {
       "name": "init",
-      "kind": "command",
-      "description": "Initialise a new RCF project on disk."
+      "kind": "cliCommand",
+      "description": "Initialise a new RCF project on disk. [legacy kind: command; mapped to cliCommand per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "view",
-      "kind": "command",
-      "description": "Generate the diagram and the static page."
+      "kind": "cliCommand",
+      "description": "Generate the diagram and the static page. [legacy kind: command; mapped to cliCommand per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "read",
-      "kind": "command",
-      "description": "Read a document by id."
+      "kind": "cliCommand",
+      "description": "Read a document by id. [legacy kind: command; mapped to cliCommand per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "create",
-      "kind": "command",
-      "description": "Create a document with parent linkage."
+      "kind": "cliCommand",
+      "description": "Create a document with parent linkage. [legacy kind: command; mapped to cliCommand per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "update",
-      "kind": "command",
-      "description": "Update fields on a document."
+      "kind": "cliCommand",
+      "description": "Update fields on a document. [legacy kind: command; mapped to cliCommand per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "delete",
-      "kind": "command",
-      "description": "Delete a document with reference safety."
+      "kind": "cliCommand",
+      "description": "Delete a document with reference safety. [legacy kind: command; mapped to cliCommand per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "coverage",
-      "kind": "command",
-      "description": "Report coverage gaps across the tree."
+      "kind": "cliCommand",
+      "description": "Report coverage gaps across the tree. [legacy kind: command; mapped to cliCommand per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "trace",
-      "kind": "command",
-      "description": "Trace forward or back along the intent chain."
+      "kind": "cliCommand",
+      "description": "Trace forward or back along the intent chain. [legacy kind: command; mapped to cliCommand per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "impact",
-      "kind": "command",
-      "description": "Report what is affected by a document change."
+      "kind": "cliCommand",
+      "description": "Report what is affected by a document change. [legacy kind: command; mapped to cliCommand per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "build",
-      "kind": "command",
-      "description": "Assemble a build prompt or mark a slice done."
+      "kind": "cliCommand",
+      "description": "Assemble a build prompt or mark a slice done. [legacy kind: command; mapped to cliCommand per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "validate",
-      "kind": "command",
-      "description": "Validate every document and list broken references."
+      "kind": "cliCommand",
+      "description": "Validate every document and list broken references. [legacy kind: command; mapped to cliCommand per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     }
   ],
   "dependencies": [
@@ -105,5 +105,5 @@
   "tradeoffs": "A single binary keeps the install and discovery story simple; a fragmented set of binaries would be more orthogonal but is overkill for a single project.",
   "notes": "Verbs are kept close to the spoken vocabulary of the method so a non-coder can guess the command from the document type.",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-10-03T18:30:00Z"
 }

package/rcf/tacs/tac-003.json

@@ -16,13 +16,13 @@
   "interfaces": [
     {
       "name": "renderDiagram",
-      "kind": "function",
-      "description": "Emit the diagram source for the whole tree."
+      "kind": "other",
+      "description": "Emit the diagram source for the whole tree. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "renderPage",
-      "kind": "function",
-      "description": "Write the static browsable page to the view output directory."
+      "kind": "other",
+      "description": "Write the static browsable page to the view output directory. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     }
   ],
   "dependencies": [
@@ -36,5 +36,5 @@
   "tradeoffs": "Mermaid is locked as the diagram format because it renders without a runtime and ships everywhere; a pluggable renderer would add an interface for a benefit the product does not yet need.",
   "notes": "The fixed output directory keeps the configuration surface zero and the output discoverable.",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-10-03T18:30:00Z"
 }

package/rcf/tacs/tac-004.json

@@ -17,23 +17,23 @@
   "interfaces": [
     {
       "name": "coverage",
-      "kind": "function",
-      "description": "Report coverage gaps across the tree."
+      "kind": "other",
+      "description": "Report coverage gaps across the tree. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "traceForward",
-      "kind": "function",
-      "description": "Trace from a document to its descendants along the intent chain."
+      "kind": "other",
+      "description": "Trace from a document to its descendants along the intent chain. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "traceBack",
-      "kind": "function",
-      "description": "Trace from a document back to its ancestors along the intent chain."
+      "kind": "other",
+      "description": "Trace from a document back to its ancestors along the intent chain. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "impact",
-      "kind": "function",
-      "description": "Compute the impact set of a change to a given document."
+      "kind": "other",
+      "description": "Compute the impact set of a change to a given document. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     }
   ],
   "dependencies": [
@@ -47,5 +47,5 @@
   "tradeoffs": "A general graph engine would be more expressive but the intent chain is small and a hand-rolled walker is easier to reason about and to keep correct.",
   "notes": "Keeping the FBS out of intent traces is a load-bearing design rule, not an optimisation.",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-10-03T18:30:00Z"
 }

package/rcf/tacs/tac-005.json

@@ -17,18 +17,18 @@
   "interfaces": [
     {
       "name": "assemblePrompt",
-      "kind": "function",
-      "description": "Assemble the implementation prompt for a named FBS."
+      "kind": "other",
+      "description": "Assemble the implementation prompt for a named FBS. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "buildOrder",
-      "kind": "function",
-      "description": "Compute the dependency-respecting order and parallel-safe groups."
+      "kind": "other",
+      "description": "Compute the dependency-respecting order and parallel-safe groups. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "markDone",
-      "kind": "function",
-      "description": "Advance the FBS and slot status when a slice is finished."
+      "kind": "other",
+      "description": "Advance the FBS and slot status when a slice is finished. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     }
   ],
   "dependencies": [
@@ -48,5 +48,5 @@
   "tradeoffs": "The prompt is assembled as a single markdown document for simplicity and portability; a richer structured payload would be more flexible but would lock the consumer to a non-portable shape.",
   "notes": "Mark-done is an explicit command so the tool stays offline and harness-agnostic; no PR-watching daemon is required.",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-10-03T18:30:00Z"
 }