rcf-lite 0.28.4 → 0.30.0

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/requirements/req-180.json

@@ -0,0 +1,31 @@
+{
+  "createdAt": "2026-10-01T18:00:00Z",
+  "updatedAt": "2026-10-02T19:30:00Z",
+  "reqId": "REQ-180",
+  "prdId": "PRD-001",
+  "title": "Readiness tab as tab 1 and the Overview-to-PRD rename",
+  "description": "src/view/readiness.js lands and html-page.js wires it as the first tab. The former Overview tab becomes PRD (same panel content; the rename is label-only). The Readiness panel renders the computeReadiness object top-to-bottom in the layout the DEFINE step 2 spec section 5 pins: tree line (formatTreeLine), two verdict pills with formatVerdictLines strings as the labels and blockedBy.length as the count, two per-persona next-action lines anchored into the stage detail, D1..D8 state chips with reason/acknowledgement text on hover, blockers grouped by persona (profile register orders the pair; the non-register group collapses with its count visible, never omitted), delta list grouped by REQ ancestor with a document-level diff on changed items (criterion-level diff deferred to the UX review per ADR-4127), per-stage check detail with persona pill and findings list when not ok, coverage tree-versus-delta with re-verify and re-execute counts, decisions outstanding in the #241 numbered format, a Freeze now control enabled iff levels.readyToBuild.ok (showing the `rcf define freeze` command and what it will record; disabled it names the failing gates from levels.readyToBuild.blockedBy; no intent-complete button), and the loaded freeze record (hash, when, note, counts, acknowledged gates with reasons). The view is pure: it never recomputes readiness, so the tab and `rcf define readiness --json` cannot disagree on the same tree hash. question cards grouped by source span rendering the questions object, per the viewer UI refresh design section 8.",
+  "category": "functional",
+  "domain": "defineDetection",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "webUi"
+    ],
+    "reason": "keyword-scan",
+    "classifiedAt": "2026-10-01T18:00:00Z",
+    "signals": [
+      {
+        "source": "description",
+        "shape": "webUi",
+        "match": "tab"
+      }
+    ]
+  },
+  "rationale": "Baz ruling 2026-09-22 (DEFINE step 2 spec section 2.4, decision 2): one object, two renderers. The CLI (REQ-175, PR B) and the tab (REQ-180, PR C) read the same computeReadiness result so they cannot disagree. Readiness is where an operator starts, so it must be tab 1. The Overview panel is just the PRD body today (phase 3.6 dropped the diagram) so the rename is honest; keeping the hash-anchor `#tab-overview` preserves every existing link into the surface. The L1 pre-population posture (ADR-4126) requires the tab to visibly distinguish [draft] shapes from settled ones, which the shapes:draftSettled check row makes legible.",
+  "tags": [
+    "capability:define-detection"
+  ]
+}

package/rcf/requirements/req-181.json

@@ -0,0 +1,31 @@
+{
+  "createdAt": "2026-10-01T18:00:00Z",
+  "updatedAt": "2026-10-01T18:00:00Z",
+  "reqId": "REQ-181",
+  "prdId": "PRD-001",
+  "title": "Shared pill, findings-list and diff view components",
+  "description": "src/view/components/{pill,findings-list,diff}.js land as three stable modules every tab can call. pill({ value, variant, title?, href? }) returns a span (or anchor when href is set) with the vocabulary class `rcf-pill--<variant>` for the vocabulary family (gate state green/amber/red; level verdict yes/no; persona po/eng; AC class) and `rcf-pill--<normalisedValue>` for the specific value, so one call site renders one markup shape across every family. findingsList({ heading, count, items }) returns a heading plus an ordered id list, each item an anchor into the document tabs with a one-line `why` string, ids capped at 20 and a `... N more suppressed` tail beyond. diff(before, after) returns a two-column rendering of two document bodies for the delta list. Readiness is the first consumer in 0.29.0; Product Map and Requirements are re-pointed only where the swap is mechanical in this PR (otherwise their markup stays and the swap is a follow-up), so no existing Product Map or Requirements test expectation changes.",
+  "category": "functional",
+  "domain": "defineDetection",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "webUi"
+    ],
+    "reason": "keyword-scan",
+    "classifiedAt": "2026-10-01T18:00:00Z",
+    "signals": [
+      {
+        "source": "description",
+        "shape": "webUi",
+        "match": "render"
+      }
+    ]
+  },
+  "rationale": "Three tabs today each ship their own markup for the same visual roles (status pill, items list, before-after). The hand-rolled copies drift so a gate state on one tab reads differently from the same gate state on another. Factoring to three shared components makes gate state, persona, level verdict and AC class read the same everywhere and is the smallest surface the Readiness tab needs. The spec is explicit (section 5): one module each, same markup shape across callers; existing tab tests change only where the PR explicitly re-points.",
+  "tags": [
+    "capability:define-detection"
+  ]
+}

