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

package/dist/core/capabilities/usecase-join.js

@@ -0,0 +1,277 @@
+/**
+ * The joins from a use case's tags: back to a declared capability, and to one
+ * of that capability's requirements.
+ *
+ * TWO TAGS, ONE CLAIM. `#cap-<slug>` says which capability a flow is about;
+ * `#req-<slug>` says which of its named promises the flow satisfies. The second
+ * is the architect's ANSWER to the analyst's requirement, and it is the only
+ * carrier a cross-service criterion has: "I enter a login and a password and I
+ * am in" cannot be promised by any single service's spec, because each promises
+ * only its own part — but a flow can, because it IS the hop sequence. That is
+ * why `Realizes:` on a service requirement is not enough on its own, and why
+ * this join exists at all.
+ *
+ * THE SECOND TAG IS SCOPED BY THE FIRST. A `Requirement-ID` is unique only
+ * inside its own document, so `#req-CHK-ONCE` means nothing until the view has
+ * said which capability it is about. A view carrying `#req-` with no resolved
+ * `#cap-`, or with two, is refused rather than guessed at — the same stance the
+ * `many` arm takes one join down.
+ *
+ * A LikeC4 `dynamic view` opts in to being graded as a business use case by
+ * carrying a tag `#cap-<slug>`, and this module is the whole of what both tags
+ * mean. It is deliberately the narrowest layer that can mean it: no file is
+ * read, no finding is emitted, and nothing is thrown — a pure function over ids
+ * somebody else supplies. That last property is not tidiness. Its caller runs
+ * inside `loam validate --all` over every document a fleet has, and the one
+ * behaviour a check added to that run may never have is failing the run it was
+ * added to.
+ *
+ * WHY A SLUG AT ALL. Neither id is spelled in characters a tag name accepts. A
+ * capability id spells its nesting inside the id — `identity/tokens` and
+ * `payments/settlement` both ship in loam's own
+ * `examples/docs/architecture/capabilities.yaml`, and `./capabilities.ts` keeps
+ * the key exactly as the requirement writes it, slashes preserved — while a
+ * `Requirement-ID` may legally contain a `.`. A LikeC4 tag name accepts exactly
+ * `[A-Za-z0-9_-]` (measured at the 1.59.2 pin, pinned in
+ * `test/likec4-view-shape.test.ts`), so both tags carry their id with the rest
+ * flattened and both joins run over the flattened form.
+ *
+ * WHY THE JOIN CAN ANSWER "MANY". The slug is NOT injective. `payments/refunds`
+ * and `payments-refunds` are two distinct, legal, declarable ids that flatten to
+ * one slug, so `#cap-payments-refunds` names both and nothing in the tag can say
+ * which. loam refuses and names ambiguity rather than guessing, and here the
+ * cost of guessing is unusually high: a silently-picked capability attributes a
+ * whole business flow — every hop, every service, every rollup built over it —
+ * to the wrong owner, and goes on doing so invisibly because the wrong answer
+ * looks exactly like the right one. The "many" arm is why this returns a union
+ * at all instead of `string | undefined`.
+ *
+ * WHAT THE CALLER STILL OWES. The vocabulary ladder in `./findings.ts` — an
+ * absent or unreadable `architecture/capabilities.yaml` means total silence, not
+ * a fleet full of unresolved tags — is applied BEFORE calling here. An empty
+ * `declared` list at this boundary therefore means "the fleet declares no
+ * capabilities", which is a real answer this module will happily grade; it does
+ * not mean "there is no vocabulary", and this module cannot tell the two apart.
+ */
+import { closeIds } from "../c4/arch.js";
+import { compareIds } from "../repo/entries.js";
+/**
+ * The reserved tag prefix, matched EXACTLY — case included.
+ *
+ * A view tag that does not start with it is not a capability claim and is
+ * invisible here: `#FEAT-101`, `#platform` and `#deprecated` are the author's
+ * own vocabulary and grading them would turn every existing hand-drawn view in
+ * a brownfield fleet red on upgrade. The match is case-sensitive because what
+ * survives it is a slug that must round-trip to a `capabilities.yaml` key, and
+ * those keys are case-sensitive YAML; accepting `#Cap-checkout` here would hand
+ * the lookup a slug whose case loam had already stopped believing in.
+ */
+export const CAP_TAG_PREFIX = "cap-";
+/**
+ * Every character a LikeC4 tag name accepts, at the 1.59.2 pin. A WHITELIST,
+ * and that is the load-bearing choice: the complement is infinite, so a rule
+ * written as "flatten a slash" is a rule that is right about one character and
+ * silent about the rest.
+ *
+ * Measured, not assumed (`test/likec4-view-shape.test.ts` pins it): `.`, `/`,
+ * `:`, a space, `+`, `@` and a non-ASCII letter each make the DECLARATION a
+ * parse error — and the failure is worse than a refusal, because the parser
+ * TRUNCATES the name at the offending character. `#x-a.b` comes back as
+ * `["x-a"]`. Nothing in loam reads a model with errors, so the truncation
+ * cannot reach a join today; it is recorded because the day something does read
+ * one, a truncated tag resolves to a different, possibly real, capability.
+ */
+const TAG_NAME_SAFE = /[^A-Za-z0-9_-]/g;
+/**
+ * An id as its tag spells it: every character a tag name cannot carry flattened
+ * to a hyphen.
+ *
+ * Used by BOTH tags this module resolves, which is why it is no longer called
+ * `capabilitySlug`. A capability id spells its nesting with `/`
+ * (`identity/tokens`) and a `Requirement-ID` may legally contain `.`
+ * (`REQUIREMENT_ID_RE` allows it) — two different characters, one rule, because
+ * an author who learns that a tag flattens the awkward character in one id
+ * should not have to learn it again for the other.
+ *
+ * Deliberately lossy, and the `many` arms below carry the whole cost of that:
+ * two ids can produce one slug and nothing here notices.
+ */
+export function tagSlug(id) {
+    return id.replace(TAG_NAME_SAFE, "-");
+}
+/**
+ * Every declared id that produces each slug.
+ *
+ * A map rather than a scan per tag because the "many" arm needs the WHOLE
+ * colliding set: a lookup that stopped at the first hit could still report
+ * "resolved" for a slug two ids answer to, which is precisely the silent wrong
+ * answer this module exists to refuse.
+ */
+function idsBySlug(declared) {
+    const bySlug = new Map();
+    for (const id of declared) {
+        const slug = tagSlug(id);
+        const ids = bySlug.get(slug);
+        if (ids === undefined)
+            bySlug.set(slug, [id]);
+        else
+            ids.push(id);
+    }
+    return bySlug;
+}
+/**
+ * Close names for a slug nothing declares — suggested against the SLUGS, then
+ * mapped back to the ids that produced them.
+ *
+ * Both halves are load-bearing. Comparing against slugs is what lets
+ * `#cap-identiy-tokns` reach `identity/tokens` at all: `closeIds` matches on
+ * substring and shared prefix, and the slash sits where the author's typo does
+ * not. Mapping back is what keeps the suggestion writable — a hint naming
+ * `identity-tokens` would send the author to look for a capability declared
+ * under a name that appears nowhere in `capabilities.yaml`.
+ *
+ * A winning slug may map back to more than one id, and the expansion is not
+ * re-capped: `closeIds` caps the SLUGS it offers at five, and dropping a real
+ * declared id afterwards to keep an arithmetic promise nobody made would hide
+ * the very collision the "many" arm is here to name.
+ */
+function closeCapabilityIds(slug, bySlug) {
+    const near = closeIds(slug, [...bySlug.keys()]);
+    // `?? []` rather than `!`: `closeIds` promises every name it offers is one it
+    // was given, so a miss here would mean that promise broke — and the honest
+    // answer to a broken invariant inside a hint is one fewer suggestion, not a
+    // `TypeError` thrown out of a `validate --all` run over somebody's fleet.
+    return [...new Set(near.flatMap((s) => bySlug.get(s) ?? []))].sort(compareIds);
+}
+/**
+ * The capability claims a view's tags make: one claim per `#cap-` tag, each
+ * answered on its own terms.
+ *
+ * A VIEW MAY CARRY MORE THAN ONE `#cap-` TAG, and the tags are never collapsed
+ * into a single verdict for the view. Both halves of that are deliberate.
+ *
+ * A use case realizing two capabilities is a real thing — a checkout flow that
+ * also issues the identity token realizes both, and there is no honest way to
+ * make its author pick one — so a second tag must NOT be read the way the "many"
+ * arm reads a second colliding id. Those two look alike and are opposites: in
+ * "many" the author wrote one name and loam cannot tell which id it means, here
+ * the author wrote two names and meant both.
+ *
+ * And a view whose tags disagree — one resolving, one naming nothing — is not a
+ * view that resolved. Collapsing to the first success would swallow the broken
+ * tag and grade the view as if the typo were not there; collapsing to the first
+ * failure would lose the capability the view genuinely does realize. One tag,
+ * one verdict, is the only shape that keeps both facts, and it leaves the caller
+ * free to emit one finding per failing tag while still collecting every id the
+ * view resolved.
+ *
+ * Claims come back SORTED BY TAG rather than in the order LikeC4 handed the tags
+ * over. Nothing in loam has measured that LikeC4 preserves the author's tag
+ * order, and an output ordered by an unmeasured upstream detail is one that
+ * reorders under a version bump — the diff-stability rule `./rollup.ts` states
+ * for its rows, applied to a smaller list. A repeated tag collapses to one
+ * claim, for the reason one breach earns one finding.
+ *
+ * An empty result means the view makes no capability claim at all — either it
+ * carries no tags or none of them are reserved — which is the opt-in, not a
+ * failure to resolve.
+ */
+export function resolveCapabilityTags(tags, declared) {
+    const bySlug = idsBySlug(declared);
+    const claimed = [...new Set(tags.filter((tag) => tag.startsWith(CAP_TAG_PREFIX)))].sort(compareIds);
+    return claimed.map((tag) => {
+        // A bare `#cap-` slugs to the empty string, and it stays a claim on purpose:
+        // the prefix is the author's opt-in however little follows it, so dropping
+        // the tag as unreserved would leave a view that asked to be graded silently
+        // ungraded. What that empty slug then resolves to is the lookup's business
+        // like any other — `none` in every real fleet, `resolved` in the one that
+        // declared an empty id, and neither is decided here.
+        const slug = tag.slice(CAP_TAG_PREFIX.length);
+        // Destructured rather than indexed so the three arms are told apart by the
+        // shape of the match itself — no bounds assertion, and no `undefined` check
+        // separate from the "nothing declared this" answer it already is.
+        const [first, ...rest] = bySlug.get(slug) ?? [];
+        if (first === undefined)
+            return { tag, slug, kind: "none", close: closeCapabilityIds(slug, bySlug) };
+        if (rest.length === 0)
+            return { tag, slug, kind: "resolved", id: first };
+        return { tag, slug, kind: "many", ids: [first, ...rest].sort(compareIds) };
+    });
+}
+/**
+ * The reserved tag prefix for the requirement claim, matched EXACTLY as
+ * `CAP_TAG_PREFIX` is and for the same two reasons: a tag that does not start
+ * with it is the author's own vocabulary and is invisible here, and the slug
+ * that survives the match must round-trip to a case-sensitive `Requirement-ID:`.
+ */
+export const REQ_TAG_PREFIX = "req-";
+/**
+ * Resolve every `#req-` tag a view carries against the capability it is about.
+ *
+ * `scope` is the capability ids the view's OWN `#cap-` tags resolved to —
+ * `resolveCapabilityTags`' `resolved` arms, and nothing else. An unresolved
+ * `#cap-` tag is already `usecase.capability-unresolved`, and letting it also
+ * scope a requirement lookup would build a second finding on top of a name loam
+ * has just said it cannot place.
+ *
+ * Claims come back SORTED BY TAG for `resolveCapabilityTags`' reason: nothing in
+ * loam has measured that LikeC4 preserves the author's tag order, and an output
+ * ordered by an unmeasured upstream detail reorders under a version bump. A
+ * repeated tag collapses to one claim, for the reason one breach earns one
+ * finding.
+ *
+ * SEVERAL `#req-` TAGS ARE LEGAL AND NORMAL. One flow commonly satisfies two of
+ * a capability's promises — a checkout flow that charges once AND honours the
+ * price — and there is no honest way to make its author pick one. That is the
+ * same shape `resolveCapabilityTags` allows for `#cap-`, and it is the opposite
+ * of the `many` arm: there the author wrote one name loam cannot place, here
+ * they wrote two and meant both.
+ */
+export function resolveRequirementTags(tags, scope, requirementsOf) {
+    const claimed = [...new Set(tags.filter((tag) => tag.startsWith(REQ_TAG_PREFIX)))].sort(compareIds);
+    if (claimed.length === 0)
+        return [];
+    const capability = scope.length === 1 ? scope[0] : null;
+    return claimed.map((tag) => {
+        // A bare `#req-` slugs to the empty string and stays a claim, exactly as a
+        // bare `#cap-` does: the prefix is the opt-in however little follows it, and
+        // dropping it would leave a view that asked to be graded silently ungraded.
+        const slug = tag.slice(REQ_TAG_PREFIX.length);
+        if (capability === null)
+            return { tag, slug, kind: "unscoped", capabilities: [...scope].sort(compareIds) };
+        const ids = requirementsOf(capability);
+        if (ids === undefined)
+            return { tag, slug, kind: "undocumented", capability };
+        if (ids.size === 0)
+            return { tag, slug, kind: "empty", capability };
+        const matching = [...ids].filter((id) => tagSlug(id) === slug).sort(compareIds);
+        const [first, ...rest] = matching;
+        if (first === undefined) {
+            return { tag, slug, kind: "none", capability, close: closeRequirementIds(slug, ids) };
+        }
+        if (rest.length === 0)
+            return { tag, slug, kind: "resolved", capability, id: first };
+        return { tag, slug, kind: "many", capability, ids: matching };
+    });
+}
+/**
+ * Close ids for a slug nothing in the document matches — suggested against the
+ * SLUGS, then mapped back to the real ids, exactly as `closeCapabilityIds`
+ * does and for its two reasons: comparing on slugs is what lets a typo reach an
+ * id whose awkward character sits where the typo does not, and mapping back is
+ * what keeps the suggestion writable.
+ */
+function closeRequirementIds(slug, ids) {
+    const bySlug = new Map();
+    for (const id of ids) {
+        const key = tagSlug(id);
+        const found = bySlug.get(key);
+        if (found === undefined)
+            bySlug.set(key, [id]);
+        else
+            found.push(id);
+    }
+    const near = closeIds(slug, [...bySlug.keys()]);
+    return [...new Set(near.flatMap((s) => bySlug.get(s) ?? []))].sort(compareIds);
+}
+//# sourceMappingURL=usecase-join.js.map

