@sdd-method/author-cli 0.2.0 → 0.4.0

package/dist/lib/api-surface/__fixtures__/serverless-repo/serverless/serverless.yml

@@ -1,15 +1,15 @@
 {{- $vpc := .Values.Vpc | default "true" -}}
-service: demo-sms
+service: northwind-receipts
 provider:
   name: aws
   runtime: nodejs18.x
 functions:
-  sendSms:
-    handler: src/sendSms.handler
+  sendReceipt:
+    handler: src/sendReceipt.handler
     events:
       - http:
           method: POST
-          path: /sms/
+          path: /receipts/
 resources:
   Resources:
     OutboundQueue:

package/dist/lib/api-surface/analyzers/serverless.js

@@ -2,7 +2,7 @@ import { parse as parseYaml } from "yaml";
 import { allBySuffix } from "../file-set.js";
 // node-serverless analyzer.
 //
-// The serverless.yml in these repos is Go/Helm-templated (`{{ ... }}`, `${self:...}`, `${opt:...}`).
+// The serverless.yml in some repos is Go/Helm-templated (`{{ ... }}`, `${self:...}`, `${opt:...}`).
 // Strategy: sanitise the template directives so the YAML parser succeeds, then read functions/events
 // /provider/resources structurally. If the sanitised doc still won't parse, fall back to a line-based
 // regex sweep so we never come back empty on a real (messy) file.

package/dist/lib/api-surface/analyzers/spring.js