package/rcf/requirements/req-182.json

@@ -0,0 +1,25 @@
+{
+  "createdAt": "2026-10-03T00:00:00Z",
+  "updatedAt": "2026-10-03T00:00:00Z",
+  "reqId": "REQ-182",
+  "prdId": "PRD-001",
+  "title": "DEFINE-stage guidance pack",
+  "description": "The DEFINE-stage guidance pack is served through `rcf guidance <slug>`, the `rcf://docs/<slug>` resources and the argument-free MCP prompts registered in guidance/manifest.json: define-intent and discovery-prototypes guidance, the elicitation-playbook restructure, two managed-block rules.",
+  "category": "functional",
+  "domain": "define",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "none"
+    ],
+    "reason": "operatorOverride",
+    "classifiedAt": "2026-10-03T00:00:00Z",
+    "signals": []
+  },
+  "rationale": "Spec 2026-10-01 (DEFINE step 3) section 6 pins the DEFINE-stage guidance surface: argument-free prompts (served from markdown in guidance/), resource URIs under `rcf://docs/`, and two managed-block rules the harness picks up through `rcf doctor`. REQ-182 was reserved by the PR 2 chain for this pack but did not land on origin/main; this PR authors it minimally with the amended description from spec section 11.8 (that shift is recorded at the top of report.md) so US-18202 has an owning REQ and the pack has a single home across DEFINE step 3 PRs. The amendment keeps room for later PRs to append: step 3 PR 7 will add `rcf_define_litmus` under the same REQ.",
+  "tags": [
+    "capability:define-intent"
+  ]
+}

package/rcf/requirements/req-186.json

@@ -0,0 +1,25 @@
+{
+  "createdAt": "2026-10-02T18:00:00Z",
+  "updatedAt": "2026-10-02T18:00:00Z",
+  "reqId": "REQ-186",
+  "prdId": "PRD-001",
+  "title": "guided product-owner elicitation",
+  "description": "rcf-lite computes, from the readiness object, the ordered set of questions one persona can answer, each with the write-back that answers it, so that a harness can conduct the intent-complete loop without an engineer. Nothing is stored; the loop ends when `levels.intentComplete.ok` is true.",
+  "category": "functional",
+  "domain": "define",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "none"
+    ],
+    "reason": "operatorOverride",
+    "classifiedAt": "2026-10-02T18:00:00Z",
+    "signals": []
+  },
+  "rationale": "Spec 2026-10-01 (DEFINE step 3) section 1 pins the loop as harness-driven. rcf-lite supplies the questions, the write-backs and the verdict; the harness holds the conversation. One new read verb `rcf define questions` turns every failing product-owner check into a per-item plain-sentence question carrying its exact write-back; `levels.intentComplete.ok === true` terminates the loop. The engineer register rides the same mechanism with `--persona engineer`.",
+  "tags": [
+    "capability:define-intent"
+  ]
+}

package/rcf/requirements/req-187.json

@@ -0,0 +1,31 @@
+{
+  "createdAt": "2026-10-02T16:40:00Z",
+  "updatedAt": "2026-10-02T16:40:00Z",
+  "reqId": "REQ-187",
+  "prdId": "PRD-001",
+  "title": "document intake into brief statements",
+  "description": "A submitted document reaches the brief ledger as kinded statements with source spans through `brief add --from`, the intake scans run over the new statements against the existing ones, and every finding becomes an open question the loop asks.",
+  "category": "functional",
+  "domain": "define",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "persistence"
+    ],
+    "reason": "keyword-scan",
+    "classifiedAt": "2026-10-02T16:40:00Z",
+    "signals": [
+      {
+        "source": "description",
+        "shape": "persistence",
+        "match": "ledger"
+      }
+    ]
+  },
+  "rationale": "Spec 2026-10-01 (DEFINE step 3) section 2.1 splits intake into two halves. The harness writes a statement file beside each source and the operator corrects it. rcf-lite mints the statements, runs the intake scans over the new statements against the existing ones, and appends one openQuestion statement per finding. This is the seam decision 4 pins down: scan findings become brief statements so the loop reads one check (brief:openQuestions) and the owner answers in one place.",
+  "tags": [
+    "capability:define-intake"
+  ]
+}