package/dist/core/capabilities/usecase-join.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"usecase-join.js","sourceRoot":"","sources":["../../../src/core/capabilities/usecase-join.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsDG;AACH,OAAO,EAAE,QAAQ,EAAE,MAAM,eAAe,CAAC;AACzC,OAAO,EAAE,UAAU,EAAE,MAAM,oBAAoB,CAAC;AAEhD;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,MAAM,CAAC;AAErC;;;;;;;;;;;;;GAaG;AACH,MAAM,aAAa,GAAG,iBAAiB,CAAC;AAExC;;;;;;;;;;;;;GAaG;AACH,MAAM,UAAU,OAAO,CAAC,EAAU;IAChC,OAAO,EAAE,CAAC,OAAO,CAAC,aAAa,EAAE,GAAG,CAAC,CAAC;AACxC,CAAC;AA6BD;;;;;;;GAOG;AACH,SAAS,SAAS,CAAC,QAA2B;IAC5C,MAAM,MAAM,GAAG,IAAI,GAAG,EAAoB,CAAC;IAC3C,KAAK,MAAM,EAAE,IAAI,QAAQ,EAAE,CAAC;QAC1B,MAAM,IAAI,GAAG,OAAO,CAAC,EAAE,CAAC,CAAC;QACzB,MAAM,GAAG,GAAG,MAAM,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QAC7B,IAAI,GAAG,KAAK,SAAS;YAAE,MAAM,CAAC,GAAG,CAAC,IAAI,EAAE,CAAC,EAAE,CAAC,CAAC,CAAC;;YACzC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACpB,CAAC;IACD,OAAO,MAAM,CAAC;AAChB,CAAC;AAED;;;;;;;;;;;;;;;GAeG;AACH,SAAS,kBAAkB,CAAC,IAAY,EAAE,MAAqC;IAC7E,MAAM,IAAI,GAAG,QAAQ,CAAC,IAAI,EAAE,CAAC,GAAG,MAAM,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC;IAChD,8EAA8E;IAC9E,2EAA2E;IAC3E,4EAA4E;IAC5E,0EAA0E;IAC1E,OAAO,CAAC,GAAG,IAAI,GAAG,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,CAAC;AACjF,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AACH,MAAM,UAAU,qBAAqB,CACnC,IAAuB,EACvB,QAA2B;IAE3B,MAAM,MAAM,GAAG,SAAS,CAAC,QAAQ,CAAC,CAAC;IACnC,MAAM,OAAO,GAAG,CAAC,GAAG,IAAI,GAAG,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,CAAC,UAAU,CAAC,cAAc,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,CAAC;IAEpG,OAAO,OAAO,CAAC,GAAG,CAAC,CAAC,GAAG,EAAE,EAAE;QACzB,6EAA6E;QAC7E,2EAA2E;QAC3E,4EAA4E;QAC5E,2EAA2E;QAC3E,0EAA0E;QAC1E,qDAAqD;QACrD,MAAM,IAAI,GAAG,GAAG,CAAC,KAAK,CAAC,cAAc,CAAC,MAAM,CAAC,CAAC;QAC9C,2EAA2E;QAC3E,4EAA4E;QAC5E,kEAAkE;QAClE,MAAM,CAAC,KAAK,EAAE,GAAG,IAAI,CAAC,GAAG,MAAM,CAAC,GAAG,CAAC,IAAI,CAAC,IAAI,EAAE,CAAC;QAChD,IAAI,KAAK,KAAK,SAAS;YAAE,OAAO,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,EAAE,MAAe,EAAE,KAAK,EAAE,kBAAkB,CAAC,IAAI,EAAE,MAAM,CAAC,EAAE,CAAC;QAC9G,IAAI,IAAI,CAAC,MAAM,KAAK,CAAC;YAAE,OAAO,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,EAAE,UAAmB,EAAE,EAAE,EAAE,KAAK,EAAE,CAAC;QAClF,OAAO,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,EAAE,MAAe,EAAE,GAAG,EAAE,CAAC,KAAK,EAAE,GAAG,IAAI,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,EAAE,CAAC;IACtF,CAAC,CAAC,CAAC;AACL,CAAC;AAED;;;;;GAKG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,MAAM,CAAC;AAiCrC;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,UAAU,sBAAsB,CACpC,IAAuB,EACvB,KAAwB,EACxB,cAAuE;IAEvE,MAAM,OAAO,GAAG,CAAC,GAAG,IAAI,GAAG,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,CAAC,UAAU,CAAC,cAAc,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,CAAC;IACpG,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,CAAC;IACpC,MAAM,UAAU,GAAG,KAAK,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAE,CAAC,CAAC,CAAC,IAAI,CAAC;IAEzD,OAAO,OAAO,CAAC,GAAG,CAAC,CAAC,GAAG,EAAoB,EAAE;QAC3C,2EAA2E;QAC3E,6EAA6E;QAC7E,4EAA4E;QAC5E,MAAM,IAAI,GAAG,GAAG,CAAC,KAAK,CAAC,cAAc,CAAC,MAAM,CAAC,CAAC;QAC9C,IAAI,UAAU,KAAK,IAAI;YAAE,OAAO,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,EAAE,UAAU,EAAE,YAAY,EAAE,CAAC,GAAG,KAAK,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,EAAE,CAAC;QAC3G,MAAM,GAAG,GAAG,cAAc,CAAC,UAAU,CAAC,CAAC;QACvC,IAAI,GAAG,KAAK,SAAS;YAAE,OAAO,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,EAAE,cAAc,EAAE,UAAU,EAAE,CAAC;QAC9E,IAAI,GAAG,CAAC,IAAI,KAAK,CAAC;YAAE,OAAO,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,EAAE,OAAO,EAAE,UAAU,EAAE,CAAC;QACpE,MAAM,QAAQ,GAAG,CAAC,GAAG,GAAG,CAAC,CAAC,MAAM,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,OAAO,CAAC,EAAE,CAAC,KAAK,IAAI,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,CAAC;QAChF,MAAM,CAAC,KAAK,EAAE,GAAG,IAAI,CAAC,GAAG,QAAQ,CAAC;QAClC,IAAI,KAAK,KAAK,SAAS,EAAE,CAAC;YACxB,OAAO,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,EAAE,MAAM,EAAE,UAAU,EAAE,KAAK,EAAE,mBAAmB,CAAC,IAAI,EAAE,GAAG,CAAC,EAAE,CAAC;QACxF,CAAC;QACD,IAAI,IAAI,CAAC,MAAM,KAAK,CAAC;YAAE,OAAO,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,EAAE,UAAU,EAAE,UAAU,EAAE,EAAE,EAAE,KAAK,EAAE,CAAC;QACrF,OAAO,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,EAAE,MAAM,EAAE,UAAU,EAAE,GAAG,EAAE,QAAQ,EAAE,CAAC;IAChE,CAAC,CAAC,CAAC;AACL,CAAC;AAED;;;;;;GAMG;AACH,SAAS,mBAAmB,CAAC,IAAY,EAAE,GAAwB;IACjE,MAAM,MAAM,GAAG,IAAI,GAAG,EAAoB,CAAC;IAC3C,KAAK,MAAM,EAAE,IAAI,GAAG,EAAE,CAAC;QACrB,MAAM,GAAG,GAAG,OAAO,CAAC,EAAE,CAAC,CAAC;QACxB,MAAM,KAAK,GAAG,MAAM,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;QAC9B,IAAI,KAAK,KAAK,SAAS;YAAE,MAAM,CAAC,GAAG,CAAC,GAAG,EAAE,CAAC,EAAE,CAAC,CAAC,CAAC;;YAC1C,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACtB,CAAC;IACD,MAAM,IAAI,GAAG,QAAQ,CAAC,IAAI,EAAE,CAAC,GAAG,MAAM,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC;IAChD,OAAO,CAAC,GAAG,IAAI,GAAG,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,CAAC;AACjF,CAAC","sourcesContent":["/**\n * The joins from a use case's tags: back to a declared capability, and to one\n * of that capability's requirements.\n *\n * TWO TAGS, ONE CLAIM. `#cap-<slug>` says which capability a flow is about;\n * `#req-<slug>` says which of its named promises the flow satisfies. The second\n * is the architect's ANSWER to the analyst's requirement, and it is the only\n * carrier a cross-service criterion has: \"I enter a login and a password and I\n * am in\" cannot be promised by any single service's spec, because each promises\n * only its own part — but a flow can, because it IS the hop sequence. That is\n * why `Realizes:` on a service requirement is not enough on its own, and why\n * this join exists at all.\n *\n * THE SECOND TAG IS SCOPED BY THE FIRST. A `Requirement-ID` is unique only\n * inside its own document, so `#req-CHK-ONCE` means nothing until the view has\n * said which capability it is about. A view carrying `#req-` with no resolved\n * `#cap-`, or with two, is refused rather than guessed at — the same stance the\n * `many` arm takes one join down.\n *\n * A LikeC4 `dynamic view` opts in to being graded as a business use case by\n * carrying a tag `#cap-<slug>`, and this module is the whole of what both tags\n * mean. It is deliberately the narrowest layer that can mean it: no file is\n * read, no finding is emitted, and nothing is thrown — a pure function over ids\n * somebody else supplies. That last property is not tidiness. Its caller runs\n * inside `loam validate --all` over every document a fleet has, and the one\n * behaviour a check added to that run may never have is failing the run it was\n * added to.\n *\n * WHY A SLUG AT ALL. Neither id is spelled in characters a tag name accepts. A\n * capability id spells its nesting inside the id — `identity/tokens` and\n * `payments/settlement` both ship in loam's own\n * `examples/docs/architecture/capabilities.yaml`, and `./capabilities.ts` keeps\n * the key exactly as the requirement writes it, slashes preserved — while a\n * `Requirement-ID` may legally contain a `.`. A LikeC4 tag name accepts exactly\n * `[A-Za-z0-9_-]` (measured at the 1.59.2 pin, pinned in\n * `test/likec4-view-shape.test.ts`), so both tags carry their id with the rest\n * flattened and both joins run over the flattened form.\n *\n * WHY THE JOIN CAN ANSWER \"MANY\". The slug is NOT injective. `payments/refunds`\n * and `payments-refunds` are two distinct, legal, declarable ids that flatten to\n * one slug, so `#cap-payments-refunds` names both and nothing in the tag can say\n * which. loam refuses and names ambiguity rather than guessing, and here the\n * cost of guessing is unusually high: a silently-picked capability attributes a\n * whole business flow — every hop, every service, every rollup built over it —\n * to the wrong owner, and goes on doing so invisibly because the wrong answer\n * looks exactly like the right one. The \"many\" arm is why this returns a union\n * at all instead of `string | undefined`.\n *\n * WHAT THE CALLER STILL OWES. The vocabulary ladder in `./findings.ts` — an\n * absent or unreadable `architecture/capabilities.yaml` means total silence, not\n * a fleet full of unresolved tags — is applied BEFORE calling here. An empty\n * `declared` list at this boundary therefore means \"the fleet declares no\n * capabilities\", which is a real answer this module will happily grade; it does\n * not mean \"there is no vocabulary\", and this module cannot tell the two apart.\n */\nimport { closeIds } from \"../c4/arch.js\";\nimport { compareIds } from \"../repo/entries.js\";\n\n/**\n * The reserved tag prefix, matched EXACTLY — case included.\n *\n * A view tag that does not start with it is not a capability claim and is\n * invisible here: `#FEAT-101`, `#platform` and `#deprecated` are the author's\n * own vocabulary and grading them would turn every existing hand-drawn view in\n * a brownfield fleet red on upgrade. The match is case-sensitive because what\n * survives it is a slug that must round-trip to a `capabilities.yaml` key, and\n * those keys are case-sensitive YAML; accepting `#Cap-checkout` here would hand\n * the lookup a slug whose case loam had already stopped believing in.\n */\nexport const CAP_TAG_PREFIX = \"cap-\";\n\n/**\n * Every character a LikeC4 tag name accepts, at the 1.59.2 pin. A WHITELIST,\n * and that is the load-bearing choice: the complement is infinite, so a rule\n * written as \"flatten a slash\" is a rule that is right about one character and\n * silent about the rest.\n *\n * Measured, not assumed (`test/likec4-view-shape.test.ts` pins it): `.`, `/`,\n * `:`, a space, `+`, `@` and a non-ASCII letter each make the DECLARATION a\n * parse error — and the failure is worse than a refusal, because the parser\n * TRUNCATES the name at the offending character. `#x-a.b` comes back as\n * `[\"x-a\"]`. Nothing in loam reads a model with errors, so the truncation\n * cannot reach a join today; it is recorded because the day something does read\n * one, a truncated tag resolves to a different, possibly real, capability.\n */\nconst TAG_NAME_SAFE = /[^A-Za-z0-9_-]/g;\n\n/**\n * An id as its tag spells it: every character a tag name cannot carry flattened\n * to a hyphen.\n *\n * Used by BOTH tags this module resolves, which is why it is no longer called\n * `capabilitySlug`. A capability id spells its nesting with `/`\n * (`identity/tokens`) and a `Requirement-ID` may legally contain `.`\n * (`REQUIREMENT_ID_RE` allows it) — two different characters, one rule, because\n * an author who learns that a tag flattens the awkward character in one id\n * should not have to learn it again for the other.\n *\n * Deliberately lossy, and the `many` arms below carry the whole cost of that:\n * two ids can produce one slug and nothing here notices.\n */\nexport function tagSlug(id: string): string {\n  return id.replace(TAG_NAME_SAFE, \"-\");\n}\n\n/** The tag a claim is about, and the slug left after the prefix. */\ninterface ClaimTag {\n  /** The tag verbatim, as the view declares it — no `#`, prefix still on. */\n  tag: string;\n  /** The tag with its reserved prefix removed: the name the join actually ran on. */\n  slug: string;\n}\n\n/**\n * What one `#cap-` tag joins to. Branch on `kind`; every arm carries the tag it\n * is about, so a message can name the tag, the slug and the answer without\n * re-deriving any of them from the view.\n */\nexport type CapabilityClaim =\n  /** Exactly one declared id flattens to this tag. `id` is the real id, slashes intact. */\n  | (ClaimTag & { kind: \"resolved\"; id: string })\n  /**\n   * No declared id flattens to it. `close` holds real capability ids — names the\n   * author can paste into `capabilities.yaml` or into the tag — never the slugs\n   * the comparison was actually made against, because a slug is loam's spelling\n   * of a name and offering it as a suggestion would be loam inventing a\n   * capability id that nobody declared.\n   */\n  | (ClaimTag & { kind: \"none\"; close: string[] })\n  /** Two or more declared ids flatten to it. Every colliding id, sorted, so a message can name them all. */\n  | (ClaimTag & { kind: \"many\"; ids: string[] });\n\n/**\n * Every declared id that produces each slug.\n *\n * A map rather than a scan per tag because the \"many\" arm needs the WHOLE\n * colliding set: a lookup that stopped at the first hit could still report\n * \"resolved\" for a slug two ids answer to, which is precisely the silent wrong\n * answer this module exists to refuse.\n */\nfunction idsBySlug(declared: readonly string[]): Map<string, string[]> {\n  const bySlug = new Map<string, string[]>();\n  for (const id of declared) {\n    const slug = tagSlug(id);\n    const ids = bySlug.get(slug);\n    if (ids === undefined) bySlug.set(slug, [id]);\n    else ids.push(id);\n  }\n  return bySlug;\n}\n\n/**\n * Close names for a slug nothing declares — suggested against the SLUGS, then\n * mapped back to the ids that produced them.\n *\n * Both halves are load-bearing. Comparing against slugs is what lets\n * `#cap-identiy-tokns` reach `identity/tokens` at all: `closeIds` matches on\n * substring and shared prefix, and the slash sits where the author's typo does\n * not. Mapping back is what keeps the suggestion writable — a hint naming\n * `identity-tokens` would send the author to look for a capability declared\n * under a name that appears nowhere in `capabilities.yaml`.\n *\n * A winning slug may map back to more than one id, and the expansion is not\n * re-capped: `closeIds` caps the SLUGS it offers at five, and dropping a real\n * declared id afterwards to keep an arithmetic promise nobody made would hide\n * the very collision the \"many\" arm is here to name.\n */\nfunction closeCapabilityIds(slug: string, bySlug: ReadonlyMap<string, string[]>): string[] {\n  const near = closeIds(slug, [...bySlug.keys()]);\n  // `?? []` rather than `!`: `closeIds` promises every name it offers is one it\n  // was given, so a miss here would mean that promise broke — and the honest\n  // answer to a broken invariant inside a hint is one fewer suggestion, not a\n  // `TypeError` thrown out of a `validate --all` run over somebody's fleet.\n  return [...new Set(near.flatMap((s) => bySlug.get(s) ?? []))].sort(compareIds);\n}\n\n/**\n * The capability claims a view's tags make: one claim per `#cap-` tag, each\n * answered on its own terms.\n *\n * A VIEW MAY CARRY MORE THAN ONE `#cap-` TAG, and the tags are never collapsed\n * into a single verdict for the view. Both halves of that are deliberate.\n *\n * A use case realizing two capabilities is a real thing — a checkout flow that\n * also issues the identity token realizes both, and there is no honest way to\n * make its author pick one — so a second tag must NOT be read the way the \"many\"\n * arm reads a second colliding id. Those two look alike and are opposites: in\n * \"many\" the author wrote one name and loam cannot tell which id it means, here\n * the author wrote two names and meant both.\n *\n * And a view whose tags disagree — one resolving, one naming nothing — is not a\n * view that resolved. Collapsing to the first success would swallow the broken\n * tag and grade the view as if the typo were not there; collapsing to the first\n * failure would lose the capability the view genuinely does realize. One tag,\n * one verdict, is the only shape that keeps both facts, and it leaves the caller\n * free to emit one finding per failing tag while still collecting every id the\n * view resolved.\n *\n * Claims come back SORTED BY TAG rather than in the order LikeC4 handed the tags\n * over. Nothing in loam has measured that LikeC4 preserves the author's tag\n * order, and an output ordered by an unmeasured upstream detail is one that\n * reorders under a version bump — the diff-stability rule `./rollup.ts` states\n * for its rows, applied to a smaller list. A repeated tag collapses to one\n * claim, for the reason one breach earns one finding.\n *\n * An empty result means the view makes no capability claim at all — either it\n * carries no tags or none of them are reserved — which is the opt-in, not a\n * failure to resolve.\n */\nexport function resolveCapabilityTags(\n  tags: readonly string[],\n  declared: readonly string[],\n): CapabilityClaim[] {\n  const bySlug = idsBySlug(declared);\n  const claimed = [...new Set(tags.filter((tag) => tag.startsWith(CAP_TAG_PREFIX)))].sort(compareIds);\n\n  return claimed.map((tag) => {\n    // A bare `#cap-` slugs to the empty string, and it stays a claim on purpose:\n    // the prefix is the author's opt-in however little follows it, so dropping\n    // the tag as unreserved would leave a view that asked to be graded silently\n    // ungraded. What that empty slug then resolves to is the lookup's business\n    // like any other — `none` in every real fleet, `resolved` in the one that\n    // declared an empty id, and neither is decided here.\n    const slug = tag.slice(CAP_TAG_PREFIX.length);\n    // Destructured rather than indexed so the three arms are told apart by the\n    // shape of the match itself — no bounds assertion, and no `undefined` check\n    // separate from the \"nothing declared this\" answer it already is.\n    const [first, ...rest] = bySlug.get(slug) ?? [];\n    if (first === undefined) return { tag, slug, kind: \"none\" as const, close: closeCapabilityIds(slug, bySlug) };\n    if (rest.length === 0) return { tag, slug, kind: \"resolved\" as const, id: first };\n    return { tag, slug, kind: \"many\" as const, ids: [first, ...rest].sort(compareIds) };\n  });\n}\n\n/**\n * The reserved tag prefix for the requirement claim, matched EXACTLY as\n * `CAP_TAG_PREFIX` is and for the same two reasons: a tag that does not start\n * with it is the author's own vocabulary and is invisible here, and the slug\n * that survives the match must round-trip to a case-sensitive `Requirement-ID:`.\n */\nexport const REQ_TAG_PREFIX = \"req-\";\n\n/**\n * What one `#req-` tag joins to, given the capabilities the same view resolved.\n *\n * Five arms because there are five different fixes, and they are deliberately\n * the same five `RealizesClaim` draws in `./realizes/join.ts`: the two carriers\n * of one claim must fail in the same vocabulary, or an author who learns the\n * `Realizes:` messages learns nothing about the tag.\n */\nexport type RequirementClaim =\n  /** Exactly one requirement of the scoping capability flattens to this tag. */\n  | (ClaimTag & { kind: \"resolved\"; capability: string; id: string })\n  /**\n   * The view resolved no capability, or more than one, so a `Requirement-ID`\n   * has no document to be unique inside. `capabilities` is what it DID resolve\n   * — empty, or the two-or-more that make the scope ambiguous.\n   */\n  | (ClaimTag & { kind: \"unscoped\"; capabilities: string[] })\n  /** The scoping capability is declared but has no `capabilities/<id>/spec.md`, so it carries no requirements. */\n  | (ClaimTag & { kind: \"undocumented\"; capability: string })\n  /** Its document exists and declares no requirements yet. */\n  | (ClaimTag & { kind: \"empty\"; capability: string })\n  /**\n   * Its document declares requirements, none flattening to this slug. `close`\n   * holds real `Requirement-ID`s — never the slugs the comparison ran against,\n   * because a slug is loam's spelling and offering it would send the author\n   * looking for an id that appears nowhere in the document.\n   */\n  | (ClaimTag & { kind: \"none\"; capability: string; close: string[] })\n  /** Two or more of its requirement ids flatten to this slug. Every colliding id, sorted. */\n  | (ClaimTag & { kind: \"many\"; capability: string; ids: string[] });\n\n/**\n * Resolve every `#req-` tag a view carries against the capability it is about.\n *\n * `scope` is the capability ids the view's OWN `#cap-` tags resolved to —\n * `resolveCapabilityTags`' `resolved` arms, and nothing else. An unresolved\n * `#cap-` tag is already `usecase.capability-unresolved`, and letting it also\n * scope a requirement lookup would build a second finding on top of a name loam\n * has just said it cannot place.\n *\n * Claims come back SORTED BY TAG for `resolveCapabilityTags`' reason: nothing in\n * loam has measured that LikeC4 preserves the author's tag order, and an output\n * ordered by an unmeasured upstream detail reorders under a version bump. A\n * repeated tag collapses to one claim, for the reason one breach earns one\n * finding.\n *\n * SEVERAL `#req-` TAGS ARE LEGAL AND NORMAL. One flow commonly satisfies two of\n * a capability's promises — a checkout flow that charges once AND honours the\n * price — and there is no honest way to make its author pick one. That is the\n * same shape `resolveCapabilityTags` allows for `#cap-`, and it is the opposite\n * of the `many` arm: there the author wrote one name loam cannot place, here\n * they wrote two and meant both.\n */\nexport function resolveRequirementTags(\n  tags: readonly string[],\n  scope: readonly string[],\n  requirementsOf: (capability: string) => ReadonlySet<string> | undefined,\n): RequirementClaim[] {\n  const claimed = [...new Set(tags.filter((tag) => tag.startsWith(REQ_TAG_PREFIX)))].sort(compareIds);\n  if (claimed.length === 0) return [];\n  const capability = scope.length === 1 ? scope[0]! : null;\n\n  return claimed.map((tag): RequirementClaim => {\n    // A bare `#req-` slugs to the empty string and stays a claim, exactly as a\n    // bare `#cap-` does: the prefix is the opt-in however little follows it, and\n    // dropping it would leave a view that asked to be graded silently ungraded.\n    const slug = tag.slice(REQ_TAG_PREFIX.length);\n    if (capability === null) return { tag, slug, kind: \"unscoped\", capabilities: [...scope].sort(compareIds) };\n    const ids = requirementsOf(capability);\n    if (ids === undefined) return { tag, slug, kind: \"undocumented\", capability };\n    if (ids.size === 0) return { tag, slug, kind: \"empty\", capability };\n    const matching = [...ids].filter((id) => tagSlug(id) === slug).sort(compareIds);\n    const [first, ...rest] = matching;\n    if (first === undefined) {\n      return { tag, slug, kind: \"none\", capability, close: closeRequirementIds(slug, ids) };\n    }\n    if (rest.length === 0) return { tag, slug, kind: \"resolved\", capability, id: first };\n    return { tag, slug, kind: \"many\", capability, ids: matching };\n  });\n}\n\n/**\n * Close ids for a slug nothing in the document matches — suggested against the\n * SLUGS, then mapped back to the real ids, exactly as `closeCapabilityIds`\n * does and for its two reasons: comparing on slugs is what lets a typo reach an\n * id whose awkward character sits where the typo does not, and mapping back is\n * what keeps the suggestion writable.\n */\nfunction closeRequirementIds(slug: string, ids: ReadonlySet<string>): string[] {\n  const bySlug = new Map<string, string[]>();\n  for (const id of ids) {\n    const key = tagSlug(id);\n    const found = bySlug.get(key);\n    if (found === undefined) bySlug.set(key, [id]);\n    else found.push(id);\n  }\n  const near = closeIds(slug, [...bySlug.keys()]);\n  return [...new Set(near.flatMap((s) => bySlug.get(s) ?? []))].sort(compareIds);\n}\n"]}

