@ybotok/loam 0.1.0-beta.3 → 0.2.0-alpha.2

package/dist/core/usecases/delta/claims.js

@@ -0,0 +1,116 @@
+import { withFeatureCapabilities } from "../../capabilities/delta/overlay.js";
+import { gradableCapabilityIds } from "../../capabilities/findings.js";
+import { resolveCapabilityTags, resolveRequirementTags } from "../../capabilities/usecase-join.js";
+import { compareIds } from "../../repo/entries.js";
+import { readFeatureFlows } from "./overlay.js";
+/**
+ * The promises this feature's own flows keep, read over the post-merge map.
+ *
+ * A feature with no flow is `read` with nothing kept, which is the ordinary
+ * answer and costs one walk over a directory that is not there.
+ */
+export async function featureFlowPromises(req) {
+    const scan = await readFeatureFlows(req);
+    if (scan.kind === "unreadable")
+        return { kind: "unreadable", errors: scan.errors };
+    // The ladder, and it is `ungraded` rather than an empty answer. Once the
+    // feature's own capability deltas are unioned in, `declared` is null for
+    // exactly one reason — `architecture/capabilities.yaml` exists and does not
+    // read as a vocabulary — so no `#cap-` tag can resolve and no claim can be
+    // made either way. Returning "keeps nothing" here is what let
+    // `capability.uncovered` convict a flow that does resolve, over a file the
+    // feature gate reports nothing else about.
+    if (req.declared === null) {
+        return {
+            kind: "ungraded",
+            why: "architecture/capabilities.yaml does not read as a capability vocabulary (`loam validate --all` reports it as capability.invalid)",
+        };
+    }
+    // A real, empty answer: loam read the flows and none of them claims anything.
+    if (scan.views.length === 0)
+        return { kind: "read", kept: [] };
+    const byPromise = new Map();
+    for (const view of scan.views) {
+        const scope = resolveCapabilityTags(view.tags, req.declared).flatMap((claim) => claim.kind === "resolved" ? [claim.id] : []);
+        for (const claim of resolveRequirementTags(view.tags, scope, req.requirementsOf)) {
+            if (claim.kind !== "resolved")
+                continue;
+            // Keyed on the pair, never on a joined string: see the header. The Map is
+            // only here to collapse two views keeping one promise into one row.
+            const key = JSON.stringify([claim.capability, claim.id]);
+            const found = byPromise.get(key);
+            if (found === undefined) {
+                byPromise.set(key, {
+                    promise: { capability: claim.capability, requirement: claim.id, flows: [] },
+                    flows: new Set([view.id]),
+                });
+            }
+            else {
+                found.flows.add(view.id);
+            }
+        }
+    }
+    // Sorted, and the view ids inside each row sorted too: nothing in loam has
+    // measured that LikeC4 preserves view declaration order, so a message built
+    // from it would reorder under a dependency bump.
+    const kept = [...byPromise.values()]
+        .map(({ promise, flows }) => ({ ...promise, flows: [...flows].sort(compareIds) }))
+        .sort((a, b) => compareIds(a.capability, b.capability) || compareIds(a.requirement, b.requirement));
+    return { kind: "read", kept };
+}
+/**
+ * What this feature's own flows keep, resolved against the vocabulary and the
+ * requirement ids its own merge would leave behind.
+ *
+ * THE WIDENING IS THE POINT, and it is `capabilities/delta/overlay.ts`'s
+ * judgement applied to the other carrier: an analyst adds `NOTIFY-ONCE` to a
+ * capability delta and an architect answers it with a flow in the same change,
+ * so a `#req-` tag resolved against the LIVING tree alone names a promise that
+ * does not exist yet — and the same archive that would land the flow lands the
+ * promise it points at.
+ *
+ * `requirementsOf` KNOWS ONLY THE CAPABILITIES THIS FEATURE HAS A DELTA FOR, and
+ * within those it carries living ∪ ADDED ∪ MODIFIED ids. The narrowing changes
+ * no answer, for a reason stronger than "it is probably fine":
+ * `uncoveredIssues` grades `r.kind === "ADDED"` and nothing else, and every
+ * ADDED requirement it grades lives in one of these documents by construction —
+ * so no id outside this map can reach a verdict. The LIVING half is in there
+ * because a widening of the graded set must not silently need a second edit
+ * here; today it decides nothing. A flow keeping a promise of a capability this
+ * feature does NOT touch resolves to `undocumented` and counts for nothing,
+ * which is correct: the fleet-scope `capability.requirement-unrealized` grades
+ * that join over the whole corpus, and answering it here from a partial index is
+ * how two surfaces start disagreeing.
+ *
+ * `declared` IS NOT NARROWED, and that asymmetry is load-bearing. It is what
+ * `resolveCapabilityTags` compares a `#cap-` slug against, and a slug is not
+ * injective — `payments/refunds` and `payments-refunds` flatten to one. Handing
+ * it a short list would resolve a tag that is genuinely ambiguous fleet-wide and
+ * attribute a whole flow to the wrong capability, silently. So the vocabulary is
+ * the fleet's whole one, read once by the caller.
+ */
+export async function flowCoverage(req) {
+    const vocab = withFeatureCapabilities(req.vocabulary, req.capabilities.map((doc) => doc.id));
+    const byCapability = new Map();
+    for (const doc of req.capabilities) {
+        const ids = new Set();
+        // REMOVED is excluded on both sides — a promise on its way out keeps nothing.
+        for (const r of doc.living)
+            if (r.kind !== "REMOVED" && r.id !== undefined)
+                ids.add(r.id);
+        for (const r of doc.reqs)
+            if ((r.kind === "ADDED" || r.kind === "MODIFIED") && r.id !== undefined)
+                ids.add(r.id);
+        byCapability.set(doc.id, ids);
+    }
+    return featureFlowPromises({
+        docsDir: req.docsDir,
+        featureDir: req.featureDir,
+        featureId: req.featureId,
+        known: req.known,
+        declared: gradableCapabilityIds(vocab),
+        requirementsOf: (capability) => byCapability.get(capability),
+        ...(req.load === undefined ? {} : { load: req.load }),
+    });
+}
+//# sourceMappingURL=claims.js.map