package/rcf/requirements/req-188.json

@@ -0,0 +1,25 @@
+{
+  "createdAt": "2026-10-03T00:00:00Z",
+  "updatedAt": "2026-10-03T00:00:00Z",
+  "reqId": "REQ-188",
+  "prdId": "PRD-001",
+  "title": "draft shapes for the engineer",
+  "description": "After intent-complete the agent pre-populates `[draft]` entities, components and interfaces as engineer entry material; `shapes:draftSettled` lists every draft home.",
+  "category": "functional",
+  "domain": "define",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "none"
+    ],
+    "reason": "operatorOverride",
+    "classifiedAt": "2026-10-03T00:00:00Z",
+    "signals": []
+  },
+  "rationale": "Spec 2026-10-01 (DEFINE step 3) section 3 and decision 8: once L1 is green, the agent populates one `[draft]` core entity per `entity` statement, one `[draft]` TAC stub per surface or external-system cluster, and `[draft]` interfaces with real kinds inside each stub, so the engineer walks into a tree whose shape is honest about what is still owed. `shapes:draftSettled` already fails `[draft]` on `TAC.interfaces[].description` in 0.29.0 (the current main; the 0.29.0 tag has not been cut). This REQ extends the marker to `TAC.purpose` and `coreEntities[].description` and extends the check to list all three id forms (`<tacId>:<name>`, `<tacId>`, `TAD.entity:<name>`). `tacHasInterface`, `kindVocabulary`, the new template-marker check and the entity join apply to drafts unchanged; nothing in the draft pass can fail a product-owner check, which is the property that keeps L1 and the draft pass independent.",
+  "tags": [
+    "capability:define-drafts"
+  ]
+}

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"
 }

package/rcf/tacs/tac-006.json

