rcf-lite 0.28.2 → 0.28.4

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-727",
+  "path": "src/cli/readiness.js",
+  "title": "rcf define readiness [--json] [--check <stage>|all]",
+  "description": "CLI handler. Parses --json / --check / --help; walks the tree; loads freeze + all four ledgers; resolves test pointers; wraps computeReadiness with runWithAdmissibilityGate; emits text or JSON; --check narrows and gates the exit code.",
+  "implementsAcIds": [
+    "AC-17501-5"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-24T14:30:00Z",
+  "updatedAt": "2026-09-24T14:30:00Z"
+}

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

@@ -0,0 +1,21 @@
+{
+  "cnId": "CN-728",
+  "path": "test/query/gates.test.js",
+  "title": "Unit tests for stage gates D1..D8",
+  "description": "Covers AC-17401-1..8: return shape, blocking-vs-warn-with-ack fold, notApplicable rules, D4 floors + per-class opt-outs, D3 interface kind vocabulary, D5 cheap checks, D6 validate + probe count, D8 tree-wide freeze checks.",
+  "implementsAcIds": [
+    "AC-17401-1",
+    "AC-17401-2",
+    "AC-17401-3",
+    "AC-17401-4",
+    "AC-17401-5",
+    "AC-17401-6",
+    "AC-17401-7",
+    "AC-17401-8"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-24T14:30:00Z",
+  "updatedAt": "2026-09-24T14:30:00Z"
+}

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

@@ -0,0 +1,18 @@
+{
+  "cnId": "CN-729",
+  "path": "test/query/readiness.test.js",
+  "title": "Unit tests for computeReadiness",
+  "description": "Covers AC-17501-1..4 and AC-17501-6: section 2.4 shape, fan-out impacted/impactedFbs, coverage tree + per-REQ, nextAction pick, loadAllLedgers-omits-absent.",
+  "implementsAcIds": [
+    "AC-17501-1",
+    "AC-17501-2",
+    "AC-17501-3",
+    "AC-17501-4",
+    "AC-17501-6"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-24T14:30:00Z",
+  "updatedAt": "2026-09-24T14:30:00Z"
+}

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-730",
+  "path": "test/cli/readiness.test.js",
+  "title": "CLI tests for rcf define readiness",
+  "description": "Covers AC-17501-5: text output, --json emission, --check exit codes (blocking 4, warn-with-ack 0 with [warn]), admissibility refusal path exit 4.",
+  "implementsAcIds": [
+    "AC-17501-5"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-24T14:30:00Z",
+  "updatedAt": "2026-09-24T14:30:00Z"
+}

package/rcf/fbs/fbs-190.json

@@ -0,0 +1,37 @@
+{
+  "fbsId": "FBS-190",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 190,
+  "executionStatus": "complete",
+  "title": "Product Map tab on the review surface",
+  "summary": "Deliver REQ-170: a new \"Product Map\" tab with five groupings (shape, status filter, component-first, trace coverage, capability) drilling group -> REQ -> US -> AC, hash-addressable.",
+  "approach": "Add a product-map tab to src/view/html-page.js after Build sequence. Extend inline script TAB list. Write src/view/product-map.js: pure bucketing over the BuiltTreeModel, one function per grouping, returning {buckets, unclassifiedCount} shapes the renderer consumes. Reuse the existing detailsWrap/renderReq helpers so REQ blocks match the Requirements tab. Deep-link hash pattern #tab=product-map&group=<g>&status=<s> handled by extending resolveHash + status filter client-side.",
+  "acIds": [
+    "AC-17001-1",
+    "AC-17001-2",
+    "AC-17002-1",
+    "AC-17003-1",
+    "AC-17004-1",
+    "AC-17005-1"
+  ],
+  "dependsOnFbsIds": [],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "deliverables": [
+    "src/view/product-map.js: pure bucketing (groupByShape, groupByComponent, groupByTraceCoverage, groupByCapability)",
+    "src/view/html-page.js: fifth tab wired, panel renderer, inline script TAB list extended, status filter handling",
+    "test/view/product-map.test.js: 5 grouping tests + status filter + hash routing shape",
+    "test/view/fixtures/phase-3-6-static.html: regenerated baseline (product-map tab is a whitelisted additive delta)",
+    "test/view/tabs.test.js: expect the fifth tab in order"
+  ],
+  "riskLevel": "low",
+  "domain": "reviewSurface",
+  "estimatedSize": "medium",
+  "estimatedHours": 8,
+  "notes": "No schema changes. Capability grouping consumes REQ.tags[] convention (FBS-191 populates the data).",
+  "createdAt": "2026-09-21T17:00:00.000Z",
+  "updatedAt": "2026-09-21T17:00:00.000Z"
+}

package/rcf/fbs/fbs-191.json

@@ -0,0 +1,34 @@
+{
+  "fbsId": "FBS-191",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 191,
+  "executionStatus": "complete",
+  "title": "Capability tag convention: taxonomy + dogfood application",
+  "summary": "Deliver REQ-171: tag every dogfood REQ with at least one capability:<slug> tag, document the taxonomy and the rule for adding a new capability.",
+  "approach": "Author a compact taxonomy (10-12 slugs) derived from the actual REQ set, hand-map each of the 103 dogfood REQs (or via a small offline script commit-editing the tags[] arrays), and add a capability-tags.md doc linked from docs/README.md.",
+  "acIds": [
+    "AC-17101-1",
+    "AC-17102-1"
+  ],
+  "dependsOnFbsIds": [
+    "FBS-190"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "deliverables": [
+    "packages/rcf-lite/rcf/requirements/*.json: every REQ has >= 1 capability:<slug> tag",
+    "packages/rcf-lite/docs/capability-tags.md: the taxonomy and the rule",
+    "packages/rcf-lite/docs/README.md: link to capability-tags.md",
+    "test/view/product-map.test.js: capability grouping assertion runs on real data"
+  ],
+  "riskLevel": "low",
+  "domain": "reviewSurface",
+  "estimatedSize": "small",
+  "estimatedHours": 3,
+  "notes": "A classifier verb (rcf discover req-capability-classify) is a follow-up, not part of this PR.",
+  "createdAt": "2026-09-21T17:00:00.000Z",
+  "updatedAt": "2026-09-21T17:00:00.000Z"
+}

package/rcf/fbs/fbs-192.json

@@ -0,0 +1,17 @@
+{
+  "createdAt": "2026-09-21T19:43:56.521Z",
+  "updatedAt": "2026-09-21T19:44:37.430Z",
+  "acIds": [
+    "AC-17006-1",
+    "AC-17007-1"
+  ],
+  "fbsId": "FBS-192",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 192,
+  "executionStatus": "complete",
+  "title": "Product Map UX rescue pass",
+  "summary": "Turn the Product Map from function-emitted to usable-every-day: sticky styled controls, collapsed-by-default buckets, jump-nav, per-status mini counts, hash-encoded open buckets, live-refresh persistence via stable data-doc-id, and a lazy first-load payload that ships only bucket-heading skeletons.",
+  "dependsOnFbsIds": [],
+  "approach": "Restyle pm-controls with the viewer indigo/rounded tokens. Wrap each bucket in <details class=\"pm-bucket\"> with a summary carrying label + count + per-status mini pills. Emit a pm-jump-nav chip row per grouping. Extend the hash schema to carry &open=<bucketIds>. Suppress raw-JSON disclosures inside pm-req cards via a suppressRawJson flag on renderReq/renderUserStory. Add a /product-map/<name> partial endpoint; the client fetches groupings on demand and invalidates the cache on every SSE swap."
+}

package/rcf/fbs/fbs-193.json

@@ -0,0 +1,37 @@
+{
+  "createdAt": "2026-09-22T11:59:39Z",
+  "updatedAt": "2026-09-22T15:00:00Z",
+  "acIds": [
+    "AC-17008-1"
+  ],
+  "fbsId": "FBS-193",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 193,
+  "executionStatus": "complete",
+  "title": "Product Map: blueprint badge and by-blueprint grouping",
+  "summary": "Add a sixth grouping to the Product Map tab: 'By blueprint', with one bucket per applied blueprint plus an Application bucket for the project's own (non-blueprint) requirements. Every REQ row contributed by an applied blueprint carries a compact blueprint badge in every grouping. The by-blueprint bucket's second level is capability, then the usual REQ->US->AC drill-down.",
+  "dependsOnFbsIds": [
+    "FBS-192"
+  ],
+  "approach": "Extend GROUPINGS with 'blueprint'. Read manifest.blueprints[].contributions[] via scope.contributionsForBlueprint as the source of truth for blueprint attribution; fall back to reqId's kebab-slug prefix only when no contributions record is present. Add renderBlueprintGrouping that emits jump-nav + one <details class=pm-bucket> per applied blueprint plus an Application bucket, each carrying a capability sub-heading before its REQ rows. Add a pm-blueprint-badge span into renderReqWrapper (or a wrapping helper) so every grouping's REQ rows render the badge when attributed. Extend inline script PM_GROUPS to include 'blueprint'; renderProductMapPanel adds a blueprint <section>; view/index.js adds a 'blueprint' partial to pmPartials.",
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "deliverables": [
+    "src/view/product-map.js: groupByBlueprint, blueprintForReq, renderBlueprintGrouping, badge in renderReqWrapper",
+    "src/view/html-page.js: PM_GROUPS extended, blueprint <section>, group label 'Blueprint'",
+    "src/view/index.js: pmPartials.blueprint",
+    "src/view/style.css: .pm-blueprint-badge token",
+    "test/view/fixtures/blueprint-applied/: fixture project with one applied blueprint (2 contributed REQs) + 2 project REQs",
+    "test/view/product-map.test.js: five tests covering AC-17008-1",
+    "test/view/fixtures/phase-3-6-static.html: regenerated baseline (blueprint grouping is a whitelisted additive delta)",
+    "docs/capability-tags.md, docs/how-it-works.md: short line about the by-blueprint grouping and badge"
+  ],
+  "riskLevel": "low",
+  "domain": "reviewSurface",
+  "estimatedSize": "medium",
+  "estimatedHours": 5,
+  "notes": "No schema change. Uses manifest.blueprints[].contributions[] as truth (project-local); id-prefix fallback only when contributions absent. Dogfood tree applies no blueprints, so the by-blueprint tab shows one Application bucket - fixture proves the multi-bucket path."
+}

package/rcf/fbs/fbs-194.json

@@ -0,0 +1,35 @@
+{
+  "createdAt": "2026-09-24T12:00:00Z",
+  "updatedAt": "2026-09-24T12:00:00Z",
+  "acIds": [
+    "AC-17201-1",
+    "AC-17201-2",
+    "AC-17201-3",
+    "AC-17201-4"
+  ],
+  "fbsId": "FBS-194",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 194,
+  "executionStatus": "complete",
+  "title": "DEFINE slice 1: delta module and freeze record I/O",
+  "summary": "Ship src/query/delta.js (hashDocument, computeTreeHash, computeDelta) and src/define/freeze-record.js (load, save, validate). Export the delta primitives from src/query/index.js. Cover every AC with unit tests in test/query/delta.test.js and test/define/freeze-record.test.js.",
+  "dependsOnFbsIds": [],
+  "approach": "Pure module with SHA-256 over canonical JSON per proposal 2026-09-22 v3 section 2.1 / 2.2. Canonicalise recurses over the parsed value, sorting object keys and stripping whitespace. Tree hash is SHA-256 over the sorted (id, docHash) pairs. Delta enumerates tree.byId once and classifies each id against the freeze docHashes, appending ledger:<name> entries for the sidecars the caller passes. Freeze record I/O treats a missing file as null; a malformed body raises FreezeRecordError with a coded reason and a named field. The writer validates first so a bad in-memory record never lands on disk.",
+  "contextRequirements": {
+    "tacIds": ["TAC-4120-define-delta-and-freeze"],
+    "adrIds": ["ADR-4120-canonical-json-hashing"]
+  },
+  "deliverables": [
+    "src/query/delta.js: canonicaliseJson, hashDocument, computeTreeHash, computeDelta (§2.2 shape)",
+    "src/query/index.js: re-export the four delta primitives",
+    "src/define/freeze-record.js: FREEZE_RECORD_REL_PATH, FreezeRecordError, validateFreezeRecord, loadFreezeRecord, saveFreezeRecord",
+    "test/query/delta.test.js: eleven tests covering AC-17201-1 and AC-17201-2",
+    "test/define/freeze-record.test.js: nine tests covering AC-17201-3 and AC-17201-4"
+  ],
+  "riskLevel": "low",
+  "domain": "defineDetection",
+  "estimatedSize": "small",
+  "estimatedHours": 3,
+  "notes": "Pure module: no filesystem I/O beyond the freeze reader / writer. computeDelta signature and return shape are the contract every later slice reads."
+}

package/rcf/fbs/fbs-195.json

@@ -0,0 +1,37 @@
+{
+  "createdAt": "2026-09-24T12:00:00Z",
+  "updatedAt": "2026-09-24T12:00:00Z",
+  "acIds": [
+    "AC-17301-1",
+    "AC-17301-2",
+    "AC-17301-3",
+    "AC-17301-4"
+  ],
+  "fbsId": "FBS-195",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 195,
+  "executionStatus": "complete",
+  "title": "DEFINE slice 1: four sidecar ledgers and rcf define ledger CLI",
+  "summary": "Ship src/define/ledgers.js (load, save, validate, addEntry, resolveEntry, parseBriefFromFile, loadAllLedgers), src/cli/ledger.js (add / resolve / list on every ledger name; renderDecisionsList prints the #241 format), and wire under define in bin/rcf.js and src/cli/help.js. Prove walker invisibility of rcf/define/ with a dedicated test.",
+  "dependsOnFbsIds": ["FBS-194"],
+  "approach": "One JSON file per ledger under rcf/define/ (brief-ledger.json, decisions-ledger.json, concern-ledger.json, probe-ledger.json). LEDGER_NAMES is the closed list of accepted names; per-ledger config maps to the filename and array key. Validation is local (no @stravica-ai/rcf-schemas change). loadLedger returns an empty ledger on ENOENT; a malformed file raises LedgerError with a coded reason. addEntry mints ids per ledger and validates the whole body before returning it. The CLI wraps parseArgs, prints per-verb usage from HELP so 'rcf help define ledger' and 'rcf define ledger --help' render the same block, and disposes of ledger-specific flags (--kind, --text, --from, --source, --question, --option, --default, --blocks, --req, --concern, --disposition, --reason, --answer, --finding, --severity). renderDecisionsList prints the numbered #241 format for decisions list. The walker never reads rcf/define/ because loader.subdirFor names its children by kind; a dedicated test seeds four ledger files plus a bug-bait req-999.json under rcf/define/ and asserts no walker error path starts with rcf/define/ and no matching id lands in tree.byId.",
+  "contextRequirements": {
+    "tacIds": ["TAC-4121-define-ledgers"],
+    "adrIds": ["ADR-4121-define-sidecars"]
+  },
+  "deliverables": [
+    "src/define/ledgers.js: LEDGER_NAMES, BRIEF_KINDS, LedgerError, emptyLedger, ledgerRelPath, ledgerPath, loadLedger, saveLedger, validateLedger, addEntry, resolveEntry, nextIdFor, parseBriefFromFile, loadAllLedgers",
+    "src/cli/ledger.js: main, HELP, renderDecisionsList, parseOptionFlags",
+    "bin/rcf.js: GROUPS.define.ledger registered",
+    "src/cli/help.js: HELP_MAP.define.ledger, DEFINE_HELP block extended, top-level listing extended",
+    "test/define/ledgers.test.js: fifteen tests covering AC-17301-1 and AC-17301-3 semantics on the pure module",
+    "test/cli/ledger.test.js: eight CLI tests covering AC-17301-1, AC-17301-2 and AC-17301-3",
+    "test/store/walker-invisible-define.test.js: one test proving AC-17301-4"
+  ],
+  "riskLevel": "low",
+  "domain": "defineLedgers",
+  "estimatedSize": "medium",
+  "estimatedHours": 5,
+  "notes": "Slice 1 leaves the intake-scan-against-frozen-statements hook on brief add --from as a named seam; slice 2's D1 gate is the intended consumer. No schema-package change."
+}

package/rcf/fbs/fbs-196.json

@@ -0,0 +1,37 @@
+{
+  "createdAt": "2026-09-24T14:30:00Z",
+  "updatedAt": "2026-09-24T14:30:00Z",
+  "acIds": [
+    "AC-17401-1",
+    "AC-17401-2",
+    "AC-17401-3",
+    "AC-17401-4",
+    "AC-17401-5",
+    "AC-17401-6",
+    "AC-17401-7",
+    "AC-17401-8"
+  ],
+  "fbsId": "FBS-196",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 196,
+  "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"],
+  "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"]
+  },
+  "deliverables": [
+    "src/query/gates.js: STAGE_ORDER, STAGE_GATES, STAGE_SHORT_NAMES, INTERFACE_KINDS, checkD1Brief..checkD8Freeze, plus foldState and parseAcClass helpers",
+    "src/query/index.js: re-export gate check functions + STAGE_ORDER, STAGE_GATES, STAGE_SHORT_NAMES so consumers import through one seam",
+    "test/query/gates.test.js: unit tests covering AC-17401-1 through AC-17401-8"
+  ],
+  "riskLevel": "low",
+  "domain": "defineDetection",
+  "estimatedSize": "medium",
+  "estimatedHours": 4,
+  "notes": "Pure module: no filesystem I/O beyond what the caller supplies. Every warn-with-ack check leaves an explicit named seam for the 0.30 slice that will land the full template parser, catalogue and scans."
+}