package/dist/core/usecases/delta/claims.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"claims.js","sourceRoot":"","sources":["../../../../src/core/usecases/delta/claims.ts"],"names":[],"mappings":"AAuCA,OAAO,EAAE,uBAAuB,EAAE,MAAM,qCAAqC,CAAC;AAE9E,OAAO,EAAE,qBAAqB,EAAE,MAAM,gCAAgC,CAAC;AACvE,OAAO,EAAE,qBAAqB,EAAE,sBAAsB,EAAE,MAAM,oCAAoC,CAAC;AAEnG,OAAO,EAAE,UAAU,EAAE,MAAM,uBAAuB,CAAC;AACnD,OAAO,EAAE,gBAAgB,EAA2B,MAAM,cAAc,CAAC;AAiDzE;;;;;GAKG;AACH,MAAM,CAAC,KAAK,UAAU,mBAAmB,CAAC,GAAwB;IAChE,MAAM,IAAI,GAAG,MAAM,gBAAgB,CAAC,GAAG,CAAC,CAAC;IACzC,IAAI,IAAI,CAAC,IAAI,KAAK,YAAY;QAAE,OAAO,EAAE,IAAI,EAAE,YAAY,EAAE,MAAM,EAAE,IAAI,CAAC,MAAM,EAAE,CAAC;IACnF,yEAAyE;IACzE,yEAAyE;IACzE,4EAA4E;IAC5E,2EAA2E;IAC3E,8DAA8D;IAC9D,2EAA2E;IAC3E,2CAA2C;IAC3C,IAAI,GAAG,CAAC,QAAQ,KAAK,IAAI,EAAE,CAAC;QAC1B,OAAO;YACL,IAAI,EAAE,UAAU;YAChB,GAAG,EAAE,kIAAkI;SACxI,CAAC;IACJ,CAAC;IACD,8EAA8E;IAC9E,IAAI,IAAI,CAAC,KAAK,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,EAAE,EAAE,CAAC;IAE/D,MAAM,SAAS,GAAG,IAAI,GAAG,EAAwD,CAAC;IAClF,KAAK,MAAM,IAAI,IAAI,IAAI,CAAC,KAAK,EAAE,CAAC;QAC9B,MAAM,KAAK,GAAG,qBAAqB,CAAC,IAAI,CAAC,IAAI,EAAE,GAAG,CAAC,QAAQ,CAAC,CAAC,OAAO,CAAC,CAAC,KAAK,EAAE,EAAE,CAC7E,KAAK,CAAC,IAAI,KAAK,UAAU,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,EAAE,CAC5C,CAAC;QACF,KAAK,MAAM,KAAK,IAAI,sBAAsB,CAAC,IAAI,CAAC,IAAI,EAAE,KAAK,EAAE,GAAG,CAAC,cAAc,CAAC,EAAE,CAAC;YACjF,IAAI,KAAK,CAAC,IAAI,KAAK,UAAU;gBAAE,SAAS;YACxC,0EAA0E;YAC1E,oEAAoE;YACpE,MAAM,GAAG,GAAG,IAAI,CAAC,SAAS,CAAC,CAAC,KAAK,CAAC,UAAU,EAAE,KAAK,CAAC,EAAE,CAAC,CAAC,CAAC;YACzD,MAAM,KAAK,GAAG,SAAS,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;YACjC,IAAI,KAAK,KAAK,SAAS,EAAE,CAAC;gBACxB,SAAS,CAAC,GAAG,CAAC,GAAG,EAAE;oBACjB,OAAO,EAAE,EAAE,UAAU,EAAE,KAAK,CAAC,UAAU,EAAE,WAAW,EAAE,KAAK,CAAC,EAAE,EAAE,KAAK,EAAE,EAAE,EAAE;oBAC3E,KAAK,EAAE,IAAI,GAAG,CAAC,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;iBAC1B,CAAC,CAAC;YACL,CAAC;iBAAM,CAAC;gBACN,KAAK,CAAC,KAAK,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;YAC3B,CAAC;QACH,CAAC;IACH,CAAC;IACD,2EAA2E;IAC3E,4EAA4E;IAC5E,iDAAiD;IACjD,MAAM,IAAI,GAAG,CAAC,GAAG,SAAS,CAAC,MAAM,EAAE,CAAC;SACjC,GAAG,CAAC,CAAC,EAAE,OAAO,EAAE,KAAK,EAAE,EAAE,EAAE,CAAC,CAAC,EAAE,GAAG,OAAO,EAAE,KAAK,EAAE,CAAC,GAAG,KAAK,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,EAAE,CAAC,CAAC;SACjF,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,UAAU,CAAC,CAAC,CAAC,UAAU,EAAE,CAAC,CAAC,UAAU,CAAC,IAAI,UAAU,CAAC,CAAC,CAAC,WAAW,EAAE,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC;IACtG,OAAO,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,CAAC;AAChC,CAAC;AAsBD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8BG;AACH,MAAM,CAAC,KAAK,UAAU,YAAY,CAAC,GAAwB;IACzD,MAAM,KAAK,GAAG,uBAAuB,CAAC,GAAG,CAAC,UAAU,EAAE,GAAG,CAAC,YAAY,CAAC,GAAG,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC,CAAC;IAC7F,MAAM,YAAY,GAAG,IAAI,GAAG,EAA+B,CAAC;IAC5D,KAAK,MAAM,GAAG,IAAI,GAAG,CAAC,YAAY,EAAE,CAAC;QACnC,MAAM,GAAG,GAAG,IAAI,GAAG,EAAU,CAAC;QAC9B,8EAA8E;QAC9E,KAAK,MAAM,CAAC,IAAI,GAAG,CAAC,MAAM;YAAE,IAAI,CAAC,CAAC,IAAI,KAAK,SAAS,IAAI,CAAC,CAAC,EAAE,KAAK,SAAS;gBAAE,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC;QAC1F,KAAK,MAAM,CAAC,IAAI,GAAG,CAAC,IAAI;YAAE,IAAI,CAAC,CAAC,CAAC,IAAI,KAAK,OAAO,IAAI,CAAC,CAAC,IAAI,KAAK,UAAU,CAAC,IAAI,CAAC,CAAC,EAAE,KAAK,SAAS;gBAAE,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC;QACjH,YAAY,CAAC,GAAG,CAAC,GAAG,CAAC,EAAE,EAAE,GAAG,CAAC,CAAC;IAChC,CAAC;IACD,OAAO,mBAAmB,CAAC;QACzB,OAAO,EAAE,GAAG,CAAC,OAAO;QACpB,UAAU,EAAE,GAAG,CAAC,UAAU;QAC1B,SAAS,EAAE,GAAG,CAAC,SAAS;QACxB,KAAK,EAAE,GAAG,CAAC,KAAK;QAChB,QAAQ,EAAE,qBAAqB,CAAC,KAAK,CAAC;QACtC,cAAc,EAAE,CAAC,UAAU,EAAE,EAAE,CAAC,YAAY,CAAC,GAAG,CAAC,UAAU,CAAC;QAC5D,GAAG,CAAC,GAAG,CAAC,IAAI,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,CAAC;KACtD,CAAC,CAAC;AACL,CAAC","sourcesContent":["/**\n * Which of this feature's own promises its own flows keep.\n *\n * A cross-service criterion — \"I enter a login and a password and I am in\" —\n * belongs to no single service's spec, because each service promises only its\n * own part. A `dynamic view` can carry it, because it IS the hop sequence, and\n * that is the whole reason `#req-` exists. Until `./flows.ts` gave a feature a\n * slot for one, this answer could only ever be empty inside a feature window:\n * the flow was a fleet document, so a tag naming a requirement the same change\n * was adding named something that was not living yet.\n *\n * WHAT THIS FEEDS. `capability.uncovered` — the archive gate that refuses a\n * promise nothing keeps. Its message used to end by telling authors to archive\n * with `--approve` and tag the flow AFTERWARDS, which was honest advice about a\n * hole rather than a workflow anybody wanted: it lands the promise first, kept\n * by nothing, and relies on somebody coming back.\n *\n * THE RULE IS `../capability.ts`'s AND MUST STAY SO. Only a RESOLVED claim\n * counts, and both halves must resolve — the `#cap-` tag to exactly one declared\n * capability, the `#req-` tag to exactly one of its requirements. A broken tag\n * of either kind is already an error (`usecase.capability-unresolved`,\n * `usecase.requirement-unresolved`) and must never also mark a promise kept: a\n * typo that silenced the gate would turn a mistake into a green archive. The two\n * resolvers are called directly rather than through\n * `useCaseRequirementClaims` for one reason, and it is not a difference of\n * opinion about the rule — that function flattens its answer to a `<cap>#<id>`\n * string, and `capabilities/delta/uncovered.ts` keys this same join on NUL\n * precisely because a capability id has no grammar forbidding `#`. Handing it a\n * key it has written down a reason not to use would be the wrong kind of reuse.\n *\n * THE LADDER TRAVELS. `declared === null` — an absent or unreadable\n * `architecture/capabilities.yaml` — is an empty answer, not a suspended one, and\n * the caller is already suppressing the whole family behind it. An `unreadable`\n * overlay is different and must NOT be flattened to \"keeps nothing\": loam did not\n * look, which is never the same answer as \"there is nothing there\", and a gate\n * that refused on it would blame the author for a map it could not read.\n */\nimport type { LoadedDoc } from \"../../c4/likec4.js\";\nimport type { CapabilityVocabulary } from \"../../capabilities/capabilities.js\";\nimport { withFeatureCapabilities } from \"../../capabilities/delta/overlay.js\";\nimport type { CapabilityDeltaDoc } from \"../../capabilities/delta/uncovered.js\";\nimport { gradableCapabilityIds } from \"../../capabilities/findings.js\";\nimport { resolveCapabilityTags, resolveRequirementTags } from \"../../capabilities/usecase-join.js\";\nimport type { DocsDir, FeatureDir } from \"../../kernel/ids/dirs.js\";\nimport { compareIds } from \"../../repo/entries.js\";\nimport { readFeatureFlows, type FlowOverlayRequest } from \"./overlay.js\";\n\n/** One promise this feature's flows keep, with the flows that keep it. */\nexport interface FlowPromise {\n  /** The capability the keeping view's `#cap-` tag resolved to. */\n  capability: string;\n  /** The `Requirement-ID` its `#req-` tag resolved to, inside that capability. */\n  requirement: string;\n  /** The view ids keeping it, deduplicated and sorted — message text, never identity. */\n  flows: readonly string[];\n}\n\n/**\n * What the feature's flows keep, or one of the two honest refusals to say.\n *\n * THREE ARMS, because the two failures are not the same failure and a caller\n * that merged them would say the wrong thing. `unreadable` is loam unable to\n * READ the flows — a parse error, a hop naming an element the merge does not\n * land — and it earns `usecase.flow-invalid` and a refusal. `ungraded` is loam\n * able to read them and unable to RESOLVE their tags, because the capability\n * vocabulary this feature's merge would leave behind does not parse; the flows\n * are fine, the file they point into is not, and refusing over the flows would\n * name the wrong document.\n *\n * `read` with an empty `kept` is the ordinary answer and a real one: loam\n * looked, and no flow of this feature keeps a promise it adds.\n */\nexport type FlowPromises =\n  | { kind: \"read\"; kept: readonly FlowPromise[] }\n  | { kind: \"ungraded\"; why: string }\n  | { kind: \"unreadable\"; errors: string[] };\n\n/** Everything the join needs, on top of what the overlay already asks for. */\nexport interface FlowPromisesRequest extends FlowOverlayRequest {\n  /**\n   * The capability ids to resolve `#cap-` against — the LIVING vocabulary\n   * widened with the ids this feature's own capability deltas introduce, which\n   * is the same both-corpora rule `Realizes:` follows\n   * (`core/capabilities/delta/overlay.ts`). `null` suspends the axis.\n   */\n  declared: readonly string[] | null;\n  /**\n   * The requirement ids per capability, widened the same way\n   * (`withFeatureRequirements`). `undefined` for a capability with no document\n   * at all is a different answer from an empty set, and both are real here.\n   */\n  requirementsOf: (capability: string) => ReadonlySet<string> | undefined;\n}\n\n/**\n * The promises this feature's own flows keep, read over the post-merge map.\n *\n * A feature with no flow is `read` with nothing kept, which is the ordinary\n * answer and costs one walk over a directory that is not there.\n */\nexport async function featureFlowPromises(req: FlowPromisesRequest): Promise<FlowPromises> {\n  const scan = await readFeatureFlows(req);\n  if (scan.kind === \"unreadable\") return { kind: \"unreadable\", errors: scan.errors };\n  // The ladder, and it is `ungraded` rather than an empty answer. Once the\n  // feature's own capability deltas are unioned in, `declared` is null for\n  // exactly one reason — `architecture/capabilities.yaml` exists and does not\n  // read as a vocabulary — so no `#cap-` tag can resolve and no claim can be\n  // made either way. Returning \"keeps nothing\" here is what let\n  // `capability.uncovered` convict a flow that does resolve, over a file the\n  // feature gate reports nothing else about.\n  if (req.declared === null) {\n    return {\n      kind: \"ungraded\",\n      why: \"architecture/capabilities.yaml does not read as a capability vocabulary (`loam validate --all` reports it as capability.invalid)\",\n    };\n  }\n  // A real, empty answer: loam read the flows and none of them claims anything.\n  if (scan.views.length === 0) return { kind: \"read\", kept: [] };\n\n  const byPromise = new Map<string, { promise: FlowPromise; flows: Set<string> }>();\n  for (const view of scan.views) {\n    const scope = resolveCapabilityTags(view.tags, req.declared).flatMap((claim) =>\n      claim.kind === \"resolved\" ? [claim.id] : [],\n    );\n    for (const claim of resolveRequirementTags(view.tags, scope, req.requirementsOf)) {\n      if (claim.kind !== \"resolved\") continue;\n      // Keyed on the pair, never on a joined string: see the header. The Map is\n      // only here to collapse two views keeping one promise into one row.\n      const key = JSON.stringify([claim.capability, claim.id]);\n      const found = byPromise.get(key);\n      if (found === undefined) {\n        byPromise.set(key, {\n          promise: { capability: claim.capability, requirement: claim.id, flows: [] },\n          flows: new Set([view.id]),\n        });\n      } else {\n        found.flows.add(view.id);\n      }\n    }\n  }\n  // Sorted, and the view ids inside each row sorted too: nothing in loam has\n  // measured that LikeC4 preserves view declaration order, so a message built\n  // from it would reorder under a dependency bump.\n  const kept = [...byPromise.values()]\n    .map(({ promise, flows }) => ({ ...promise, flows: [...flows].sort(compareIds) }))\n    .sort((a, b) => compareIds(a.capability, b.capability) || compareIds(a.requirement, b.requirement));\n  return { kind: \"read\", kept };\n}\n\n/** Everything the coverage join needs, and nothing it would have to read twice. */\nexport interface FlowCoverageRequest {\n  docsDir: DocsDir;\n  featureDir: FeatureDir;\n  featureId: string;\n  /**\n   * The feature's capability deltas, ALREADY PARSED by the caller's walk. They\n   * arrive rather than being read because the one caller has just produced them,\n   * and re-reading a document to answer a question about it is how two answers\n   * about one file appear.\n   */\n  capabilities: readonly CapabilityDeltaDoc[];\n  /** The LIVING capability vocabulary, read by the caller through its own index. */\n  vocabulary: CapabilityVocabulary;\n  /** The enumerated fleet, for `readFeatureFlows`' resolver and for its reason. */\n  known: ReadonlySet<string>;\n  /** The caller's memoised LikeC4 read; see `./overlay.ts`. */\n  load?: (path: string) => Promise<LoadedDoc>;\n}\n\n/**\n * What this feature's own flows keep, resolved against the vocabulary and the\n * requirement ids its own merge would leave behind.\n *\n * THE WIDENING IS THE POINT, and it is `capabilities/delta/overlay.ts`'s\n * judgement applied to the other carrier: an analyst adds `NOTIFY-ONCE` to a\n * capability delta and an architect answers it with a flow in the same change,\n * so a `#req-` tag resolved against the LIVING tree alone names a promise that\n * does not exist yet — and the same archive that would land the flow lands the\n * promise it points at.\n *\n * `requirementsOf` KNOWS ONLY THE CAPABILITIES THIS FEATURE HAS A DELTA FOR, and\n * within those it carries living ∪ ADDED ∪ MODIFIED ids. The narrowing changes\n * no answer, for a reason stronger than \"it is probably fine\":\n * `uncoveredIssues` grades `r.kind === \"ADDED\"` and nothing else, and every\n * ADDED requirement it grades lives in one of these documents by construction —\n * so no id outside this map can reach a verdict. The LIVING half is in there\n * because a widening of the graded set must not silently need a second edit\n * here; today it decides nothing. A flow keeping a promise of a capability this\n * feature does NOT touch resolves to `undocumented` and counts for nothing,\n * which is correct: the fleet-scope `capability.requirement-unrealized` grades\n * that join over the whole corpus, and answering it here from a partial index is\n * how two surfaces start disagreeing.\n *\n * `declared` IS NOT NARROWED, and that asymmetry is load-bearing. It is what\n * `resolveCapabilityTags` compares a `#cap-` slug against, and a slug is not\n * injective — `payments/refunds` and `payments-refunds` flatten to one. Handing\n * it a short list would resolve a tag that is genuinely ambiguous fleet-wide and\n * attribute a whole flow to the wrong capability, silently. So the vocabulary is\n * the fleet's whole one, read once by the caller.\n */\nexport async function flowCoverage(req: FlowCoverageRequest): Promise<FlowPromises> {\n  const vocab = withFeatureCapabilities(req.vocabulary, req.capabilities.map((doc) => doc.id));\n  const byCapability = new Map<string, ReadonlySet<string>>();\n  for (const doc of req.capabilities) {\n    const ids = new Set<string>();\n    // REMOVED is excluded on both sides — a promise on its way out keeps nothing.\n    for (const r of doc.living) if (r.kind !== \"REMOVED\" && r.id !== undefined) ids.add(r.id);\n    for (const r of doc.reqs) if ((r.kind === \"ADDED\" || r.kind === \"MODIFIED\") && r.id !== undefined) ids.add(r.id);\n    byCapability.set(doc.id, ids);\n  }\n  return featureFlowPromises({\n    docsDir: req.docsDir,\n    featureDir: req.featureDir,\n    featureId: req.featureId,\n    known: req.known,\n    declared: gradableCapabilityIds(vocab),\n    requirementsOf: (capability) => byCapability.get(capability),\n    ...(req.load === undefined ? {} : { load: req.load }),\n  });\n}\n"]}

