@sdd-method/author-cli 0.1.0 → 0.3.0

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.

package/dist/lib/catalogue/builders/evidence-class.js

@@ -7,8 +7,8 @@
 //
 //   ```yaml
 //   evidence-class: vendor-doc
-//   vendor: workos
-//   vendor-version: workos-docs@2026-06-10
+//   vendor: acme-idp
+//   vendor-version: acme-idp-docs@2026-01-01
 //   anchors: [...]
 //   ```
 //

package/dist/lib/catalogue/builders/external-system-exemption.js

@@ -1,4 +1,4 @@
-// external_system_exemption builder — M-ADR 0189 §4.6 (gov WS15).
+// external_system_exemption builder — M-ADR 0189 §4.6.
 //
 // Emits one row per entry in `orchestration/external-system-exemptions.yaml`:
 //

package/dist/lib/catalogue/builders/feature-contract.js

@@ -7,9 +7,7 @@
 // pairs are deduplicated with a `[finding] inferred` log line recording that
 // both paths produced the same edge.
 //
-// Added in schema 2.3.0 — see catalogue-metamodel.md §"Edge catalogue status"
-// and the companion plan
-// `content/plans/document-non-catalogued-artefacts-and-add-feature-contract.md`.
+// Added in schema 2.3.0 — see catalogue-metamodel.md §"Edge catalogue status".
 export function buildFeatureContract(inputs) {
     const seen = new Map();
     // Path 1 (forward): capability_feature ⋈ capability_contract on capability_id.

package/dist/lib/catalogue/builders/feature-grounding.js

@@ -107,8 +107,7 @@ export async function buildFeatureGrounding(inputs) {
             // feature_repo and feature_service edges: emit unconditionally per
             // ADR 0143 §2 (these are the source's unique contribution; nothing
             // else carries per-row code-mapping). Pre-0.30.2 the collision skip
-            // dropped these edges too — bug fixed per
-            // `coordination/feature-grounding-collision-edges-coordination.md`.
+            // dropped these edges too — bug fixed.
             if (featureRowCollides) {
                 // ONE CHECK, TWO MEANINGS — split them, because they are not the same
                 // event and only one of them is a defect.

package/dist/lib/catalogue/builders/feature-groups.js

@@ -1,7 +1,6 @@
 // FeatureGroups discoverer — emits `feature_groups.csv` rows from
 // hierarchical `feature-tree.md` files.
 //
-// Per Q7.2 resolution (adopt-canonical-catalogue-builder.md §7.2),
 // FeatureGroups are first-class entities. This builder consumes the
 // shared `feature-tree-walker` and emits one row per H2/H3 heading
 // outside fenced code blocks.

package/dist/lib/catalogue/builders/feature-subscription-channels.js

@@ -2,9 +2,8 @@
 // `subscription_channels:` entry in any `reverse-evidence/feature-grounding-evidence.yaml`
 // file in the SDD. Added in schema 2.9.0.
 //
-// Per resolved decision §1 of `content/plans/v0-9-0-cohort-sweep-derived-bundle.md`
-// (see also `docs/method/methods/reverse/rubrics/reverse-application-evidence-quality.md`
-// per-feature slot vocabulary): `subscription_channels:` is a peer of
+// Per the per-feature slot vocabulary in
+// `docs/method/methods/reverse/rubrics/reverse-application-evidence-quality.md`: `subscription_channels:` is a peer of
 // `graphql_operations:` in the per-feature evidence shape — `graphql_operations:`
 // carries the operation names declared in the GraphQL schema; this builder
 // captures the channel/topic layer (AppSync WebSocket, Pekko WS, MQTT, SSE,

package/dist/lib/catalogue/builders/feature-tree-walker.js

@@ -162,7 +162,7 @@ const SERVICE_ID_RE = /^[a-z0-9][a-z0-9_-]*$/;
 /**
  * Parse the `## Feature Services` section of a `feature-tree.md` body (the
  * application-product authoring surface for `feature_service`, per M-ADR
- * 0157 — see WS0c of `catalogue-coverage-invariants.md`). Table shape:
+ * 0157). Table shape:
  *
  *     | Feature | Services |
  *     |---------|----------|

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

@@ -4,8 +4,8 @@
 //      Folder→capability mapping uses (a) the traceability manifest's
 //      `capability.feature_directory` field — authoritative when a
 //      capability spec uses a folder name that differs from the
-//      canonical capability_id (e.g. capability_id "alerts-rules-engine"
-//      with feature_directory pointing at "features/alerts-rules/") —
+//      canonical capability_id (e.g. capability_id "gift-card-rules-engine"
+//      with feature_directory pointing at "features/gift-card-rules/") —
 //      then (b) the folder name itself when it equals a known capability_id.
 //      id format: `{capability_id}-{feature-slug}`.
 //
@@ -26,8 +26,7 @@
 // then walker (2) (standalone specs), then walker (3) (bullets). When
 // a bullet's id is already in `seen` from a standalone spec the spec
 // wins — divergence finding fires for the bullet. This matches the
-// "standalone is more authoritative than bullet inventory" rule from
-// plan extract-feature-tree-bullets.md §1.4.
+// "standalone is more authoritative than bullet inventory" rule.
 import { readdir, readFile } from "node:fs/promises";
 import { basename, join, relative, sep } from "node:path";
 import { featureGroupId, findFeatureTreeFile, walkFeatureTree, } from "./feature-tree-walker.js";

package/dist/lib/catalogue/builders/glossary-xref.js

@@ -342,7 +342,7 @@ function collectPairs(raw) {
     return out;
 }
 function resolveTerm(raw, inputs) {
-    // Direct id (e.g. "asset-vehicle")
+    // Direct id (e.g. "stock-sku")
     if (inputs.knownGlossaryIds.has(raw))
         return raw;
     // domain:term lookup

package/dist/lib/catalogue/builders/persona-c4system.js

@@ -9,19 +9,19 @@
 // are skipped (no dangling FK). The optional interaction label comes from a
 // `Rel(person, system, "label")` line.
 //
-// `Person_Ext(...)` is discriminated by EVIDENCE, not notation (F10; F9's
-// first fix keyed on notation and broke the external-human case): the
+// `Person_Ext(...)` is discriminated by EVIDENCE, not notation (a
+// discriminator keyed on notation breaks the external-human case): the
 // notation is idiomatic both for a non-human external actor (a device) and
 // for a human legitimately outside the boundary. Whether a persona row
 // resolves is the declaration of humanity — a Person_Ext that resolves
 // emits its edge; one that doesn't is silent (a device is not an authoring
-// gap, and a typo'd human still surfaces through F8's reverse finding on
+// gap, and a typo'd human still surfaces through the reverse finding on
 // the edgeless persona row).
 //
 // `Person(...)` asserts a human, so an unresolved one stays a forward
 // coverage finding.
 //
-// Both directions report (F8, M-ADR 0157 parity + M-ADR 0133 §4.2c
+// Both directions report (M-ADR 0157 parity + M-ADR 0133 §4.2c
 // no-silent-drop): a Person with no persona row is a coverage finding
 // (forward), and a persona with no edge is a coverage finding stating WHY —
 // no system row, no identity-sourcing L1, no Person actors, or no actor
@@ -31,7 +31,7 @@ import { readFile } from "node:fs/promises";
 import { join } from "node:path";
 import { resolveIdentityL1 } from "./c4-l1-candidates.js";
 // `Person(id, "name", "desc")` / `Person_Ext(id, "name", "desc")` — the
-// _Ext capture drives the evidence discriminator (F10; see header).
+// _Ext capture drives the evidence discriminator (see header).
 const PERSON_RE = /Person(_Ext)?\s*\(\s*(\w+)\s*,\s*"([^"]+)"\s*(?:,\s*"([^"]*)")?\s*\)/;
 const REL_RE = /^(?:Bi)?Rel(?:_[A-Za-z]+)?\s*\(\s*(\w+)\s*,\s*(\w+)\s*(?:,\s*"([^"]*)")?/;
 export async function buildPersonaC4System(inputs) {
@@ -65,7 +65,7 @@ export async function buildPersonaC4System(inputs) {
         if (personaId === undefined) {
             // Person_Ext with no persona row: a device or other non-human external
             // actor — silence is correct, and a typo'd human surfaces through the
-            // reverse finding on its edgeless persona row (F10).
+            // reverse finding on its edgeless persona row.
             if (person.external)
                 continue;
             inputs.findings.add("coverage", `persona_c4system: Person "${person.name}" on the L1 diagram has no matching persona row — edge skipped`);
@@ -87,7 +87,7 @@ export async function buildPersonaC4System(inputs) {
     rows.sort((a, b) => String(a["id"]).localeCompare(String(b["id"])));
     return rows;
 }
-// F8 — the reverse direction (M-ADR 0157 parity): every persona that ends
+// The reverse direction (M-ADR 0157 parity): every persona that ends
 // the build without an edge is reported, with the reason. A persona with
 // neither an edge nor a finding is indistinguishable from one that was
 // never considered.

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

@@ -1,17 +1,17 @@
-// persona_container edge builder — M-ADR 0189 F26 §3 (schema 2.34.0).
+// persona_container edge builder — M-ADR 0189 (schema 2.34.0).
 //
 // The L2-granularity companion to persona_c4system: a Rel(...) between a
-// Person and a container had no catalogue and, until F26, no finding —
+// Person and a container had neither a catalogue nor a finding —
 // eleven of one estate's L2s and the bulk of another's 81 unroutable Rels
-// were exactly this class. F26 made the silence loud; this gives the
+// were exactly this class. The unroutable-Rel finding made the silence loud; this gives the
 // loudness a destination.
 //
 // Person entries are file-local (a Person declared in the same diagram as
-// the Rel); containers resolve SDD-wide (F20's rule). Either Rel direction
+// the Rel); containers resolve SDD-wide (container-first). Either Rel direction
 // normalises to persona→container. A Person that matches no persona row is
 // a coverage finding, never a silent skip (the persona_c4system precedent).
-// The syndicated platform L1 is skipped for non-root SDDs (F14); parallel
-// labels concatenate loudly (F25).
+// The syndicated platform L1 is skipped for non-root SDDs; parallel
+// labels concatenate loudly.
 import { readFile } from "node:fs/promises";
 import { collectC4DiagramFiles } from "./c4-external-systems.js";
 import { mergeEdgeLabel } from "./edge-label-merge.js";
@@ -37,11 +37,11 @@ export async function buildPersonaContainer(inputs) {
         }
         if (personNameByEntry.size === 0)
             continue;
-        // F31: only the SDD's OWN system entry is persona_c4system's domain —
+        // Only the SDD's OWN system entry is persona_c4system's domain —
         // that catalogue emits one edge per persona to THE system, nothing
         // else. The 0.89.0 skip silenced person Rels to ANY System(...) entry,
         // a silence delegated to a catalogue that never held those edges
-        // (F5's shape, one tier over): four of an estate's best-authored
+        // (a delegated silence one tier over): four of an estate's best-authored
         // persona edges vanished, while the same file's person→external edge
         // was announced. Own entry = the first System(...) line, mirroring
         // c4-systems' parseSystemLine; every other target takes exits 1/3/4.
@@ -58,17 +58,17 @@ export async function buildPersonaContainer(inputs) {
             if (!m)
                 continue;
             const [, fromEntry, toEntry, label] = m;
-            // F29/F30 — the person tier's exits, designed once. Identify the
+            // The person tier's exits, designed once. Identify the
             // person endpoint (file-local; container resolution wins on a
-            // dual-use id per F20), then route by the OTHER endpoint's kind:
+            // dual-use id), then route by the OTHER endpoint's kind:
             //   local container      → persona_container row
             //   own System(...)      → persona_c4system's domain; silent here
-            //   external             → announced skip (F30): a human using an
+            //   external             → announced skip: a human using an
             //                          external system has no persona-tier
             //                          catalogue YET — it must never transmute
             //                          into sed/ssd, whose semantics are runtime
             //                          calls between software
-            //   anything else        → announced skip (F29): claimed by no
+            //   anything else        → announced skip: claimed by no
             //                          catalogue is said, never silent
             const fromIsContainer = inputs.containerIdByEntryId.has(fromEntry ?? "");
             const toIsContainer = inputs.containerIdByEntryId.has(toEntry ?? "");
@@ -100,8 +100,8 @@ export async function buildPersonaContainer(inputs) {
             if (targetContainer === undefined) {
                 const isExternal = inputs.externalIdByEntryId?.has(targetEntry ?? "") ?? false;
                 inputs.findings.add("coverage", isExternal
-                    ? `persona_container: persona "${personaId}" → external "${inputs.externalIdByEntryId.get(targetEntry ?? "")}"${label ? ` ("${label}")` : ""} — a human using an external system has no persona-tier catalogue; skipped, never transmuted into a system edge (F30)`
-                    : `persona_container: persona "${personaId}" → "${targetEntry}"${label ? ` ("${label}")` : ""} resolves to no container — claimed by no catalogue; skipped (F29)`);
+                    ? `persona_container: persona "${personaId}" → external "${inputs.externalIdByEntryId.get(targetEntry ?? "")}"${label ? ` ("${label}")` : ""} — a human using an external system has no persona-tier catalogue; skipped, never transmuted into a system edge`
+                    : `persona_container: persona "${personaId}" → "${targetEntry}"${label ? ` ("${label}")` : ""} resolves to no container — claimed by no catalogue; skipped`);
                 continue;
             }
             const id = `${personaId}__${targetContainer}`;

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

@@ -9,8 +9,7 @@
 //   ## Summary
 //   {1-2 sentences}
 //
-// Cross-profile path (per coordination/persona-walker-platform-product-gap-
-// coordination.md, 2026-05-29): the walker reads `personas/` at SDD root
+// Cross-profile path: the walker reads `personas/` at SDD root
 // for every profile. Each SDD's personas/ carries personas at that SDD's
 // scope — for application-product that's app-specific personas, for
 // platform-product that's platform-wide / cross-app personas surfaced as

package/dist/lib/catalogue/builders/product-platform-dependencies.js

@@ -32,7 +32,7 @@
 // The aggregator subsequently joins synchronous rows against platform-side
 // `capability_service` to derive `cross_sdd_platform_capability` edges (per
 // ADR 0134, federation); async rows resolve via the capability leg (no
-// realiser service to join on) and skip the F18 realiser-join.
+// realiser service to join on) and skip the realiser-join.
 //
 // Cross-SDD references (target_capability_id, target_service_id) are
 // declared `external: true` in the schema — per-SDD FK validation
@@ -62,7 +62,7 @@ const FORWARD_REL_PATH = "app-platform-dependencies.yaml";
  * Contract types that denote an ASYNC shared-stream dependency (M-ADR 0192).
  * A dependency of one of these kinds binds to a stream contract published by a
  * capability, not to a synchronous realiser service — so it characteristically
- * has no `service_id`, and the F18 realiser-join does not apply to it at
+ * has no `service_id`, and the realiser-join does not apply to it at
  * aggregation. Kept lowercase; callers normalise before testing.
  */
 export const ASYNC_CONTRACT_TYPES = new Set([

package/dist/lib/catalogue/builders/quality-scores.js

@@ -468,7 +468,7 @@ export async function buildQualityScores(inputs) {
             }
             // Flat headline keys beside a `current:` block are a compatibility
             // shim, and a shim that DISAGREES with the effective record is the
-            // silent-failure shape found live (ledger §3am): an ingestion updated
+            // silent-failure shape found live: an ingestion updated
             // the flat score and left `current:` stale, and the catalogue published
             // the stale value with the right one inches away in the same entry —
             // no complaint anywhere. The disagreement is loud now. scored_at is

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

@@ -83,7 +83,7 @@ const ServiceCapabilityExemptionSchema = z
 const ServicesBlockSchema = z.unknown().optional();
 // `additional_context` accepts strings OR loosely-parsed key:value
 // objects (which arise when adopters leave colons unquoted in their
-// YAML — e.g. `- docs/.../ADR 0017: Use WorkOS for Auth.md`). The
+// YAML — e.g. `- docs/.../ADR 0017: Use Acme IdP for Auth.md`). The
 // canonical builder reconstructs the original string downstream.
 const RepoConfigSchema = z.object({
     repo: z.string(),
@@ -117,7 +117,7 @@ const RepoConfigSchema = z.object({
  * Reconstruct a string from a possibly-mis-parsed YAML list entry.
  *
  * Adopters sometimes write list entries with unquoted colons like:
- *   - docs/.../ADR 0017: Use WorkOS for Auth.md
+ *   - docs/.../ADR 0017: Use Acme IdP for Auth.md
  *
  * The YAML parser reads each such entry as a single-key object whose key
  * is the part before the first colon and whose value is the part after.

package/dist/lib/catalogue/builders/screen-tree.js

@@ -35,7 +35,7 @@ const STRING_RE = /"[^"]*"|'[^']*'/g;
  * line-structure-preserving) so call-head lexing can never fire on quoted
  * content — `Table("Odometer (km)")` must not mint a phantom `Odometer`
  * component, and `"total (sum)"` must not false-fire the lowercase-call-head
- * finding (tomfosteruk/sdd-cli#1). Quote characters are kept; newlines inside
+ * finding (sdd-cli issue 1). Quote characters are kept; newlines inside
  * a span survive. The grammar defines no escape sequences (a quote always
  * closes the literal), matching STRING_RE and stripLineComment.
  *
@@ -112,7 +112,7 @@ function parseStatements(cleanBlock) {
         const id = m[1];
         const rhs = m[2];
         // A component statement's RHS is a call (`Text("Q4")`) or a reference — never a
-        // bare string literal. A line like `action="user-details-changed"` (the block-level
+        // bare string literal. A line like `action="basket-updated"` (the block-level
         // screen_action messaging contract, ADR 0166) matches the statement shape with
         // id=`action`; skip it so it isn't lexed as a phantom component (and so a node
         // carrying an `action=` attr doesn't pick it up as a spurious child).

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

@@ -23,8 +23,7 @@
 // `action="..."` declarations -> screen_action. The frontmatter supplies the
 // catalogue keys + FK lists. This is the forward / authored path; the reverse
 // toolkit projects an app's router + component tree into the same shape (the
-// upstream step that produces these artefacts — see
-// research/adr-0166-prototypes/ for the Phase Pre validation).
+// upstream step that produces these artefacts).
 //
 // Per ADR 0135 the rows are identical regardless of authoring direction; only
 // the `source` discriminator differs (screen-spec vs screen-extraction).
@@ -305,8 +304,8 @@ function isTemplate(name) {
         lower.endsWith("-spec-template.md"));
 }
 // entity-style slug: ALLCAPS-then-Pascal split so naming variation across
-// `MyEcoDrive` / `map_tracking_container` / `TE_driver` resolves stably
-// (per the Phase Pre real-menu finding; mirrors entitySlug).
+// `GiftCardHub` / `order_tracking_container` / `POS_checkout` resolves stably
+// (a measured real-menu finding; mirrors entitySlug).
 function screenSlug(s) {
     return s
         .replace(/([A-Z]+)([A-Z][a-z])/g, "$1-$2")

package/dist/lib/catalogue/builders/system-external-dependency.js

@@ -14,7 +14,7 @@ import { mergeEdgeLabel } from "./edge-label-merge.js";
 // Any C4-PlantUML relationship macro: Rel, Rel_U/D/L/R, BiRel, Rel_Back, etc.
 // Capture the first two positional args (from, to) and an optional label.
 const REL_RE = /^(?:Bi)?Rel(?:_[A-Za-z]+)?\s*\(\s*(\w+)\s*,\s*(\w+)\s*(?:,\s*"([^"]*)")?/;
-// Diagram files come from the shared collector (F11c) — see
+// Diagram files come from the shared collector — see
 // c4-external-systems.ts / c4-l1-candidates.ts. This builder previously
 // kept a private, pre-0.30.1-ordered copy missing the domain-scoped L1
 // path, so Rel(...) lines there were never harvested.
@@ -30,7 +30,7 @@ export async function buildSystemExternalDependency(inputs) {
     const rows = [];
     const seen = new Set();
     const rowsById = new Map();
-    // F14: a Rel in the syndicated platform L1 is a statement about the
+    // A Rel in the syndicated platform L1 is a statement about the
     // PLATFORM. For any other SDD those lines minted the platform's
     // dependencies (and even its persona interactions) as the sibling's own
     // edges — measured at 28% of one estate's dependency graph and 35/35
@@ -42,11 +42,11 @@ export async function buildSystemExternalDependency(inputs) {
     for (const { abs, syndicated } of files) {
         if (syndicated && !isRoot)
             continue;
-        // (F17) the non-external Rel endpoint may be a local container — carry
+        // the non-external Rel endpoint may be a local container — carry
         // its id so adjudication can rewrite this edge onto container_dependency
         // instead of destroying it when the external endpoint proves internal.
         const content = await readFile(abs, "utf-8");
-        // F30: a Person-sourced Rel must never enter this catalogue — its
+        // A Person-sourced Rel must never enter this catalogue — its
         // semantics are runtime calls between software, and attributing a
         // human's Rel to the system erases the person-ness (which adjudication
         // then launders into system_system_dependency). The persona-container
@@ -60,14 +60,14 @@ export async function buildSystemExternalDependency(inputs) {
         for (const rel of parseRels(content)) {
             if (personEntries.has(rel.from) || personEntries.has(rel.to))
                 continue;
-            // F28: classification is CONTAINER-FIRST, uniformly with the
-            // container-dependency builder (F20 / ledger L6). An entry-id that
+            // Classification is CONTAINER-FIRST, uniformly with the
+            // container-dependency builder. An entry-id that
             // resolves to a local container IS a container, whatever a sibling
             // diagram called it — the old external-first read here meant a
             // dual-use SOURCE made the pair look external↔external to this
             // builder while looking container→external to its sibling, and the
             // edge fell between them: claimed by neither, reported by nothing.
-            // L6's fix was applied to one builder and not swept into this one.
+            // A fix applied to one builder must be swept into this one too.
             const fromIsContainer = inputs.containerIdByEntryId?.has(rel.from) ?? false;
             const toIsContainer = inputs.containerIdByEntryId?.has(rel.to) ?? false;
             const fromExt = fromIsContainer