package/rcf/fbs/fbs-197.json

@@ -0,0 +1,41 @@
+{
+  "createdAt": "2026-09-24T14:30:00Z",
+  "updatedAt": "2026-09-24T14:30:00Z",
+  "acIds": [
+    "AC-17501-1",
+    "AC-17501-2",
+    "AC-17501-3",
+    "AC-17501-4",
+    "AC-17501-5",
+    "AC-17501-6"
+  ],
+  "fbsId": "FBS-197",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 197,
+  "executionStatus": "complete",
+  "title": "DEFINE slice 2: computeReadiness compose and rcf define readiness CLI",
+  "summary": "Ship src/query/readiness.js (computeReadiness composing delta + fan-out + gates + coverage + decisions into the section 2.4 object), src/cli/readiness.js (rcf define readiness [--json] [--check <stage>|all]), wire into bin/rcf.js and src/cli/help.js, resolve the slice-1 P3 by correcting loadAllLedgers to omit absent ledger files from the returned bundle.",
+  "dependsOnFbsIds": ["FBS-196"],
+  "approach": "Pure composer over TAC-4122's gates. computeImpact is called once per id in changed union added; impacted is the deduplicated union of every impact node id excluding pivots; impactedFbs is the subset { kind === 'fbs' AND actionNeeded === 're-execute' }. Coverage runs tree-wide (strict per-AC) plus once per REQ ancestor of the delta. nextAction picks the first failing stage in D1..D8 order and the first failing check inside it. freezeable is the AND of every stage state being passed / acknowledged / notApplicable. The CLI wraps its producer with runWithAdmissibilityGate; on refuse the wrapper's refusal envelope prints on stderr and the CLI exits 4. Text output follows section 6.2 (tree line, next action, chip line, delta list, failing items). --json emits JSON.stringify(result, null, 2). --check <stage> narrows the output and gates the exit code per AC-17501-5. loadAllLedgers is updated to stat each file first and omit missing ones (P3 resolution).",
+  "contextRequirements": {
+    "tacIds": ["TAC-4123-define-readiness"],
+    "adrIds": ["ADR-4123-readiness-single-object"]
+  },
+  "deliverables": [
+    "src/query/readiness.js: computeReadiness, computeScope, composeStages, deriveNextAction, deriveTreeSummary",
+    "src/cli/readiness.js: HELP, main; --json / --check / --help flags; runWithAdmissibilityGate wrap",
+    "src/define/ledgers.js: loadAllLedgers refactor to omit absent files (P3)",
+    "src/query/index.js: export computeReadiness + gates re-exports",
+    "bin/rcf.js: GROUPS.define.readiness registered",
+    "src/cli/help.js: HELP_MAP.define.readiness wired; DEFINE_HELP block extended; top-level DEFINE listing extended",
+    "test/query/readiness.test.js: tests covering AC-17501-1..4 and AC-17501-6",
+    "test/cli/readiness.test.js: CLI tests covering AC-17501-5",
+    "test/define/ledgers.test.js: extension test covering AC-17501-6 (loadAllLedgers omits missing files)"
+  ],
+  "riskLevel": "low",
+  "domain": "defineDetection",
+  "estimatedSize": "medium",
+  "estimatedHours": 4,
+  "notes": "Depth-2 slice: no sub-agents. Chain first, code next, tests last. Every warn-with-ack check leaves a named seam for the 0.30 slice."
+}

