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

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/arch.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"]}

package/dist/core/usecases/operations.js

@@ -0,0 +1,111 @@
+/**
+ * Which hops of which business flows a contract removal breaks.
+ *
+ * `loam diff --base` already answers "who still depends on this operation" with
+ * landscape edges and other services' living requirements. Both are true and
+ * neither is the sentence a reviewer wants: an edge is a line in a diagram and a
+ * requirement is a heading in somebody else's spec, while "step 4 of Checkout
+ * stops working" is the fact a human weighs a pull request against. This module
+ * is the join that produces that sentence, and it produces NOTHING ELSE — no
+ * finding, no code, no severity. `core/diff/victims.ts` folds its answers into
+ * the `details[]` of the two codes that already exist.
+ *
+ * ## Attributed is a victim; contested is a suspension
+ *
+ * The distinction is the whole reason this module is careful rather than a
+ * filter. `attributeStep` (core/c4/arch.ts) grades a hop by the DISTINCT-op
+ * count across the relationships backing it:
+ *
+ *  - `attributed` with `op === X` means every relationship behind the hop agrees
+ *    the hop exercises X. Remove X and the flow breaks at that hop. That is
+ *    positive evidence, and it is a victim.
+ *  - `contested` means the relationships DISAGREE, so loam does not know which
+ *    operation the hop exercises. It must not claim the flow breaks — a guessed
+ *    victim reads exactly like a real one and turns a warn into an error on
+ *    somebody's PR — and it must not go silent either, because silence here is
+ *    the fail-open shape `ConsumerScan.suspended` exists to forbid. It is a
+ *    suspension: loam says it could not answer.
+ *
+ * A contested hop is suspended only when X is among its candidate operations.
+ * That is not a noise trade, it is the honest boundary: the candidates ARE the
+ * relationships backing the hop, so an operation none of them names is an
+ * operation the hop cannot be exercising under any reading of the disagreement.
+ * Suspending every contested hop in the fleet on every removal would report
+ * doubt loam does not actually have.
+ *
+ * An `unbacked` hop is neither. Nothing in the model backs it, so it names no
+ * operation of anybody's contract — `usecase.step-unbacked` is already the error
+ * that convicts it, and repeating that here would file a modelling defect
+ * against whoever happened to remove an endpoint.
+ */
+import { attributeStep } from "../c4/arch.js";
+import { hopPlace } from "./place.js";
+const EMPTY = { breaks: [], unsure: [] };
+/** Every hop of every graded use case, view order preserved, so output is stable. */
+function hops(scan) {
+    return scan.views.flatMap((view) => view.steps.map((step) => ({ view, step })));
+}
+/**
+ * The flows one removed operation breaks, and the ones loam cannot answer for.
+ *
+ * An `unreadable` scan contributes NOTHING — neither break nor suspension — and
+ * that is `core/diff/victims.ts`'s own landscape doctrine applied one axis over:
+ * an unreadable fleet map proves nothing either way, `landscape.invalid` is
+ * validate's finding to make, and inventing doubt out of a parse error would
+ * point the reviewer at a file their change never touched. The caller reports
+ * the hole; this join stays quiet about it.
+ */
+export function hopsExercising(scan, removed) {
+    if (scan.kind !== "read")
+        return EMPTY;
+    const out = { breaks: [], unsure: [] };
+    for (const { view, step } of hops(scan)) {
+        const attribution = attributeStep(step, scan.model);
+        if (attribution.verdict === "unbacked")
+            continue;
+        // The callee, through the SAME resolver every other join in this run uses,
+        // so a hop drawn into a modelled container `payment.api` is filed against
+        // payment-service rather than against a service called "api".
+        if (scan.resolve(attribution.to) !== removed.provider)
+            continue;
+        if (attribution.verdict === "attributed") {
+            if (attribution.op === removed.op)
+                out.breaks.push(hopPlace(view, step));
+            continue;
+        }
+        if (!attribution.ops.includes(removed.op))
+            continue;
+        out.unsure.push(`${hopPlace(view, step)} — ${attribution.rels.length} relationships back ` +
+            `${attribution.from} -> ${attribution.to} and they name different operations, so whether this hop ` +
+            `exercises '${removed.op}' could not be answered`);
+    }
+    return out;
+}
+/**
+ * The flows one removed message breaks.
+ *
+ * No suspension arm, and the asymmetry is a fact about the model rather than an
+ * omission: `attributeStep` contests OPERATIONS, because that is where two
+ * relationships between one pair of endpoints can disagree. A `consumes` edge
+ * names a message outright, so a hop either is backed by one or is not — there
+ * is no disagreement for loam to refuse to resolve.
+ *
+ * The provider exclusion mirrors `messageConsumers` exactly: an edge INTO the
+ * provider is the provider's own consumption, which leaves with the same change,
+ * so a hop backed only by that edge is not a victim of it.
+ */
+export function hopsConsuming(scan, removed) {
+    if (scan.kind !== "read")
+        return [];
+    const out = [];
+    for (const { view, step } of hops(scan)) {
+        const attribution = attributeStep(step, scan.model);
+        if (attribution.verdict === "unbacked")
+            continue;
+        const consumes = attribution.rels.some((rel) => rel.consumes === removed.name && scan.resolve(rel.target) !== removed.provider);
+        if (consumes)
+            out.push(hopPlace(view, step));
+    }
+    return out;
+}
+//# sourceMappingURL=operations.js.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"operations.js","sourceRoot":"","sources":["../../../src/core/usecases/operations.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAuCG;AACH,OAAO,EAAE,aAAa,EAAE,MAAM,eAAe,CAAC;AAE9C,OAAO,EAAE,QAAQ,EAAE,MAAM,YAAY,CAAC;AA4BtC,MAAM,KAAK,GAAgB,EAAE,MAAM,EAAE,EAAE,EAAE,MAAM,EAAE,EAAE,EAAE,CAAC;AAEtD,qFAAqF;AACrF,SAAS,IAAI,CAAC,IAA4C;IACxD,OAAO,IAAI,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,EAAE,IAAI,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC;AAClF,CAAC;AAED;;;;;;;;;GASG;AACH,MAAM,UAAU,cAAc,CAAC,IAAiB,EAAE,OAAyB;IACzE,IAAI,IAAI,CAAC,IAAI,KAAK,MAAM;QAAE,OAAO,KAAK,CAAC;IACvC,MAAM,GAAG,GAAgB,EAAE,MAAM,EAAE,EAAE,EAAE,MAAM,EAAE,EAAE,EAAE,CAAC;IACpD,KAAK,MAAM,EAAE,IAAI,EAAE,IAAI,EAAE,IAAI,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC;QACxC,MAAM,WAAW,GAAG,aAAa,CAAC,IAAI,EAAE,IAAI,CAAC,KAAK,CAAC,CAAC;QACpD,IAAI,WAAW,CAAC,OAAO,KAAK,UAAU;YAAE,SAAS;QACjD,2EAA2E;QAC3E,0EAA0E;QAC1E,8DAA8D;QAC9D,IAAI,IAAI,CAAC,OAAO,CAAC,WAAW,CAAC,EAAE,CAAC,KAAK,OAAO,CAAC,QAAQ;YAAE,SAAS;QAChE,IAAI,WAAW,CAAC,OAAO,KAAK,YAAY,EAAE,CAAC;YACzC,IAAI,WAAW,CAAC,EAAE,KAAK,OAAO,CAAC,EAAE;gBAAE,GAAG,CAAC,MAAM,CAAC,IAAI,CAAC,QAAQ,CAAC,IAAI,EAAE,IAAI,CAAC,CAAC,CAAC;YACzE,SAAS;QACX,CAAC;QACD,IAAI,CAAC,WAAW,CAAC,GAAG,CAAC,QAAQ,CAAC,OAAO,CAAC,EAAE,CAAC;YAAE,SAAS;QACpD,GAAG,CAAC,MAAM,CAAC,IAAI,CACb,GAAG,QAAQ,CAAC,IAAI,EAAE,IAAI,CAAC,MAAM,WAAW,CAAC,IAAI,CAAC,MAAM,sBAAsB;YACxE,GAAG,WAAW,CAAC,IAAI,OAAO,WAAW,CAAC,EAAE,2DAA2D;YACnG,cAAc,OAAO,CAAC,EAAE,yBAAyB,CACpD,CAAC;IACJ,CAAC;IACD,OAAO,GAAG,CAAC;AACb,CAAC;AAUD;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,aAAa,CAAC,IAAiB,EAAE,OAAuB;IACtE,IAAI,IAAI,CAAC,IAAI,KAAK,MAAM;QAAE,OAAO,EAAE,CAAC;IACpC,MAAM,GAAG,GAAa,EAAE,CAAC;IACzB,KAAK,MAAM,EAAE,IAAI,EAAE,IAAI,EAAE,IAAI,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC;QACxC,MAAM,WAAW,GAAG,aAAa,CAAC,IAAI,EAAE,IAAI,CAAC,KAAK,CAAC,CAAC;QACpD,IAAI,WAAW,CAAC,OAAO,KAAK,UAAU;YAAE,SAAS;QACjD,MAAM,QAAQ,GAAG,WAAW,CAAC,IAAI,CAAC,IAAI,CACpC,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,CAAC,QAAQ,KAAK,OAAO,CAAC,IAAI,IAAI,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,MAAM,CAAC,KAAK,OAAO,CAAC,QAAQ,CACxF,CAAC;QACF,IAAI,QAAQ;YAAE,GAAG,CAAC,IAAI,CAAC,QAAQ,CAAC,IAAI,EAAE,IAAI,CAAC,CAAC,CAAC;IAC/C,CAAC;IACD,OAAO,GAAG,CAAC;AACb,CAAC","sourcesContent":["/**\n * Which hops of which business flows a contract removal breaks.\n *\n * `loam diff --base` already answers \"who still depends on this operation\" with\n * landscape edges and other services' living requirements. Both are true and\n * neither is the sentence a reviewer wants: an edge is a line in a diagram and a\n * requirement is a heading in somebody else's spec, while \"step 4 of Checkout\n * stops working\" is the fact a human weighs a pull request against. This module\n * is the join that produces that sentence, and it produces NOTHING ELSE — no\n * finding, no code, no severity. `core/diff/victims.ts` folds its answers into\n * the `details[]` of the two codes that already exist.\n *\n * ## Attributed is a victim; contested is a suspension\n *\n * The distinction is the whole reason this module is careful rather than a\n * filter. `attributeStep` (core/c4/arch.ts) grades a hop by the DISTINCT-op\n * count across the relationships backing it:\n *\n *  - `attributed` with `op === X` means every relationship behind the hop agrees\n *    the hop exercises X. Remove X and the flow breaks at that hop. That is\n *    positive evidence, and it is a victim.\n *  - `contested` means the relationships DISAGREE, so loam does not know which\n *    operation the hop exercises. It must not claim the flow breaks — a guessed\n *    victim reads exactly like a real one and turns a warn into an error on\n *    somebody's PR — and it must not go silent either, because silence here is\n *    the fail-open shape `ConsumerScan.suspended` exists to forbid. It is a\n *    suspension: loam says it could not answer.\n *\n * A contested hop is suspended only when X is among its candidate operations.\n * That is not a noise trade, it is the honest boundary: the candidates ARE the\n * relationships backing the hop, so an operation none of them names is an\n * operation the hop cannot be exercising under any reading of the disagreement.\n * Suspending every contested hop in the fleet on every removal would report\n * doubt loam does not actually have.\n *\n * An `unbacked` hop is neither. Nothing in the model backs it, so it names no\n * operation of anybody's contract — `usecase.step-unbacked` is already the error\n * that convicts it, and repeating that here would file a modelling defect\n * against whoever happened to remove an endpoint.\n */\nimport { attributeStep } from \"../c4/arch.js\";\nimport type { ParsedStep, ParsedView } from \"../c4/parsed/dynamic-views.js\";\nimport { hopPlace } from \"./place.js\";\nimport type { UseCaseScan } from \"./fleet.js\";\n\n/**\n * What one contract removal does to the fleet's use cases.\n *\n * Two lists rather than `victims`/`suspended` — the vocabulary\n * `core/diff/victims.ts` uses — because this module answers about FLOWS and that\n * one answers about consumers. The caller does the folding, and naming the two\n * differently is what stops a reader taking this for a second implementation of\n * `ConsumerScan` (it is not: it never scans a document, and it cannot be\n * unreadable — the scan it runs over was already graded).\n */\nexport interface UseCaseHits {\n  /** Hops the removal breaks, each spelled by `hopPlace`. */\n  breaks: string[];\n  /** Hops loam refuses to grade, each saying why in its own sentence. */\n  unsure: string[];\n}\n\n/** The one removal a scan is being asked about. */\nexport interface RemovedOperation {\n  /** The service dropping it — the same id the diff files its findings under. */\n  provider: string;\n  /** The operationId leaving the contract. */\n  op: string;\n}\n\nconst EMPTY: UseCaseHits = { breaks: [], unsure: [] };\n\n/** Every hop of every graded use case, view order preserved, so output is stable. */\nfunction hops(scan: Extract<UseCaseScan, { kind: \"read\" }>): Array<{ view: ParsedView; step: ParsedStep }> {\n  return scan.views.flatMap((view) => view.steps.map((step) => ({ view, step })));\n}\n\n/**\n * The flows one removed operation breaks, and the ones loam cannot answer for.\n *\n * An `unreadable` scan contributes NOTHING — neither break nor suspension — and\n * that is `core/diff/victims.ts`'s own landscape doctrine applied one axis over:\n * an unreadable fleet map proves nothing either way, `landscape.invalid` is\n * validate's finding to make, and inventing doubt out of a parse error would\n * point the reviewer at a file their change never touched. The caller reports\n * the hole; this join stays quiet about it.\n */\nexport function hopsExercising(scan: UseCaseScan, removed: RemovedOperation): UseCaseHits {\n  if (scan.kind !== \"read\") return EMPTY;\n  const out: UseCaseHits = { breaks: [], unsure: [] };\n  for (const { view, step } of hops(scan)) {\n    const attribution = attributeStep(step, scan.model);\n    if (attribution.verdict === \"unbacked\") continue;\n    // The callee, through the SAME resolver every other join in this run uses,\n    // so a hop drawn into a modelled container `payment.api` is filed against\n    // payment-service rather than against a service called \"api\".\n    if (scan.resolve(attribution.to) !== removed.provider) continue;\n    if (attribution.verdict === \"attributed\") {\n      if (attribution.op === removed.op) out.breaks.push(hopPlace(view, step));\n      continue;\n    }\n    if (!attribution.ops.includes(removed.op)) continue;\n    out.unsure.push(\n      `${hopPlace(view, step)} — ${attribution.rels.length} relationships back ` +\n        `${attribution.from} -> ${attribution.to} and they name different operations, so whether this hop ` +\n        `exercises '${removed.op}' could not be answered`,\n    );\n  }\n  return out;\n}\n\n/** The one message removal a scan is being asked about. */\nexport interface RemovedMessage {\n  /** The service dropping the declaration — the diff's own subject. */\n  provider: string;\n  /** The AsyncAPI message name leaving the contract. */\n  name: string;\n}\n\n/**\n * The flows one removed message breaks.\n *\n * No suspension arm, and the asymmetry is a fact about the model rather than an\n * omission: `attributeStep` contests OPERATIONS, because that is where two\n * relationships between one pair of endpoints can disagree. A `consumes` edge\n * names a message outright, so a hop either is backed by one or is not — there\n * is no disagreement for loam to refuse to resolve.\n *\n * The provider exclusion mirrors `messageConsumers` exactly: an edge INTO the\n * provider is the provider's own consumption, which leaves with the same change,\n * so a hop backed only by that edge is not a victim of it.\n */\nexport function hopsConsuming(scan: UseCaseScan, removed: RemovedMessage): string[] {\n  if (scan.kind !== \"read\") return [];\n  const out: string[] = [];\n  for (const { view, step } of hops(scan)) {\n    const attribution = attributeStep(step, scan.model);\n    if (attribution.verdict === \"unbacked\") continue;\n    const consumes = attribution.rels.some(\n      (rel) => rel.consumes === removed.name && scan.resolve(rel.target) !== removed.provider,\n    );\n    if (consumes) out.push(hopPlace(view, step));\n  }\n  return out;\n}\n"]}