@@ -182,7 +182,7 @@ async function collectConfigInfra(fileSet, sharedInfra) {
     }
 }
 function stripVar(v) {
-    // Keep env-var placeholders readable: `${GATEWAY_KAFKAPRODUCERTOPIC}` → GATEWAY_KAFKAPRODUCERTOPIC.
+    // Keep env-var placeholders readable: `${KAFKA_TOPIC}` → KAFKA_TOPIC.
     const m = v.match(/\$\{([^:}]+)/);
     if (m)
         return m[1];

package/dist/lib/briefing/render.js

@@ -1,6 +1,5 @@
 /**
- * Renderer for the briefing-layer templates per ADR 0148 + Phase 4 of
- * `adopt-agent-instructions-briefing-layer.md`.
+ * Renderer for the briefing-layer templates per ADR 0148.
  *
  * Templates ship via the method baseline bundle and land at
  * `<target>/orchestration/templates/briefing/...` after sync's

package/dist/lib/briefing/variables.js

@@ -1,6 +1,5 @@
 /**
- * Variable resolution for the briefing layer per ADR 0148 §4.1 + the
- * Phase 4 setup notes in `adopt-agent-instructions-briefing-layer.md`.
+ * Variable resolution for the briefing layer per ADR 0148 §4.1.
  *
  * The four variables are sourced from target-repo state:
  *

package/dist/lib/catalogue/archetype/wireframe.js

@@ -343,7 +343,7 @@ function humaniseName(name, prefixes) {
     let s = name;
     for (const p of prefixes) {
         // Strip only at a PascalCase boundary (next char uppercase) so a short prefix
-        // like "St" peels "StLayout" → "Layout" but never "Status" → "atus".
+        // like "Ui" peels "UiLayout" → "Layout" but never "Uint" → "nt".
         if (s.length > p.length && s.startsWith(p) && /[A-Z]/.test(s.charAt(p.length))) {
             s = s.slice(p.length);
             break;

package/dist/lib/catalogue/build.js

@@ -4,8 +4,7 @@
  * Per ADR 0134 §4.6, the canonical builder reads method-defined declarative
  * inputs and emits `catalogues/*.csv` matching the canonical schema.
  *
- * This is Phase 1 of the canonical-builder implementation per
- * adopt-canonical-catalogue-builder.md Step F. Phase 1 ships:
+ * The orchestrator provides:
  *   - manifest loading + schema-version compat check,
  *   - schema loading,
  *   - headers-only emission for every catalogue declared in the schema,
@@ -13,9 +12,9 @@
  *   - findings + row-count reporting.
  *
  * Per-source discoverers (domains, repos, services, capabilities, features,
- * etc.) land in subsequent phases. Until then the builder produces a valid
- * but empty `catalogues/` directory — useful as a smoke test that the
- * infrastructure works end-to-end on any SDD repo.
+ * etc.) live in `builders/`. With none of their inputs present the builder
+ * still produces a valid but empty `catalogues/` directory — useful as a
+ * smoke test that the infrastructure works end-to-end on any SDD repo.
  */
 import { checkCapabilityServicePopulation } from "./population-checks.js";
 import { basename, join, relative, resolve } from "node:path";
@@ -73,8 +72,7 @@ export async function runCatalogueBuild(inputs, write) {
     // more than one walker; each walker's own seen-set only dedupes intra-walker.
     // This union-dedupes identical rows across sources and hard-fails the build
     // on same-PK/different-payload, so the per-SDD catalogue is set-correct over
-    // its declared PK before aggregation ever sees it. See
-    // `coordination/feature-edge-cross-source-duplicate-coordination.md`.
+    // its declared PK before aggregation ever sees it.
     const dedupe = dedupeKeyedTables(schema, rowsByCatalogue, findings);
     // 3b. Population collapse, before anything is overwritten. A whole score family can
     // vanish while its catalogue keeps other rows: one estate's 71 traceability-manifest
@@ -293,7 +291,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     // is the mistake M-ADR 0191 §4.1 / the 0.92.1 membership move corrected.
     out.set("application_data_plane_bindings", buildApplicationDataPlaneBindings({ manifest, findings }));
     out.set("application_data_plane_deviations", buildApplicationDataPlaneDeviations({ manifest, findings }));
-    // Conformance coverage (M-ADR 0191 §4.3 WS4) — the product's declared coverage
+    // Conformance coverage (M-ADR 0191 §4.3) — the product's declared coverage
     // of / deviations from its archetype's conformance expectations. The
     // conformance GATE that reads these runs at aggregation tier (like the binding
     // overlay), where the reference-architecture `conformance` tags resolve.
@@ -389,8 +387,8 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     // Slug → capability-id aliases for feature-grounding path resolution.
     // The grounding walker derives a capability slug from the design dir
     // name (docs/domains/<dom>/design/<slug>/), but a capability's declared
-    // id may legitimately differ from its path slug — e.g. design/alerts-rules
-    // maps to id "alerts-rules-engine". Map each capability's spec +
+    // id may legitimately differ from its path slug — e.g. design/gift-card-rules
+    // maps to id "gift-card-rules-engine". Map each capability's spec +
     // feature-directory basename to its id so the walker resolves these
     // without forcing a directory rename. Only non-identity, non-colliding
     // slugs are aliased (first manifest wins).
@@ -412,7 +410,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     const knownServiceIds = new Set(services.map((s) => String(s["id"])));
     // C4 L1 external systems are built here (rather than at step 15b) so the
     // capability_service builder can categorise unresolved `services[].id`
-    // findings — an id naming a known external system (authzed, workos, …) is
+    // findings — an id naming a known external system (an auth provider, an identity SaaS, …) is
     // a convention finding, not an orphan. The rows are emitted at their usual
     // place in step 15b; only the computation is hoisted.
     const c4External = await buildC4ExternalSystems({
@@ -593,8 +591,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     // emit even when every grounding row collides on feature id with an
     // earlier source (`feature-tree` / `feature-spec`). Pre-0.30.2 the
     // conditional above gated feature_repo on the row emission, dropping
-    // the edges in the all-collide case. Fixed per
-    // `coordination/feature-grounding-collision-edges-coordination.md`.
+    // the edges in the all-collide case. Fixed.
     out.set("feature_repo", [
         ...(out.get("feature_repo") ?? []),
         ...grounding.featureRepoRows,
@@ -635,8 +632,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     // emit even when every capability-spec row collides on feature id with an
     // earlier source. Pre-fix the conditional above gated these edges on the
     // row emission, dropping them in the all-collide case (same two-level bug
-    // feature-grounding had pre-0.30.2). Fixed per
-    // `coordination/capability-spec-collision-edges-coordination.md`.
+    // feature-grounding had pre-0.30.2). Fixed.
     out.set("feature_repo", [
         ...(out.get("feature_repo") ?? []),
         ...capabilitySpec.featureRepoRows,
@@ -646,10 +642,9 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         ...capabilitySpec.featureServiceRows,
     ]);
     // 10b-ter. feature_service — application-product Feature Services table.
-    // WS0c (catalogue-coverage-invariants.md) found this table authored and
-    // unread: 12 SDDs carry a populated `## Feature Services` table in
-    // feature-tree.md, 155 declared rows / 385 feature×service pairs, 0
-    // emitted, because the two extractors above only ever walk
+    // A coverage audit found this table authored and unread: 12 SDDs carry a
+    // populated `## Feature Services` table in feature-tree.md, 155 declared
+    // rows / 385 feature×service pairs, 0 emitted, because the two extractors above only ever walk
     // feature-grounding.md / capability-spec paths (platform / integration
     // profiles). Runs last so knownFeatureIds reflects every prior source.
     // No `source` column exists on feature_service (schema has none), so rows
@@ -1157,8 +1152,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
     // declared (repo-config depends_on) and derived (per-component sharedLibraries).
     out.set("repo_dependency", await buildRepoDependencies({ sddPath, configs: reposResult.configs, knownRepoIds: knownRepoIdsFinal, findings }));
     // 15. C4 systems + containers + components (L1 + L2 + L3). The L3 walker
-    // shipped per `coordination/c4-l3-walker-and-path-convention-coordination.md`
-    // (method governance, 2026-05-29) — forward-method authoring path reading
+    // is the forward-method authoring path reading
     // `c4-l3-*.mermaid.md` files alongside the L2 layout. The earlier Path-B
     // deferral assumed reverse-method code-walking; this walker is the
     // forward-method analogue, granularity-agnostic (per-container or
@@ -1218,7 +1212,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         externalIdByEntryId: c4External.idByEntryId,
         containerIdByEntryId,
     }));
-    // container_dependency member tier (F19): the C4-correct authoring —
+    // container_dependency member tier: the C4-correct authoring —
     // Rel(container_a, container_b) — emits its edge here; the aggregator's
     // adjudication leg merges rather than being the only source.
     out.set("container_dependency", await buildContainerDependency({
@@ -1228,7 +1222,7 @@ async function collectRows(schema, manifest, findings, sddPath, snapshotStore) {
         containerIdByEntryId,
         externalIdByEntryId: c4External.idByEntryId,
     }));
-    // persona_container per M-ADR 0189 F26 §3 (schema 2.34.0) — the
+    // persona_container per M-ADR 0189 (schema 2.34.0) — the
     // L2-granularity companion to persona_c4system.
     out.set("persona_container", await buildPersonaContainer({
         sddPath,

package/dist/lib/catalogue/builders/application-conformance-coverage.js

@@ -1,4 +1,4 @@
-// application_conformance_coverage builder (M-ADR 0191 §4.3 overlay, WS4).
+// application_conformance_coverage builder (M-ADR 0191 §4.3 overlay).
 //
 // Emits one row per conformance tag the product declares about its archetype's
 // conformance expectations: `status=covered` (its suite exercises the tag) or

package/dist/lib/catalogue/builders/c4-components.js

@@ -4,9 +4,8 @@
 //   - docs/platform/diagrams/c4-l3-*.mermaid.md
 //   - docs/c4-l3-*.mermaid.md (per-product, application/integration SDDs)
 //
-// Mirrors c4-containers.ts at one level down. Source convention per
-// `coordination/c4-l3-walker-and-path-convention-coordination.md`
-// (method governance, 2026-05-29). The walker is granularity-agnostic — both
+// Mirrors c4-containers.ts at one level down, reading the method's
+// `c4-l3-*.mermaid.md` source convention. The walker is granularity-agnostic — both
 // per-container files (one `Container_Boundary` block per file) and
 // per-domain rollup files (multiple `Container_Boundary` blocks per file)
 // produce identical row output. Adopters pick the file shape that suits
@@ -44,8 +43,8 @@ export async function buildC4Components(inputs) {
         return [];
     // Index containers by suffix-after-system-prefix for slug-of-name matching.
     // c4_containers.id shape per c4-containers.ts:93 is `{systemId}-{slug}`.
-    // The suffix-match lets us resolve `Container_Boundary(_, "Asset Twin")`
-    // (slug = "asset-twin") to `{anything}-asset-twin`.
+    // The suffix-match lets us resolve `Container_Boundary(_, "Asset Register")`
+    // (slug = "asset-register") to `{anything}-asset-register`.
     const containerBySuffix = new Map();
     for (const row of inputs.c4ContainerRows) {
         const id = String(row["id"] ?? "");

package/dist/lib/catalogue/builders/c4-containers.js

@@ -76,7 +76,7 @@ export async function buildC4Containers(inputs) {
             }
             const collapsed = rowById.get(id);
             if (collapsed !== undefined) {
-                // F21: dedup-by-id is first-seen and was SILENT — two containers
+                // Dedup-by-id is first-seen and was SILENT — two containers
                 // sharing a display name collapse into one row, and every edge
                 // referencing either binds to the merge. When their technology
                 // strings flatly contradict, that is two different things wearing
@@ -85,7 +85,7 @@ export async function buildC4Containers(inputs) {
                     inputs.findings.add("convention", `c4_containers: two containers share the display name "${entry.name}" with contradictory ` +
                         `technologies ("${String(collapsed["technology"])}" vs "${entry.technology}") — collapsed ` +
                         `into one row "${id}" — either different referents wearing one name (rename one) ` +
-                        `or a misused technology field on a shared reference (correct it) (F21)`);
+                        `or a misused technology field on a shared reference (correct it)`);
                 }
                 continue;
             }
@@ -218,7 +218,7 @@ function slugify(s) {
         .replace(/^-+|-+$/g, "");
 }
 /**
- * F21: two technology strings flatly contradict when both are present and
+ * Two technology strings flatly contradict when both are present and
  * share no token — ".NET 6 (in Kestrel)" vs "Java" needs no NLP. Absent or
  * overlapping strings are NOT a contradiction (silence, not a guess).
  */

package/dist/lib/catalogue/builders/c4-entity-rollups.js

@@ -10,7 +10,7 @@
 //   c4_container_entity ⋈ c4_containers.system_id
 //   → aggregate (system_id, entity_id) with container_count.
 //
-// Both handle empty inputs gracefully (an adopter's pre-lock state has zero
+// Both handle empty inputs gracefully (an adopter's state before agreement has zero
 // service_entity edges → both roll-up outputs are empty; no errors).
 export function buildC4ContainerEntity(inputs) {
     // Index containers by service_id.

package/dist/lib/catalogue/builders/c4-external-systems.js

@@ -134,7 +134,7 @@ function parseExternals(content) {
 /**
  * Every C4 diagram file an SDD can carry (all L1 candidates incl.
  * domain-scoped, plus every L2), scope-tagged. Shared with
- * system-external-dependency (F11c: that builder kept a private,
+ * system-external-dependency (that builder kept a private,
  * pre-0.30.1-ordered copy MISSING the domain-scoped path — the fourth
  * divergent copy of this list, and a silent drop inside adjudication:
  * a Rel in a domain-scoped L1 was never harvested, so a converted

package/dist/lib/catalogue/builders/c4-l1-candidates.js

@@ -5,7 +5,7 @@
 // Under federation a sibling SDD typically carries a syndicated copy of the
 // platform-root's L1 at `docs/platform/diagrams/c4-l1-context.mermaid.md`
 // for cross-reference, AND may author its own L1. The sibling's own L1 must
-// outrank the syndicated copy — and, per F7/WS8, the syndicated copy must
+// outrank the syndicated copy — and the syndicated copy must
 // not source a sibling's identity AT ALL: on two measured estates roughly
 // half of all systems carried the platform's name and description because
 // the fallback fired for every sibling that authored no own L1. A sibling

package/dist/lib/catalogue/builders/capabilities.js

@@ -146,12 +146,12 @@ export async function buildCapabilities(inputs) {
         if (specRel) {
             usedSpecPaths.add(specRel);
             const specAbs = join(inputs.sddPath, specRel);
-            // F22: an emitted spec_path must exist — a dangling path silently
+            // An emitted spec_path must exist — a dangling path silently
             // produced an empty name/description while the column pointed at
             // nothing. The row still emits (the capability is declared); the
             // dangle is loud.
             if (!(await fileExists(specAbs))) {
-                inputs.findings.add("coverage", `${m.relPath}: capability "${cap.id}" declares capability_spec "${specRel}" which does not exist — name/description left empty, spec_path emitted dangling (F22)`);
+                inputs.findings.add("coverage", `${m.relPath}: capability "${cap.id}" declares capability_spec "${specRel}" which does not exist — name/description left empty, spec_path emitted dangling`);
             }
             // M-ADR 0211 §4.2 — the manifest is a declaration and its row is correct. The finding
             // fires ONLY on a CONTRADICTION between two declaration surfaces: this manifest

package/dist/lib/catalogue/builders/capability-edges.js

@@ -5,7 +5,7 @@
 // canonical schema declares capability_id and the target column as
 // required FKs — so each builder skips entries whose target doesn't
 // resolve in the known-target set passed in.
-// capability_service is the exception (F4, schema 2.29.0): its service_id
+// capability_service is the exception (schema 2.29.0): its service_id
 // FK is external, and an entry marked `owner_sdd:` declares a cross-SDD
 // reference — the edge is emitted despite not resolving locally and is
 // validated hard at aggregation against the owning sibling's rows.
@@ -40,7 +40,7 @@ export function buildCapabilityService(inputs) {
             if (!inputs.knownServiceIds.has(sid)) {
                 // Never drop silently (61 missing edges sat invisible in the field
                 // until a manual sweep). Resolution order:
-                //  - `owner_sdd:` marked (F4, schema 2.29.0) — a DECLARED cross-SDD
+                //  - `owner_sdd:` marked (schema 2.29.0) — a DECLARED cross-SDD
                 //    reference (e.g. the service moved to a sibling at a carve).
                 //    Emit the edge; the external FK logs it and aggregation
                 //    validates it hard against the sibling's rows.
@@ -174,7 +174,7 @@ export function buildCapabilityContract(inputs) {
             const contractId = resolveContractPath(path, inputs.contractIdByPath);
             if (contractId === "") {
                 // Never drop silently. This guard dropped every unresolvable entry with no
-                // trace until WS2 of the coverage-invariants work measured it: 62 of 188
+                // trace until it was measured: 62 of 188
                 // declared entries across two estates, and NOT ONE of them dangling — every
                 // one named a real artefact. So the resolution failure is the interesting
                 // fact, and the reader needs it.
@@ -236,7 +236,7 @@ function resolveContractPath(path, index) {
     const direct = index.get(cleaned);
     if (direct !== undefined)
         return direct;
-    // Suffix: last two parts (e.g. "asset/asset-twin.yaml")
+    // Suffix: last two parts (e.g. "asset/asset-register.yaml")
     const parts = cleaned.split(sep);
     if (parts.length >= 2) {
         const suffix = parts.slice(-2).join("/");

package/dist/lib/catalogue/builders/capability-spec-walker.js

@@ -6,7 +6,7 @@
  *
  *     | Feature | Implementation | Grounding Doc |
  *     |---|---|---|
- *     | `alerts-module` | `alerts` Vuex module + `src/components/alerts` | docs/.../feature-grounding.md |
+ *     | `banners-module` | `banners` store module + `src/components/banners` | docs/.../feature-grounding.md |
  *
  * Path convention (per ADR 0145 §4.3):
  *   - platform-profile: `docs/domains/<dom>/product/<capability>.md`
@@ -67,8 +67,8 @@ export async function findCapabilitySpecFiles(sddPath) {
  * Resolve the capability id from a capability spec file's absolute
  * path. Returns the filename stem (`.md` stripped).
  *
- *   docs/domains/applications/product/alerts-and-notifications.md
- *     → "alerts-and-notifications"
+ *   docs/domains/storefront/product/banners-and-toasts.md
+ *     → "banners-and-toasts"
  */
 export function capabilityIdFromSpecPath(absPath, sddPath) {
     const rel = relative(sddPath, absPath);

package/dist/lib/catalogue/builders/container-dependency.js

@@ -1,18 +1,18 @@
-// container_dependency member-tier builder — F19 (M-ADR 0189 §4.4/F17
-// follow-on, schema 2.33.1).
+// container_dependency member-tier builder (M-ADR 0189 §4.4 follow-on,
+// schema 2.33.1).
 //
-// F17 made the aggregator's adjudication leg the ONLY source of
+// Container conversion made the aggregator's adjudication leg the ONLY source of
 // container_dependency rows — populated exactly when an author
 // mis-declared an internal container as `System_Ext`. An author who wrote
 // the C4-correct thing instead — `Rel(container_a, container_b)` between
 // two `Container(...)` nodes — got no row and no finding: the metamodel
 // rewarded the wrong authoring and silently discarded the right one,
-// inverting the incentive F17 was built to create.
+// inverting the incentive container conversion was built to create.
 //
 // This builder harvests intra-SDD container→container `Rel(...)` lines:
 // both endpoints must resolve to local containers (via the entry-id map
 // the c4-containers builder fills), neither may be external, and the
-// syndicated platform L1 is skipped for non-root SDDs (F14 — its Rel
+// syndicated platform L1 is skipped for non-root SDDs (its Rel
 // lines are the platform's statements). The adjudication leg then MERGES
 // into a catalogue that already has content, rather than being its only
 // source; dedup is by id, member rows first.
@@ -34,7 +34,7 @@ export async function buildContainerDependency(inputs) {
         if (syndicated && !isRoot)
             continue;
         const content = await readFile(abs, "utf-8");
-        // F26: per-file Person entries — the endpoint class that has no edge
+        // Per-file Person entries — the endpoint class that has no edge
         // catalogue to a container.
         const personEntries = new Set();
         for (const raw of content.split(/\r?\n/)) {
@@ -47,7 +47,7 @@ export async function buildContainerDependency(inputs) {
             if (!m)
                 continue;
             const [, fromEntry, toEntry, label] = m;
-            // F20: resolve the container FIRST. Both maps are SDD-wide, and an
+            // Resolve the container FIRST. Both maps are SDD-wide, and an
             // entry-id that resolves to a local container IS a container —
             // whatever a sibling diagram in the same SDD called it. The old
             // external-guard-first order silently discarded a true edge whenever
@@ -60,10 +60,10 @@ export async function buildContainerDependency(inputs) {
             const from = inputs.containerIdByEntryId.get(fromEntry ?? "");
             const to = inputs.containerIdByEntryId.get(toEntry ?? "");
             if (from === undefined || to === undefined) {
-                // F26: a Rel the builder RESOLVES but cannot catalogue must say so
-                // — following F23's rename prescription turned exactly this
+                // A Rel the builder RESOLVES but cannot catalogue must say so
+                // — following the rename prescription turned exactly this
                 // silence into a two-edge delete. Classification is
-                // container-first (F20), then external, then Person (file-local);
+                // container-first, then external, then Person (file-local);
                 // anything unknown stays silent (no confident classification, no
                 // guess). Pairs with a home elsewhere (one-external →
                 // system_external_dependency; person→system → persona_c4system)
@@ -83,7 +83,7 @@ export async function buildContainerDependency(inputs) {
                 // resolve) — only the pairs with NO home remain findings here.
                 if (pair === "external→external") {
                     inputs.findings.add("convention", `container_dependency: Rel(${fromEntry}, ${toEntry}${label ? `, "${label}"` : ""}) resolves as ` +
-                        `${pair} — no catalogue holds that pair; the relationship is recorded nowhere (F26)`);
+                        `${pair} — no catalogue holds that pair; the relationship is recorded nowhere`);
                 }
                 continue;
             }
@@ -110,8 +110,8 @@ export async function buildContainerDependency(inputs) {
     return rows;
 }
 /**
- * F21 referent-collision check — corroborate on an INDEPENDENT evidence
- * channel, never the one under guard. The F20-era version decided referent
+ * Referent-collision check — corroborate on an INDEPENDENT evidence
+ * channel, never the one under guard. An earlier version decided referent
  * identity by comparing display names — the same evidence class the guard
  * existed to distrust — so it was circular: the estate sweep that declared
  * different-referent collisions absent USED this predicate and could not
@@ -144,18 +144,17 @@ export function reportEntryIdReferentCollisions(inputs) {
         if (externalTech !== "" && techContradicts(containerTech, externalTech)) {
             inputs.findings.add("convention", `c4 diagrams: entry-id "${entryId}" is declared Container ("${containerName}", "${containerTech}") and ` +
                 `System_Ext ("${externalName}", "${externalTech}") with contradictory technologies — ` +
-                `different referents wearing one id; the container interpretation wins for Rel edges — rename one entry-id to split them (F21)`);
+                `different referents wearing one id; the container interpretation wins for Rel edges — rename one entry-id to split them`);
             continue;
         }
         if (externalTech !== "")
             continue; // corroborating tech — same referent, silent
-        // F23: System_Ext carries no technology argument, so the primary
+        // System_Ext carries no technology argument, so the primary
         // dual-use case has NO independent evidence channel — measured: 0 of
         // 109 external rows carry a technology. Weak corroboration is
         // accepted (the external's description mentioning a container-tech
         // token); otherwise the guard says what it cannot do, loudly. A
-        // dual-use entry-id buys nothing post-F20 (the container always wins
-        // for Rel edges) and risks a silent different-referent bind — the
+        // dual-use entry-id buys nothing once the container is resolved first for Rel edges and risks a silent different-referent bind — the
         // retirement is a rename, cheap because entry-ids are diagram-local
         // and row identity derives from the display name.
         const externalDesc = inputs.externalDescByEntryId.get(entryId) ?? "";
@@ -175,9 +174,9 @@ export function reportEntryIdReferentCollisions(inputs) {
             `("${externalName}") with no independent evidence to adjudicate referent identity — System_Ext ` +
             `carries no technology field; cannot corroborate, cannot contradict. Rename one entry-id to split ` +
             `the namespaces — but check first whether the dual use is load-bearing: if Rel edges exist only via ` +
-            `the Container reading, a rename orphans them (they will surface as F26 findings); in that case ` +
+            `the Container reading, a rename orphans them (they will surface as unroutable-Rel findings); in that case ` +
             `annotate the System_Ext description with the technology instead, so weak corroboration can silence ` +
-            `this honestly (F23/F26)`);
+            `this honestly`);
     }
 }
 //# sourceMappingURL=container-dependency.js.map

package/dist/lib/catalogue/builders/contracts.js

@@ -27,12 +27,11 @@ const KIND_SPECS = [
     { subdir: "avro", extensions: [".avsc"], kind: "event" },
     // `authz` — authorization/policy schemas (SpiceDB `.zed` and equivalents).
     //
-    // Added because an adopter's contract lock-in gate APPROVED two `.zed` schemas
-    // as contracts ("all 11 contracts lock"), while `kind` had no member able to
-    // represent them — so the catalogue could not hold an artefact the method's own
-    // gate had certified. That gate had already recorded the tension itself, passing
-    // SpiceDB "with-waiver on rubric-fit grounds"; this closes the same gap one
-    // layer down.
+    // Added because a contract agreement gate can approve `.zed` schemas as
+    // contracts while `kind` had no member able to represent them — so the
+    // catalogue could not hold an artefact the method's own gate had certified.
+    // Such a gate records the tension itself, passing the schema with a waiver on
+    // rubric-fit grounds; this closes the same gap one layer down.
     //
     // Zero-delta when added: no estate holds an in-repo `contracts/spicedb/` tree,
     // so this discovers nothing today and exists so that a declared or migrated

package/dist/lib/catalogue/builders/data-store-mapping.js

@@ -90,8 +90,8 @@ const PERSISTENCE_KIND_RULES = [
         "event-payload",
     ],
     // Transient / in-memory state (not a system of record) — the schema's
-    // `dto` classification. Real-world values: "In-memory (Vuex)",
-    // "Transient (API response)", "Runtime (Vue plugin)".
+    // `dto` classification. Typical values: "In-memory (client store)",
+    // "Transient (API response)", "Runtime (framework plugin)".
     [/\b(in-memory|transient|ephemeral|runtime)\b/, "dto"],
 ];
 /** Cells that mean "no store", treated as empty. */
@@ -104,7 +104,7 @@ export function derivePersistenceKind(store) {
         if (re.test(s))
             return { kind, recognised: true };
     }
-    // Present but unmapped (e.g. Elasticsearch, in-memory/Vuex) → a valid
+    // Present but unmapped (e.g. Elasticsearch, in-memory client store) → a valid
     // recommended value, but flagged so the rule set can grow.
     return { kind: "other", recognised: false };
 }

package/dist/lib/catalogue/builders/edge-label-merge.js

@@ -1,4 +1,4 @@
-// F25 — one edge per node pair is the metamodel's rule (schema-stated since
+// One edge per node pair is the metamodel's rule (schema-stated since
 // 2.30.0) and it stands. The defect was the SILENCE: distinct parallel
 // labels merged first-seen-wins at member and aggregate tier, discarding
 // authored facts without a word (measured: 20 labels already lost before
@@ -14,6 +14,6 @@ export function mergeEdgeLabel(row, label, catalogue, findings) {
     row["interaction"] =
         existing === "" ? label : `${existing}; ${label}`;
     findings.add("convention", `${catalogue}: edge "${String(row["id"])}" is declared with multiple distinct labels — ` +
-        `one edge per node pair (schema rule); labels concatenated, nothing dropped (F25)`);
+        `one edge per node pair (schema rule); labels concatenated, nothing dropped`);
 }
 //# sourceMappingURL=edge-label-merge.js.map

package/dist/lib/catalogue/builders/entities-manifest.js

@@ -13,7 +13,7 @@
 // at aggregation. Profile-gating mirrors the precedent set by
 // domain-models.ts per ADR 0142 (same scope, same syndication shape).
 //
-// Behaviour (Phase Pre Step E acceptance):
+// Behaviour (ADR 0159 acceptance):
 // - For each models[] entry, derive domain_id from its `domain` field.
 //   `platform-wide` and other non-canonical hints map to empty domain_id
 //   and the entity PK uses the `_platform-wide-{slug}` sentinel prefix

package/dist/lib/catalogue/builders/entities-mermaid.js

@@ -47,7 +47,7 @@ export async function buildEntitiesFromMermaid(inputs) {
         // entity extracted from this file inherits it; absence → "".
         const fileEvidenceClass = extractFileEvidenceClass(text);
         // Within-file dedup by id is enforced inside parseFile via seen-set;
-        // cross-file dedup is enforced here (shouldn't fire in current Adopter A,
+        // cross-file dedup is enforced here (not expected to fire in a one-file-per-domain estate,
         // defensive against future authoring that splits a domain across files).
         for (const p of parsed) {
             const id = `${p.domainId}-${entitySlug(p.name)}`;
@@ -169,8 +169,8 @@ function resolveGlossaryTermBySlug(entityName, domainId, knownGlossaryIds) {
             return id;
     }
     // ADR 0165 follow-on: the glossary builder collapses multi-word term slugs
-    // (CONTAINER_MESSAGING → "...-containermessaging"), while entitySlug
-    // hyphenates ("container-messaging"), so multi-word terms miss the suffix
+    // (BASKET_MESSAGE → "...-basketmessage"), while entitySlug
+    // hyphenates ("basket-message"), so multi-word terms miss the suffix
     // match above. Reconcile boundary-insensitively (compare hyphen-stripped
     // forms), scoped to the entity's OWN domain to avoid cross-domain
     // false positives.

package/dist/lib/catalogue/builders/entity-slug.js

@@ -7,18 +7,17 @@
 // authoring resolves to a single canonical slug.
 //
 // Examples:
-//   entitySlug("OBUConfigurationTemplate")   → "obu-configuration-template"
-//   entitySlug("OBU_CONFIGURATION_TEMPLATE") → "obu-configuration-template"
+//   entitySlug("POSTerminalConfig")   → "pos-terminal-config"
+//   entitySlug("POS_TERMINAL_CONFIG") → "pos-terminal-config"
 //   entitySlug("Vehicle")                    → "vehicle"
-//   entitySlug("APIKeyRotationRecord")       → "api-key-rotation-record"
+//   entitySlug("GTINBarcodeRecord")          → "gtin-barcode-record"
 //   entitySlug("customer")                   → "customer" (lowercase Mermaid)
-//   entitySlug("accountFeatures")            → "account-features"
+//   entitySlug("basketItems")                → "basket-items"
 //
-// Phase Pre finding (research/adr-0159-prototypes/PHASE-PRE-SYNTHESIS.md):
-// without the ALLCAPS-then-Pascal rule, the Data Store Mapping table form
-// (`OBUConfigurationTemplate`) never resolves to the Mermaid form
-// (`OBU_CONFIGURATION_TEMPLATE`), breaking ~50% of expected service_entity
-// edges in Adopter A.
+// Measured finding: without the ALLCAPS-then-Pascal rule, the Data Store
+// Mapping table form (`POSTerminalConfig`) never resolves to the Mermaid form
+// (`POS_TERMINAL_CONFIG`), breaking ~50% of expected service_entity
+// edges in one reference estate.
 //
 // Acronym-run rule (ADR 0164 wave-2 follow-on): the first replace requires the
 // leading uppercase run to be >=2 chars (`[A-Z]{2,}`). A *single* leading
@@ -29,9 +28,9 @@
 // Before the >=2 rule these produced "o-auth-client" vs "oauth-client".
 // Verified zero PK churn across both reference adopters (263 + 414 entities).
 // This cannot reconcile names whose PascalCase and UPPER_SNAKE forms genuinely
-// disagree on word boundaries — e.g. "SigLink" (two words) vs "SIGLINK" (one)
-// -> "sig-link" vs "siglink". That is adopter authoring drift, resolved by
-// aligning the spellings (author `SIG_LINK`), not by this normaliser.
+// disagree on word boundaries — e.g. "KeyHub" (two words) vs "KEYHUB" (one)
+// -> "key-hub" vs "keyhub". That is adopter authoring drift, resolved by
+// aligning the spellings (author `KEY_HUB`), not by this normaliser.
 //
 // Kept local to the entity walkers to avoid affecting events / contracts /
 // capability id generation. Promote to a shared module only if a fourth

package/dist/lib/catalogue/builders/event-catalog-walker.js

@@ -80,8 +80,8 @@ export async function walkEventCatalogs(inputs) {
             const explicitId = String(e["id"] ?? "").trim();
             const name = String(e["name"] ?? "").trim();
             // Derive id: explicit id wins when present (allows future override);
-            // otherwise slug from name. Original ADR 0156 coordination doc spec:
-            // "derive `id` from `name` (slugged)". Some adopters' authoring uses
+            // otherwise slug from name, per ADR 0156: "derive `id` from `name`
+            // (slugged)". Some adopters' authoring uses
             // `name:` only (no `id:` field).
             let id;
             if (explicitId !== "") {
@@ -141,7 +141,7 @@ export async function walkEventCatalogs(inputs) {
 /**
  * Slugify an event name into an id.
  *
- * - Inserts a hyphen at camelCase boundaries (`AssetTwin` → `Asset-Twin`).
+ * - Inserts a hyphen at camelCase boundaries (`AssetRegister` → `Asset-Register`).
  * - Lowercases.
  * - Replaces any run of non-alphanumeric characters with a single hyphen.
  * - Trims leading/trailing hyphens.