package/rcf/requirements/req-001.json

@@ -8,6 +8,7 @@
   "priority": "must",
   "rationale": "The in-repository differentiator depends on RCF documents living beside the code. A predictable on-disk layout is the foundation every other capability reads from and writes to.",
   "tags": [
+    "capability:project-init",
     "structure",
     "manifest",
     "filesystem"
@@ -15,5 +16,5 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-09-21T17:00:00.000Z"
 }

package/rcf/requirements/req-002.json

@@ -8,6 +8,7 @@
   "priority": "must",
   "rationale": "The owner cannot review code and will not read raw JSON. A visual surface is the only way they can see and steer what is being built in their name. It is delivered first (Phase 3) so every later phase has a review surface.",
   "tags": [
+    "capability:review-surface",
     "view",
     "diagram",
     "review"
@@ -15,5 +16,5 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-09-21T17:00:00.000Z"
 }

package/rcf/requirements/req-003.json

@@ -8,6 +8,7 @@
   "priority": "must",
   "rationale": "Deterministic CRUD is the foundational primitive everything else sits on. Hand-writing the tree in this phase surfaces exactly which operations the owner and the agent need.",
   "tags": [
+    "capability:requirements-authoring",
     "crud",
     "cli",
     "validation"
@@ -15,5 +16,5 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-09-21T17:00:00.000Z"
 }