package/dist/core/usecases/delta/flows.js

@@ -0,0 +1,103 @@
+/**
+ * A feature's own flows: `features/<FEAT>/usecases/<name>.likec4`.
+ *
+ * A `dynamic view` is the only realizer a cross-service promise has, and until
+ * this slot existed it was the one realizer no feature could carry. Every other
+ * axis had a delta — a C4 delta, a requirement delta on both spec axes, both
+ * contract deltas, a capability delta, a glossary term — so the business axis's
+ * own headline case had to be written backwards: an analyst adds a capability
+ * requirement, the architect answers it with a flow, and the flow could not ship
+ * in that change. It merged only after the promise was already living, which
+ * meant the promise landed first with nothing keeping it.
+ *
+ * CREATE-ONLY, for `core/glossary/delta.ts`'s reasons rather than a weaker
+ * version of them. A capability document is a DELTA because it merges INTO a
+ * living document and two features editing one requirement would otherwise
+ * overwrite each other silently. A flow has none of that: the file is one
+ * ordered hop sequence, the merge is a whole-file copy, and there is nothing to
+ * merge partially. Rewriting a living flow through a feature would be a silent
+ * whole-file replacement with no pin to collide on, where editing
+ * `architecture/usecases/<name>.likec4` directly in the same pull request
+ * produces an ordinary git conflict a human resolves. `usecase.flow-exists`
+ * refuses the first and names the second — the same shape, and the same
+ * severity, as `glossary.term-exists`.
+ *
+ * WHY A FILE OF ITS OWN AND NOT `delta.likec4`. The C4 delta is a MODEL delta:
+ * it re-declares the landscape's own identifiers to anchor its new edges, and it
+ * carries its own `specification` block because LikeC4 parses it standalone.
+ * Both make it unstageable beside the landscape in one project — a duplicate
+ * specification is an error blamed on both files, and a re-declared element is a
+ * duplicate id. A views-only document declares neither, which is exactly why
+ * living use cases already live in files of their own; the feature-local slot
+ * mirrors that layout so the merge is a copy and the overlay is a stage.
+ * `core/c4/splice/delta-blocks.ts` goes on refusing a `dynamic view` inside
+ * `delta.likec4` and now names this slot as the place it belongs.
+ *
+ * ONE CALL for the walk. `architectureDocuments` already implements "every
+ * `.likec4` under a directory, recursively, in a stable order, and an absent
+ * directory is an empty list" — which is the whole of what a feature's flow
+ * directory is. A second walk would be two implementations free to disagree
+ * about what a flow file is, and they would disagree first about nesting.
+ */
+import { existsSync } from "node:fs";
+import { join, relative, resolve } from "node:path";
+import { architectureDocuments } from "../../c4/project/documents.js";
+import { architectureDir } from "../../c4/project/architecture.js";
+import { featureUseCasesDir } from "../../repo/authored/paths.js";
+import {} from "../../vocabulary/issue.js";
+/** The directory living flows are filed under, inside `architecture/`. */
+export const USECASE_SUBDIR = "usecases";
+/**
+ * The flows one feature carries, ordered by path.
+ *
+ * Zero readdirs when the feature has no `usecases/` directory, which is every
+ * feature in a fleet that has not adopted the axis: `architectureDocuments`
+ * answers an absent directory with an empty list rather than a throw.
+ */
+export async function featureFlows(featureDir) {
+    const dir = featureUseCasesDir(featureDir);
+    const paths = await architectureDocuments(dir);
+    const base = resolve(dir);
+    return paths.map((path) => ({ rel: relative(base, path).split(/[\\/]/).join("/"), path }));
+}
+/**
+ * The LIVING path a feature-local flow addresses. Spelled here because three
+ * readers need it — the refusal below, the archive merge, and the overlay that
+ * grades the flow before either — and a reader resolving it differently would
+ * refuse a flow the merge then wrote anyway.
+ *
+ * `rel` is joined un-split, which `node:path` normalizes. What holds the join is
+ * PROVENANCE, exactly as it holds `livingTermPath` one axis over: every `rel`
+ * here came out of an `architectureDocuments` walk, so each component is a
+ * directory entry that exists. No caller takes one from argv.
+ */
+export function livingFlowPath(docsDir, rel) {
+    return join(architectureDir(docsDir), USECASE_SUBDIR, rel);
+}
+/**
+ * `usecase.flow-exists` — a flow this feature introduces that the living
+ * `architecture/` already holds.
+ *
+ * An ERROR and never a warning-that-gates, for `glossary.term-exists`'s reason:
+ * there is no legal reading of it. The merge would replace an authored flow
+ * wholesale, and no `--approve` makes that a different act than it is. Two
+ * features introducing the same flow is the case that makes it load-bearing
+ * rather than pedantic — whichever archives first creates the living document,
+ * and the second is told before it merges that its own file is the one to
+ * delete.
+ */
+export async function flowDeltaIssues(docsDir, featureDir) {
+    const flows = await featureFlows(featureDir);
+    return flows
+        .filter((flow) => existsSync(livingFlowPath(docsDir, flow.rel)))
+        .map((flow) => ({
+        severity: "error",
+        code: "usecase.flow-exists",
+        subject: flow.rel,
+        message: `architecture/${USECASE_SUBDIR}/${flow.rel} already exists, so this feature's flow would replace an authored one wholesale — ` +
+            "a feature-local flow INTRODUCES a use case, it does not rewrite one. " +
+            `Delete features/<FEAT>/${USECASE_SUBDIR}/${flow.rel} and edit architecture/${USECASE_SUBDIR}/${flow.rel} directly in this same change, ` +
+            "where git produces an ordinary conflict if somebody else is editing it too.",
+    }));
+}
+//# sourceMappingURL=flows.js.map

