rcf-lite 0.8.0 → 0.10.0

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

@@ -1,14 +1,14 @@
 {
   "cnId": "CN-057",
-  "path": "bin/rcf-verify.js",
+  "path": "bin/rcf.js",
   "implementsAcIds": [
     "AC-901-3"
   ],
   "dependencies": [],
-  "version": "0.1.0",
+  "version": "0.2.0",
   "status": "draft",
   "createdAt": "2026-08-11T00:00:00Z",
-  "updatedAt": "2026-08-11T00:00:00Z",
-  "title": "Alias bin: transition-grace deprecation notice",
-  "description": "Direct invocation of the `rcf-verify` alias bin emits a one-line stderr notice pointing at `rcf verify` as the preferred invocation. Guarded by RCF_QUIET for scripted callers who cannot tolerate stderr chatter."
+  "updatedAt": "2026-08-26T00:00:00Z",
+  "title": "Clean-break dispatcher: old-flat-form refusal with pointer at the new grouped form",
+  "description": "The 0.10.0 CLI reorganisation deletes the standalone `rcf-verify` bin outright. bin/rcf.js recognises the old flat verb tokens via OLD_FLAT_MAP and, on match, writes a one-line stderr hint naming the new grouped form ('Try rcf <group> <verb>...') before exiting 2. Not a back-compat fallback; the invocation still fails."
 }

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