package/rcf/requirements/req-004.json

@@ -8,6 +8,7 @@
   "priority": "must",
   "rationale": "Traceability is the confidence the framework is named for. The owner needs to know that nothing is unspecified and nothing is untested, and what an edit ripples into, without reading the documents end to end.",
   "tags": [
+    "capability:requirements-authoring",
     "traceability",
     "query",
     "coverage"
@@ -15,5 +16,5 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-09-21T17:00:00.000Z"
 }

package/rcf/requirements/req-005.json

@@ -8,6 +8,7 @@
   "priority": "must",
   "rationale": "For someone who cannot read code, the specification-to-build loop is the only thing between them and a confident but wrong result. Assembling the prompt from the tree is what makes the output solid and traceable to an agreed decision.",
   "tags": [
+    "capability:build-sequence",
     "build",
     "sdd",
     "fbs"
@@ -15,5 +16,5 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-09-21T17:00:00.000Z"
 }

package/rcf/requirements/req-006.json

@@ -8,6 +8,7 @@
   "priority": "should",
   "rationale": "The harness is where the owner's AI tooling lives. A local stdio MCP surface gives that tooling the full RCF feature set while preserving filesystem access and the source-of-truth rule. Remote MCP is excluded because it cannot see the user's codebase.",
   "tags": [
+    "capability:mcp",
     "mcp",
     "harness",
     "stdio"
@@ -15,5 +16,5 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-09-21T17:00:00.000Z"
 }