package/dist/core/coherence/authoring/scaffold.js

@@ -0,0 +1,177 @@
+/**
+ * The gate between `loam new` and `loam archive`: a scaffold nobody edited must
+ * not become the living truth.
+ *
+ * `loam new` writes documents whose whole point is to be replaced — a TODO
+ * requirement heading, angle-bracket step fill-ins, a TODO service description,
+ * an intent whose Why/Scope are comments. Every one of them parsed as real
+ * content, validated clean, and archived at exit 0, which put literal `TODO —
+ * name the behaviour` into a living spec the rest of the fleet then reads as a
+ * requirement somebody meant. These checks refuse that merge.
+ *
+ * Both are warnings that GATE (issue.ts: severity says the DOCUMENT is legal —
+ * it is, it parses — gating says the MERGE is unsafe). `--approve` overrides,
+ * as with every judgment about the feature.
+ *
+ * BOTH DELTA CORPORA ARE READ, because `loam new` scaffolds into both. A
+ * `--capability` run writes `features/<FEAT>/capabilities/<id>/spec.md` from a
+ * template whose example sits inside an HTML comment exactly like the two spec
+ * templates', and an author who copies that block out and archives without
+ * editing it would publish `TODO — name the promise` into a LIVING capability
+ * document — which is strictly worse than the service case this gate was built
+ * for: a capability document outlives every service that realizes it, and a
+ * `Realizes:` line pointed at the placeholder's id would then be a join to a
+ * promise nobody wrote. The capability deltas are read HERE rather than handed
+ * in through `AuthoringScope`, because this is a walk over the feature's own
+ * documents and the scope already names the feature; the read is one
+ * `existsSync` for the fleets that have not adopted the axis, and the memo when
+ * a context was threaded.
+ */
+import { existsSync } from "node:fs";
+import { readFile } from "node:fs/promises";
+import { parseRequirements } from "../../document/parse.js";
+import { featureCapabilityDeltas } from "../../capabilities/delta/tree.js";
+import { featurePaths, featureSpecPaths, SPEC_AXES } from "../../repo/paths.js";
+import { BODY_SENTINELS, HEADING_SENTINELS, SERVICE_DESCRIPTION_SENTINEL, } from "./sentinels.js";
+export async function authoringIssues(scope) {
+    const issues = [];
+    await intentIssue(scope, issues);
+    for (const e of scope.splicedEls) {
+        if (e.description !== SERVICE_DESCRIPTION_SENTINEL)
+            continue;
+        issues.push({
+            severity: "warn",
+            gates: true,
+            code: "scaffold.placeholder",
+            message: `delta.likec4: '${e.title}' (${e.id}) still carries the scaffolded description '${SERVICE_DESCRIPTION_SENTINEL}' — the merge would publish it to the fleet map. Say what the service owns, or archive with --approve.`,
+        });
+    }
+    for (const svc of scope.svcNames) {
+        const paths = featureSpecPaths(scope.featureDir, svc);
+        for (const axis of SPEC_AXES) {
+            const path = paths[axis.key];
+            if (!existsSync(path))
+                continue;
+            const found = unauthored(await requirementsOf(scope, path));
+            if (found.size === 0)
+                continue;
+            issues.push({
+                severity: "warn",
+                gates: true,
+                code: "scaffold.placeholder",
+                subject: svc,
+                message: `${svc}: ${axis.file} still carries scaffold placeholder(s) nobody authored — ${quote(found)}. The merge would write them into the living spec as requirements somebody meant. Replace them, or archive with --approve.`,
+            });
+        }
+    }
+    // The business corpus. `subject` is the capability id — a THIRD provenance
+    // for this code's subject, after a service id and none at all — and the
+    // artifact table resolves it by MEMBERSHIP against the capability documents
+    // the feature carries (`status/feature/artifacts.ts`), the same resolution
+    // every `delta.*` issue on this axis already relies on. So the capability's
+    // own row turns draft, and a service row does too only where a fleet holds a
+    // service and a capability of one name, which is that module's deliberately
+    // pessimistic answer rather than a mis-attribution here.
+    const capabilities = scope.context === undefined
+        ? await featureCapabilityDeltas(scope.featureDir)
+        : await scope.context.featureCapabilityDeltas(scope.featureDir);
+    for (const doc of capabilities.docs) {
+        const found = unauthored(await requirementsOf(scope, doc.spec));
+        if (found.size === 0)
+            continue;
+        issues.push({
+            severity: "warn",
+            gates: true,
+            code: "scaffold.placeholder",
+            subject: doc.id,
+            message: `capability ${doc.id}: spec.md still carries scaffold placeholder(s) nobody authored — ${quote(found)}. The merge would write them into the living capabilities/${doc.id}/spec.md as promises somebody meant — and a capability document outlives every service that realizes it. Replace them, or archive with --approve.`,
+        });
+    }
+    return issues;
+}
+/** One delta document's requirements, through the invocation's read index when there is one. */
+async function requirementsOf(scope, path) {
+    if (scope.context === undefined)
+        return parseRequirements(await readFile(path, "utf8"));
+    return scope.context.readRequirements(path);
+}
+/**
+ * The scaffold strings a delta's MERGING requirements still carry.
+ *
+ * ADDED/MODIFIED only: those are the texts this MERGE would write. A BASE
+ * requirement is a quote of the living state — if a sentinel sits there, some
+ * earlier archive published it and this feature is not the author to gate on it
+ * — and a REMOVED one is leaving the document anyway.
+ */
+function unauthored(reqs) {
+    const found = new Set();
+    for (const r of reqs) {
+        if (r.kind === "ADDED" || r.kind === "MODIFIED")
+            sentinelsIn(r, found);
+    }
+    return found;
+}
+/** The found sentinels as a message fragment — one spelling, so the two corpora read alike. */
+function quote(found) {
+    return [...found].map((s) => `'${s}'`).join(", ");
+}
+/** The exact template strings this requirement still carries, if any. */
+function sentinelsIn(r, found) {
+    for (const heading of HEADING_SENTINELS) {
+        if (r.name === heading)
+            found.add(heading);
+        for (const s of r.scenarios) {
+            if (s.name === heading)
+                found.add(heading);
+        }
+    }
+    const body = [r.text.join("\n"), ...r.scenarios.map((s) => s.lines.join("\n"))].join("\n");
+    for (const marker of BODY_SENTINELS) {
+        if (body.includes(marker))
+            found.add(marker);
+    }
+}
+/**
+ * Does intent.md SAY anything? The scaffold's Why/Scope bodies are HTML
+ * comments, so "strip frontmatter, comments and headings, look for prose" is
+ * exactly the question "did a person write the sentence the reviewer reads
+ * first". A missing file gates the same way: a feature with no stated intent
+ * is not less anonymous for not having the file.
+ */
+async function intentIssue(scope, issues) {
+    const path = featurePaths(scope.featureDir).intent;
+    const empty = { severity: "warn", gates: true, code: "intent.empty" };
+    if (!existsSync(path)) {
+        issues.push({
+            ...empty,
+            message: `intent.md is missing — nothing says why ${scope.featureId} exists. Write the Why before archiving it into the living docs, or archive with --approve.`,
+        });
+        return;
+    }
+    if (hasProse(await readFile(path, "utf8")))
+        return;
+    issues.push({
+        ...empty,
+        message: `intent.md says nothing yet — its Why and Scope are still the scaffold's comments. Write why ${scope.featureId} exists before archiving it into the living docs, or archive with --approve.`,
+    });
+}
+/** Is there any authored text outside frontmatter, HTML comments and headings? */
+function hasProse(text) {
+    // Normalized BEFORE the fence regex, the discipline document/parse.ts
+    // applies to every other markdown read: `---\r` is not `---`, so a CRLF
+    // rewrite (or a BOM some Windows editor prefixed) kept the frontmatter,
+    // which then counted as prose — and the untouched scaffold archived at
+    // exit 0 through the exact gate built to refuse it.
+    // The BOM is spelled as an escape, never as the raw character — a raw one is
+    // invisible in review and to grep, which is how it would survive a rewrite.
+    let body = text.replace(/^\uFEFF/, "").replace(/\r\n/g, "\n");
+    // Frontmatter: the leading `---` block only, exactly where the scaffold puts it.
+    const fm = /^---\n[\s\S]*?\n---\n/.exec(body);
+    if (fm !== null)
+        body = body.slice(fm[0].length);
+    body = body.replace(/<!--[\s\S]*?-->/g, "");
+    return body
+        .split("\n")
+        .some((line) => line.trim().length > 0 && !line.trimStart().startsWith("#"));
+}
+//# sourceMappingURL=scaffold.js.map

