@milehimikey/em 1.10.0 → 1.12.0

package/dist/render/sliceStatus.js

@@ -11,20 +11,27 @@
 // docs for them (first one gets the real file, the second honestly gets null).
 //
 // MIL-121 fallback: when a slice has no own `slices/<key>.md`, scan the `slices/` directory for
-// a sibling doc whose frontmatter `covers:` names this slice's key, and borrow IT. This
-// is filename+frontmatter discovery only — same convention as the direct lookup above, and
-// still never reads `note` (the tested invariant test/catalog.e2e.test.ts pins for `em catalog`'s
-// parallel doc discovery) — a slice's `note "slices/<other>.md"` cross-binding declaration is
-// docJoin.ts's concern (`em export`/`em validate --slice-ready`), not this module's.
-import { existsSync, readdirSync, readFileSync } from "node:fs";
+// a sibling doc whose frontmatter `covers:` names this slice's key, and borrow IT. The scan
+// itself (readCoverageDocs) is shared with `em catalog`'s own covered-slice handling (MIL-137,
+// src/catalog/coverage.ts) so the two never disagree about which doc covers a slice.
+//
+// MIL-208 fallback (checked last, after own file and the covers: scan both come up empty): a
+// continuation slice (an again-view-only slice) borrows the ORIGINATING slice's own file
+// directly — same predicate/resolution as catalog/docJoin.ts's note-gated join, model/
+// continuation.ts, just applied to this module's filename-convention resolution instead of
+// notes.
+import { existsSync, readFileSync } from "node:fs";
 import { join } from "node:path";
 import { computeRefs } from "../model/refs.js";
+import { continuationOf } from "../model/continuation.js";
+import { readCoverageDocs } from "../catalog/coverage.js";
 import { parseSliceDoc } from "../catalog/sliceDoc.js";