package/rcf/requirements/req-007.json

@@ -8,6 +8,7 @@
   "priority": "must",
   "rationale": "A non-coder cannot catch a malformed document by eye. The tool must refuse to write invalid state and must explain why, so the owner can trust that what is on disk is always valid.",
   "tags": [
+    "capability:requirements-authoring",
     "validation",
     "quality",
     "schemas"
@@ -15,5 +16,5 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-06-25T00:00:00Z"
+  "updatedAt": "2026-09-21T17:00:00.000Z"
 }

package/rcf/requirements/req-008.json

@@ -1,6 +1,6 @@
 {
   "createdAt": "2026-07-20T17:01:21.557Z",
-  "updatedAt": "2026-07-28T16:40:04.361Z",
+  "updatedAt": "2026-09-21T17:00:00.000Z",
   "category": "functional",
   "priority": "must",
   "description": "The agent guidance pack teaches a build method that keeps the deployment runtime present in the loop from elicitation to verification, so that a non-coding owner who cannot self-verify is not led into an undeployable stack or a false 'verified' claim. It requires four properties of the method the tool ships: (1) every build lands a working, documented local preview loop as its default outcome; (2) elicitation establishes where the app will run early and constrains the stack to that answer, with a jargon-free hosting-choice walkthrough when the owner does not know; (3) every 'verified' or 'tested' claim names the runtime it was checked against and never implies deploy-runtime verification that did not happen; (4) the method carries guidance for a periodic and end-of-build fresh-context self-review that drives the app against its acceptance criteria, subordinate to the independent verification gate rather than a substitute for it. This requirement governs the shipped guidance/prompt surface, not a new runtime subsystem.",
@@ -12,6 +12,7 @@
   "version": "0.1.0",
   "status": "draft",
   "tags": [
+    "capability:build-sequence",
     "guidance",
     "deploy",
     "verification"

package/rcf/requirements/req-009.json

@@ -8,6 +8,7 @@
   "priority": "must",
   "rationale": "The packaging consolidation ruling (docs/2026-08-06_packaging-consolidation-proposal.md, ratified 2026-08-11) picks one install (`rcf-lite`) with one CLI verb space (`rcf`). Verify is a first-class part of the RCF chain (define, build, verify) and must sit inside that verb space, not beside it. Keeping `rcf verify` as an alias avoids a hard break for existing scripts across a transition window.",
   "tags": [
+    "capability:project-init",
     "packaging",
     "cli",
     "verify"
@@ -15,5 +16,5 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-08-11T00:00:00Z",
-  "updatedAt": "2026-08-11T00:00:00Z"
+  "updatedAt": "2026-09-21T17:00:00.000Z"
 }

package/rcf/requirements/req-010.json

@@ -1,6 +1,6 @@
 {
   "createdAt": "2026-08-18T22:54:27.031Z",
-  "updatedAt": "2026-08-18T22:57:45.660Z",
+  "updatedAt": "2026-09-22T13:47:34.538Z",
   "description": "The framework provides a Blueprint mechanism the operator uses to compose blueprint packages (specifications + assets, not code) onto a project tree at any point in its life. Composition is many blueprints per project. Blueprint-contributed docs are namespaced by the blueprint's slug so multiple blueprints cannot collide on ids. Standards packs register at rcf init (or later via rcf define standards add), reference-by-default, copied to rcf/standards/<slug>/ only when the source lives outside the project root. Manifest registration is authoritative. Selective retrieval populates fbs.contextRequirements.standardIds at bundle-assembly time by analysing the FBS work text against the standards tag vocabulary; operator override is supported by authoring the array on the FBS. scope:global ADR contributions surface as blocking conflicts at rcf define blueprint add time.",
   "reqId": "REQ-010",
   "prdId": "PRD-001",
@@ -16,5 +16,8 @@
     ],
     "reason": "keyword-scan",
     "classifiedAt": "2026-08-18T22:54:27.048Z"
-  }
+  },
+  "tags": [
+    "capability:blueprint-library"
+  ]
 }