package/dist/core/coherence/authoring/scaffold.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"scaffold.js","sourceRoot":"","sources":["../../../../src/core/coherence/authoring/scaffold.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AACH,OAAO,EAAE,UAAU,EAAE,MAAM,SAAS,CAAC;AACrC,OAAO,EAAE,QAAQ,EAAE,MAAM,kBAAkB,CAAC;AAM5C,OAAO,EAAE,iBAAiB,EAAE,MAAM,yBAAyB,CAAC;AAC5D,OAAO,EAAE,uBAAuB,EAAE,MAAM,kCAAkC,CAAC;AAC3E,OAAO,EAAE,YAAY,EAAE,gBAAgB,EAAE,SAAS,EAAE,MAAM,qBAAqB,CAAC;AAEhF,OAAO,EACL,cAAc,EACd,iBAAiB,EACjB,4BAA4B,GAC7B,MAAM,gBAAgB,CAAC;AAmBxB,MAAM,CAAC,KAAK,UAAU,eAAe,CAAC,KAAqB;IACzD,MAAM,MAAM,GAAY,EAAE,CAAC;IAC3B,MAAM,WAAW,CAAC,KAAK,EAAE,MAAM,CAAC,CAAC;IAEjC,KAAK,MAAM,CAAC,IAAI,KAAK,CAAC,UAAU,EAAE,CAAC;QACjC,IAAI,CAAC,CAAC,WAAW,KAAK,4BAA4B;YAAE,SAAS;QAC7D,MAAM,CAAC,IAAI,CAAC;YACV,QAAQ,EAAE,MAAM;YAChB,KAAK,EAAE,IAAI;YACX,IAAI,EAAE,sBAAsB;YAC5B,OAAO,EAAE,kBAAkB,CAAC,CAAC,KAAK,MAAM,CAAC,CAAC,EAAE,+CAA+C,4BAA4B,wGAAwG;SAChO,CAAC,CAAC;IACL,CAAC;IAED,KAAK,MAAM,GAAG,IAAI,KAAK,CAAC,QAAQ,EAAE,CAAC;QACjC,MAAM,KAAK,GAAG,gBAAgB,CAAC,KAAK,CAAC,UAAU,EAAE,GAAG,CAAC,CAAC;QACtD,KAAK,MAAM,IAAI,IAAI,SAAS,EAAE,CAAC;YAC7B,MAAM,IAAI,GAAG,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;YAC7B,IAAI,CAAC,UAAU,CAAC,IAAI,CAAC;gBAAE,SAAS;YAChC,MAAM,KAAK,GAAG,UAAU,CAAC,MAAM,cAAc,CAAC,KAAK,EAAE,IAAI,CAAC,CAAC,CAAC;YAC5D,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC;gBAAE,SAAS;YAC/B,MAAM,CAAC,IAAI,CAAC;gBACV,QAAQ,EAAE,MAAM;gBAChB,KAAK,EAAE,IAAI;gBACX,IAAI,EAAE,sBAAsB;gBAC5B,OAAO,EAAE,GAAG;gBACZ,OAAO,EAAE,GAAG,GAAG,KAAK,IAAI,CAAC,IAAI,4DAA4D,KAAK,CAAC,KAAK,CAAC,4HAA4H;aAClO,CAAC,CAAC;QACL,CAAC;IACH,CAAC;IAED,2EAA2E;IAC3E,wEAAwE;IACxE,4EAA4E;IAC5E,2EAA2E;IAC3E,4EAA4E;IAC5E,6EAA6E;IAC7E,4EAA4E;IAC5E,yDAAyD;IACzD,MAAM,YAAY,GAChB,KAAK,CAAC,OAAO,KAAK,SAAS;QACzB,CAAC,CAAC,MAAM,uBAAuB,CAAC,KAAK,CAAC,UAAU,CAAC;QACjD,CAAC,CAAC,MAAM,KAAK,CAAC,OAAO,CAAC,uBAAuB,CAAC,KAAK,CAAC,UAAU,CAAC,CAAC;IACpE,KAAK,MAAM,GAAG,IAAI,YAAY,CAAC,IAAI,EAAE,CAAC;QACpC,MAAM,KAAK,GAAG,UAAU,CAAC,MAAM,cAAc,CAAC,KAAK,EAAE,GAAG,CAAC,IAAI,CAAC,CAAC,CAAC;QAChE,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC;YAAE,SAAS;QAC/B,MAAM,CAAC,IAAI,CAAC;YACV,QAAQ,EAAE,MAAM;YAChB,KAAK,EAAE,IAAI;YACX,IAAI,EAAE,sBAAsB;YAC5B,OAAO,EAAE,GAAG,CAAC,EAAE;YACf,OAAO,EAAE,cAAc,GAAG,CAAC,EAAE,qEAAqE,KAAK,CAAC,KAAK,CAAC,6DAA6D,GAAG,CAAC,EAAE,mJAAmJ;SACrU,CAAC,CAAC;IACL,CAAC;IACD,OAAO,MAAM,CAAC;AAChB,CAAC;AAED,gGAAgG;AAChG,KAAK,UAAU,cAAc,CAAC,KAAqB,EAAE,IAAY;IAC/D,IAAI,KAAK,CAAC,OAAO,KAAK,SAAS;QAAE,OAAO,iBAAiB,CAAC,MAAM,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC,CAAC,CAAC;IACxF,OAAO,KAAK,CAAC,OAAO,CAAC,gBAAgB,CAAC,IAAI,CAAC,CAAC;AAC9C,CAAC;AAED;;;;;;;GAOG;AACH,SAAS,UAAU,CAAC,IAAmB;IACrC,MAAM,KAAK,GAAG,IAAI,GAAG,EAAU,CAAC;IAChC,KAAK,MAAM,CAAC,IAAI,IAAI,EAAE,CAAC;QACrB,IAAI,CAAC,CAAC,IAAI,KAAK,OAAO,IAAI,CAAC,CAAC,IAAI,KAAK,UAAU;YAAE,WAAW,CAAC,CAAC,EAAE,KAAK,CAAC,CAAC;IACzE,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC;AAED,+FAA+F;AAC/F,SAAS,KAAK,CAAC,KAA0B;IACvC,OAAO,CAAC,GAAG,KAAK,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AACpD,CAAC;AAED,yEAAyE;AACzE,SAAS,WAAW,CAAC,CAAc,EAAE,KAAkB;IACrD,KAAK,MAAM,OAAO,IAAI,iBAAiB,EAAE,CAAC;QACxC,IAAI,CAAC,CAAC,IAAI,KAAK,OAAO;YAAE,KAAK,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC;QAC3C,KAAK,MAAM,CAAC,IAAI,CAAC,CAAC,SAAS,EAAE,CAAC;YAC5B,IAAI,CAAC,CAAC,IAAI,KAAK,OAAO;gBAAE,KAAK,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC;QAC7C,CAAC;IACH,CAAC;IACD,MAAM,IAAI,GAAG,CAAC,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,GAAG,CAAC,CAAC,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IAC3F,KAAK,MAAM,MAAM,IAAI,cAAc,EAAE,CAAC;QACpC,IAAI,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC;YAAE,KAAK,CAAC,GAAG,CAAC,MAAM,CAAC,CAAC;IAC/C,CAAC;AACH,CAAC;AAED;;;;;;GAMG;AACH,KAAK,UAAU,WAAW,CAAC,KAAqB,EAAE,MAAe;IAC/D,MAAM,IAAI,GAAG,YAAY,CAAC,KAAK,CAAC,UAAU,CAAC,CAAC,MAAM,CAAC;IACnD,MAAM,KAAK,GAAG,EAAE,QAAQ,EAAE,MAAM,EAAE,KAAK,EAAE,IAAI,EAAE,IAAI,EAAE,cAAc,EAAW,CAAC;IAC/E,IAAI,CAAC,UAAU,CAAC,IAAI,CAAC,EAAE,CAAC;QACtB,MAAM,CAAC,IAAI,CAAC;YACV,GAAG,KAAK;YACR,OAAO,EAAE,2CAA2C,KAAK,CAAC,SAAS,6FAA6F;SACjK,CAAC,CAAC;QACH,OAAO;IACT,CAAC;IACD,IAAI,QAAQ,CAAC,MAAM,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC,CAAC;QAAE,OAAO;IACnD,MAAM,CAAC,IAAI,CAAC;QACV,GAAG,KAAK;QACR,OAAO,EAAE,+FAA+F,KAAK,CAAC,SAAS,8EAA8E;KACtM,CAAC,CAAC;AACL,CAAC;AAED,kFAAkF;AAClF,SAAS,QAAQ,CAAC,IAAY;IAC5B,sEAAsE;IACtE,wEAAwE;IACxE,wEAAwE;IACxE,uEAAuE;IACvE,oDAAoD;IACpD,6EAA6E;IAC7E,4EAA4E;IAC5E,IAAI,IAAI,GAAG,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,EAAE,CAAC,CAAC,OAAO,CAAC,OAAO,EAAE,IAAI,CAAC,CAAC;IAC9D,iFAAiF;IACjF,MAAM,EAAE,GAAG,uBAAuB,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IAC9C,IAAI,EAAE,KAAK,IAAI;QAAE,IAAI,GAAG,IAAI,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC;IACjD,IAAI,GAAG,IAAI,CAAC,OAAO,CAAC,kBAAkB,EAAE,EAAE,CAAC,CAAC;IAC5C,OAAO,IAAI;SACR,KAAK,CAAC,IAAI,CAAC;SACX,IAAI,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,EAAE,CAAC,MAAM,GAAG,CAAC,IAAI,CAAC,IAAI,CAAC,SAAS,EAAE,CAAC,UAAU,CAAC,GAAG,CAAC,CAAC,CAAC;AACjF,CAAC","sourcesContent":["/**\n * The gate between `loam new` and `loam archive`: a scaffold nobody edited must\n * not become the living truth.\n *\n * `loam new` writes documents whose whole point is to be replaced — a TODO\n * requirement heading, angle-bracket step fill-ins, a TODO service description,\n * an intent whose Why/Scope are comments. Every one of them parsed as real\n * content, validated clean, and archived at exit 0, which put literal `TODO —\n * name the behaviour` into a living spec the rest of the fleet then reads as a\n * requirement somebody meant. These checks refuse that merge.\n *\n * Both are warnings that GATE (issue.ts: severity says the DOCUMENT is legal —\n * it is, it parses — gating says the MERGE is unsafe). `--approve` overrides,\n * as with every judgment about the feature.\n *\n * BOTH DELTA CORPORA ARE READ, because `loam new` scaffolds into both. A\n * `--capability` run writes `features/<FEAT>/capabilities/<id>/spec.md` from a\n * template whose example sits inside an HTML comment exactly like the two spec\n * templates', and an author who copies that block out and archives without\n * editing it would publish `TODO — name the promise` into a LIVING capability\n * document — which is strictly worse than the service case this gate was built\n * for: a capability document outlives every service that realizes it, and a\n * `Realizes:` line pointed at the placeholder's id would then be a join to a\n * promise nobody wrote. The capability deltas are read HERE rather than handed\n * in through `AuthoringScope`, because this is a walk over the feature's own\n * documents and the scope already names the feature; the read is one\n * `existsSync` for the fleets that have not adopted the axis, and the memo when\n * a context was threaded.\n */\nimport { existsSync } from \"node:fs\";\nimport { readFile } from \"node:fs/promises\";\nimport type { Elem } from \"../../c4/likec4.js\";\nimport type { PathableService } from \"../../kernel/ids/service.js\";\nimport type { Issue } from \"../../vocabulary/issue.js\";\nimport type { FleetContext } from \"../../fleet-context.js\";\nimport type { Requirement } from \"../../document/spec.js\";\nimport { parseRequirements } from \"../../document/parse.js\";\nimport { featureCapabilityDeltas } from \"../../capabilities/delta/tree.js\";\nimport { featurePaths, featureSpecPaths, SPEC_AXES } from \"../../repo/paths.js\";\nimport type { FeatureDir } from \"../../kernel/ids/dirs.js\";\nimport {\n  BODY_SENTINELS,\n  HEADING_SENTINELS,\n  SERVICE_DESCRIPTION_SENTINEL,\n} from \"./sentinels.js\";\n\n/** What the placeholder gate reads: the feature's own documents, nothing else. */\nexport interface AuthoringScope {\n  featureDir: FeatureDir;\n  featureId: string;\n  /**\n   * Every element whose authored block the landscape merge would SPLICE — the\n   * tagged elements and everything nested inside their blocks. The scope is\n   * the splice's, not the tag's, for `c4.service-binding-invalid`'s reason\n   * (coherence.ts): the merge carries a tagged element's block over byte for\n   * byte, untagged children included, so a TODO description on a nested child\n   * reaches the fleet map exactly as its tagged parent's would.\n   */\n  splicedEls: Elem[];\n  svcNames: PathableService[];\n  context?: FleetContext;\n}\n\nexport async function authoringIssues(scope: AuthoringScope): Promise<Issue[]> {\n  const issues: Issue[] = [];\n  await intentIssue(scope, issues);\n\n  for (const e of scope.splicedEls) {\n    if (e.description !== SERVICE_DESCRIPTION_SENTINEL) continue;\n    issues.push({\n      severity: \"warn\",\n      gates: true,\n      code: \"scaffold.placeholder\",\n      message: `delta.likec4: '${e.title}' (${e.id}) still carries the scaffolded description '${SERVICE_DESCRIPTION_SENTINEL}' — the merge would publish it to the fleet map. Say what the service owns, or archive with --approve.`,\n    });\n  }\n\n  for (const svc of scope.svcNames) {\n    const paths = featureSpecPaths(scope.featureDir, svc);\n    for (const axis of SPEC_AXES) {\n      const path = paths[axis.key];\n      if (!existsSync(path)) continue;\n      const found = unauthored(await requirementsOf(scope, path));\n      if (found.size === 0) continue;\n      issues.push({\n        severity: \"warn\",\n        gates: true,\n        code: \"scaffold.placeholder\",\n        subject: svc,\n        message: `${svc}: ${axis.file} still carries scaffold placeholder(s) nobody authored — ${quote(found)}. The merge would write them into the living spec as requirements somebody meant. Replace them, or archive with --approve.`,\n      });\n    }\n  }\n\n  // The business corpus. `subject` is the capability id — a THIRD provenance\n  // for this code's subject, after a service id and none at all — and the\n  // artifact table resolves it by MEMBERSHIP against the capability documents\n  // the feature carries (`status/feature/artifacts.ts`), the same resolution\n  // every `delta.*` issue on this axis already relies on. So the capability's\n  // own row turns draft, and a service row does too only where a fleet holds a\n  // service and a capability of one name, which is that module's deliberately\n  // pessimistic answer rather than a mis-attribution here.\n  const capabilities =\n    scope.context === undefined\n      ? await featureCapabilityDeltas(scope.featureDir)\n      : await scope.context.featureCapabilityDeltas(scope.featureDir);\n  for (const doc of capabilities.docs) {\n    const found = unauthored(await requirementsOf(scope, doc.spec));\n    if (found.size === 0) continue;\n    issues.push({\n      severity: \"warn\",\n      gates: true,\n      code: \"scaffold.placeholder\",\n      subject: doc.id,\n      message: `capability ${doc.id}: spec.md still carries scaffold placeholder(s) nobody authored — ${quote(found)}. The merge would write them into the living capabilities/${doc.id}/spec.md as promises somebody meant — and a capability document outlives every service that realizes it. Replace them, or archive with --approve.`,\n    });\n  }\n  return issues;\n}\n\n/** One delta document's requirements, through the invocation's read index when there is one. */\nasync function requirementsOf(scope: AuthoringScope, path: string): Promise<Requirement[]> {\n  if (scope.context === undefined) return parseRequirements(await readFile(path, \"utf8\"));\n  return scope.context.readRequirements(path);\n}\n\n/**\n * The scaffold strings a delta's MERGING requirements still carry.\n *\n * ADDED/MODIFIED only: those are the texts this MERGE would write. A BASE\n * requirement is a quote of the living state — if a sentinel sits there, some\n * earlier archive published it and this feature is not the author to gate on it\n * — and a REMOVED one is leaving the document anyway.\n */\nfunction unauthored(reqs: Requirement[]): Set<string> {\n  const found = new Set<string>();\n  for (const r of reqs) {\n    if (r.kind === \"ADDED\" || r.kind === \"MODIFIED\") sentinelsIn(r, found);\n  }\n  return found;\n}\n\n/** The found sentinels as a message fragment — one spelling, so the two corpora read alike. */\nfunction quote(found: ReadonlySet<string>): string {\n  return [...found].map((s) => `'${s}'`).join(\", \");\n}\n\n/** The exact template strings this requirement still carries, if any. */\nfunction sentinelsIn(r: Requirement, found: Set<string>): void {\n  for (const heading of HEADING_SENTINELS) {\n    if (r.name === heading) found.add(heading);\n    for (const s of r.scenarios) {\n      if (s.name === heading) found.add(heading);\n    }\n  }\n  const body = [r.text.join(\"\\n\"), ...r.scenarios.map((s) => s.lines.join(\"\\n\"))].join(\"\\n\");\n  for (const marker of BODY_SENTINELS) {\n    if (body.includes(marker)) found.add(marker);\n  }\n}\n\n/**\n * Does intent.md SAY anything? The scaffold's Why/Scope bodies are HTML\n * comments, so \"strip frontmatter, comments and headings, look for prose\" is\n * exactly the question \"did a person write the sentence the reviewer reads\n * first\". A missing file gates the same way: a feature with no stated intent\n * is not less anonymous for not having the file.\n */\nasync function intentIssue(scope: AuthoringScope, issues: Issue[]): Promise<void> {\n  const path = featurePaths(scope.featureDir).intent;\n  const empty = { severity: \"warn\", gates: true, code: \"intent.empty\" } as const;\n  if (!existsSync(path)) {\n    issues.push({\n      ...empty,\n      message: `intent.md is missing — nothing says why ${scope.featureId} exists. Write the Why before archiving it into the living docs, or archive with --approve.`,\n    });\n    return;\n  }\n  if (hasProse(await readFile(path, \"utf8\"))) return;\n  issues.push({\n    ...empty,\n    message: `intent.md says nothing yet — its Why and Scope are still the scaffold's comments. Write why ${scope.featureId} exists before archiving it into the living docs, or archive with --approve.`,\n  });\n}\n\n/** Is there any authored text outside frontmatter, HTML comments and headings? */\nfunction hasProse(text: string): boolean {\n  // Normalized BEFORE the fence regex, the discipline document/parse.ts\n  // applies to every other markdown read: `---\\r` is not `---`, so a CRLF\n  // rewrite (or a BOM some Windows editor prefixed) kept the frontmatter,\n  // which then counted as prose — and the untouched scaffold archived at\n  // exit 0 through the exact gate built to refuse it.\n  // The BOM is spelled as an escape, never as the raw character — a raw one is\n  // invisible in review and to grep, which is how it would survive a rewrite.\n  let body = text.replace(/^\\uFEFF/, \"\").replace(/\\r\\n/g, \"\\n\");\n  // Frontmatter: the leading `---` block only, exactly where the scaffold puts it.\n  const fm = /^---\\n[\\s\\S]*?\\n---\\n/.exec(body);\n  if (fm !== null) body = body.slice(fm[0].length);\n  body = body.replace(/<!--[\\s\\S]*?-->/g, \"\");\n  return body\n    .split(\"\\n\")\n    .some((line) => line.trim().length > 0 && !line.trimStart().startsWith(\"#\"));\n}\n"]}