package/dist/core/usecases/delta/flows.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"flows.js","sourceRoot":"","sources":["../../../../src/core/usecases/delta/flows.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAwCG;AACH,OAAO,EAAE,UAAU,EAAE,MAAM,SAAS,CAAC;AACrC,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AACpD,OAAO,EAAE,qBAAqB,EAAE,MAAM,+BAA+B,CAAC;AACtE,OAAO,EAAE,eAAe,EAAE,MAAM,kCAAkC,CAAC;AACnE,OAAO,EAAE,kBAAkB,EAAE,MAAM,8BAA8B,CAAC;AAElE,OAAO,EAAc,MAAM,2BAA2B,CAAC;AAEvD,0EAA0E;AAC1E,MAAM,CAAC,MAAM,cAAc,GAAG,UAAU,CAAC;AAezC;;;;;;GAMG;AACH,MAAM,CAAC,KAAK,UAAU,YAAY,CAAC,UAAsB;IACvD,MAAM,GAAG,GAAG,kBAAkB,CAAC,UAAU,CAAC,CAAC;IAC3C,MAAM,KAAK,GAAG,MAAM,qBAAqB,CAAC,GAAG,CAAC,CAAC;IAC/C,MAAM,IAAI,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC;IAC1B,OAAO,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,EAAE,GAAG,EAAE,QAAQ,CAAC,IAAI,EAAE,IAAI,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;AAC7F,CAAC;AAED;;;;;;;;;;GAUG;AACH,MAAM,UAAU,cAAc,CAAC,OAAgB,EAAE,GAAW;IAC1D,OAAO,IAAI,CAAC,eAAe,CAAC,OAAO,CAAC,EAAE,cAAc,EAAE,GAAG,CAAC,CAAC;AAC7D,CAAC;AAED;;;;;;;;;;;GAWG;AACH,MAAM,CAAC,KAAK,UAAU,eAAe,CAAC,OAAgB,EAAE,UAAsB;IAC5E,MAAM,KAAK,GAAG,MAAM,YAAY,CAAC,UAAU,CAAC,CAAC;IAC7C,OAAO,KAAK;SACT,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,UAAU,CAAC,cAAc,CAAC,OAAO,EAAE,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC;SAC/D,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC;QACd,QAAQ,EAAE,OAAgB;QAC1B,IAAI,EAAE,qBAA8B;QACpC,OAAO,EAAE,IAAI,CAAC,GAAG;QACjB,OAAO,EACL,gBAAgB,cAAc,IAAI,IAAI,CAAC,GAAG,oFAAoF;YAC9H,uEAAuE;YACvE,0BAA0B,cAAc,IAAI,IAAI,CAAC,GAAG,0BAA0B,cAAc,IAAI,IAAI,CAAC,GAAG,iCAAiC;YACzI,6EAA6E;KAChF,CAAC,CAAC,CAAC;AACR,CAAC","sourcesContent":["/**\n * A feature's own flows: `features/<FEAT>/usecases/<name>.likec4`.\n *\n * A `dynamic view` is the only realizer a cross-service promise has, and until\n * this slot existed it was the one realizer no feature could carry. Every other\n * axis had a delta — a C4 delta, a requirement delta on both spec axes, both\n * contract deltas, a capability delta, a glossary term — so the business axis's\n * own headline case had to be written backwards: an analyst adds a capability\n * requirement, the architect answers it with a flow, and the flow could not ship\n * in that change. It merged only after the promise was already living, which\n * meant the promise landed first with nothing keeping it.\n *\n * CREATE-ONLY, for `core/glossary/delta.ts`'s reasons rather than a weaker\n * version of them. A capability document is a DELTA because it merges INTO a\n * living document and two features editing one requirement would otherwise\n * overwrite each other silently. A flow has none of that: the file is one\n * ordered hop sequence, the merge is a whole-file copy, and there is nothing to\n * merge partially. Rewriting a living flow through a feature would be a silent\n * whole-file replacement with no pin to collide on, where editing\n * `architecture/usecases/<name>.likec4` directly in the same pull request\n * produces an ordinary git conflict a human resolves. `usecase.flow-exists`\n * refuses the first and names the second — the same shape, and the same\n * severity, as `glossary.term-exists`.\n *\n * WHY A FILE OF ITS OWN AND NOT `delta.likec4`. The C4 delta is a MODEL delta:\n * it re-declares the landscape's own identifiers to anchor its new edges, and it\n * carries its own `specification` block because LikeC4 parses it standalone.\n * Both make it unstageable beside the landscape in one project — a duplicate\n * specification is an error blamed on both files, and a re-declared element is a\n * duplicate id. A views-only document declares neither, which is exactly why\n * living use cases already live in files of their own; the feature-local slot\n * mirrors that layout so the merge is a copy and the overlay is a stage.\n * `core/c4/splice/delta-blocks.ts` goes on refusing a `dynamic view` inside\n * `delta.likec4` and now names this slot as the place it belongs.\n *\n * ONE CALL for the walk. `architectureDocuments` already implements \"every\n * `.likec4` under a directory, recursively, in a stable order, and an absent\n * directory is an empty list\" — which is the whole of what a feature's flow\n * directory is. A second walk would be two implementations free to disagree\n * about what a flow file is, and they would disagree first about nesting.\n */\nimport { existsSync } from \"node:fs\";\nimport { join, relative, resolve } from \"node:path\";\nimport { architectureDocuments } from \"../../c4/project/documents.js\";\nimport { architectureDir } from \"../../c4/project/architecture.js\";\nimport { featureUseCasesDir } from \"../../repo/authored/paths.js\";\nimport type { DocsDir, FeatureDir } from \"../../kernel/ids/dirs.js\";\nimport { type Issue } from \"../../vocabulary/issue.js\";\n\n/** The directory living flows are filed under, inside `architecture/`. */\nexport const USECASE_SUBDIR = \"usecases\";\n\n/** One flow document a feature carries. */\nexport interface FeatureFlow {\n  /**\n   * The path INSIDE the feature's `usecases/` directory, `/`-separated — the id\n   * this axis has, and the same path the merge writes under\n   * `architecture/usecases/`. Nesting is spelled by the tree, as it is for every\n   * other authored tree in the repo.\n   */\n  rel: string;\n  /** The absolute path of the authored file. */\n  path: string;\n}\n\n/**\n * The flows one feature carries, ordered by path.\n *\n * Zero readdirs when the feature has no `usecases/` directory, which is every\n * feature in a fleet that has not adopted the axis: `architectureDocuments`\n * answers an absent directory with an empty list rather than a throw.\n */\nexport async function featureFlows(featureDir: FeatureDir): Promise<FeatureFlow[]> {\n  const dir = featureUseCasesDir(featureDir);\n  const paths = await architectureDocuments(dir);\n  const base = resolve(dir);\n  return paths.map((path) => ({ rel: relative(base, path).split(/[\\\\/]/).join(\"/\"), path }));\n}\n\n/**\n * The LIVING path a feature-local flow addresses. Spelled here because three\n * readers need it — the refusal below, the archive merge, and the overlay that\n * grades the flow before either — and a reader resolving it differently would\n * refuse a flow the merge then wrote anyway.\n *\n * `rel` is joined un-split, which `node:path` normalizes. What holds the join is\n * PROVENANCE, exactly as it holds `livingTermPath` one axis over: every `rel`\n * here came out of an `architectureDocuments` walk, so each component is a\n * directory entry that exists. No caller takes one from argv.\n */\nexport function livingFlowPath(docsDir: DocsDir, rel: string): string {\n  return join(architectureDir(docsDir), USECASE_SUBDIR, rel);\n}\n\n/**\n * `usecase.flow-exists` — a flow this feature introduces that the living\n * `architecture/` already holds.\n *\n * An ERROR and never a warning-that-gates, for `glossary.term-exists`'s reason:\n * there is no legal reading of it. The merge would replace an authored flow\n * wholesale, and no `--approve` makes that a different act than it is. Two\n * features introducing the same flow is the case that makes it load-bearing\n * rather than pedantic — whichever archives first creates the living document,\n * and the second is told before it merges that its own file is the one to\n * delete.\n */\nexport async function flowDeltaIssues(docsDir: DocsDir, featureDir: FeatureDir): Promise<Issue[]> {\n  const flows = await featureFlows(featureDir);\n  return flows\n    .filter((flow) => existsSync(livingFlowPath(docsDir, flow.rel)))\n    .map((flow) => ({\n      severity: \"error\" as const,\n      code: \"usecase.flow-exists\" as const,\n      subject: flow.rel,\n      message:\n        `architecture/${USECASE_SUBDIR}/${flow.rel} already exists, so this feature's flow would replace an authored one wholesale — ` +\n        \"a feature-local flow INTRODUCES a use case, it does not rewrite one. \" +\n        `Delete features/<FEAT>/${USECASE_SUBDIR}/${flow.rel} and edit architecture/${USECASE_SUBDIR}/${flow.rel} directly in this same change, ` +\n        \"where git produces an ordinary conflict if somebody else is editing it too.\",\n    }));\n}\n"]}