package/rcf/requirements/req-011.json

@@ -8,6 +8,7 @@
   "priority": "must",
   "rationale": "Verify is the ship gate. A silent runtime change in the browser MCP on the next verify run is the reproducibility hole Baz named on 2026-09-03. Pinning the MCP closes it. Formalising e2e as a declared test level gives browser-facing projects a first-class contract instead of relying on the verify browser stage as a proxy for coverage. Doctor and init together make Playwright the operator's decision, not rcf-lite's ambient inheritance.",
   "tags": [
+    "capability:verify",
     "verify",
     "playwright-mcp",
     "e2e",
@@ -18,5 +19,5 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-09-03T16:56:00Z",
-  "updatedAt": "2026-09-03T16:56:00Z"
+  "updatedAt": "2026-09-21T17:00:00.000Z"
 }

package/rcf/requirements/req-012.json

@@ -8,6 +8,7 @@
   "priority": "must",
   "rationale": "The shipped shelf carried three literal probe-path opinions before this alignment (essentials /healthz + /readyz, probe-endpoints /live + /ready, api-rest /healthz/live + /healthz/ready + /healthz/startup). Composing any two of the three on one project either fired a designed-in `globalAdrTopic` conflict on healthProbes/readinessSemantics or silently shipped three disagreeing probe bindings. WSD-012 mandates /live and /ready, which is the probe-endpoints Kubernetes default; Dex's A4 wsd-service-anatomy binds those two paths as a parameter and required this item as its dependency. Aligning ownership to one blueprint (probe-endpoints) and making the other two defer is the smallest change that closes both the conflict-by-design surface and the silent-disagreement surface without inventing a new composer primitive. Ratified spec: `projects/rcf-lite-wsd/specs/rcf-lite-probe-path-alignment-spec-2026-09-04.md` (sections 1 through 11).",
   "tags": [
+    "capability:blueprint-library",
     "blueprints",
     "observability",
     "probe-endpoints",
@@ -18,5 +19,5 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-09-04T00:00:00Z",
-  "updatedAt": "2026-09-04T00:00:00Z"
+  "updatedAt": "2026-09-22T13:47:34.538Z"
 }