package/dist/core/coherence/authoring/sentinels.js

@@ -0,0 +1,74 @@
+/**
+ * The placeholder strings `loam new` scaffolds, spelled ONCE.
+ *
+ * Both sides of the placeholder gate read this module: the templates in
+ * `commands/new/templates.ts` write these exact strings, and the coherence
+ * check in `./scaffold.ts` refuses to archive them. Spelling a sentinel in two
+ * places is how the gate stops matching the scaffold — a one-character rewording
+ * of a template would silently retire the check that guards it.
+ *
+ * Detection is EXACT on purpose. A requirement whose author genuinely writes
+ * "TODO" in prose is that author's call to make; only the strings loam itself
+ * scaffolded are ones nobody wrote.
+ */
+/** The scaffolded business-requirement heading (`specs/<svc>/spec.md`). */
+export const REQUIREMENT_SENTINEL = "TODO — name the behaviour";
+/** The scaffolded architecture-requirement heading (`specs/<svc>/arch.spec.md`). */
+export const ARCH_REQUIREMENT_SENTINEL = "TODO — name the architectural obligation";
+/**
+ * The scaffolded capability-requirement heading
+ * (`features/<FEAT>/capabilities/<id>/spec.md`).
+ *
+ * Its own string rather than a reuse of `REQUIREMENT_SENTINEL`, because the two
+ * documents ask for different things and the heading is where the template says
+ * so: a service requirement names a BEHAVIOUR the service performs, a capability
+ * requirement names a PROMISE the fleet keeps. A shared "TODO — name the
+ * behaviour" would scaffold the business document with the altitude
+ * `capability.requirement-service-scoped` exists to refuse.
+ */
+export const CAPABILITY_REQUIREMENT_SENTINEL = "TODO — name the promise";
+/** The scaffolded scenario heading, shared by both spec axes. */
+export const SCENARIO_SENTINEL = "TODO — name the case";
+/** The scaffolded description on a `--new-service` element in delta.likec4. */
+export const SERVICE_DESCRIPTION_SENTINEL = "TODO — what this service owns";
+/** The scaffolded SHALL fill-in on the business axis. */
+export const SHALL_SENTINEL = "<observable behaviour, testable without reading the code>";
+/** The scaffolded SHALL fill-in on the architecture axis. */
+export const ARCH_SHALL_SENTINEL = "<the operational/integration behaviour, observable in test>";
+/** The scaffolded SHALL fill-in on the business axis — a promise, not a mechanism. */
+export const CAPABILITY_SHALL_SENTINEL = "<the promise, observable outside the fleet — a customer could check it>";
+/** The scaffolded Given/When/Then fill-ins, shared by both spec axes. Three
+ * constants rather than one keyed object because a `then` property makes an
+ * object thenable — one accidental `await` away from a hang the linter
+ * refuses outright. */
+export const GIVEN_SENTINEL = "<the starting state>";
+export const WHEN_SENTINEL = "<the trigger>";
+export const THEN_SENTINEL = "<the observable outcome>";
+/**
+ * The angle-bracket fill-ins inside scaffolded requirement bodies and steps.
+ * Any one of them surviving to archive means the line around it was never
+ * authored — the brackets are the template telling the author what to replace.
+ */
+export const BODY_SENTINELS = [
+    SHALL_SENTINEL,
+    ARCH_SHALL_SENTINEL,
+    CAPABILITY_SHALL_SENTINEL,
+    GIVEN_SENTINEL,
+    WHEN_SENTINEL,
+    THEN_SENTINEL,
+];
+/**
+ * Every scaffolded heading a requirement or scenario may still carry.
+ *
+ * The list is not partitioned by which document scaffolded which string, and
+ * that is deliberate: the gate asks "did anybody author this line", and a
+ * capability heading pasted into a service delta was authored exactly as little
+ * as it was in the document it came from.
+ */
+export const HEADING_SENTINELS = [
+    REQUIREMENT_SENTINEL,
+    ARCH_REQUIREMENT_SENTINEL,
+    CAPABILITY_REQUIREMENT_SENTINEL,
+    SCENARIO_SENTINEL,
+];
+//# sourceMappingURL=sentinels.js.map