package/dist/core/usecases/delta/overlay.js

@@ -0,0 +1,72 @@
+/**
+ * A feature's flows, read against the fleet map AS THIS FEATURE'S MERGE WOULD
+ * LEAVE IT.
+ *
+ * The staging and the merge preview that make that possible are no longer here:
+ * they moved to `core/c4/project/staged.ts` when the deployment slot became the
+ * second feature-local `.likec4` document, because a second copy of that
+ * machinery is the copy that drifts, and the two would disagree first about the
+ * merge preview — the one thing both axes' refusals rest on. That module's
+ * header carries the WHY of the post-merge corpus; this one keeps what is
+ * particular to use cases, which is the interpretation: which of the staged
+ * views are this feature's, and what they resolve against.
+ *
+ * FAIL CLOSED, and not silently. Every failure is the `unreadable` arm carrying
+ * LikeC4's own messages: a flow this cannot read is never a flow that grades
+ * clean, which is the asymmetry `../fleet.ts` states for the fleet-scope scan.
+ */
+import {} from "../../c4/likec4.js";
+import { stageMergedProject } from "../../c4/project/staged.js";
+import { serviceResolver } from "../../c4/resolve/service.js";
+import { isUseCase } from "../fleet.js";
+import { featureFlows, USECASE_SUBDIR } from "./flows.js";
+/**
+ * The flows this feature carries, parsed over the post-merge map — or the
+ * honest refusal to say.
+ *
+ * A feature with no `usecases/` directory is `read` with no views, at the cost
+ * of one walk over a directory that is not there. That is the axis's
+ * per-feature opt-in and the whole price a fleet that has not adopted it pays.
+ */
+export async function readFeatureFlows(req) {
+    const flows = await featureFlows(req.featureDir);
+    if (flows.length === 0) {
+        return { kind: "read", views: [], model: { elements: [], relationships: [], known: req.known }, resolve: (id) => id };
+    }
+    const staged = await stageMergedProject({
+        docsDir: req.docsDir,
+        featureDir: req.featureDir,
+        featureId: req.featureId,
+        documents: flows.map((flow) => ({ rel: `${USECASE_SUBDIR}/${flow.rel}`, path: flow.path })),
+        ...(req.load === undefined ? {} : { load: req.load }),
+    });
+    return interpret(staged, req.known);
+}
+/**
+ * The staged parse as the use-case axis reads it.
+ *
+ * THE FEATURE'S OWN FLOWS ONLY. A living use case is the fleet scan's to report,
+ * and repeating it here would file somebody else's finding against this
+ * feature's gate — the same scoping every other feature-side check keeps.
+ */
+function interpret(staged, known) {
+    if (staged.kind === "unreadable")
+        return { kind: "unreadable", errors: staged.errors };
+    const { doc, real, mine } = staged;
+    // Through `isUseCase`, because `UseCaseScan.views` is documented as the
+    // reserved-tag views ONLY and this is the type's second producer. The
+    // resolvers below filter on the prefix anyway, so no answer changes today —
+    // but `flowsClaiming` and `servicesInFlowsClaiming` take a `UseCaseScan` and
+    // read `scan.views` straight, and the whole point of exporting one predicate
+    // was that a second spelling of the opt-in drifts.
+    const views = (doc.views ?? [])
+        .filter((view) => view.sourcePath !== undefined && mine.has(view.sourcePath))
+        .filter(isUseCase);
+    return {
+        kind: "read",
+        views: views.map((view) => ({ ...view, sourcePath: view.sourcePath === undefined ? view.sourcePath : real(view.sourcePath) })),
+        model: { elements: doc.elements, relationships: doc.relationships, known },
+        resolve: serviceResolver(doc.elements, known),
+    };
+}
+//# sourceMappingURL=overlay.js.map