-/** Each slice's resolved design doc (own `slices/<key>.md`, or the MIL-121 covering doc, or
- *  null), same order as model.slices (and so the same order as the header row's columns —
- *  see layout/grid.ts's sliceNames). */
+/** Each slice's resolved design doc (own `slices/<key>.md`, the MIL-121 covering doc, the
+ *  MIL-208 originating slice's own file, or null), same order as model.slices (and so the same
+ *  order as the header row's columns — see layout/grid.ts's sliceNames). */
 export function readSliceDocs(model, baseDir) {
-    const { sliceKeys } = computeRefs(model);
+    const refs = computeRefs(model);
+    const { sliceKeys } = refs;
     const slicesDir = join(baseDir, "slices");
     let coverage = null; // built lazily, only if ever needed
     return model.slices.map((_slice, i) => {
@@ -33,7 +40,16 @@ export function readSliceDocs(model, baseDir) {
         if (existsSync(docPath))
             return parseSliceDoc(readFileSync(docPath, "utf8"));
         coverage ??= readCoverageDocs(slicesDir);
-        return coverage.get(sliceKey) ?? null;
+        const covering = coverage.get(sliceKey)?.doc;
+        if (covering)
+            return covering;
+        const continuation = continuationOf(model, refs, i);
+        if (continuation) {
+            const originatingPath = join(slicesDir, `${continuation.sliceKey}.md`);
+            if (existsSync(originatingPath))
+                return parseSliceDoc(readFileSync(originatingPath, "utf8"));
+        }
+        return null;
     });
 }
 /** One status per slice, same order/resolution as readSliceDocs. null means no doc was found
@@ -41,22 +57,4 @@ export function readSliceDocs(model, baseDir) {
 export function readSliceStatuses(model, baseDir) {
     return readSliceDocs(model, baseDir).map((doc) => doc?.status ?? null);
 }
-/** Scans every `slices/*.md` file (sorted, for deterministic first-wins on an overlapping
- *  `covers:` claim) and maps each covered slice key to that doc. Directory-scan, not
- *  the single-file existsSync check every other doc lookup in em uses — the one precedent for
- *  it is `em ledger`'s (src/cli/ledgerCheck.ts) own `readdirSync(slicesDir)` sweep. */
-function readCoverageDocs(slicesDir) {
-    const coverage = new Map();
-    if (!existsSync(slicesDir))
-        return coverage;
-    const files = readdirSync(slicesDir).filter((f) => f.endsWith(".md")).sort();
-    for (const file of files) {
-        const doc = parseSliceDoc(readFileSync(join(slicesDir, file), "utf8"));
-        for (const coveredKey of doc.covers) {
-            if (!coverage.has(coveredKey))
-                coverage.set(coveredKey, doc);
-        }
-    }
-    return coverage;
-}
 //# sourceMappingURL=sliceStatus.js.map

package/dist/render/sliceStatus.js.map

@@ -1 +1 @@
-{"version":3,"file":"sliceStatus.js","sourceRoot":"","sources":["../../src/render/sliceStatus.ts"],"names":[],"mappings":"AAAA,+BAA+B;AAC/B,qEAAqE;AACrE,kFAAkF;AAClF,kFAAkF;AAClF,iFAAiF;AACjF,kDAAkD;AAClD,EAAE;AACF,6EAA6E;AAC7E,6EAA6E;AAC7E,+EAA+E;AAC/E,+EAA+E;AAC/E,EAAE;AACF,gGAAgG;AAChG,wFAAwF;AACxF,2FAA2F;AAC3F,kGAAkG;AAClG,8FAA8F;AAC9F,qFAAqF;AAErF,OAAO,EAAE,UAAU,EAAE,WAAW,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AAChE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAEjC,OAAO,EAAE,WAAW,EAAE,MAAM,kBAAkB,CAAC;AAC/C,OAAO,EAAE,aAAa,EAAY,MAAM,wBAAwB,CAAC;AAEjE;;wCAEwC;AACxC,MAAM,UAAU,aAAa,CAAC,KAAsB,EAAE,OAAe;IACnE,MAAM,EAAE,SAAS,EAAE,GAAG,WAAW,CAAC,KAAK,CAAC,CAAC;IACzC,MAAM,SAAS,GAAG,IAAI,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;IAC1C,IAAI,QAAQ,GAAiC,IAAI,CAAC,CAAC,oCAAoC;IAEvF,OAAO,KAAK,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE;QACpC,MAAM,QAAQ,GAAG,SAAS,CAAC,CAAC,CAAC,CAAC;QAC9B,MAAM,OAAO,GAAG,IAAI,CAAC,SAAS,EAAE,GAAG,QAAQ,KAAK,CAAC,CAAC;QAClD,IAAI,UAAU,CAAC,OAAO,CAAC;YAAE,OAAO,aAAa,CAAC,YAAY,CAAC,OAAO,EAAE,MAAM,CAAC,CAAC,CAAC;QAC7E,QAAQ,KAAK,gBAAgB,CAAC,SAAS,CAAC,CAAC;QACzC,OAAO,QAAQ,CAAC,GAAG,CAAC,QAAQ,CAAC,IAAI,IAAI,CAAC;IACxC,CAAC,CAAC,CAAC;AACL,CAAC;AAED;qEACqE;AACrE,MAAM,UAAU,iBAAiB,CAAC,KAAsB,EAAE,OAAe;IACvE,OAAO,aAAa,CAAC,KAAK,EAAE,OAAO,CAAC,CAAC,GAAG,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,EAAE,MAAM,IAAI,IAAI,CAAC,CAAC;AACzE,CAAC;AAED;;;uFAGuF;AACvF,SAAS,gBAAgB,CAAC,SAAiB;IACzC,MAAM,QAAQ,GAAG,IAAI,GAAG,EAAoB,CAAC;IAC7C,IAAI,CAAC,UAAU,CAAC,SAAS,CAAC;QAAE,OAAO,QAAQ,CAAC;IAC5C,MAAM,KAAK,GAAG,WAAW,CAAC,SAAS,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;IAC7E,KAAK,MAAM,IAAI,IAAI,KAAK,EAAE,CAAC;QACzB,MAAM,GAAG,GAAG,aAAa,CAAC,YAAY,CAAC,IAAI,CAAC,SAAS,EAAE,IAAI,CAAC,EAAE,MAAM,CAAC,CAAC,CAAC;QACvE,KAAK,MAAM,UAAU,IAAI,GAAG,CAAC,MAAM,EAAE,CAAC;YACpC,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,UAAU,CAAC;gBAAE,QAAQ,CAAC,GAAG,CAAC,UAAU,EAAE,GAAG,CAAC,CAAC;QAC/D,CAAC;IACH,CAAC;IACD,OAAO,QAAQ,CAAC;AAClB,CAAC"}
+{"version":3,"file":"sliceStatus.js","sourceRoot":"","sources":["../../src/render/sliceStatus.ts"],"names":[],"mappings":"AAAA,+BAA+B;AAC/B,qEAAqE;AACrE,kFAAkF;AAClF,kFAAkF;AAClF,iFAAiF;AACjF,kDAAkD;AAClD,EAAE;AACF,6EAA6E;AAC7E,6EAA6E;AAC7E,+EAA+E;AAC/E,+EAA+E;AAC/E,EAAE;AACF,gGAAgG;AAChG,4FAA4F;AAC5F,+FAA+F;AAC/F,qFAAqF;AACrF,EAAE;AACF,6FAA6F;AAC7F,yFAAyF;AACzF,uFAAuF;AACvF,2FAA2F;AAC3F,SAAS;AAET,OAAO,EAAE,UAAU,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AACnD,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAEjC,OAAO,EAAE,WAAW,EAAE,MAAM,kBAAkB,CAAC;AAC/C,OAAO,EAAE,cAAc,EAAE,MAAM,0BAA0B,CAAC;AAC1D,OAAO,EAAE,gBAAgB,EAAe,MAAM,wBAAwB,CAAC;AACvE,OAAO,EAAE,aAAa,EAAY,MAAM,wBAAwB,CAAC;AAEjE;;4EAE4E;AAC5E,MAAM,UAAU,aAAa,CAAC,KAAsB,EAAE,OAAe;IACnE,MAAM,IAAI,GAAG,WAAW,CAAC,KAAK,CAAC,CAAC;IAChC,MAAM,EAAE,SAAS,EAAE,GAAG,IAAI,CAAC;IAC3B,MAAM,SAAS,GAAG,IAAI,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;IAC1C,IAAI,QAAQ,GAAoC,IAAI,CAAC,CAAC,oCAAoC;IAE1F,OAAO,KAAK,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE;QACpC,MAAM,QAAQ,GAAG,SAAS,CAAC,CAAC,CAAC,CAAC;QAC9B,MAAM,OAAO,GAAG,IAAI,CAAC,SAAS,EAAE,GAAG,QAAQ,KAAK,CAAC,CAAC;QAClD,IAAI,UAAU,CAAC,OAAO,CAAC;YAAE,OAAO,aAAa,CAAC,YAAY,CAAC,OAAO,EAAE,MAAM,CAAC,CAAC,CAAC;QAC7E,QAAQ,KAAK,gBAAgB,CAAC,SAAS,CAAC,CAAC;QACzC,MAAM,QAAQ,GAAG,QAAQ,CAAC,GAAG,CAAC,QAAQ,CAAC,EAAE,GAAG,CAAC;QAC7C,IAAI,QAAQ;YAAE,OAAO,QAAQ,CAAC;QAC9B,MAAM,YAAY,GAAG,cAAc,CAAC,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;QACpD,IAAI,YAAY,EAAE,CAAC;YACjB,MAAM,eAAe,GAAG,IAAI,CAAC,SAAS,EAAE,GAAG,YAAY,CAAC,QAAQ,KAAK,CAAC,CAAC;YACvE,IAAI,UAAU,CAAC,eAAe,CAAC;gBAAE,OAAO,aAAa,CAAC,YAAY,CAAC,eAAe,EAAE,MAAM,CAAC,CAAC,CAAC;QAC/F,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC,CAAC,CAAC;AACL,CAAC;AAED;qEACqE;AACrE,MAAM,UAAU,iBAAiB,CAAC,KAAsB,EAAE,OAAe;IACvE,OAAO,aAAa,CAAC,KAAK,EAAE,OAAO,CAAC,CAAC,GAAG,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,EAAE,MAAM,IAAI,IAAI,CAAC,CAAC;AACzE,CAAC"}

package/dist/templates.d.ts

@@ -1,8 +1,11 @@
 export declare const STARTER_EM = "model \"Order Fulfillment\"\n\npersona Customer\npersona Manager\n\ncontext Order\ncontext Payment\n\n# --- Command pattern: UI -> command -> event ---\nslice \"Browse Catalog\" {\n  ui Product Catalog @Customer\n  command Place Order\n  event Order Placed @Order\n}\n\n# --- View pattern: event -> read model -> UI ---\nslice \"View Open Orders\" {\n  view Open Orders from \"Order Placed\"\n  ui Order List @Customer\n}\n\nslice \"Checkout\" {\n  ui Checkout Screen @Customer\n  command Submit Payment\n  event Payment Requested @Payment\n}\n\n# --- View pattern: a human view of pending payments ---\nslice \"Manager Review\" {\n  view Pending Payments from \"Payment Requested\"\n  ui Payment Dashboard @Manager\n}\n\n# --- Read model the automation watches, in its own slice ---\nslice \"Payments To Process\" {\n  view Payments To Process from \"Payment Requested\"\n}\n\n# --- Automation slice: the processor, the command it triggers, and that command's event ---\nslice \"Capture Payment\" {\n  processor Payment Gateway from \"Payments To Process\"\n  command Capture Payment\n  event Payment Captured @Payment\n}\n\nslice \"Show Receipt\" {\n  view Receipts from \"Payment Captured\"\n  ui Receipt Screen @Customer\n}\n";
 /** Raw copy of templates/model-readme.md, \`{{...}}\` placeholders intact — see scaffoldReadme(). */
-export declare const MODEL_README_TEMPLATE = "# {{Model Name}}\n\n{{One-paragraph description of the business process(es) this event model covers.}}\n\n## Live view\nWhile modeling, run the live view so the team can watch the diagram update:\n\n```bash\nem watch {{model-name}}.em -o {{model-name}}.svg --serve   # re-render + instant push-reload\n# then open the URL it prints (http://localhost:5173/?svg={{model-name}}.svg) and share the screen\n```\n\nPan/zoom to navigate the diagram (drag, scroll; **Fit** resets), and click **Review mode** in\nthe header for a slice-by-slice walkthrough. If a save fails to render, the viewer keeps the\nlast good diagram and shows an error banner until the next successful load.\n\nStatic render: `em render {{model-name}}.em -o {{model-name}}.svg`\n\n## Patterns legend\n- **State Change** \u2014 UI \u2192 Command \u2192 Event\n- **State View** \u2014 Event(s) \u2192 Read Model \u2192 UI\n- **Automation** \u2014 Read Model (slice before) \u2192 Processor + Command \u2192 Event, together\n- **Translation** \u2014 External input (or Read Model, slice before) \u2192 Translation + Command \u2192 Event, together\n\nBetween them these are the only legal connections: `ui \u2192 command`, `command \u2192 event`,\n`event \u2192 read model`, `read model \u2192 ui`, `read model \u2192 reaction`, `reaction \u2192 command`. A command\nnever reaches a read model directly \u2014 the event goes between them. Every slice is joined up at\nboth ends: something triggers each command (the screen it's issued from, or the reaction that\ntriggers it, also in this slice), and every event a command records is read by some read model \u2014 so each State\nChange slice is paired with the State View slice that projects its event. A read model repeated\nalong the timeline (`view X again`) shows the same projection at a later point; the instances are\nnever connected to one another.\n\n## Slices\n<!-- The canonical slice index \u2014 the ONE place slices are enumerated (the state file\n     points here rather than keeping its own copy). Generated \u2014 run\n     `em slice index {{model-name}}.em` to (re)write the table below from the model and its\n     slice docs; never hand-edit between the markers. -->\n<!-- GENERATED:slices:start -->\n| # | Slice | Pattern | Status | Ratified by | Owner | Tracking | Implemented in | Design doc |\n|---|-------|---------|--------|-------------|-------|----------|----------------|------------|\n<!-- GENERATED:slices:end -->\n\n## Status\nSee [`.event-modeling.md`](.event-modeling.md) for current phase, decisions, and open questions.\n";
+export declare const MODEL_README_TEMPLATE = "# {{Model Name}}\n\n{{One-paragraph description of the business process(es) this event model covers.}}\n\n## Live view\nWhile modeling, run the live view so the team can watch the diagram update:\n\n```bash\nem watch {{model-name}}.em -o {{model-name}}.svg --serve   # re-render + instant push-reload\n# then open the URL it prints (http://localhost:5173/?svg={{model-name}}.svg) and share the screen\n```\n\nPan/zoom to navigate the diagram (drag, scroll; **Fit** resets), and click **Review mode** in\nthe header for a slice-by-slice walkthrough. If a save fails to render, the viewer keeps the\nlast good diagram and shows an error banner until the next successful load.\n\nStatic render: `em render {{model-name}}.em -o {{model-name}}.svg`\n\n## Patterns legend\n- **State Change** \u2014 UI \u2192 Command \u2192 Event\n- **State View** \u2014 Event(s) \u2192 Read Model \u2192 UI\n- **Automation** \u2014 Read Model (slice before) \u2192 Processor + Command \u2192 Event, together\n- **Translation** \u2014 External input (or Read Model, slice before) \u2192 Translation + Command \u2192 Event, together\n\nBetween them these are the only legal connections: `ui \u2192 command`, `command \u2192 event`,\n`event \u2192 read model`, `read model \u2192 ui`, `read model \u2192 reaction`, `reaction \u2192 command`. A command\nnever reaches a read model directly \u2014 the event goes between them. Every slice is joined up at\nboth ends: something triggers each command (the screen it's issued from, or the reaction that\ntriggers it, also in this slice), and every event a command records is read by some read model \u2014 so each State\nChange slice is paired with the State View slice that projects its event. A read model repeated\nalong the timeline (`view X again`) shows the same projection at a later point; the instances are\nnever connected to one another.\n\n## Slices\n<!-- The canonical slice index \u2014 the ONE place slices are enumerated (the state file\n     points here rather than keeping its own copy). Generated \u2014 run\n     `em slice index {{model-name}}.em` to (re)write the table below from the model and its\n     slice docs; never hand-edit between the markers. -->\n<!-- GENERATED:slices:start -->\n| # | Slice | Pattern | Status | Reviewed by | Ratified by | Owner | Tracking | Implemented in | Design doc |\n|---|-------|---------|--------|-------------|-------------|-------|----------|----------------|------------|\n<!-- GENERATED:slices:end -->\n\n## Status\nSee [`.event-modeling.md`](.event-modeling.md) for current phase, decisions, and open questions.\n";
 /** Raw copy of templates/state.md, \`{{...}}\` placeholders intact — see scaffoldStateFile(). */
 export declare const STATE_TEMPLATE = "<!--\nResumable progress state for an event model. Stored as <model>/.event-modeling.md\nThe skill reads this on `/event-modeling` (no arg) to resume where you left off.\nKeep it current at the end of every working session.\n-->\n\n# Event Modeling Progress \u2014 {{Model Name}}\n\n- **Model file:** `{{model-name}}.em`\n- **Current phase:** {{discover | extract | model | slice | implement | conform | review | validate}}\n- **Current step:** {{1\u20137, see methodology; or extraction round R1\u2013R7}}\n- **Last updated:** {{YYYY-MM-DD}}\n- **Last conformance:** {{YYYY-MM-DD @ <target-repo revision> \u2014 report: conformance/<date>-report.md | never}}\n- **Last stakeholder review:** {{YYYY-MM-DD \u2014 attendees: see Participants | never}}\n\n## Session inputs\n- **Scope line:** {{one-line description of what's in/out of bounds for this model}}\n- **PRD / spec reference:** {{path, link, or \"none\"}}\n- **Headless/API model:** {{yes | no}}\n- **Source mode:** {{greenfield | extract-event-driven | extract-procedural}}\n- **Existing system refs:** {{repo paths, event-schema/topic locations, docs \u2014 or \"n/a\"}}\n\n## Participants\n<!-- Populate at session start. Live workshop: one human proxy relays questions to the room;\n     attribute every answer/decision in the Decisions log to a named participant here. -->\n- {{Name}} \u2014 {{role}} \u2014 {{domain area}}\n\n## Extraction progress (existing-system models only \u2014 delete for greenfield)\n- [ ] R1. Candidate events (extracted/synthesized, filtered, confirmed)\n- [ ] R2. Timeline order (as-is narrative, actors/callers, first render)\n- [ ] R3. Commands / inputs\n- [ ] R4. Read models / outputs (validate from here)\n- [ ] R5. Boundaries & reactions (reaction shares its slice with the command it triggers)\n- [ ] R6. Gap & TBD reconciliation\n- [ ] R7. Convergence (render + validate clean, user confirmed as-is)\n\n## Steps completed\n- [ ] 1. Brainstorm events\n- [ ] 2. Plot / storyboard (personas + UI)\n- [ ] 3. Inputs (commands)\n- [ ] 4. Outputs (read models)\n- [ ] 5. Swimlanes & apply patterns\n- [ ] 6. Elaborate scenarios\n- [ ] 7. Evaluate completeness (`em validate` clean)\n\n## Decisions log\n<!-- Resolved choices, with the reasoning, so they aren't re-litigated. In a live workshop,\n     attribute each entry to the participant who made the call (see Participants above). -->\n- {{YYYY-MM-DD}}: {{decision}} \u2014 {{why}} \u2014 by {{participant, if a live workshop}}\n\n## Usage log\n<!-- The team's only usage signal today (see docs/usage-data.md) \u2014 cheap and coarse on purpose.\n     One line per session: phase(s) touched, and validate diagnostic *categories* hit (one of\n     the exact fixed strings in docs/usage-data.md#categories, e.g. \"read model has no\n     consumer\" \u2014 never the full instance message or any domain content). Append, never edit\n     past entries. -->\n- {{YYYY-MM-DD}}: phases: {{discover | extract | model | slice | implement | conform | review | validate | watch, ...}} \u2014 validate: {{diagnostic category (docs/usage-data.md#categories), ... | none}}\n\n## Open questions / parking lot\n<!-- Unresolved items to bring back to the user. Never guess these. Metadata is optional and\n     flat \u2014 add only what's known: source (ticket/conversation that spawned it), blocked on\n     (who/what), revisit (when). -->\n- [ ] {{question}} \u2014 source: {{ticket/conversation link, optional}} \u2014 blocked on: {{who/what, optional}} \u2014 revisit: {{when, optional}}\n\n## Slice inventory\n<!-- Deliberately NOT a table: the canonical slice index (slice, pattern, status, doc link)\n     lives in README.md's \"Slices\" section \u2014 one source of truth, updated there. This file\n     only tracks resumable session state. -->\nSee `README.md` \u2192 **Slices** for the slice index and per-slice doc status.\n";
+/** Raw copy of templates/constitution.md, \`{{...}}\` placeholders intact — see
+ *  scaffoldConstitution(). */
+export declare const CONSTITUTION_TEMPLATE = "<!--\nThe implementation constitution: the house rules an implementing agent follows on EVERY slice \u2014\nstack, code style, testing norms, NFR baselines, review norms. It answers \"how do we build things\nhere\" once, so no slice doc has to repeat it and no agent has to invent it. Slice docs say WHAT to\nbuild; this says HOW it gets built here.\n\nWhere this document lives:\n  - No SDD tool: `constitution.md` beside the model \u2014 `em scaffold` writes it there.\n  - spec-kit project (a `.specify/` directory exists anywhere above the model): the document IS\n    `.specify/memory/constitution.md`. em writes no second copy; the sections below merge into\n    that file under these same headings, never overwriting text already there, and ratification is\n    recorded in spec-kit's own `**Ratified**:` footer line instead of the frontmatter below.\n\nHow it gets filled: not by an agent guessing. Each section opens with the question a short\nfacilitated conversation asks before the first slice is implemented \u2014 the procedure is \"Before the\nfirst slice: the constitution\" in the `event-modeling-implement` skill's `reference/implement.md`\n(`em contract` prints it). Replace each `{{...}}` block with the real answers; delete the guidance\ncomments and any row that doesn't apply.\n\nRatification: `ratifiedBy:`/`ratifiedOn:` are the same identity discipline slice docs use \u2014 a\nNAMED human and an ISO date, hand-filled at sign-off (no `em` command writes this file).\n**A constitution with an empty `ratifiedBy:` is a draft**: an implementing agent treats it as\nunratified, says so, and does not proceed on unilateral style or stack decisions for a first slice.\n\n`em status` reports this document as present or absent per model \u2014 existence only. em never reads\nor validates its content, and nothing here is machine-parsed.\n-->\n\n---\nschemaVersion: 1\nratifiedBy:\nratifiedOn:\n---\n# {{Project Name}} \u2014 implementation constitution\n\nThe house rules for how implementation happens in this project. They bound every \"purely\ntechnical choice\" an implementing agent would otherwise make alone.\n\n## Stack and architectural shape\n\n> **What do we build on, what shape does the code take, and which implementation skill or\n> approach does each slice pattern route to?**\n\n- **Languages / runtimes:** {{e.g. Kotlin 2.x on JVM 21; TypeScript 5 on Node 24}}\n- **Frameworks / platform:** {{web framework, persistence, messaging, build tool}}\n- **Architectural pattern:** {{e.g. event-sourced CQRS with vertical slices; layered service over\n  a relational store; functional core / imperative shell}}\n- **Where a slice's code lives:** {{one package per slice, per context, ...}}\n- **Interface conventions:** {{resource style \u2014 REST/RPC/GraphQL, etc.; error/rejection mapping;\n  versioning; auth at the edge \u2014 the shape every `ui`-triggered command or `ui`-consumed view's\n  endpoint follows, decided once here rather than invented per slice}}\n\nRouting \u2014 which implementation skill or approach each of the four slice patterns uses:\n\n| Pattern | Skill / approach |\n|---|---|\n| State Change | {{e.g. the `axon-*` skill set \u2014 axon-entity-patterns, then axon-entity-testing}} |\n| State View | {{e.g. the `axon-*` skill set \u2014 axon-projection-patterns, then axon-projection-testing}} |\n| Automation | {{e.g. the `axon-*` skill set \u2014 axon-policy-patterns, then axon-policy-testing}} |\n| Translation | {{e.g. the `axon-*` skill set \u2014 axon-translation-patterns}} |\n\nAn agent implementing a slice reads the doc's `pattern:` frontmatter and follows that row \u2014 this\ntable is the only routing rule.\n\n## Code style\n\n> **What does \"idiomatic\" mean in this codebase \u2014 formatting, naming, module layout?**\n\n- **Formatter / linter:** {{the tool and the command that runs it \u2014 never hand-format against it}}\n- **Naming:** {{commands, events, handlers, files, test names}}\n- **Module layout:** {{what lives in which file/package, and what may not import what}}\n- **Idiomatic here means:** {{the two or three habits a new contributor most often gets wrong}}\n\n## Testing norms\n\n> **What must be tested for each slice pattern, where do those tests live, and how are they named\n> so `em coverage` can trace invariant IDs?**\n\n- **Levels required per pattern:** {{e.g. State Change \u2014 decider unit tests plus a\n  given/when/then fixture test; State View \u2014 projection tests; Automation / Translation \u2014\n  reaction tests, including a negative case}}\n- **Invariant tests:** {{where they live}} \u2014 every `INV-<MNEMONIC>-n` in a slice doc needs at least\n  one test **citing that exact ID** in its name or a comment, so\n  `em coverage <model>.em --tests <dir>` can trace it.\n- **Scenario tests:** {{where they live}} \u2014 one per `## Scenarios (Given / When / Then)` entry,\n  with rejection scenarios asserting the doc's named rejection reason.\n- **Test naming convention:** {{the exact pattern, e.g. `INV-ORD-3: rejects a second submit`}}\n- **What \"green\" means:** {{the command CI runs}}\n\n## NFR baselines\n\n> **What standing non-functional defaults does every slice inherit \u2014 authz, PII, performance,\n> observability?**\n\n- **Authorization model:** {{who may issue which commands, how it's enforced, and where}}\n- **PII / data handling:** {{what is sensitive, what may be logged, retention}}\n- **Performance defaults:** {{latency / throughput budgets that apply unless a slice says otherwise}}\n- **Observability:** {{logging, metrics, tracing every slice is expected to emit}}\n\nA slice doc's own `## Non-Functional Requirements` section overrides these for that slice; where\nit is silent, these apply.\n\n## Review and merge norms\n\n> **Who reviews an implementation PR, what blocks a merge, and how does the slice doc's status\n> flip fit in?**\n\n- **Reviewers:** {{who \u2014 a team, a CODEOWNERS rule, the slice's ratifier}}\n- **What blocks a merge:** {{e.g. a failing suite, an uncovered invariant, a gap that belongs back\n  at the model}}\n- **Branch / commit conventions:** {{...}} \u2014 name only branch naming and commit-message style\n  here. **One slice doc = one PR is the implement contract's rule, not this document's to\n  amend** \u2014 a `covers:` doc ships as one PR for both keys; a read model is one doc, so a later\n  `again` instance is a continuation of the doc that first declared it, not a PR of its own. See\n  the agent guide's \u00A75/\u00A710.\n- **At merge:** run `em slice mark-implemented <model>.em <slice-key> <pr-url>` \u2014 the one edit an\n  implementing agent makes to a ratified slice doc, run by {{the PR author | CI}}. Never bump\n  `version:`; that moves only when a delta is ratified.\n";
 /** Same STARTER_EM content `em init` writes, titled from an arbitrary display name — used by
  *  `em scaffold`, which (unlike `em init`) knows a name to title the model with. */
 export declare function starterEmFor(title: string): string;
@@ -18,3 +21,13 @@ export declare function scaffoldReadme(displayName: string, slugName: string): s
  *  the template's own guidance comment intact where it has one — per the skill's "don't guess,
  *  park it" principle, never a fabricated example. Never leaves \`{{...}}\` in the result. */
 export declare function scaffoldStateFile(displayName: string, slugName: string, today: string): string;
+/** Fill CONSTITUTION_TEMPLATE's project-name placeholder for `em scaffold` (MIL-202).
+ *
+ *  Unlike `scaffoldReadme`/`scaffoldStateFile`, this one **deliberately leaves every other
+ *  \`{{...}}\` block intact**: they are the unanswered questions of the elicitation conversation
+ *  the implement skill runs before the first slice ("Before the first slice: the constitution"),
+ *  not mechanical fields em could fill. An unanswered constitution must read as unanswered — the
+ *  placeholders are the todo list, and the empty `ratifiedBy:` frontmatter says it's still a
+ *  draft. Nothing in `em` ever parses this file's body; only its existence is reported
+ *  (`em status`'s `constitution` field). */
+export declare function scaffoldConstitution(displayName: string): string;

package/dist/templates.js

@@ -56,9 +56,9 @@ slice "Show Receipt" {
 // mirroring STARTER_EM above — the compiled CLI never reads .claude/skills/ at runtime to
 // produce these, so `em scaffold` behaves identically whether em is run from a checkout or
 // installed from npm. test/scaffoldTemplatesSync.test.ts asserts each constant below stays
-// byte-identical to its source file in .claude/skills/event-modeling/templates/, so the two
-// copies can't silently drift — regenerate by hand (or re-run the one-off script noted there)
-// whenever a template file changes.
+// byte-identical to its source file in .claude/skills/event-modeling-shared/templates/, so the
+// two copies can't silently drift — regenerate by hand (or re-run the one-off script noted
+// there) whenever a template file changes.
 /** Raw copy of templates/model-readme.md, \`{{...}}\` placeholders intact — see scaffoldReadme(). */
 export const MODEL_README_TEMPLATE = `# {{Model Name}}
 
@@ -99,8 +99,8 @@ never connected to one another.
      \`em slice index {{model-name}}.em\` to (re)write the table below from the model and its
      slice docs; never hand-edit between the markers. -->
 <!-- GENERATED:slices:start -->
-| # | Slice | Pattern | Status | Ratified by | Owner | Tracking | Implemented in | Design doc |
-|---|-------|---------|--------|-------------|-------|----------|----------------|------------|
+| # | Slice | Pattern | Status | Reviewed by | Ratified by | Owner | Tracking | Implemented in | Design doc |
+|---|-------|---------|--------|-------------|-------------|-------|----------|----------------|------------|
 <!-- GENERATED:slices:end -->
 
 ## Status
@@ -177,6 +177,127 @@ Keep it current at the end of every working session.
      only tracks resumable session state. -->
 See \`README.md\` → **Slices** for the slice index and per-slice doc status.
 `;
+/** Raw copy of templates/constitution.md, \`{{...}}\` placeholders intact — see
+ *  scaffoldConstitution(). */
+export const CONSTITUTION_TEMPLATE = `<!--
+The implementation constitution: the house rules an implementing agent follows on EVERY slice —
+stack, code style, testing norms, NFR baselines, review norms. It answers "how do we build things
+here" once, so no slice doc has to repeat it and no agent has to invent it. Slice docs say WHAT to
+build; this says HOW it gets built here.
+
+Where this document lives:
+  - No SDD tool: \`constitution.md\` beside the model — \`em scaffold\` writes it there.
+  - spec-kit project (a \`.specify/\` directory exists anywhere above the model): the document IS
+    \`.specify/memory/constitution.md\`. em writes no second copy; the sections below merge into
+    that file under these same headings, never overwriting text already there, and ratification is
+    recorded in spec-kit's own \`**Ratified**:\` footer line instead of the frontmatter below.
+
+How it gets filled: not by an agent guessing. Each section opens with the question a short
+facilitated conversation asks before the first slice is implemented — the procedure is "Before the
+first slice: the constitution" in the \`event-modeling-implement\` skill's \`reference/implement.md\`
+(\`em contract\` prints it). Replace each \`{{...}}\` block with the real answers; delete the guidance
+comments and any row that doesn't apply.
+
+Ratification: \`ratifiedBy:\`/\`ratifiedOn:\` are the same identity discipline slice docs use — a
+NAMED human and an ISO date, hand-filled at sign-off (no \`em\` command writes this file).
+**A constitution with an empty \`ratifiedBy:\` is a draft**: an implementing agent treats it as
+unratified, says so, and does not proceed on unilateral style or stack decisions for a first slice.
+
+\`em status\` reports this document as present or absent per model — existence only. em never reads
+or validates its content, and nothing here is machine-parsed.
+-->
+
+---
+schemaVersion: 1
+ratifiedBy:
+ratifiedOn:
+---
+# {{Project Name}} — implementation constitution
+
+The house rules for how implementation happens in this project. They bound every "purely
+technical choice" an implementing agent would otherwise make alone.
+
+## Stack and architectural shape
+
+> **What do we build on, what shape does the code take, and which implementation skill or
+> approach does each slice pattern route to?**
+
+- **Languages / runtimes:** {{e.g. Kotlin 2.x on JVM 21; TypeScript 5 on Node 24}}
+- **Frameworks / platform:** {{web framework, persistence, messaging, build tool}}
+- **Architectural pattern:** {{e.g. event-sourced CQRS with vertical slices; layered service over
+  a relational store; functional core / imperative shell}}
+- **Where a slice's code lives:** {{one package per slice, per context, ...}}
+- **Interface conventions:** {{resource style — REST/RPC/GraphQL, etc.; error/rejection mapping;
+  versioning; auth at the edge — the shape every \`ui\`-triggered command or \`ui\`-consumed view's
+  endpoint follows, decided once here rather than invented per slice}}
+
+Routing — which implementation skill or approach each of the four slice patterns uses:
+
+| Pattern | Skill / approach |
+|---|---|
+| State Change | {{e.g. the \`axon-*\` skill set — axon-entity-patterns, then axon-entity-testing}} |
+| State View | {{e.g. the \`axon-*\` skill set — axon-projection-patterns, then axon-projection-testing}} |
+| Automation | {{e.g. the \`axon-*\` skill set — axon-policy-patterns, then axon-policy-testing}} |
+| Translation | {{e.g. the \`axon-*\` skill set — axon-translation-patterns}} |
+
+An agent implementing a slice reads the doc's \`pattern:\` frontmatter and follows that row — this
+table is the only routing rule.
+
+## Code style
+
+> **What does "idiomatic" mean in this codebase — formatting, naming, module layout?**
+
+- **Formatter / linter:** {{the tool and the command that runs it — never hand-format against it}}
+- **Naming:** {{commands, events, handlers, files, test names}}
+- **Module layout:** {{what lives in which file/package, and what may not import what}}
+- **Idiomatic here means:** {{the two or three habits a new contributor most often gets wrong}}
+
+## Testing norms
+
+> **What must be tested for each slice pattern, where do those tests live, and how are they named
+> so \`em coverage\` can trace invariant IDs?**
+
+- **Levels required per pattern:** {{e.g. State Change — decider unit tests plus a
+  given/when/then fixture test; State View — projection tests; Automation / Translation —
+  reaction tests, including a negative case}}
+- **Invariant tests:** {{where they live}} — every \`INV-<MNEMONIC>-n\` in a slice doc needs at least
+  one test **citing that exact ID** in its name or a comment, so
+  \`em coverage <model>.em --tests <dir>\` can trace it.
+- **Scenario tests:** {{where they live}} — one per \`## Scenarios (Given / When / Then)\` entry,
+  with rejection scenarios asserting the doc's named rejection reason.
+- **Test naming convention:** {{the exact pattern, e.g. \`INV-ORD-3: rejects a second submit\`}}
+- **What "green" means:** {{the command CI runs}}
+
+## NFR baselines
+
+> **What standing non-functional defaults does every slice inherit — authz, PII, performance,
+> observability?**
+
+- **Authorization model:** {{who may issue which commands, how it's enforced, and where}}
+- **PII / data handling:** {{what is sensitive, what may be logged, retention}}
+- **Performance defaults:** {{latency / throughput budgets that apply unless a slice says otherwise}}
+- **Observability:** {{logging, metrics, tracing every slice is expected to emit}}
+
+A slice doc's own \`## Non-Functional Requirements\` section overrides these for that slice; where
+it is silent, these apply.
+
+## Review and merge norms
+
+> **Who reviews an implementation PR, what blocks a merge, and how does the slice doc's status
+> flip fit in?**
+
+- **Reviewers:** {{who — a team, a CODEOWNERS rule, the slice's ratifier}}
+- **What blocks a merge:** {{e.g. a failing suite, an uncovered invariant, a gap that belongs back
+  at the model}}
+- **Branch / commit conventions:** {{...}} — name only branch naming and commit-message style
+  here. **One slice doc = one PR is the implement contract's rule, not this document's to
+  amend** — a \`covers:\` doc ships as one PR for both keys; a read model is one doc, so a later
+  \`again\` instance is a continuation of the doc that first declared it, not a PR of its own. See
+  the agent guide's §5/§10.
+- **At merge:** run \`em slice mark-implemented <model>.em <slice-key> <pr-url>\` — the one edit an
+  implementing agent makes to a ratified slice doc, run by {{the PR author | CI}}. Never bump
+  \`version:\`; that moves only when a delta is ratified.
+`;
 /** Same STARTER_EM content `em init` writes, titled from an arbitrary display name — used by
  *  `em scaffold`, which (unlike `em init`) knows a name to title the model with. */
 export function starterEmFor(title) {
@@ -219,4 +340,19 @@ export function scaffoldStateFile(displayName, slugName, today) {
         .filter((line) => !line.includes("{{"))
         .join("\n");
 }
+/** Fill CONSTITUTION_TEMPLATE's project-name placeholder for `em scaffold` (MIL-202).
+ *
+ *  Unlike `scaffoldReadme`/`scaffoldStateFile`, this one **deliberately leaves every other
+ *  \`{{...}}\` block intact**: they are the unanswered questions of the elicitation conversation
+ *  the implement skill runs before the first slice ("Before the first slice: the constitution"),
+ *  not mechanical fields em could fill. An unanswered constitution must read as unanswered — the
+ *  placeholders are the todo list, and the empty `ratifiedBy:` frontmatter says it's still a
+ *  draft. Nothing in `em` ever parses this file's body; only its existence is reported
+ *  (`em status`'s `constitution` field). */
+export function scaffoldConstitution(displayName) {
+    // Replacer function, not a string pattern — a string replacement would let `$&`/`$$`/etc. in
+    // displayName expand against the match instead of being inserted literally (the CLI layer
+    // separately rejects `{{` in the name).
+    return CONSTITUTION_TEMPLATE.replace("{{Project Name}}", () => displayName);
+}
 //# sourceMappingURL=templates.js.map

package/dist/templates.js.map

@@ -1 +1 @@
-{"version":3,"file":"templates.js","sourceRoot":"","sources":["../src/templates.ts"],"names":[],"mappings":"AAAA,+BAA+B;AAC/B,mCAAmC;AAEnC,MAAM,CAAC,MAAM,UAAU,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiDzB,CAAC;AAEF,wDAAwD;AACxD,EAAE;AACF,2FAA2F;AAC3F,0FAA0F;AAC1F,2FAA2F;AAC3F,2FAA2F;AAC3F,4FAA4F;AAC5F,8FAA8F;AAC9F,oCAAoC;AAEpC,qGAAqG;AACrG,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6CpC,CAAC;AAEF,iGAAiG;AACjG,MAAM,CAAC,MAAM,cAAc,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqE7B,CAAC;AAEF;oFACoF;AACpF,MAAM,UAAU,YAAY,CAAC,KAAa;IACxC,0FAA0F;IAC1F,yFAAyF;IACzF,6FAA6F;IAC7F,OAAO,UAAU,CAAC,OAAO,CAAC,2BAA2B,EAAE,GAAG,EAAE,CAAC,UAAU,KAAK,GAAG,CAAC,CAAC;AACnF,CAAC;AAED;;;;4DAI4D;AAC5D,MAAM,UAAU,cAAc,CAAC,WAAmB,EAAE,QAAgB;IAClE,6FAA6F;IAC7F,4EAA4E;IAC5E,OAAO,qBAAqB,CAAC,OAAO,CAAC,qBAAqB,EAAE,GAAG,EAAE,CAAC,WAAW,CAAC;SAC3E,OAAO,CAAC,qBAAqB,EAAE,GAAG,EAAE,CAAC,QAAQ,CAAC;SAC9C,OAAO,CACN,oFAAoF,EACpF,yFAAyF,CAC1F,CAAC;AACN,CAAC;AAED;;;;8FAI8F;AAC9F,MAAM,UAAU,iBAAiB,CAAC,WAAmB,EAAE,QAAgB,EAAE,KAAa;IACpF,qFAAqF;IACrF,wFAAwF;IACxF,4BAA4B;IAC5B,MAAM,MAAM,GAAG,cAAc,CAAC,OAAO,CAAC,gBAAgB,EAAE,GAAG,EAAE,CAAC,WAAW,CAAC;SACvE,OAAO,CAAC,gBAAgB,EAAE,GAAG,EAAE,CAAC,QAAQ,CAAC;SACzC,OAAO,CAAC,kFAAkF,EAAE,UAAU,CAAC;SACvG,OAAO,CAAC,+DAA+D,EAAE,GAAG,CAAC;SAC7E,OAAO,CAAC,gBAAgB,EAAE,KAAK,CAAC,CAAC,8DAA8D;QAChG,oEAAoE;SACnE,OAAO,CAAC,6FAA6F,EAAE,OAAO,CAAC;SAC/G,OAAO,CAAC,2DAA2D,EAAE,OAAO,CAAC,CAAC;IAEjF,OAAO,MAAM;SACV,KAAK,CAAC,IAAI,CAAC;SACX,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC;SACtC,IAAI,CAAC,IAAI,CAAC,CAAC;AAChB,CAAC"}
+{"version":3,"file":"templates.js","sourceRoot":"","sources":["../src/templates.ts"],"names":[],"mappings":"AAAA,+BAA+B;AAC/B,mCAAmC;AAEnC,MAAM,CAAC,MAAM,UAAU,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiDzB,CAAC;AAEF,wDAAwD;AACxD,EAAE;AACF,2FAA2F;AAC3F,0FAA0F;AAC1F,2FAA2F;AAC3F,2FAA2F;AAC3F,+FAA+F;AAC/F,2FAA2F;AAC3F,2CAA2C;AAE3C,qGAAqG;AACrG,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6CpC,CAAC;AAEF,iGAAiG;AACjG,MAAM,CAAC,MAAM,cAAc,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqE7B,CAAC;AAEF;8BAC8B;AAC9B,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsHpC,CAAC;AAEF;oFACoF;AACpF,MAAM,UAAU,YAAY,CAAC,KAAa;IACxC,0FAA0F;IAC1F,yFAAyF;IACzF,6FAA6F;IAC7F,OAAO,UAAU,CAAC,OAAO,CAAC,2BAA2B,EAAE,GAAG,EAAE,CAAC,UAAU,KAAK,GAAG,CAAC,CAAC;AACnF,CAAC;AAED;;;;4DAI4D;AAC5D,MAAM,UAAU,cAAc,CAAC,WAAmB,EAAE,QAAgB;IAClE,6FAA6F;IAC7F,4EAA4E;IAC5E,OAAO,qBAAqB,CAAC,OAAO,CAAC,qBAAqB,EAAE,GAAG,EAAE,CAAC,WAAW,CAAC;SAC3E,OAAO,CAAC,qBAAqB,EAAE,GAAG,EAAE,CAAC,QAAQ,CAAC;SAC9C,OAAO,CACN,oFAAoF,EACpF,yFAAyF,CAC1F,CAAC;AACN,CAAC;AAED;;;;8FAI8F;AAC9F,MAAM,UAAU,iBAAiB,CAAC,WAAmB,EAAE,QAAgB,EAAE,KAAa;IACpF,qFAAqF;IACrF,wFAAwF;IACxF,4BAA4B;IAC5B,MAAM,MAAM,GAAG,cAAc,CAAC,OAAO,CAAC,gBAAgB,EAAE,GAAG,EAAE,CAAC,WAAW,CAAC;SACvE,OAAO,CAAC,gBAAgB,EAAE,GAAG,EAAE,CAAC,QAAQ,CAAC;SACzC,OAAO,CAAC,kFAAkF,EAAE,UAAU,CAAC;SACvG,OAAO,CAAC,+DAA+D,EAAE,GAAG,CAAC;SAC7E,OAAO,CAAC,gBAAgB,EAAE,KAAK,CAAC,CAAC,8DAA8D;QAChG,oEAAoE;SACnE,OAAO,CAAC,6FAA6F,EAAE,OAAO,CAAC;SAC/G,OAAO,CAAC,2DAA2D,EAAE,OAAO,CAAC,CAAC;IAEjF,OAAO,MAAM;SACV,KAAK,CAAC,IAAI,CAAC;SACX,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC;SACtC,IAAI,CAAC,IAAI,CAAC,CAAC;AAChB,CAAC;AAED;;;;;;;;4CAQ4C;AAC5C,MAAM,UAAU,oBAAoB,CAAC,WAAmB;IACtD,6FAA6F;IAC7F,0FAA0F;IAC1F,wCAAwC;IACxC,OAAO,qBAAqB,CAAC,OAAO,CAAC,kBAAkB,EAAE,GAAG,EAAE,CAAC,WAAW,CAAC,CAAC;AAC9E,CAAC"}

package/dist/util/localDate.d.ts

@@ -0,0 +1,2 @@
+/** `YYYY-MM-DD` for `d`'s local calendar date (default: now). Zero-pads month/day. */
+export declare function localIsoDate(d?: Date): string;

package/dist/util/localDate.js

@@ -0,0 +1,17 @@
+// SPDX-License-Identifier: MIT
+// Shared "what calendar date is it" helper for every date-defaulting command (MIL-206).
+//
+// `new Date().toISOString().slice(0, 10)` reads the UTC calendar date, not the caller's. After
+// ~17:00 in the Americas (any zone west of UTC), that's already tomorrow: someone ratifying a
+// slice at 6pm local time on the 6th got `ratifiedOn: 2026-09-07` stamped instead. Build the
+// string from the local getters instead, so the default always matches what the caller's own
+// clock and calendar say "today" is. A caller who wants UTC (or any other zone) can still pass
+// an explicit date through `--on`.
+/** `YYYY-MM-DD` for `d`'s local calendar date (default: now). Zero-pads month/day. */
+export function localIsoDate(d = new Date()) {
+    const year = d.getFullYear();
+    const month = String(d.getMonth() + 1).padStart(2, "0");
+    const day = String(d.getDate()).padStart(2, "0");
+    return `${year}-${month}-${day}`;
+}
+//# sourceMappingURL=localDate.js.map

package/dist/util/localDate.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"localDate.js","sourceRoot":"","sources":["../../src/util/localDate.ts"],"names":[],"mappings":"AAAA,+BAA+B;AAC/B,wFAAwF;AACxF,EAAE;AACF,+FAA+F;AAC/F,8FAA8F;AAC9F,6FAA6F;AAC7F,6FAA6F;AAC7F,+FAA+F;AAC/F,mCAAmC;AAEnC,sFAAsF;AACtF,MAAM,UAAU,YAAY,CAAC,IAAU,IAAI,IAAI,EAAE;IAC/C,MAAM,IAAI,GAAG,CAAC,CAAC,WAAW,EAAE,CAAC;IAC7B,MAAM,KAAK,GAAG,MAAM,CAAC,CAAC,CAAC,QAAQ,EAAE,GAAG,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,EAAE,GAAG,CAAC,CAAC;IACxD,MAAM,GAAG,GAAG,MAAM,CAAC,CAAC,CAAC,OAAO,EAAE,CAAC,CAAC,QAAQ,CAAC,CAAC,EAAE,GAAG,CAAC,CAAC;IACjD,OAAO,GAAG,IAAI,IAAI,KAAK,IAAI,GAAG,EAAE,CAAC;AACnC,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@milehimikey/em",
-  "version": "1.10.0",
+  "version": "1.12.0",
   "description": "AI-friendly Event Modeling — a slice-first text DSL rendered to a strict, self-contained Graphviz grid (SVG/PNG)",
   "type": "module",
   "bin": {