@@ -0,0 +1,18 @@
+{
+  "cnId": "CN-058",
+  "path": "src/blueprint/apply.js#applyBlueprint",
+  "title": "Blueprint apply orchestrator",
+  "description": "Loads a blueprint from a source directory, runs the conflict-detection pass BEFORE any file write, stamps contribution ids into the blueprint's namespace, copies contribution files into the tree, and appends a validated entry to manifest.blueprints[]. Idempotent on same-slug + same-version re-apply. From Phase 3.5 (w-2026-08-19-008) also composes any operator --resolve declarations into manifest.resolutions[] BEFORE detection so the resolution is honoured this run and persists alongside the applied-blueprint update, wires the singular --reason onto every generated declaration (whitespace-only refused at the writer edge), and dedupes duplicate --resolve topics within a single add (first-wins) surfacing a warning to the caller.",
+  "implementsAcIds": [
+    "AC-1001-1",
+    "AC-1001-4",
+    "AC-1002-2",
+    "AC-1002-6",
+    "AC-1002-7"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-059",
+  "path": "src/blueprint/list.js#listBlueprints",
+  "title": "Blueprint list projection",
+  "description": "Reads manifest.blueprints[] and returns rows in appliedAt order.",
+  "implementsAcIds": [
+    "AC-1001-2"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-060",
+  "path": "src/blueprint/remove.js#removeBlueprint",
+  "title": "Blueprint remove with referring-doc guard",
+  "description": "Refuses when any project-authored doc references a contribution id; otherwise unlinks contribution files and rewrites the manifest.",
+  "implementsAcIds": [
+    "AC-1001-3"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-061",
+  "path": "src/cli/blueprint.js#main",
+  "title": "rcf define blueprint CLI dispatcher",
+  "description": "Wires the blueprint verb family into the unified rcf bin; dispatches add|list|remove.",
+  "implementsAcIds": [
+    "AC-1001-5"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-062",
+  "path": "src/blueprint/namespace.js#stampId",
+  "title": "Blueprint id namespacing (prefix + suffix families)",
+  "description": "Stamps a doc id with a blueprint slug according to family: prefix for REQ/US/PRD/BS/TAD/TS, suffix for ADR/TAC/FBS/CN.",
+  "implementsAcIds": [
+    "AC-1002-1"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

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

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-063",
+  "path": "src/blueprint/conflicts.js#detectGlobalAdrConflicts",
+  "title": "scope:global ADR conflict detection",
+  "description": "Detects two applied blueprints each contributing a scope:global ADR on the same topic; returns Conflict records.",
+  "implementsAcIds": [
+    "AC-1002-2",
+    "AC-1002-4"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

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

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-064",
+  "path": "src/blueprint/conflicts.js#renderConflictReport",
+  "title": "Conflict-presentation report writer",
+  "description": "Renders a Conflict[] list into an operator-facing block with per-side `blueprint <slug>: <title> — <decision>` headers (Phase 3.5 reshape; falls back to `<id> at <path>` when the tree did not carry the ADR body), a refs footer, and four honest resolution paths with actual conflicting blueprint slugs substituted. Symmetric enrichment: BOTH sides (incoming from the blueprint's ADR file on disk, existing from the walker's tree) are decorated with title + one-sentence decision before rendering. A parallel `conflictReportJson(conflicts)` returns the same shape as a JSON object with per-conflict `resolutions[]` triples for agent-driven composition.",
+  "implementsAcIds": [
+    "AC-1002-3",
+    "AC-1002-8"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

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

@@ -0,0 +1,16 @@
+{
+  "cnId": "CN-065",
+  "path": "src/blueprint/standards.js#registerStandardsPack",
+  "title": "Standards ingestion (reference-by-default + out-of-root copy)",
+  "description": "Detects whether the source lives inside the project root; references-in-place when yes, copies into rcf/standards/<slug>/ when no; writes the manifest.standards[] entry.",
+  "implementsAcIds": [
+    "AC-1003-1",
+    "AC-1003-2",
+    "AC-1003-3"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-066",
+  "path": "src/cli/standards.js#main",
+  "title": "rcf define standards CLI dispatcher",
+  "description": "Wires the standards verb family into the unified rcf bin; dispatches add|list.",
+  "implementsAcIds": [
+    "AC-1003-4"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

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

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-067",
+  "path": "src/build/standards-selector.js#selectStandards",
+  "title": "Deterministic tag-scoring standards selector",
+  "description": "Reads FBS work text against manifest standards tags and returns the deterministic subset of relevant slugs.",
+  "implementsAcIds": [
+    "AC-1004-1",
+    "AC-1004-4"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

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

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-068",
+  "path": "src/build/bundle.js#assembleBundle",
+  "title": "Bundle assembler standardIds host (0.4.4)",
+  "description": "Bundle assembler branch that hosts operator-authored contextRequirements.standardIds override + agentic selection, and renders the standards payload alongside TACs/ADRs.",
+  "implementsAcIds": [
+    "AC-1004-2",
+    "AC-1004-3"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

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

@@ -0,0 +1,16 @@
+{
+  "cnId": "CN-069",
+  "path": "src/blueprint/supersede.js#supersedeBlueprintTopic",
+  "title": "Project-ADR supersession scaffolder (conflict-pair second side)",
+  "description": "Scaffolds a project-level ADR under rcf/adrs/adr-NNN-<kebab-topic>.json that supersedes the CONFLICT PAIR on the topic (one currently-applied blueprint's scope:global ADR + one incoming blueprint's scope:global ADR — Baz ruling, w-2026-08-19-008 round 3), and appends a matching manifest.resolutions[] record so the conflict detector honours the resolution when the operator re-runs `rcf define blueprint add <incoming source>`. The verb accepts an optional `--incoming <source>` argument (required when applied count on the topic is < 2; informational when >= 2): the verb loads the incoming blueprint from disk, finds its scope:global ADR on the topic, stamps the id into the incoming blueprint's namespace, and uses that {slug, adrId} as the second side of supersedes[]. This lets option 3 as printed by the reshaped conflict message execute VERBATIM from the refused-add state — no --resolve prep, no menu-copy weakening. Topic is a LOOKUP KEY (see ADR-010): any string that exact-matches an applied ADR's declared topic is accepted (schema minLength:1, whitespace-only refused at the writer edge; camelCase, snake_case and kebab-case all pass). The scaffolded ADR id derives its slug tail by kebab-ifying the topic (`authModel` -> `ADR-NNN-auth-model`) so the ADR grammar's `[a-z0-9](-[a-z0-9]+)*` tail is satisfied. Every rcfError message returned by this module is prefix-free (no `blueprint supersede: ` in the message body); the CLI edge prepends the single `[error] blueprint supersede: ` line. Refuses when the manifest is missing prd or tad, when applied+incoming count on the topic is < 2, and when a file already exists at the scaffolded ADR path.",
+  "implementsAcIds": [
+    "AC-1002-5",
+    "AC-1002-9",
+    "AC-1002-10"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T14:35:00.000Z",
+  "updatedAt": "2026-08-19T14:35:00.000Z"
+}

package/rcf/fbs/fbs-005.json

@@ -22,7 +22,7 @@
   "estimatedSize": "small",
   "estimatedHours": 3,
   "deliverables": [
-    "rcf read verb with structured outcome",
+    "rcf define read verb with structured outcome",
     "Combined content and validation rendering"
   ],
   "riskLevel": "low",

package/rcf/fbs/fbs-006.json

@@ -31,8 +31,8 @@
   "estimatedSize": "medium",
   "estimatedHours": 8,
   "deliverables": [
-    "rcf create verb with parent linkage and conflict detection",
-    "rcf update verb with safe field updates",
+    "rcf define create verb with parent linkage and conflict detection",
+    "rcf define update verb with safe field updates",
     "Validation-error renderer covering both verbs"
   ],
   "riskLevel": "medium",

package/rcf/fbs/fbs-007.json

@@ -22,7 +22,7 @@
   "estimatedSize": "medium",
   "estimatedHours": 6,
   "deliverables": [
-    "rcf delete verb with reference-safe default",
+    "rcf define delete verb with reference-safe default",
     "Cascade flag with parent-reference cleanup"
   ],
   "riskLevel": "medium",

package/rcf/fbs/fbs-014.json

@@ -2,7 +2,7 @@
   "createdAt": "2026-07-20T17:05:46.941Z",
   "updatedAt": "2026-07-20T17:05:46.941Z",
   "summary": "Harden the build-cycle guidance so every build lands a documented local preview as its default outcome, every verification claim names the runtime it was checked against, and the method carries interim fresh-context self-review guidance. Edits the build-cycle playbook, the build-cycle contract and the harness fragment; no runtime subsystem.",
-  "approach": "In the build-cycle guidance, make a working, documented local preview loop (dev server, seeded data where needed, ideally one command) a required, hosting-independent part of a build's definition of done. Require every 'verified'/'tested' claim - in the Test and Finalise stages and in the PR body's verification section - to name the runtime it was checked against, forbid any claim implying deploy-runtime verification that did not happen, and add an explicit labelled-claim example. Add an interim self-review section describing a periodic and end-of-build fresh-context reviewer dispatch that drives the app against its ACs, targeting session-class bugs, false-promise UI, runtime mismatch, dead auth paths and dead code, scoped honestly as a stopgap until rcf-verify-lite and explicitly not the independent gate. Add matching harness-fragment rules and extend the guidance drift tests.",
+  "approach": "In the build-cycle guidance, make a working, documented local preview loop (dev server, seeded data where needed, ideally one command) a required, hosting-independent part of a build's definition of done. Require every 'verified'/'tested' claim - in the Test and Finalise stages and in the PR body's verification section - to name the runtime it was checked against, forbid any claim implying deploy-runtime verification that did not happen, and add an explicit labelled-claim example. Add an interim self-review section describing a periodic and end-of-build fresh-context reviewer dispatch that drives the app against its ACs, targeting session-class bugs, false-promise UI, runtime mismatch, dead auth paths and dead code, scoped honestly as a stopgap until rcf verify-lite and explicitly not the independent gate. Add matching harness-fragment rules and extend the guidance drift tests.",
   "deliverables": [
     "Build-cycle guidance: local preview loop as default, hosting-independent definition-of-done item",
     "Build-cycle and PR-authoring guidance: runtime-provenance labelling with a worked example",

package/rcf/fbs/fbs-015.json

@@ -4,19 +4,20 @@
   "bsId": "BS-001",
   "buildOrder": 15,
   "executionStatus": "complete",
-  "title": "`rcf verify` subcommand routing (0.7.1 consolidation)",
-  "summary": "Route the adversarial ship-gate verifier under the unified `rcf` CLI as `rcf verify <run|report|provision|cleanup|mcp>`. The pre-existing `rcf-verify` bin becomes a transition-grace alias that dispatches through the same handlers and emits a one-line stderr deprecation notice when invoked directly.",
-  "approach": "One dispatcher, two entry points. bin/rcf.js imports the `main` export from bin/rcf-verify.js and registers it as the `verify` entry on the top-level SUBCOMMANDS map, so `rcf verify --help` and `rcf-verify --help` share the same code path by construction. The alias bin gains a deprecation notice guarded by RCF_QUIET for scripted callers. The unified CLI's help output lists `verify <verb>` alongside the other top-level commands, sourced from the same verify TOP_LEVEL_HELP the alias bin uses (single-source rule).",
+  "title": "`rcf verify` group routing (0.10.0 CLI reorganisation)",
+  "summary": "Route the adversarial ship-gate verifier under the unified `rcf` CLI as `rcf verify <run|report|provision|cleanup|mcp|browser>`. The legacy standalone `rcf-verify` bin (0.7.1 transition-grace alias) is deleted outright; consumers move to `rcf verify <verb>` in one hop.",
+  "approach": "bin/rcf.js declares a `verify` entry in the top-level GROUPS map whose sub-verbs (run, report, provision, cleanup, mcp, browser) resolve to the corresponding main() exports from src/verify/cli/*.js and src/cli/browser-verify.js. The unified CLI's help output lists the verify group with its sub-verbs, sourced from the per-verb HELP exports via HELP_MAP.verify (single-source rule). The dispatcher additionally recognises pre-0.10.0 flat verb tokens through OLD_FLAT_MAP: on match it writes a one-line stderr hint naming the new grouped form before exiting 2. This is a usage-error affordance, not a fallback; the invocation fails.",
   "deliverables": [
-    "bin/rcf.js: `verify` on the top-level SUBCOMMANDS map, dispatching to the alias bin's exported main",
-    "bin/rcf-verify.js: one-line stderr deprecation notice on direct invocation, suppressible via RCF_QUIET",
-    "src/cli/help.js: `verify <verb>` listed in the top-level command table; `help verify` prints the alias bin's TOP_LEVEL_HELP block"
+    "bin/rcf.js: `verify` on the top-level GROUPS map, dispatching per sub-verb to the verify-suite handlers plus browser-verify",
+    "bin/rcf.js: OLD_FLAT_MAP recognises pre-0.10.0 flat verbs and emits a stderr hint at the new grouped form before exit 2",
+    "package.json: `bin` field carries only `rcf`; the historical `rcf-verify` entry and bin/rcf-verify.js file are deleted",
+    "src/cli/help.js: verify group header + sub-verb catalogue in TOP_LEVEL_HELP; `rcf help verify` prints the group help; `rcf help verify <verb>` prints per-verb help via HELP_MAP"
   ],
   "estimatedSize": "small",
   "estimatedHours": 1,
   "riskLevel": "low",
   "domain": "cli",
-  "notes": "Ratified in the 2026-08-06 packaging-consolidation proposal (R3). Pure repackage relative to 0.7.0 verify behaviour; the invocation form gains a canonical route, existing scripts keep working via the alias.",
+  "notes": "Ratified in the 2026-08-26 CLI group-design ruling (clean break: no aliases, no shims, no back-compat fallbacks). Supersedes the 0.7.1 alias-bin transition-grace posture; the alias bin is deleted.",
   "contextRequirements": {
     "tacIds": [],
     "adrIds": []
@@ -28,5 +29,5 @@
   ],
   "dependsOnFbsIds": [],
   "createdAt": "2026-08-11T00:00:00Z",
-  "updatedAt": "2026-08-11T00:00:00Z"
+  "updatedAt": "2026-08-26T00:00:00Z"
 }

package/rcf/fbs/fbs-016.json

@@ -0,0 +1,39 @@
+{
+  "fbsId": "FBS-016",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 16,
+  "executionStatus": "notStarted",
+  "title": "Blueprint verb family (add, list, remove, upgrade) with manifest.blueprints[] writes",
+  "summary": "Introduce the `rcf define blueprint <verb>` verb family and its manifest-writing path. Adds `src/blueprint/` module (loader, applier, contribution-writer) and `src/cli/blueprint.js` (parseArgs, dispatch, HELP block). Adds `blueprint` to the top-level SUBCOMMANDS map on `bin/rcf.js` and to the `TOP_LEVEL` block on `src/cli/help.js` so `rcf --help` advertises it. Every apply writes an entry to `manifest.blueprints[]` per the 0.4.4 schema (slug, version, appliedAt, source, namespace, contributions[]). `add` is idempotent on a clean re-apply; `remove` refuses when any project-authored doc references a contribution id.",
+  "approach": "One dispatcher, one loader, one applier, one writer. bin/rcf.js gains `blueprint: blueprintMain` on SUBCOMMANDS; src/cli/blueprint.js parses `add|list|remove|upgrade` and dispatches to src/blueprint/ handlers. Blueprint loading is a small package-metadata reader (slug, version, ADR contributions with optional scope, doc contributions manifest); Phase 1 keeps the resolver `file://` and `link:` only, with the registry/git-ref shape captured in the source string so the schema forward-compat holds. Contribution writing goes through the existing store writer paths so a blueprint apply produces the same doc files a hand-created doc would. Removal is a manifest patch + contribution-path unlink; the referring-doc check reuses the existing tree walker to enumerate every string field for id occurrences.",
+  "deliverables": [
+    "src/cli/blueprint.js: parseArgs + HELP + main() dispatching add/list/remove/upgrade",
+    "src/blueprint/index.js: barrel re-exporting apply, list, remove, upgrade, loadBlueprint, detectGlobalAdrConflicts",
+    "src/blueprint/apply.js: apply(tree, blueprint, opts) — idempotency + conflict detection + contribution writes + manifest update",
+    "src/blueprint/loader.js: loadBlueprint(source) — reads a blueprint's metadata (slug, version, ADR contributions with scope, doc contributions)",
+    "src/blueprint/remove.js: remove(tree, slug, opts) — referring-doc scan + manifest patch + file unlinks",
+    "src/blueprint/list.js: list(tree) — reads manifest.blueprints[] and returns rows",
+    "bin/rcf.js: `blueprint: blueprintMain` on SUBCOMMANDS",
+    "src/cli/help.js: `blueprint <verb>` on the TOP_LEVEL block, `help blueprint` prints the blueprint HELP",
+    "test/blueprint/apply.test.js, list.test.js, remove.test.js, cli.test.js — behaviour tests keyed to AC-1001-1..5"
+  ],
+  "acIds": [
+    "AC-1001-1",
+    "AC-1001-2",
+    "AC-1001-3",
+    "AC-1001-4",
+    "AC-1001-5"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "dependsOnFbsIds": [],
+  "domain": "cli",
+  "estimatedSize": "medium",
+  "riskLevel": "low",
+  "notes": "Landing car of Phase 1 blueprint mechanism (w-2026-08-18-016, design-brief.md v2 §Composition model). Written against @stravica-ai/rcf-schemas 0.4.4 (blueprints[] host schema); dev pin to feature/blueprint-additive-0.4.4 on the schemas repo carries until the Baz 2FA publish flips the pin to registry-resolved 0.4.4.",
+  "createdAt": "2026-08-18T22:56:02.353Z",
+  "updatedAt": "2026-08-18T22:56:02.353Z"
+}

package/rcf/fbs/fbs-017.json

@@ -0,0 +1,40 @@
+{
+  "fbsId": "FBS-017",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 17,
+  "executionStatus": "notStarted",
+  "title": "Namespaced blueprint ids and scope:global ADR conflict surfacing",
+  "summary": "Blueprint-contributed docs are namespaced by the blueprint's slug: REQ/US/PRD/BS/TAD/TS via the 0.4.4 slug PREFIX (e.g. `spa-REQ-001`), and ADR/TAC/FBS/CN via the 0.4.3 kebab SUFFIX (e.g. `ADR-005-rest-versioning`). `rcf define blueprint add` runs a conflict-detection pass BEFORE writing anything: two blueprints both contributing an ADR tagged `scope: global` on the same topic exit non-zero with both sides printed and four honest resolution paths named (adopt-incoming, keep-existing, supersede via project ADR, declare-on-add via `--resolve`). Non-global TACs, ADRs, REQs, USs and FBSes namespace cleanly and cannot topic-conflict; cross-blueprint id claims (an incoming id already recorded on another applied blueprint) are refused via the authoritative manifest record, not string grammar.",
+  "approach": "Namespacing is enforced at the loader: contribution ids are stamped with the blueprint slug at load time; a contribution whose declared id already carries a namespace is trusted verbatim (author declaration is the truth for what that blueprint owns; the earlier grammar-veto of legitimate slug-tail ids like `ADR-201-spa-theme` under blueprint `spa` was retired in w-2026-08-19-005). Ownership of a written contribution is answered by the manifest's `appliedBlueprintRecord.contributions[]` list — the authoritative record — not by re-parsing the id string. Conflict detection reads the applied `blueprints[]` and the applying blueprint's contributions, and scores collisions along two axes: `scope: global` ADR topic collision (two applied ADRs both tagged `scope: global` with a matching `topic` field), and cross-blueprint ownership (an incoming id whose manifest record is on a DIFFERENT applied blueprint's contribution list — the class the record consultation catches once grammar stopped being a trust surface). Presentation: per-conflict block leads with both ADR titles and their one-sentence decisions, ids and paths as a footer, and four honest resolution paths with actual blueprint slugs filled in — no placeholders. A `--json` output shape is available for agent-driven composition. Phase 3.5 (w-2026-08-19-008) added the `supersede` and `diff` verbs plus the `--resolve` add-time flag, backed by `manifest.resolutions[]` on the 0.4.5 schema; both blueprint ADRs may now co-reside on disk as superseded history alongside a project-level ADR that supersedes them.",
+  "deliverables": [
+    "src/blueprint/namespace.js: pure functions that stamp/verify contribution namespacing for all doc kinds",
+    "src/blueprint/conflicts.js: detectGlobalAdrConflicts(appliedBlueprints, incomingContributions) returning zero-or-more Conflict records",
+    "Updates to src/blueprint/apply.js: conflict pass runs BEFORE any file write; non-empty conflict list short-circuits with a printed report + non-zero exit",
+    "test/blueprint/namespace.test.js: prefix/suffix stamping tests keyed to AC-1002-1",
+    "test/blueprint/conflicts.test.js: global-ADR conflict cases keyed to AC-1002-2 / AC-1002-3, non-conflict cases for AC-1002-4"
+  ],
+  "acIds": [
+    "AC-1002-1",
+    "AC-1002-2",
+    "AC-1002-3",
+    "AC-1002-4",
+    "AC-1002-5",
+    "AC-1002-6",
+    "AC-1002-7",
+    "AC-1002-8",
+    "AC-1002-9",
+    "AC-1002-10"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "dependsOnFbsIds": ["FBS-016"],
+  "domain": "cli",
+  "estimatedSize": "medium",
+  "riskLevel": "medium",
+  "notes": "Prototype-unknown #1 (design-brief.md v2 §Depth for v1) — conflict-presentation ergonomics settled here as first pass; Phase 3 (REST blueprint) exposed the ergonomic friction against the real SPA+REST conflict; Phase 3.5 (w-2026-08-19-008) reshaped the message and added the supersede / diff / --resolve verbs plus the `manifest.resolutions[]` seam (rcf-schemas 0.4.5). Ownership-via-manifest-record rewrite landed separately in w-2026-08-19-005.",
+  "createdAt": "2026-08-18T22:56:02.353Z",
+  "updatedAt": "2026-08-18T22:56:02.353Z"
+}

package/rcf/fbs/fbs-018.json

@@ -0,0 +1,34 @@
+{
+  "fbsId": "FBS-018",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 18,
+  "executionStatus": "notStarted",
+  "title": "Standards ingestion: rcf define standards add + reference-by-default",
+  "summary": "Introduce a `rcf define standards <verb>` verb family (`add`, `list`) that registers standards packs on the project manifest. Reference-by-default when the source lives inside the project root; copy into `rcf/standards/<slug>/` only when the source lives outside. Manifest registration is authoritative; every add writes a `manifest.standards[]` entry per the 0.4.4 `standardsPackRecord` schema.",
+  "approach": "One dispatcher, one applier. src/cli/standards.js parses `add|list`; src/blueprint/standards.js resolves whether the source is inside or outside the project root (via node:path.relative + startsWith), copies when needed, and writes the manifest entry. Copy path is fs.cp recursive with a per-run overwrite guard (idempotent re-adds refuse to re-copy unless `--refresh` is passed; Phase 1 keeps to add-only + idempotent read, `refresh` verb deferred to Phase 3).",
+  "deliverables": [
+    "src/cli/standards.js: parseArgs + HELP + main() for add/list",
+    "src/blueprint/standards.js: registerStandardsPack(root, opts) — in-root vs out-of-root detection + optional copy + manifest.standards[] write",
+    "bin/rcf.js: `standards: standardsMain` on SUBCOMMANDS",
+    "src/cli/help.js: `standards <verb>` on the TOP_LEVEL block",
+    "test/blueprint/standards.test.js: in-root reference / out-of-root copy / idempotency cases keyed to AC-1003-1..4"
+  ],
+  "acIds": [
+    "AC-1003-1",
+    "AC-1003-2",
+    "AC-1003-3",
+    "AC-1003-4"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "dependsOnFbsIds": [],
+  "domain": "cli",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Reference-by-default is ratified decision 2 (design-brief.md v2). Copy path targets rcf/standards/<slug>/ (ratified decision 3).",
+  "createdAt": "2026-08-18T22:56:02.353Z",
+  "updatedAt": "2026-08-18T22:56:02.353Z"
+}

package/rcf/fbs/fbs-019.json

@@ -0,0 +1,33 @@
+{
+  "fbsId": "FBS-019",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 19,
+  "executionStatus": "notStarted",
+  "title": "Selective retrieval at bundle assembly (contextRequirements.standardIds)",
+  "summary": "Extend `src/build/bundle.js#assembleBundle` so its `context` section reads `contextRequirements.standardIds`. When the FBS carries an operator-authored `standardIds` array, that array is honoured verbatim. Otherwise a deterministic tag-scoring selector reads the FBS work text (title + summary + approach + notes + AC descriptions) against `manifest.standards[]` (tags + slug + summary) and returns the subset of slugs whose tags occur in the work text. The bundle's context.standardIds carries the selection; the standards' summaries render into the standards payload alongside TACs and ADRs.",
+  "approach": "The selector is a pure function in src/build/standards-selector.js — no wall clock, no random source, no network. Scoring is deterministic tag-hit counting with lowercase-normalised substring match; ties break by manifest order (standards[] is authored). The bundle assembler prefers operator-authored `contextRequirements.standardIds` when present (design principle 5 override path) and calls the selector otherwise. Empty selection is legitimate and never blocks. Phase 1 keeps the selector local and heuristic; the design brief allows a small model call, but adding an LLM dependency to a pure projection is out of scope for the mechanism landing — the heuristic satisfies the ACs and the seam is where a smarter selector plugs in.",
+  "deliverables": [
+    "src/build/standards-selector.js: selectStandards(fbs, standards) — deterministic tag-hit scoring returning the ordered subset of slugs",
+    "src/build/bundle.js: contextRequirements.standardIds hosts operator override or selector output; standards payload rendered into context alongside tacs/adrs",
+    "test/build/standards-selector.test.js: deterministic-selection cases keyed to AC-1004-1, AC-1004-3, AC-1004-4",
+    "test/build/bundle-standards.test.js: bundle-shape cases (default + override) keyed to AC-1004-1, AC-1004-2"
+  ],
+  "acIds": [
+    "AC-1004-1",
+    "AC-1004-2",
+    "AC-1004-3",
+    "AC-1004-4"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "dependsOnFbsIds": ["FBS-018"],
+  "domain": "build",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Ratified decision 4 (agentic at bundle-assembly time, operator override supported). Heuristic-tag selector satisfies the deterministic ACs; a smarter selector plugs into the same seam without touching the bundle assembler.",
+  "createdAt": "2026-08-18T22:56:02.353Z",
+  "updatedAt": "2026-08-18T22:56:02.353Z"
+}

package/rcf/requirements/req-008.json

@@ -4,7 +4,7 @@
   "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.",
-  "rationale": "The five-run rcf-persona-testing programme (concluded 2026-07-20) found the tool builds excellently at every level but its own loop missed a ship-blocking or user-facing defect in three of five runs, with a single root cause: the deploy runtime is absent from the loop. It is absent from elicitation (runs 03/04 chose Cloudflare-incompatible stacks a CF-only holder cannot host, run 03 silently) and absent from verification (run 05 shipped a production auth 500 while 89/89 tests were green and the tool claimed a live-Worker verification its E2E never ran). The target user cannot diagnose 'wrong stack for your host' or 'verified against the wrong runtime', so the method itself must foreclose both. These are Tier-1 hardening fixes to make the base offering usable now, while the productised independent verification gate (rcf-verify-lite) is built separately.",
+  "rationale": "The five-run rcf-persona-testing programme (concluded 2026-07-20) found the tool builds excellently at every level but its own loop missed a ship-blocking or user-facing defect in three of five runs, with a single root cause: the deploy runtime is absent from the loop. It is absent from elicitation (runs 03/04 chose Cloudflare-incompatible stacks a CF-only holder cannot host, run 03 silently) and absent from verification (run 05 shipped a production auth 500 while 89/89 tests were green and the tool claimed a live-Worker verification its E2E never ran). The target user cannot diagnose 'wrong stack for your host' or 'verified against the wrong runtime', so the method itself must foreclose both. These are Tier-1 hardening fixes to make the base offering usable now, while the productised independent verification gate (rcf verify-lite) is built separately.",
   "reqId": "REQ-008",
   "prdId": "PRD-001",
   "title": "Deploy-aware, runtime-honest build guidance",

package/rcf/requirements/req-009.json

@@ -2,11 +2,11 @@
   "reqId": "REQ-009",
   "prdId": "PRD-001",
   "title": "Umbrella CLI: verify as a first-class subcommand",
-  "description": "Post 0.7.1 packaging consolidation the RCF Lite suite ships as one npm package with one unified `rcf` CLI. The adversarial ship-gate verifier that used to live behind its own `rcf-verify` bin is mounted as `rcf verify <run|report|provision|cleanup|mcp>` on that unified CLI. The pre-existing `rcf-verify` bin remains as a transition-grace alias that dispatches through the same handlers, deprecated in favour of `rcf verify`. Behaviour of each verify verb is unchanged; only the invocation form gains a canonical route.",
+  "description": "Post 0.7.1 packaging consolidation the RCF Lite suite ships as one npm package with one unified `rcf` CLI. The adversarial ship-gate verifier that used to live behind its own `rcf verify` bin is mounted as `rcf verify <run|report|provision|cleanup|mcp>` on that unified CLI. The pre-existing `rcf verify` bin remains as a transition-grace alias that dispatches through the same handlers, deprecated in favour of `rcf verify`. Behaviour of each verify verb is unchanged; only the invocation form gains a canonical route.",
   "category": "functional",
   "domain": "cli",
   "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.",
+  "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": [
     "packaging",
     "cli",

package/rcf/requirements/req-010.json

@@ -0,0 +1,20 @@
+{
+  "createdAt": "2026-08-18T22:54:27.031Z",
+  "updatedAt": "2026-08-18T22:57:45.660Z",
+  "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",
+  "title": "Blueprint library mechanism (composition, standards, selective retrieval)",
+  "category": "functional",
+  "domain": "cli",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "none"
+    ],
+    "reason": "keyword-scan",
+    "classifiedAt": "2026-08-18T22:54:27.048Z"
+  }
+}

package/rcf/test-suites/PENDING.md

@@ -15,8 +15,8 @@ a genuine feature gap - was closed by porting the parallel-safe tier
 computation from the full RCF platform into the build queue and binding
 TC-014-independent-items-share-tier to it.
 
-Status: **76 bound / 0 pending** of 76 ACs. `rcf coverage --strict`
-exits 0, and CI runs `rcf validate` and `rcf coverage --strict` as
+Status: **76 bound / 0 pending** of 76 ACs. `rcf audit coverage --strict`
+exits 0, and CI runs `rcf define validate` and `rcf audit coverage --strict` as
 required steps, so a new uncovered AC or a non-resolving testPointer
 fails the build. A future genuine gap gets a row here (AC id, US, kind,
 what a sufficient test must assert, nearest existing test) until its

package/rcf/test-suites/ts-004.json

@@ -37,7 +37,7 @@
       "acId": "AC-202-1",
       "description": "the view serves from a local server process and never writes files to disk",
       "status": "pending",
-      "testPointer": "test/view/cli.test.js::rcf view never writes any files to disk (regression against static mode)"
+      "testPointer": "test/view/cli.test.js::rcf audit view never writes any files to disk (regression against static mode)"
     }
   ],
   "status": "draft"

package/rcf/test-suites/ts-006.json

@@ -15,21 +15,21 @@
       "acId": "AC-301-2",
       "description": "reading an unknown id exits 2 with a structured not-found usage error",
       "status": "pending",
-      "testPointer": "test/cli/read.test.js::rcf read UNKNOWN-999 exits 2 (usage, unknown id)"
+      "testPointer": "test/cli/read.test.js::rcf define read UNKNOWN-999 exits 2 (usage, unknown id)"
     },
     {
       "id": "TC-006-read-reports-valid",
       "acId": "AC-301-1",
       "description": "read returns the body on stdout and reports the document valid against its schema on stderr",
       "status": "pending",
-      "testPointer": "test/cli/read.test.js::rcf read REQ-001 returns the body and reports it valid against its schema (AC-301-1)"
+      "testPointer": "test/cli/read.test.js::rcf define read REQ-001 returns the body and reports it valid against its schema (AC-301-1)"
     },
     {
       "id": "TC-006-read-invalid-content-plus-errors",
       "acId": "AC-301-3",
       "description": "read on an invalid-but-present document returns the content together with the validation errors",
       "status": "pending",
-      "testPointer": "test/cli/read.test.js::rcf read on an invalid-but-present document returns the content together with the validation errors (AC-301-3)"
+      "testPointer": "test/cli/read.test.js::rcf define read on an invalid-but-present document returns the content together with the validation errors (AC-301-3)"
     }
   ],
   "status": "draft"

package/rcf/test-suites/ts-008.json

@@ -16,7 +16,7 @@
       "acId": "AC-303-1",
       "description": "a valid update persists the change and advances updatedAt on disk",
       "status": "pending",
-      "testPointer": "test/cli/update.test.js::rcf update REQ-001 --set title=X changes the title and bumps updatedAt"
+      "testPointer": "test/cli/update.test.js::rcf define update REQ-001 --set title=X changes the title and bumps updatedAt"
     },
     {
       "id": "TC-008-invalid-update-refused",
@@ -30,7 +30,7 @@
       "acId": "AC-303-3",
       "description": "update on a nonexistent id returns a structured not-found error naming the id and writes nothing",
       "status": "pending",
-      "testPointer": "test/cli/update.test.js::rcf update REQ-999 returns a structured not-found error and writes nothing (AC-303-3)"
+      "testPointer": "test/cli/update.test.js::rcf define update REQ-999 returns a structured not-found error and writes nothing (AC-303-3)"
     }
   ],
   "status": "draft"

package/rcf/test-suites/ts-009.json

@@ -17,7 +17,7 @@
       "acId": "AC-304-1",
       "description": "delete without cascade refuses with exit 4 naming dependents",
       "status": "pending",
-      "testPointer": "test/cli/delete.test.js::rcf delete REQ-001 without --cascade refuses with exit 4"
+      "testPointer": "test/cli/delete.test.js::rcf define delete REQ-001 without --cascade refuses with exit 4"
     },
     {
       "id": "TC-009-cascade-removes-subtree",
@@ -31,7 +31,7 @@
       "acId": "AC-304-3",
       "description": "deleting an unreferenced leaf removes the file with exit 0 on a still-valid tree",
       "status": "pending",
-      "testPointer": "test/cli/delete.test.js::rcf delete leaf ADR-001 removes the file (exit 0)"
+      "testPointer": "test/cli/delete.test.js::rcf define delete leaf ADR-001 removes the file (exit 0)"
     }
   ],
   "status": "draft"