package/dist/core/usecases/delta/overlay.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"overlay.js","sourceRoot":"","sources":["../../../../src/core/usecases/delta/overlay.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AACH,OAAO,EAAkB,MAAM,oBAAoB,CAAC;AACpD,OAAO,EAAE,kBAAkB,EAAsB,MAAM,4BAA4B,CAAC;AACpF,OAAO,EAAE,eAAe,EAAE,MAAM,6BAA6B,CAAC;AAE9D,OAAO,EAAE,SAAS,EAAoB,MAAM,aAAa,CAAC;AAC1D,OAAO,EAAE,YAAY,EAAE,cAAc,EAAE,MAAM,YAAY,CAAC;AA+B1D;;;;;;;GAOG;AACH,MAAM,CAAC,KAAK,UAAU,gBAAgB,CAAC,GAAuB;IAC5D,MAAM,KAAK,GAAG,MAAM,YAAY,CAAC,GAAG,CAAC,UAAU,CAAC,CAAC;IACjD,IAAI,KAAK,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;QACvB,OAAO,EAAE,IAAI,EAAE,MAAM,EAAE,KAAK,EAAE,EAAE,EAAE,KAAK,EAAE,EAAE,QAAQ,EAAE,EAAE,EAAE,aAAa,EAAE,EAAE,EAAE,KAAK,EAAE,GAAG,CAAC,KAAK,EAAE,EAAE,OAAO,EAAE,CAAC,EAAE,EAAE,EAAE,CAAC,EAAE,EAAE,CAAC;IACxH,CAAC;IACD,MAAM,MAAM,GAAG,MAAM,kBAAkB,CAAC;QACtC,OAAO,EAAE,GAAG,CAAC,OAAO;QACpB,UAAU,EAAE,GAAG,CAAC,UAAU;QAC1B,SAAS,EAAE,GAAG,CAAC,SAAS;QACxB,SAAS,EAAE,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,EAAE,GAAG,EAAE,GAAG,cAAc,IAAI,IAAI,CAAC,GAAG,EAAE,EAAE,IAAI,EAAE,IAAI,CAAC,IAAI,EAAE,CAAC,CAAC;QAC3F,GAAG,CAAC,GAAG,CAAC,IAAI,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,CAAC;KACtD,CAAC,CAAC;IACH,OAAO,SAAS,CAAC,MAAM,EAAE,GAAG,CAAC,KAAK,CAAC,CAAC;AACtC,CAAC;AAED;;;;;;GAMG;AACH,SAAS,SAAS,CAAC,MAAqB,EAAE,KAA0B;IAClE,IAAI,MAAM,CAAC,IAAI,KAAK,YAAY;QAAE,OAAO,EAAE,IAAI,EAAE,YAAY,EAAE,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,CAAC;IACvF,MAAM,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,EAAE,GAAG,MAAM,CAAC;IACnC,wEAAwE;IACxE,sEAAsE;IACtE,4EAA4E;IAC5E,6EAA6E;IAC7E,6EAA6E;IAC7E,mDAAmD;IACnD,MAAM,KAAK,GAAG,CAAC,GAAG,CAAC,KAAK,IAAI,EAAE,CAAC;SAC5B,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,UAAU,KAAK,SAAS,IAAI,IAAI,CAAC,GAAG,CAAC,IAAI,CAAC,UAAU,CAAC,CAAC;SAC5E,MAAM,CAAC,SAAS,CAAC,CAAC;IACrB,OAAO;QACL,IAAI,EAAE,MAAM;QACZ,KAAK,EAAE,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,EAAE,GAAG,IAAI,EAAE,UAAU,EAAE,IAAI,CAAC,UAAU,KAAK,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,UAAU,CAAC,EAAE,CAAC,CAAC;QAC9H,KAAK,EAAE,EAAE,QAAQ,EAAE,GAAG,CAAC,QAAQ,EAAE,aAAa,EAAE,GAAG,CAAC,aAAa,EAAE,KAAK,EAAE;QAC1E,OAAO,EAAE,eAAe,CAAC,GAAG,CAAC,QAAQ,EAAE,KAAK,CAAC;KAC9C,CAAC;AACJ,CAAC","sourcesContent":["/**\n * A feature's flows, read against the fleet map AS THIS FEATURE'S MERGE WOULD\n * LEAVE IT.\n *\n * The staging and the merge preview that make that possible are no longer here:\n * they moved to `core/c4/project/staged.ts` when the deployment slot became the\n * second feature-local `.likec4` document, because a second copy of that\n * machinery is the copy that drifts, and the two would disagree first about the\n * merge preview — the one thing both axes' refusals rest on. That module's\n * header carries the WHY of the post-merge corpus; this one keeps what is\n * particular to use cases, which is the interpretation: which of the staged\n * views are this feature's, and what they resolve against.\n *\n * FAIL CLOSED, and not silently. Every failure is the `unreadable` arm carrying\n * LikeC4's own messages: a flow this cannot read is never a flow that grades\n * clean, which is the asymmetry `../fleet.ts` states for the fleet-scope scan.\n */\nimport { type LoadedDoc } from \"../../c4/likec4.js\";\nimport { stageMergedProject, type StagedProject } from \"../../c4/project/staged.js\";\nimport { serviceResolver } from \"../../c4/resolve/service.js\";\nimport type { DocsDir, FeatureDir } from \"../../kernel/ids/dirs.js\";\nimport { isUseCase, type UseCaseScan } from \"../fleet.js\";\nimport { featureFlows, USECASE_SUBDIR } from \"./flows.js\";\n\n/** Everything the overlay needs, and nothing it would have to read twice. */\nexport interface FlowOverlayRequest {\n  docsDir: DocsDir;\n  featureDir: FeatureDir;\n  /** The feature's id — the tag that selects the delta's own additions. */\n  featureId: string;\n  /**\n   * The enumerated fleet, for the element→service resolver. It rides in for the\n   * reason every other edge join carries it: without it a hop drawn into a\n   * modelled container `payment.api` resolves to a service called \"api\" that\n   * has never existed.\n   */\n  known: ReadonlySet<string>;\n  /**\n   * The caller's memoised LikeC4 read, when it has one. Only `delta.likec4` goes\n   * through it, and only to compute the merge preview — but the caller\n   * (`featureCoherence`) has already loaded that exact document, and loading one\n   * spins a fresh Langium workspace, which `core/coherence/coherence.ts` calls\n   * the dominant per-feature cost.\n   *\n   * A FUNCTION rather than the `FleetContext` itself, deliberately: this package\n   * has no edge to `core/fleet-context.ts`, one memoised read does not justify\n   * adding one, and the edge would push `core/usecases/` up a DAG level for\n   * nothing. Absent, the load happens directly, which is right for a caller\n   * running outside an invocation index.\n   */\n  load?: (path: string) => Promise<LoadedDoc>;\n}\n\n/**\n * The flows this feature carries, parsed over the post-merge map — or the\n * honest refusal to say.\n *\n * A feature with no `usecases/` directory is `read` with no views, at the cost\n * of one walk over a directory that is not there. That is the axis's\n * per-feature opt-in and the whole price a fleet that has not adopted it pays.\n */\nexport async function readFeatureFlows(req: FlowOverlayRequest): Promise<UseCaseScan> {\n  const flows = await featureFlows(req.featureDir);\n  if (flows.length === 0) {\n    return { kind: \"read\", views: [], model: { elements: [], relationships: [], known: req.known }, resolve: (id) => id };\n  }\n  const staged = await stageMergedProject({\n    docsDir: req.docsDir,\n    featureDir: req.featureDir,\n    featureId: req.featureId,\n    documents: flows.map((flow) => ({ rel: `${USECASE_SUBDIR}/${flow.rel}`, path: flow.path })),\n    ...(req.load === undefined ? {} : { load: req.load }),\n  });\n  return interpret(staged, req.known);\n}\n\n/**\n * The staged parse as the use-case axis reads it.\n *\n * THE FEATURE'S OWN FLOWS ONLY. A living use case is the fleet scan's to report,\n * and repeating it here would file somebody else's finding against this\n * feature's gate — the same scoping every other feature-side check keeps.\n */\nfunction interpret(staged: StagedProject, known: ReadonlySet<string>): UseCaseScan {\n  if (staged.kind === \"unreadable\") return { kind: \"unreadable\", errors: staged.errors };\n  const { doc, real, mine } = staged;\n  // Through `isUseCase`, because `UseCaseScan.views` is documented as the\n  // reserved-tag views ONLY and this is the type's second producer. The\n  // resolvers below filter on the prefix anyway, so no answer changes today —\n  // but `flowsClaiming` and `servicesInFlowsClaiming` take a `UseCaseScan` and\n  // read `scan.views` straight, and the whole point of exporting one predicate\n  // was that a second spelling of the opt-in drifts.\n  const views = (doc.views ?? [])\n    .filter((view) => view.sourcePath !== undefined && mine.has(view.sourcePath))\n    .filter(isUseCase);\n  return {\n    kind: \"read\",\n    views: views.map((view) => ({ ...view, sourcePath: view.sourcePath === undefined ? view.sourcePath : real(view.sourcePath) })),\n    model: { elements: doc.elements, relationships: doc.relationships, known },\n    resolve: serviceResolver(doc.elements, known),\n  };\n}\n"]}

package/dist/core/usecases/fleet.js