package/dist/core/usecases/place.js

@@ -0,0 +1,44 @@
+/**
+ * The document the view was written in, spelled repo-relative.
+ *
+ * `sourcePath` is relative to the LikeC4 PROJECT root, which for
+ * `loadArchitecture` is `architecture/`, so the prefix is added here and nowhere
+ * else. The caller owes one thing in exchange: only views that came from
+ * `loadProject` may be spelled with this, because the single-file loaders name
+ * every document after themselves (`source.c4`) and this function would then
+ * spell a path that has never existed.
+ *
+ * An ABSENT `sourcePath` names the directory rather than guessing a file.
+ * LikeC4 synthesizes only element views and `readDynamicViews` drops those, so
+ * nothing at the 1.59.2 pin reaches this arm; if a release ever stopped emitting
+ * the field, falling back to `architecture/landscape.likec4` would put a false
+ * cross-reference in a message.
+ */
+export function viewFile(view) {
+    return view.sourcePath === undefined ? "architecture/" : `architecture/${view.sourcePath}`;
+}
+/**
+ * `step 4 'confirms the order'`, or `step 4` where the author labelled nothing.
+ *
+ * The ordinal is the view's own leaf numbering (`ParsedStep.ordinal`), which
+ * skips group brackets — so it counts what the author sees on the diagram, and
+ * a message naming step 4 is naming the fourth arrow.
+ */
+export function stepPlace(step) {
+    return step.title === undefined ? `step ${step.ordinal}` : `step ${step.ordinal} '${step.title}'`;
+}
+/**
+ * A use case and one of its hops, named the way a reader outside `validate`
+ * meets them: `use case 'uc_checkout' step 4 'authorizes the payment'
+ * (architecture/usecases/checkout.likec4)`.
+ *
+ * The file goes LAST here and first in validate's `viewPlace`, and that is not
+ * an inconsistency to tidy away. A validate finding is a line in a report about
+ * documents, so it leads with the document; a diff victim is one entry in a
+ * `details[]` list whose other entries name edges and requirements, so it has to
+ * lead with the thing that broke and carry the file as the place to go fix it.
+ */
+export function hopPlace(view, step) {
+    return `use case '${view.id}' ${stepPlace(step)} (${viewFile(view)})`;
+}
+//# sourceMappingURL=place.js.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"place.js","sourceRoot":"","sources":["../../../src/core/usecases/place.ts"],"names":[],"mappings":"AAqBA;;;;;;;;;;;;;;;GAeG;AACH,MAAM,UAAU,QAAQ,CAAC,IAAgB;IACvC,OAAO,IAAI,CAAC,UAAU,KAAK,SAAS,CAAC,CAAC,CAAC,eAAe,CAAC,CAAC,CAAC,gBAAgB,IAAI,CAAC,UAAU,EAAE,CAAC;AAC7F,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,SAAS,CAAC,IAAgB;IACxC,OAAO,IAAI,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,QAAQ,IAAI,CAAC,OAAO,EAAE,CAAC,CAAC,CAAC,QAAQ,IAAI,CAAC,OAAO,KAAK,IAAI,CAAC,KAAK,GAAG,CAAC;AACpG,CAAC;AAED;;;;;;;;;;GAUG;AACH,MAAM,UAAU,QAAQ,CAAC,IAAgB,EAAE,IAAgB;IACzD,OAAO,aAAa,IAAI,CAAC,EAAE,KAAK,SAAS,CAAC,IAAI,CAAC,KAAK,QAAQ,CAAC,IAAI,CAAC,GAAG,CAAC;AACxE,CAAC","sourcesContent":["/**\n * Where a use case lives and where one of its hops sits — the two spellings\n * every surface that mentions a use case has to agree on.\n *\n * They began in `commands/validate/fleet/usecases/place.ts`, beside the four\n * `usecase.*` graders that were their only reader. `loam diff` naming the flow a\n * removal breaks is the second reader and `loam delta`/`loam context` are the\n * third and fourth, and `core/` may not import from `commands/` (AGENTS.md), so\n * the alternative was a second spelling of `architecture/<sourcePath>` in core.\n * The two would drift silently and in the worst possible direction: a file path\n * in a message that no longer names the file the view is in is how the next\n * reader stops looking (docs/CODE-STYLE.md).\n *\n * What did NOT move is `viewPlace`, the `landscape: …` opening the validate\n * findings carry. That prefix is the name of a validate TARGET, so it is command\n * vocabulary — a `loam diff` finding is filed against a service, not against the\n * fleet map, and borrowing validate's prefix there would claim a target that run\n * does not have.\n */\nimport type { ParsedStep, ParsedView } from \"../c4/parsed/dynamic-views.js\";\n\n/**\n * The document the view was written in, spelled repo-relative.\n *\n * `sourcePath` is relative to the LikeC4 PROJECT root, which for\n * `loadArchitecture` is `architecture/`, so the prefix is added here and nowhere\n * else. The caller owes one thing in exchange: only views that came from\n * `loadProject` may be spelled with this, because the single-file loaders name\n * every document after themselves (`source.c4`) and this function would then\n * spell a path that has never existed.\n *\n * An ABSENT `sourcePath` names the directory rather than guessing a file.\n * LikeC4 synthesizes only element views and `readDynamicViews` drops those, so\n * nothing at the 1.59.2 pin reaches this arm; if a release ever stopped emitting\n * the field, falling back to `architecture/landscape.likec4` would put a false\n * cross-reference in a message.\n */\nexport function viewFile(view: ParsedView): string {\n  return view.sourcePath === undefined ? \"architecture/\" : `architecture/${view.sourcePath}`;\n}\n\n/**\n * `step 4 'confirms the order'`, or `step 4` where the author labelled nothing.\n *\n * The ordinal is the view's own leaf numbering (`ParsedStep.ordinal`), which\n * skips group brackets — so it counts what the author sees on the diagram, and\n * a message naming step 4 is naming the fourth arrow.\n */\nexport function stepPlace(step: ParsedStep): string {\n  return step.title === undefined ? `step ${step.ordinal}` : `step ${step.ordinal} '${step.title}'`;\n}\n\n/**\n * A use case and one of its hops, named the way a reader outside `validate`\n * meets them: `use case 'uc_checkout' step 4 'authorizes the payment'\n * (architecture/usecases/checkout.likec4)`.\n *\n * The file goes LAST here and first in validate's `viewPlace`, and that is not\n * an inconsistency to tidy away. A validate finding is a line in a report about\n * documents, so it leads with the document; a diff victim is one entry in a\n * `details[]` list whose other entries name edges and requirements, so it has to\n * lead with the thing that broke and carry the file as the place to go fix it.\n */\nexport function hopPlace(view: ParsedView, step: ParsedStep): string {\n  return `use case '${view.id}' ${stepPlace(step)} (${viewFile(view)})`;\n}\n"]}