@@ -16,53 +16,53 @@
   "interfaces": [
     {
       "name": "rcf.read",
-      "kind": "mcpTool",
-      "description": "Read any RCF document by id over MCP."
+      "kind": "other",
+      "description": "Read any RCF document by id over MCP. [legacy kind: mcpTool; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "rcf.create",
-      "kind": "mcpTool",
-      "description": "Create a document with parent linkage over MCP."
+      "kind": "other",
+      "description": "Create a document with parent linkage over MCP. [legacy kind: mcpTool; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "rcf.update",
-      "kind": "mcpTool",
-      "description": "Update fields on a document over MCP."
+      "kind": "other",
+      "description": "Update fields on a document over MCP. [legacy kind: mcpTool; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "rcf.delete",
-      "kind": "mcpTool",
-      "description": "Delete a document with reference safety over MCP."
+      "kind": "other",
+      "description": "Delete a document with reference safety over MCP. [legacy kind: mcpTool; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "rcf.coverage",
-      "kind": "mcpTool",
-      "description": "Report coverage gaps over MCP."
+      "kind": "other",
+      "description": "Report coverage gaps over MCP. [legacy kind: mcpTool; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "rcf.trace",
-      "kind": "mcpTool",
-      "description": "Trace forward or back over MCP."
+      "kind": "other",
+      "description": "Trace forward or back over MCP. [legacy kind: mcpTool; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "rcf.impact",
-      "kind": "mcpTool",
-      "description": "Report impact over MCP."
+      "kind": "other",
+      "description": "Report impact over MCP. [legacy kind: mcpTool; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "rcf.view",
-      "kind": "mcpTool",
-      "description": "Generate the diagram and the static page over MCP."
+      "kind": "other",
+      "description": "Generate the diagram and the static page over MCP. [legacy kind: mcpTool; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "rcf.build.assemble",
-      "kind": "mcpTool",
-      "description": "Assemble a build prompt over MCP."
+      "kind": "other",
+      "description": "Assemble a build prompt over MCP. [legacy kind: mcpTool; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "rcf.build.markDone",
-      "kind": "mcpTool",
-      "description": "Mark a slice done over MCP."
+      "kind": "other",
+      "description": "Mark a slice done over MCP. [legacy kind: mcpTool; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     }
   ],
   "dependencies": [
@@ -100,5 +100,5 @@
   "tradeoffs": "Local stdio sacrifices the convenience of a hosted MCP but is the only transport that preserves filesystem access; the trade is locked by the differentiator.",
   "notes": "The MCP surface mirrors the CLI verb set so behaviour is identical across surfaces.",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-10-03T18:30:00Z"
 }

package/rcf/tacs/tac-007.json

@@ -16,23 +16,23 @@
   "interfaces": [
     {
       "name": "RcfError",
-      "kind": "type",
-      "description": "The structured error type used throughout the tool."
+      "kind": "recordShape",
+      "description": "The structured error type used throughout the tool. [legacy kind: type; mapped to recordShape per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "renderForTerminal",
-      "kind": "function",
-      "description": "Render an RcfError as human-readable terminal output."
+      "kind": "other",
+      "description": "Render an RcfError as human-readable terminal output. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "renderForMcp",
-      "kind": "function",
-      "description": "Serialise an RcfError as a structured object for an MCP client."
+      "kind": "other",
+      "description": "Serialise an RcfError as a structured object for an MCP client. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     }
   ],
   "dependencies": [],
   "tradeoffs": "A single error type across surfaces costs a small loss of surface-specific detail but guarantees that error reporting does not drift between CLI and MCP.",
   "notes": "Validation failures aggregate; the renderers preserve the full list, not just the first.",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-10-03T18:30:00Z"
 }

package/rcf/tacs/tac-008.json

@@ -1,6 +1,6 @@
 {
   "createdAt": "2026-07-20T17:01:52.768Z",
-  "updatedAt": "2026-07-20T17:01:52.768Z",
+  "updatedAt": "2026-10-03T18:30:00Z",
   "purpose": "Ship the agent-facing method layer - the elicitation and build-cycle playbooks, the reference docs and the harness fragment - that teaches an AI agent how to run the RCF method well, served over MCP as resources and prompts and readable in place under guidance/.",
   "responsibilities": [
     "Carry the elicitation method (question frames, AC-depth bar, deploy-target elicitation, hosting-choice guidance) the eliciting agent runs with a human",
@@ -12,18 +12,18 @@
   "interfaces": [
     {
       "name": "rcf_elicit_requirements",
-      "kind": "prompt",
-      "description": "The elicitation playbook, served as an MCP prompt to the eliciting agent."
+      "kind": "other",
+      "description": "The elicitation playbook, served as an MCP prompt to the eliciting agent. [legacy kind: prompt; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "rcf_execute_build_cycle",
-      "kind": "prompt",
-      "description": "The build-cycle playbook, served as an MCP prompt to the operating agent."
+      "kind": "other",
+      "description": "The build-cycle playbook, served as an MCP prompt to the operating agent. [legacy kind: prompt; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "harness fragment",
-      "kind": "artifact",
-      "description": "The RULE-bearing block rcf init writes into CLAUDE.md and AGENTS.md."
+      "kind": "fileFormat",
+      "description": "The RULE-bearing block rcf init writes into CLAUDE.md and AGENTS.md. [legacy kind: artifact; mapped to fileFormat per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     }
   ],
   "dependencies": [

package/rcf/tacs/tac-4101-feedback-cli.json

@@ -17,13 +17,13 @@
   "interfaces": [
     {
       "name": "feedbackMain",
-      "kind": "function",
-      "description": "Argv-driven main; matches the core-verb signature the top-level dispatcher expects."
+      "kind": "other",
+      "description": "Argv-driven main; matches the core-verb signature the top-level dispatcher expects. [legacy kind: function; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     },
     {
       "name": "HELP",
-      "kind": "constant",
-      "description": "Static help text asserted by the help-parity test."
+      "kind": "other",
+      "description": "Static help text asserted by the help-parity test. [legacy kind: constant; mapped to other per DEFINE spec \u00a75.2 closed vocabulary, 0.30.0 PR 8]"
     }
   ],
   "dependencies": [
@@ -73,5 +73,5 @@
   "tradeoffs": "A single core verb keeps the surface easy to reference in RULE 17 and in docs; the cost is a moderately sized sub-dispatcher, matched by preflight and other multi-verb families already in the tree.",
   "notes": "The verb is core, not grouped, because it spans discover-to-audit and is invoked from harness hooks; OLD_FLAT_MAP is untouched (no legacy form existed). Design section 9 decision: no MCP tool for feedback in v1 (rejected: an rcf_feedback_add MCP tool, adds a second code path to test before the first has users; add when an MCP-only harness appears).",
   "createdAt": "2026-09-16T13:45:23.000Z",
-  "updatedAt": "2026-09-16T14:14:36Z"
+  "updatedAt": "2026-10-03T18:30:00Z"
 }