@@ -0,0 +1,137 @@
+/**
+ * The fleet's use cases, read once for whoever asks — and NOT read at all when
+ * the fleet demonstrably has none.
+ *
+ * `validate --all` grades use cases as part of a run that was already loading
+ * `architecture/` as a LikeC4 project, so it pays nothing extra. Every reader
+ * added in phase 4 is in a different position: `loam diff`, `loam delta`,
+ * `loam context` and `loam explore` did not load the fleet map as a project
+ * before, and `loam delta` in particular sits in `/loam-implement`'s inner loop
+ * — a Langium workspace spin-up there is felt on every iteration of somebody's
+ * day. So this module's whole job is to answer "which use cases does the fleet
+ * declare?" and, in the common case where the answer is none, to answer it
+ * without starting LikeC4 at all.
+ *
+ * THE CHEAP GATE IS A BYTE SCAN, and it is sound rather than heuristic. A view
+ * is a use case only if it carries a reserved tag — `#cap-<slug>` or
+ * `#req-<slug>`, `isUseCase` below is the whole test — and LikeC4 refuses an
+ * undeclared tag, so a fleet with a use case has the literal text `cap-` or
+ * `req-` in the file that declares the view AND in the file that declares the
+ * tag. A document set in which no file contains either substring therefore
+ * declares no use case, and `{ views: [] }` is the correct answer, not an
+ * evasion. The scan reads bytes rather than decoded text on purpose: it is
+ * looking for an ASCII substring, and `readFile(path, "utf8")` on a document
+ * that is not UTF-8 would substitute U+FFFD and could hide it.
+ *
+ * BOTH PREFIXES, because the gate and the predicate answer one question and a
+ * gate narrower than the predicate is silence rather than a smaller answer. A
+ * fleet whose only flow is tagged `#req-` alone declares `tag req-…` and no
+ * `cap-` anywhere, so a `cap-`-only scan returned `false` and none of the five
+ * readers ever loaded the project — the widening below would have fixed nothing
+ * without this one.
+ *
+ * The gate FAILS CLOSED. A document this module cannot open is treated as one
+ * that might mention the prefix, so the project load happens and reports the
+ * failure as a hole. The alternative — reading an EACCES as "no tag here" — is
+ * the fail-open shape docs/CODE-STYLE.md forbids at a validator, arriving in an
+ * optimisation.
+ */
+import { readFile } from "node:fs/promises";
+import { CAP_TAG_PREFIX, REQ_TAG_PREFIX } from "../capabilities/usecase-join.js";
+import { architectureDir, loadArchitecture } from "../c4/project/architecture.js";
+import { architectureDocuments } from "../c4/project/documents.js";
+import { serviceResolver } from "../c4/resolve/service.js";
+import { subsystemViewsPath } from "../repo/paths.js";
+/**
+ * Does any document in the set even mention a reserved tag prefix?
+ *
+ * Sequential and short-circuiting ON PURPOSE — the usual "no await in a loop"
+ * rule is about independent work that all has to finish, and this loop exists
+ * precisely so that a fleet whose first file declares a use case stops reading
+ * the other ninety-nine.
+ *
+ * `req-` is the looser of the two substrings and that is accepted knowingly: a
+ * document mentioning it in prose costs one project load loam would otherwise
+ * have skipped, which is a slower right answer. Dropping it costs a wrong one.
+ */
+async function mentionsTagPrefix(paths) {
+    for (const path of paths) {
+        try {
+            const bytes = await readFile(path);
+            if (bytes.includes(CAP_TAG_PREFIX) || bytes.includes(REQ_TAG_PREFIX))
+                return true;
+        }
+        catch {
+            // Unreadable is not "no tag": the project load below owns that failure and
+            // will report it as a hole naming the document. Answering `false` here
+            // would let an unopenable file grade the fleet as having no use cases.
+            return true;
+        }
+    }
+    return false;
+}
+/**
+ * Is this a use case at all? — the ONE answer, for `validate` and every reader
+ * alike.
+ *
+ * EITHER RESERVED PREFIX OPTS A VIEW IN. A view carrying `#req-CHK-ONCE` and no
+ * `#cap-` tag is an author who asked to be graded and forgot half the claim; it
+ * earns `usecase.requirement-unresolved`'s `unscoped` arm rather than silence,
+ * and SCHEMA.md has said so since the tag shipped.
+ *
+ * It is exported because it was the asymmetry, not the rule, that was the
+ * defect. `validate --all` widened here and the readers did not, so a
+ * `#req-`-only flow was graded hop by hop by the gate and invisible to `loam
+ * diff`, `delta`, `status`, the packs and `list capabilities` — a fleet where
+ * the gate and the report disagree about what exists, which is worse than
+ * either answer alone. One predicate is what stops that recurring: a caller
+ * that spells `startsWith` itself is a second answer waiting to drift.
+ *
+ * The parameter is the smallest shape the test needs rather than `ParsedView`,
+ * so a caller holding a view-like row does not have to build one to ask. Both
+ * prefix tests match their resolver's exactly, case included, so a view can
+ * never be opted in here and read as untagged in `resolveCapabilityTags`.
+ *
+ * NOT the same question as `flowsClaiming`'s. That one asks which flows claim
+ * capability X and matches the whole `cap-<slug>` tag; a `#req-`-only view
+ * claims none, and it is correct for it to stay out of that answer while
+ * counting as a use case here.
+ */
+export function isUseCase(view) {
+    return view.tags.some((tag) => tag.startsWith(CAP_TAG_PREFIX) || tag.startsWith(REQ_TAG_PREFIX));
+}
+/**
+ * The fleet's declared use cases, with the model they are drawn over.
+ *
+ * Reads only, throws nothing, and refuses nothing: every failure is the
+ * `unreadable` arm. Callers memoise this per invocation — nothing is cached
+ * here, because a module-level cache keyed on a docsDir would leak across the
+ * `chdir`-per-test processes AGENTS.md warns about and, in a long-running host,
+ * across invocations.
+ */
+export async function readUseCases(req) {
+    const none = {
+        kind: "read",
+        views: [],
+        model: { elements: [], relationships: [], known: req.known },
+        resolve: (id) => id,
+    };
+    const dir = architectureDir(req.docsDir);
+    const documents = await architectureDocuments(dir, [subsystemViewsPath(req.docsDir)]);
+    if (!(await mentionsTagPrefix(documents)))
+        return none;
+    const doc = await loadArchitecture(req.docsDir);
+    // loam's standing rule, at project altitude: errors mean no model. A use-case
+    // file with one unresolved element leaves the whole project unusable, and
+    // grading a flow against half a map is the wrong answer this refuses to give.
+    if (doc.errors.length > 0) {
+        return { kind: "unreadable", errors: doc.errors.map((e) => e.message) };
+    }
+    return {
+        kind: "read",
+        views: (doc.views ?? []).filter(isUseCase),
+        model: { elements: doc.elements, relationships: doc.relationships, known: req.known },
+        resolve: serviceResolver(doc.elements, req.known),
+    };
+}
+//# sourceMappingURL=fleet.js.map