package/dist/core/usecases/touch.js

@@ -0,0 +1,101 @@
+/**
+ * Which business flows run through a service — the blast radius `loam delta`
+ * and `loam status` report beside the requirements and contracts a feature
+ * changes.
+ *
+ * ## The join is on ENDPOINTS, never on relationships
+ *
+ * `core/usecases/operations.ts` asks what a hop EXERCISES, which needs the
+ * relationship behind it. This asks something weaker and more useful early:
+ * does this hop mention the service at all? So it resolves the step's own two
+ * endpoints and stops — no `attributeStep`, no candidate scan.
+ *
+ * That is the difference between answering and not answering for the service a
+ * feature is about to INTRODUCE. A flow drawn for work that has not happened yet
+ * has hops nothing in the model backs — `usecase.step-unbacked` is validate's
+ * finding about exactly that, and it is an ERROR precisely because the fleet map
+ * has not caught up — and a relationship join reports such a flow as touching
+ * nobody. The endpoints are still there; the arrow is what is missing. An
+ * implementer reading a delta brief needs to know the flow exists most of all in
+ * that state, because that is the state their change is supposed to end.
+ *
+ * ## Everything a caller sees, it sees per HOP
+ *
+ * A view is reported only when at least one of its hops touches the addressed
+ * services, and only those hops travel. "Checkout touches you" is not actionable;
+ * "Checkout touches you at step 4" is where the reader goes to look.
+ */
+import { compareIds } from "../repo/entries.js";
+import { readUseCases } from "./fleet.js";
+import { viewFile } from "./place.js";
+/** The addressed services one hop mentions, source and target both, sorted and de-duplicated. */
+function touched(step, scan, services) {
+    const hit = [step.source, step.target].map((id) => scan.resolve(id)).filter((id) => services.has(id));
+    return [...new Set(hit)].sort(compareIds);
+}
+/** One view's touching hops, in the author's own step order — the order the diagram reads in. */
+function touchedView(view, scan, services) {
+    const steps = [];
+    for (const step of view.steps) {
+        const hit = touched(step, scan, services);
+        if (hit.length === 0)
+            continue;
+        steps.push({
+            ordinal: step.ordinal,
+            ...(step.title === undefined ? {} : { title: step.title }),
+            source: step.source,
+            target: step.target,
+            services: hit,
+        });
+    }
+    if (steps.length === 0)
+        return null;
+    return {
+        id: view.id,
+        ...(view.title === undefined ? {} : { title: view.title }),
+        file: viewFile(view),
+        tags: [...view.tags].sort(compareIds),
+        steps,
+    };
+}
+/**
+ * The flows touching a set of services, over a scan somebody already has.
+ *
+ * Separate from `useCaseBlastRadius` below because `core/pack/joins.ts` reads
+ * the scan ONCE and asks two different questions of it — this one and the
+ * capability claim join — and a second read there would be a second LikeC4
+ * project load inside a single `loam context`.
+ *
+ * An `unreadable` scan answers with nothing. Every caller pairs this with the
+ * scan's own health, because an empty list means "no flow mentions these
+ * services" and "nobody could look" only when read together.
+ */
+export function flowsTouching(scan, services) {
+    if (scan.kind !== "read")
+        return [];
+    return (scan.views
+        .map((view) => touchedView(view, scan, services))
+        .filter((flow) => flow !== null)
+        // Sorted by (file, view id) rather than reported in LikeC4's own record
+        // order: nothing in loam has measured that the parse preserves declaration
+        // order, so a payload ordered by it would reorder under a dependency bump.
+        .sort((a, b) => compareIds(a.file, b.file) || compareIds(a.id, b.id)));
+}
+/**
+ * The flows touching a set of services, read and joined in one call.
+ *
+ * The load underneath is `readUseCases`, which carries its own cheap gate: a
+ * fleet whose `architecture/` documents never mention the reserved tag prefix
+ * answers `{ flows: [] }` without starting LikeC4 at all. That gate is what
+ * makes this callable from `loam delta`, which sits in `/loam-implement`'s inner
+ * loop and would otherwise pay a Langium workspace spin-up on every iteration of
+ * somebody's afternoon.
+ */
+export async function useCaseBlastRadius(req) {
+    const scan = await readUseCases({ docsDir: req.docsDir, known: req.known });
+    if (scan.kind !== "read") {
+        return { unreadable: true, ...(scan.errors[0] === undefined ? {} : { error: scan.errors[0] }), flows: [] };
+    }
+    return { unreadable: false, flows: flowsTouching(scan, req.services) };
+}
+//# sourceMappingURL=touch.js.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"touch.js","sourceRoot":"","sources":["../../../src/core/usecases/touch.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AACH,OAAO,EAAE,UAAU,EAAE,MAAM,oBAAoB,CAAC;AAGhD,OAAO,EAAE,YAAY,EAAoB,MAAM,YAAY,CAAC;AAC5D,OAAO,EAAE,QAAQ,EAAE,MAAM,YAAY,CAAC;AAkEtC,iGAAiG;AACjG,SAAS,OAAO,CAAC,IAAgB,EAAE,IAA4C,EAAE,QAA6B;IAC5G,MAAM,GAAG,GAAG,CAAC,IAAI,CAAC,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,IAAI,CAAC,OAAO,CAAC,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,QAAQ,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC,CAAC;IACtG,OAAO,CAAC,GAAG,IAAI,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,CAAC;AAC5C,CAAC;AAED,iGAAiG;AACjG,SAAS,WAAW,CAAC,IAAgB,EAAE,IAA4C,EAAE,QAA6B;IAChH,MAAM,KAAK,GAAkB,EAAE,CAAC;IAChC,KAAK,MAAM,IAAI,IAAI,IAAI,CAAC,KAAK,EAAE,CAAC;QAC9B,MAAM,GAAG,GAAG,OAAO,CAAC,IAAI,EAAE,IAAI,EAAE,QAAQ,CAAC,CAAC;QAC1C,IAAI,GAAG,CAAC,MAAM,KAAK,CAAC;YAAE,SAAS;QAC/B,KAAK,CAAC,IAAI,CAAC;YACT,OAAO,EAAE,IAAI,CAAC,OAAO;YACrB,GAAG,CAAC,IAAI,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,IAAI,CAAC,KAAK,EAAE,CAAC;YAC1D,MAAM,EAAE,IAAI,CAAC,MAAM;YACnB,MAAM,EAAE,IAAI,CAAC,MAAM;YACnB,QAAQ,EAAE,GAAG;SACd,CAAC,CAAC;IACL,CAAC;IACD,IAAI,KAAK,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,IAAI,CAAC;IACpC,OAAO;QACL,EAAE,EAAE,IAAI,CAAC,EAAE;QACX,GAAG,CAAC,IAAI,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,IAAI,CAAC,KAAK,EAAE,CAAC;QAC1D,IAAI,EAAE,QAAQ,CAAC,IAAI,CAAC;QACpB,IAAI,EAAE,CAAC,GAAG,IAAI,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC;QACrC,KAAK;KACN,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,aAAa,CAAC,IAAiB,EAAE,QAA6B;IAC5E,IAAI,IAAI,CAAC,IAAI,KAAK,MAAM;QAAE,OAAO,EAAE,CAAC;IACpC,OAAO,CACL,IAAI,CAAC,KAAK;SACP,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,WAAW,CAAC,IAAI,EAAE,IAAI,EAAE,QAAQ,CAAC,CAAC;SAChD,MAAM,CAAC,CAAC,IAAI,EAA0B,EAAE,CAAC,IAAI,KAAK,IAAI,CAAC;QACxD,wEAAwE;QACxE,2EAA2E;QAC3E,2EAA2E;SAC1E,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,UAAU,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,UAAU,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,EAAE,CAAC,CAAC,CACxE,CAAC;AACJ,CAAC;AAED;;;;;;;;;GASG;AACH,MAAM,CAAC,KAAK,UAAU,kBAAkB,CAAC,GAAuB;IAC9D,MAAM,IAAI,GAAG,MAAM,YAAY,CAAC,EAAE,OAAO,EAAE,GAAG,CAAC,OAAO,EAAE,KAAK,EAAE,GAAG,CAAC,KAAK,EAAE,CAAC,CAAC;IAC5E,IAAI,IAAI,CAAC,IAAI,KAAK,MAAM,EAAE,CAAC;QACzB,OAAO,EAAE,UAAU,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,KAAK,EAAE,EAAE,EAAE,CAAC;IAC7G,CAAC;IACD,OAAO,EAAE,UAAU,EAAE,KAAK,EAAE,KAAK,EAAE,aAAa,CAAC,IAAI,EAAE,GAAG,CAAC,QAAQ,CAAC,EAAE,CAAC;AACzE,CAAC","sourcesContent":["/**\n * Which business flows run through a service — the blast radius `loam delta`\n * and `loam status` report beside the requirements and contracts a feature\n * changes.\n *\n * ## The join is on ENDPOINTS, never on relationships\n *\n * `core/usecases/operations.ts` asks what a hop EXERCISES, which needs the\n * relationship behind it. This asks something weaker and more useful early:\n * does this hop mention the service at all? So it resolves the step's own two\n * endpoints and stops — no `attributeStep`, no candidate scan.\n *\n * That is the difference between answering and not answering for the service a\n * feature is about to INTRODUCE. A flow drawn for work that has not happened yet\n * has hops nothing in the model backs — `usecase.step-unbacked` is validate's\n * finding about exactly that, and it is an ERROR precisely because the fleet map\n * has not caught up — and a relationship join reports such a flow as touching\n * nobody. The endpoints are still there; the arrow is what is missing. An\n * implementer reading a delta brief needs to know the flow exists most of all in\n * that state, because that is the state their change is supposed to end.\n *\n * ## Everything a caller sees, it sees per HOP\n *\n * A view is reported only when at least one of its hops touches the addressed\n * services, and only those hops travel. \"Checkout touches you\" is not actionable;\n * \"Checkout touches you at step 4\" is where the reader goes to look.\n */\nimport { compareIds } from \"../repo/entries.js\";\nimport type { DocsDir } from \"../kernel/ids/dirs.js\";\nimport type { ParsedStep, ParsedView } from \"../c4/parsed/dynamic-views.js\";\nimport { readUseCases, type UseCaseScan } from \"./fleet.js\";\nimport { viewFile } from \"./place.js\";\n\n/** One hop of a flow that mentions a service the caller asked about. */\nexport interface TouchedStep {\n  /** The view's own leaf numbering — what the author sees on the diagram. */\n  ordinal: number;\n  title?: string;\n  /** The step's endpoints as the view declares them: element ids, already oriented. */\n  source: string;\n  target: string;\n  /**\n   * Which of the ADDRESSED services this hop mentions, sorted. Both, when a flow\n   * calls a service and it answers within the same addressed set.\n   */\n  services: string[];\n}\n\n/** One flow that touches the addressed services, with only the hops that do. */\nexport interface TouchedUseCase {\n  id: string;\n  title?: string;\n  /** Repo-relative document the view is written in — where the reader goes to change it. */\n  file: string;\n  /**\n   * The `#cap-` tags the view carries, verbatim and unresolved.\n   *\n   * Verbatim because resolving them means reading\n   * `architecture/capabilities.yaml`, and a slug is not injective — the join can\n   * legitimately answer \"two capabilities\" (core/capabilities/usecase-join.ts).\n   * A blast-radius list is not the place to make that call: `loam validate --all`\n   * already grades every tag with `usecase.capability-unresolved`, and a second\n   * resolution here would be a second answer to the same question.\n   */\n  tags: string[];\n  steps: TouchedStep[];\n}\n\n/**\n * The flows over a set of services, and whether loam could look at all.\n *\n * `unreadable` is a HOLE, in the sense `core/pack/pack.ts` uses the word: `flows`\n * is empty because `architecture/` did not parse, not because the fleet draws no\n * use cases. A consumer that cannot tell those apart reads \"no business flow\n * depends on this\" off a directory nobody could open, which is the vacuously\n * green answer every surface in loam is built to refuse.\n */\nexport interface UseCaseBlastRadius {\n  unreadable: boolean;\n  /** LikeC4's first message, so a reader knows which document to open. */\n  error?: string;\n  flows: TouchedUseCase[];\n}\n\nexport interface BlastRadiusRequest {\n  docsDir: DocsDir;\n  /**\n   * The fleet the element→service resolver is built with. Wider than `services`\n   * on purpose: it should be every service the resolver could legitimately land\n   * on, so a hop into a modelled container resolves to its owner rather than to\n   * the container's own title.\n   */\n  known: ReadonlySet<string>;\n  /** The services being asked about. */\n  services: ReadonlySet<string>;\n}\n\n/** The addressed services one hop mentions, source and target both, sorted and de-duplicated. */\nfunction touched(step: ParsedStep, scan: Extract<UseCaseScan, { kind: \"read\" }>, services: ReadonlySet<string>): string[] {\n  const hit = [step.source, step.target].map((id) => scan.resolve(id)).filter((id) => services.has(id));\n  return [...new Set(hit)].sort(compareIds);\n}\n\n/** One view's touching hops, in the author's own step order — the order the diagram reads in. */\nfunction touchedView(view: ParsedView, scan: Extract<UseCaseScan, { kind: \"read\" }>, services: ReadonlySet<string>): TouchedUseCase | null {\n  const steps: TouchedStep[] = [];\n  for (const step of view.steps) {\n    const hit = touched(step, scan, services);\n    if (hit.length === 0) continue;\n    steps.push({\n      ordinal: step.ordinal,\n      ...(step.title === undefined ? {} : { title: step.title }),\n      source: step.source,\n      target: step.target,\n      services: hit,\n    });\n  }\n  if (steps.length === 0) return null;\n  return {\n    id: view.id,\n    ...(view.title === undefined ? {} : { title: view.title }),\n    file: viewFile(view),\n    tags: [...view.tags].sort(compareIds),\n    steps,\n  };\n}\n\n/**\n * The flows touching a set of services, over a scan somebody already has.\n *\n * Separate from `useCaseBlastRadius` below because `core/pack/joins.ts` reads\n * the scan ONCE and asks two different questions of it — this one and the\n * capability claim join — and a second read there would be a second LikeC4\n * project load inside a single `loam context`.\n *\n * An `unreadable` scan answers with nothing. Every caller pairs this with the\n * scan's own health, because an empty list means \"no flow mentions these\n * services\" and \"nobody could look\" only when read together.\n */\nexport function flowsTouching(scan: UseCaseScan, services: ReadonlySet<string>): TouchedUseCase[] {\n  if (scan.kind !== \"read\") return [];\n  return (\n    scan.views\n      .map((view) => touchedView(view, scan, services))\n      .filter((flow): flow is TouchedUseCase => flow !== null)\n      // Sorted by (file, view id) rather than reported in LikeC4's own record\n      // order: nothing in loam has measured that the parse preserves declaration\n      // order, so a payload ordered by it would reorder under a dependency bump.\n      .sort((a, b) => compareIds(a.file, b.file) || compareIds(a.id, b.id))\n  );\n}\n\n/**\n * The flows touching a set of services, read and joined in one call.\n *\n * The load underneath is `readUseCases`, which carries its own cheap gate: a\n * fleet whose `architecture/` documents never mention the reserved tag prefix\n * answers `{ flows: [] }` without starting LikeC4 at all. That gate is what\n * makes this callable from `loam delta`, which sits in `/loam-implement`'s inner\n * loop and would otherwise pay a Langium workspace spin-up on every iteration of\n * somebody's afternoon.\n */\nexport async function useCaseBlastRadius(req: BlastRadiusRequest): Promise<UseCaseBlastRadius> {\n  const scan = await readUseCases({ docsDir: req.docsDir, known: req.known });\n  if (scan.kind !== \"read\") {\n    return { unreadable: true, ...(scan.errors[0] === undefined ? {} : { error: scan.errors[0] }), flows: [] };\n  }\n  return { unreadable: false, flows: flowsTouching(scan, req.services) };\n}\n"]}