package/dist/core/coherence/authoring/sentinels.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sentinels.js","sourceRoot":"","sources":["../../../../src/core/coherence/authoring/sentinels.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,2EAA2E;AAC3E,MAAM,CAAC,MAAM,oBAAoB,GAAG,2BAA2B,CAAC;AAEhE,oFAAoF;AACpF,MAAM,CAAC,MAAM,yBAAyB,GAAG,0CAA0C,CAAC;AAEpF;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,+BAA+B,GAAG,yBAAyB,CAAC;AAEzE,iEAAiE;AACjE,MAAM,CAAC,MAAM,iBAAiB,GAAG,sBAAsB,CAAC;AAExD,+EAA+E;AAC/E,MAAM,CAAC,MAAM,4BAA4B,GAAG,+BAA+B,CAAC;AAE5E,yDAAyD;AACzD,MAAM,CAAC,MAAM,cAAc,GAAG,2DAA2D,CAAC;AAE1F,6DAA6D;AAC7D,MAAM,CAAC,MAAM,mBAAmB,GAAG,6DAA6D,CAAC;AAEjG,sFAAsF;AACtF,MAAM,CAAC,MAAM,yBAAyB,GAAG,yEAAyE,CAAC;AAEnH;;;uBAGuB;AACvB,MAAM,CAAC,MAAM,cAAc,GAAG,sBAAsB,CAAC;AACrD,MAAM,CAAC,MAAM,aAAa,GAAG,eAAe,CAAC;AAC7C,MAAM,CAAC,MAAM,aAAa,GAAG,0BAA0B,CAAC;AAExD;;;;GAIG;AACH,MAAM,CAAC,MAAM,cAAc,GAAsB;IAC/C,cAAc;IACd,mBAAmB;IACnB,yBAAyB;IACzB,cAAc;IACd,aAAa;IACb,aAAa;CACd,CAAC;AAEF;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,iBAAiB,GAAsB;IAClD,oBAAoB;IACpB,yBAAyB;IACzB,+BAA+B;IAC/B,iBAAiB;CAClB,CAAC","sourcesContent":["/**\n * The placeholder strings `loam new` scaffolds, spelled ONCE.\n *\n * Both sides of the placeholder gate read this module: the templates in\n * `commands/new/templates.ts` write these exact strings, and the coherence\n * check in `./scaffold.ts` refuses to archive them. Spelling a sentinel in two\n * places is how the gate stops matching the scaffold — a one-character rewording\n * of a template would silently retire the check that guards it.\n *\n * Detection is EXACT on purpose. A requirement whose author genuinely writes\n * \"TODO\" in prose is that author's call to make; only the strings loam itself\n * scaffolded are ones nobody wrote.\n */\n\n/** The scaffolded business-requirement heading (`specs/<svc>/spec.md`). */\nexport const REQUIREMENT_SENTINEL = \"TODO — name the behaviour\";\n\n/** The scaffolded architecture-requirement heading (`specs/<svc>/arch.spec.md`). */\nexport const ARCH_REQUIREMENT_SENTINEL = \"TODO — name the architectural obligation\";\n\n/**\n * The scaffolded capability-requirement heading\n * (`features/<FEAT>/capabilities/<id>/spec.md`).\n *\n * Its own string rather than a reuse of `REQUIREMENT_SENTINEL`, because the two\n * documents ask for different things and the heading is where the template says\n * so: a service requirement names a BEHAVIOUR the service performs, a capability\n * requirement names a PROMISE the fleet keeps. A shared \"TODO — name the\n * behaviour\" would scaffold the business document with the altitude\n * `capability.requirement-service-scoped` exists to refuse.\n */\nexport const CAPABILITY_REQUIREMENT_SENTINEL = \"TODO — name the promise\";\n\n/** The scaffolded scenario heading, shared by both spec axes. */\nexport const SCENARIO_SENTINEL = \"TODO — name the case\";\n\n/** The scaffolded description on a `--new-service` element in delta.likec4. */\nexport const SERVICE_DESCRIPTION_SENTINEL = \"TODO — what this service owns\";\n\n/** The scaffolded SHALL fill-in on the business axis. */\nexport const SHALL_SENTINEL = \"<observable behaviour, testable without reading the code>\";\n\n/** The scaffolded SHALL fill-in on the architecture axis. */\nexport const ARCH_SHALL_SENTINEL = \"<the operational/integration behaviour, observable in test>\";\n\n/** The scaffolded SHALL fill-in on the business axis — a promise, not a mechanism. */\nexport const CAPABILITY_SHALL_SENTINEL = \"<the promise, observable outside the fleet — a customer could check it>\";\n\n/** The scaffolded Given/When/Then fill-ins, shared by both spec axes. Three\n * constants rather than one keyed object because a `then` property makes an\n * object thenable — one accidental `await` away from a hang the linter\n * refuses outright. */\nexport const GIVEN_SENTINEL = \"<the starting state>\";\nexport const WHEN_SENTINEL = \"<the trigger>\";\nexport const THEN_SENTINEL = \"<the observable outcome>\";\n\n/**\n * The angle-bracket fill-ins inside scaffolded requirement bodies and steps.\n * Any one of them surviving to archive means the line around it was never\n * authored — the brackets are the template telling the author what to replace.\n */\nexport const BODY_SENTINELS: readonly string[] = [\n  SHALL_SENTINEL,\n  ARCH_SHALL_SENTINEL,\n  CAPABILITY_SHALL_SENTINEL,\n  GIVEN_SENTINEL,\n  WHEN_SENTINEL,\n  THEN_SENTINEL,\n];\n\n/**\n * Every scaffolded heading a requirement or scenario may still carry.\n *\n * The list is not partitioned by which document scaffolded which string, and\n * that is deliberate: the gate asks \"did anybody author this line\", and a\n * capability heading pasted into a service delta was authored exactly as little\n * as it was in the document it came from.\n */\nexport const HEADING_SENTINELS: readonly string[] = [\n  REQUIREMENT_SENTINEL,\n  ARCH_REQUIREMENT_SENTINEL,\n  CAPABILITY_REQUIREMENT_SENTINEL,\n  SCENARIO_SENTINEL,\n];\n"]}