package/dist/core/usecases/fleet.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"fleet.js","sourceRoot":"","sources":["../../../src/core/usecases/fleet.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqCG;AACH,OAAO,EAAE,QAAQ,EAAE,MAAM,kBAAkB,CAAC;AAE5C,OAAO,EAAE,cAAc,EAAE,cAAc,EAAE,MAAM,iCAAiC,CAAC;AAEjF,OAAO,EAAE,eAAe,EAAE,gBAAgB,EAAE,MAAM,+BAA+B,CAAC;AAClF,OAAO,EAAE,qBAAqB,EAAE,MAAM,4BAA4B,CAAC;AACnE,OAAO,EAAE,eAAe,EAAE,MAAM,0BAA0B,CAAC;AAE3D,OAAO,EAAE,kBAAkB,EAAE,MAAM,kBAAkB,CAAC;AAyDtD;;;;;;;;;;;GAWG;AACH,KAAK,UAAU,iBAAiB,CAAC,KAAwB;IACvD,KAAK,MAAM,IAAI,IAAI,KAAK,EAAE,CAAC;QACzB,IAAI,CAAC;YACH,MAAM,KAAK,GAAG,MAAM,QAAQ,CAAC,IAAI,CAAC,CAAC;YACnC,IAAI,KAAK,CAAC,QAAQ,CAAC,cAAc,CAAC,IAAI,KAAK,CAAC,QAAQ,CAAC,cAAc,CAAC;gBAAE,OAAO,IAAI,CAAC;QACpF,CAAC;QAAC,MAAM,CAAC;YACP,2EAA2E;YAC3E,uEAAuE;YACvE,uEAAuE;YACvE,OAAO,IAAI,CAAC;QACd,CAAC;IACH,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AACH,MAAM,UAAU,SAAS,CAAC,IAAiC;IACzD,OAAO,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,CAAC,UAAU,CAAC,cAAc,CAAC,IAAI,GAAG,CAAC,UAAU,CAAC,cAAc,CAAC,CAAC,CAAC;AACnG,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,CAAC,KAAK,UAAU,YAAY,CAAC,GAAmB;IACpD,MAAM,IAAI,GAAgB;QACxB,IAAI,EAAE,MAAM;QACZ,KAAK,EAAE,EAAE;QACT,KAAK,EAAE,EAAE,QAAQ,EAAE,EAAE,EAAE,aAAa,EAAE,EAAE,EAAE,KAAK,EAAE,GAAG,CAAC,KAAK,EAAE;QAC5D,OAAO,EAAE,CAAC,EAAE,EAAE,EAAE,CAAC,EAAE;KACpB,CAAC;IACF,MAAM,GAAG,GAAG,eAAe,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC;IACzC,MAAM,SAAS,GAAG,MAAM,qBAAqB,CAAC,GAAG,EAAE,CAAC,kBAAkB,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC;IACtF,IAAI,CAAC,CAAC,MAAM,iBAAiB,CAAC,SAAS,CAAC,CAAC;QAAE,OAAO,IAAI,CAAC;IAEvD,MAAM,GAAG,GAAG,MAAM,gBAAgB,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC;IAChD,8EAA8E;IAC9E,0EAA0E;IAC1E,8EAA8E;IAC9E,IAAI,GAAG,CAAC,MAAM,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC1B,OAAO,EAAE,IAAI,EAAE,YAAY,EAAE,MAAM,EAAE,GAAG,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;IAC1E,CAAC;IACD,OAAO;QACL,IAAI,EAAE,MAAM;QACZ,KAAK,EAAE,CAAC,GAAG,CAAC,KAAK,IAAI,EAAE,CAAC,CAAC,MAAM,CAAC,SAAS,CAAC;QAC1C,KAAK,EAAE,EAAE,QAAQ,EAAE,GAAG,CAAC,QAAQ,EAAE,aAAa,EAAE,GAAG,CAAC,aAAa,EAAE,KAAK,EAAE,GAAG,CAAC,KAAK,EAAE;QACrF,OAAO,EAAE,eAAe,CAAC,GAAG,CAAC,QAAQ,EAAE,GAAG,CAAC,KAAK,CAAC;KAClD,CAAC;AACJ,CAAC","sourcesContent":["/**\n * The fleet's use cases, read once for whoever asks — and NOT read at all when\n * the fleet demonstrably has none.\n *\n * `validate --all` grades use cases as part of a run that was already loading\n * `architecture/` as a LikeC4 project, so it pays nothing extra. Every reader\n * added in phase 4 is in a different position: `loam diff`, `loam delta`,\n * `loam context` and `loam explore` did not load the fleet map as a project\n * before, and `loam delta` in particular sits in `/loam-implement`'s inner loop\n * — a Langium workspace spin-up there is felt on every iteration of somebody's\n * day. So this module's whole job is to answer \"which use cases does the fleet\n * declare?\" and, in the common case where the answer is none, to answer it\n * without starting LikeC4 at all.\n *\n * THE CHEAP GATE IS A BYTE SCAN, and it is sound rather than heuristic. A view\n * is a use case only if it carries a reserved tag — `#cap-<slug>` or\n * `#req-<slug>`, `isUseCase` below is the whole test — and LikeC4 refuses an\n * undeclared tag, so a fleet with a use case has the literal text `cap-` or\n * `req-` in the file that declares the view AND in the file that declares the\n * tag. A document set in which no file contains either substring therefore\n * declares no use case, and `{ views: [] }` is the correct answer, not an\n * evasion. The scan reads bytes rather than decoded text on purpose: it is\n * looking for an ASCII substring, and `readFile(path, \"utf8\")` on a document\n * that is not UTF-8 would substitute U+FFFD and could hide it.\n *\n * BOTH PREFIXES, because the gate and the predicate answer one question and a\n * gate narrower than the predicate is silence rather than a smaller answer. A\n * fleet whose only flow is tagged `#req-` alone declares `tag req-…` and no\n * `cap-` anywhere, so a `cap-`-only scan returned `false` and none of the five\n * readers ever loaded the project — the widening below would have fixed nothing\n * without this one.\n *\n * The gate FAILS CLOSED. A document this module cannot open is treated as one\n * that might mention the prefix, so the project load happens and reports the\n * failure as a hole. The alternative — reading an EACCES as \"no tag here\" — is\n * the fail-open shape docs/CODE-STYLE.md forbids at a validator, arriving in an\n * optimisation.\n */\nimport { readFile } from \"node:fs/promises\";\nimport type { StepScope } from \"../c4/resolve/steps.js\";\nimport { CAP_TAG_PREFIX, REQ_TAG_PREFIX } from \"../capabilities/usecase-join.js\";\nimport type { ParsedView } from \"../c4/parsed/dynamic-views.js\";\nimport { architectureDir, loadArchitecture } from \"../c4/project/architecture.js\";\nimport { architectureDocuments } from \"../c4/project/documents.js\";\nimport { serviceResolver } from \"../c4/resolve/service.js\";\nimport type { DocsDir } from \"../kernel/ids/dirs.js\";\nimport { subsystemViewsPath } from \"../repo/paths.js\";\n\n/**\n * What the fleet's use cases are, or the honest refusal to say.\n *\n * Two variants rather than a record with an `unreadable` flag, because the\n * fields are not independent: a project that did not parse has no elements to\n * resolve against and no views to grade, and a caller handed\n * `{ views: [], unreadable: true }` is one `.length` check away from printing\n * \"no use cases touch this service\" about a fleet nobody could read. Tagged,\n * that state stops being constructible — every caller has to name the\n * `unreadable` arm to get at the views.\n *\n * `read` with an empty `views` is the ordinary answer for a fleet that draws no\n * use cases, and it is exactly what the cheap gate returns without loading\n * anything: the gate is an optimisation over a question with a known answer,\n * never a third verdict.\n */\nexport type UseCaseScan =\n  | {\n      kind: \"read\";\n      /** The reserved-tag views ONLY — `isUseCase` below is the opt-in, and the only one. */\n      views: readonly ParsedView[];\n      /**\n       * What a hop is attributed against, built ONCE per scan. It carries the\n       * fleet set that `resolve` below was built from, which is what stops\n       * \"which service is this element\" being answered one way by\n       * `attributeStep`'s fallback tier and another by a caller's own join —\n       * the same reason `validate`'s `StepGrading` holds both together.\n       *\n       * `known` is REQUIRED here while `StepScope` leaves it optional, and the\n       * narrowing is load-bearing rather than tidy: every scan is built from a\n       * `UseCaseRequest` that has one, so a consumer reading `model.known` was\n       * writing an `undefined` branch that could not be reached and could not be\n       * tested. A `StepScope` is still what `attributeStep` receives.\n       */\n      model: StepScope & { known: ReadonlySet<string> };\n      /** One element→service resolver for the whole scan, built with the enumerated fleet. */\n      resolve: (id: string) => string;\n    }\n  | {\n      kind: \"unreadable\";\n      /** LikeC4's own messages, so a caller can say WHICH document broke. */\n      errors: string[];\n    };\n\nexport interface UseCaseRequest {\n  docsDir: DocsDir;\n  /**\n   * The enumerated fleet. It rides into the resolver for the reason every other\n   * edge join carries it: without it, a step drawn into a modelled container\n   * `payment.api` resolves to a service called \"api\" that has never existed\n   * (docs/DESIGN.md's serviceResolver-known row).\n   */\n  known: ReadonlySet<string>;\n}\n\n/**\n * Does any document in the set even mention a reserved tag prefix?\n *\n * Sequential and short-circuiting ON PURPOSE — the usual \"no await in a loop\"\n * rule is about independent work that all has to finish, and this loop exists\n * precisely so that a fleet whose first file declares a use case stops reading\n * the other ninety-nine.\n *\n * `req-` is the looser of the two substrings and that is accepted knowingly: a\n * document mentioning it in prose costs one project load loam would otherwise\n * have skipped, which is a slower right answer. Dropping it costs a wrong one.\n */\nasync function mentionsTagPrefix(paths: readonly string[]): Promise<boolean> {\n  for (const path of paths) {\n    try {\n      const bytes = await readFile(path);\n      if (bytes.includes(CAP_TAG_PREFIX) || bytes.includes(REQ_TAG_PREFIX)) return true;\n    } catch {\n      // Unreadable is not \"no tag\": the project load below owns that failure and\n      // will report it as a hole naming the document. Answering `false` here\n      // would let an unopenable file grade the fleet as having no use cases.\n      return true;\n    }\n  }\n  return false;\n}\n\n/**\n * Is this a use case at all? — the ONE answer, for `validate` and every reader\n * alike.\n *\n * EITHER RESERVED PREFIX OPTS A VIEW IN. A view carrying `#req-CHK-ONCE` and no\n * `#cap-` tag is an author who asked to be graded and forgot half the claim; it\n * earns `usecase.requirement-unresolved`'s `unscoped` arm rather than silence,\n * and SCHEMA.md has said so since the tag shipped.\n *\n * It is exported because it was the asymmetry, not the rule, that was the\n * defect. `validate --all` widened here and the readers did not, so a\n * `#req-`-only flow was graded hop by hop by the gate and invisible to `loam\n * diff`, `delta`, `status`, the packs and `list capabilities` — a fleet where\n * the gate and the report disagree about what exists, which is worse than\n * either answer alone. One predicate is what stops that recurring: a caller\n * that spells `startsWith` itself is a second answer waiting to drift.\n *\n * The parameter is the smallest shape the test needs rather than `ParsedView`,\n * so a caller holding a view-like row does not have to build one to ask. Both\n * prefix tests match their resolver's exactly, case included, so a view can\n * never be opted in here and read as untagged in `resolveCapabilityTags`.\n *\n * NOT the same question as `flowsClaiming`'s. That one asks which flows claim\n * capability X and matches the whole `cap-<slug>` tag; a `#req-`-only view\n * claims none, and it is correct for it to stay out of that answer while\n * counting as a use case here.\n */\nexport function isUseCase(view: { tags: readonly string[] }): boolean {\n  return view.tags.some((tag) => tag.startsWith(CAP_TAG_PREFIX) || tag.startsWith(REQ_TAG_PREFIX));\n}\n\n/**\n * The fleet's declared use cases, with the model they are drawn over.\n *\n * Reads only, throws nothing, and refuses nothing: every failure is the\n * `unreadable` arm. Callers memoise this per invocation — nothing is cached\n * here, because a module-level cache keyed on a docsDir would leak across the\n * `chdir`-per-test processes AGENTS.md warns about and, in a long-running host,\n * across invocations.\n */\nexport async function readUseCases(req: UseCaseRequest): Promise<UseCaseScan> {\n  const none: UseCaseScan = {\n    kind: \"read\",\n    views: [],\n    model: { elements: [], relationships: [], known: req.known },\n    resolve: (id) => id,\n  };\n  const dir = architectureDir(req.docsDir);\n  const documents = await architectureDocuments(dir, [subsystemViewsPath(req.docsDir)]);\n  if (!(await mentionsTagPrefix(documents))) return none;\n\n  const doc = await loadArchitecture(req.docsDir);\n  // loam's standing rule, at project altitude: errors mean no model. A use-case\n  // file with one unresolved element leaves the whole project unusable, and\n  // grading a flow against half a map is the wrong answer this refuses to give.\n  if (doc.errors.length > 0) {\n    return { kind: \"unreadable\", errors: doc.errors.map((e) => e.message) };\n  }\n  return {\n    kind: \"read\",\n    views: (doc.views ?? []).filter(isUseCase),\n    model: { elements: doc.elements, relationships: doc.relationships, known: req.known },\n    resolve: serviceResolver(doc.elements, req.known),\n  };\n}\n"]}