package/rcf/requirements/req-013.json

@@ -8,6 +8,7 @@
   "priority": "must",
   "rationale": "The core shelf carried no logging or error-handling blueprint before this train; every WSD-facing service blueprint (Dex's `wsd-api-rest`) stated its companion suggestions in prose only, with no core fallback for projects that had not registered the WSD library. Baz on 2026-09-03 during the WSD blueprint round review ratified two decisions in one clause: the core shelf carries a `logging` and an `error-handling` blueprint written to general enterprise practice (not to any one organisation's standards), and a companion-suggestion mechanism (REQ-014) surfaces them at apply time. Shipping the two blueprints as general-enterprise-practice siblings of the WSD library halves means every project falls back to a sensible logging and error-handling contract without adopting a library, and the WSD library becomes a specialisation (adds `standardsTrace[]`, adds WSD-specific ADR clauses) that the mechanism resolves in preference to the core when the library is registered.",
   "tags": [
+    "capability:blueprint-library",
     "blueprints",
     "observability",
     "logging",
@@ -18,5 +19,5 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-09-04T12:20:00Z",
-  "updatedAt": "2026-09-04T12:20:00Z"
+  "updatedAt": "2026-09-22T13:47:34.538Z"
 }

package/rcf/requirements/req-014.json

@@ -8,6 +8,7 @@
   "priority": "must",
   "rationale": "Before this train, service blueprints named their companion suggestions in prose in each README and each guide, and the machine could not act on them: `rcf define blueprint add` could not print a suggestion, `rcf define blueprint list` could not annotate an outstanding one, the agent could not know which library provider to prefer, and the operator had no place to record a project-level choice that outlived any single apply. Baz on 2026-09-03 during the WSD blueprint round review ratified the mechanism in the same clause as the two new core blueprints: the mechanism surfaces the suggestion three ways from one resolution rule, the agent surfaces the resolved companions verbally, and the operator adopts explicitly. Suggestion by role (not by slug) is the load-bearing choice: a service blueprint ships once and works with every library that provides the role; the operator's opt-in to a library IS the choice the resolution rule records.",
   "tags": [
+    "capability:blueprint-library",
     "blueprints",
     "companions",
     "provides-roles",
@@ -18,5 +19,5 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-09-04T12:20:00Z",
-  "updatedAt": "2026-09-04T12:20:00Z"
+  "updatedAt": "2026-09-22T13:47:34.538Z"
 }

package/rcf/requirements/req-015.json

@@ -8,6 +8,7 @@
   "priority": "must",
   "rationale": "Dex's WSD library composes on the WSD-001 through WSD-012 standards with clause-level trace tables under `docs/standards-trace.md`. Before this train, the trace lived in prose only, and a library blueprint's ADR could omit any standard reference without the loader noticing. Baz on 2026-09-03 during the WSD blueprint round review ratified the discipline as `really good idea` and made it the shelf standard for any future library or shipped blueprint that composes on named standards. Baz amendment A2 (2026-09-04T12:20:31Z) refined the MUST-to-kind mapping to admit choice-shaped MUSTs as ADRs so the WSD library's 41 MUSTs (27 to AC, 8 to ADR, 8 not-carried per Dex's tables) fit under the discipline without renumbering. The additive fields and load-time validation give machine-checkable adherence without changing any existing blueprint (zero shelf blueprints declare `standardsTrace[]` today).",
   "tags": [
+    "capability:blueprint-library",
     "blueprints",
     "authoring",
     "standards",
@@ -17,5 +18,5 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-09-04T12:20:00Z",
-  "updatedAt": "2026-09-04T12:20:00Z"
+  "updatedAt": "2026-09-22T13:47:34.538Z"
 }