@milehimikey/em 1.14.0 → 1.14.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -480,6 +480,14 @@ diverges from git, grows unboundedly over a long-lived slice's life, and forces
480
480
  work out which resolutions are still relevant to the *current* version versus leftover from a
481
481
  prior one — exactly the ambiguity a live, current-version-only section avoids.
482
482
 
483
+ **Deferral marker (MIL-275).** A question this version will not answer is not left `- [ ]` and
484
+ not deleted: `em slice defer` checks it and rewrites it as `- [x] <original> — v<current>:
485
+ <decision>; deferred to v<n> (<date>[, <by>])`. The `deferred to v<n>` marker is what
486
+ `em slice reratify` reads: when a bump reaches v<n> it rewrites each such item back to
487
+ `- [ ] <original>`, so the question must be resolved or re-deferred before `--slice-ready` passes
488
+ again. The prune rule above does not apply to a deferred item before v<n> (it stays as the
489
+ record); once reopened it is an ordinary open question.
490
+
483
491
  **Not a parsing/grammar change.** `countOpenQuestions()` (`sliceDoc.ts`) and
484
492
  `slice-ready-open-questions-unchecked` (`sliceReadyValidate.ts`,
485
493
  [validation.md#slice-readiness](https://github.com/milehimikey/em/blob/main/docs/validation.md#slice-readiness)) are unaffected: both already
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: conform
3
- em-version: 1.14.0
3
+ em-version: 1.14.1
4
4
  description: >-
5
5
  Use when checking a ratified event model (and its slice docs) for drift against the codebase
6
6
  that implements it — advisory only, never a gate, never an unprompted edit — or when walking
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: design
3
- em-version: 1.14.0
3
+ em-version: 1.14.1
4
4
  description: >-
5
5
  Use when structuring a draft event model into swimlanes and the four patterns (State Change,
6
6
  State View, Automation, Translation), evaluating a model's structural completeness, or writing
@@ -212,6 +212,7 @@ For each slice:
212
212
  (`em validate` flags a block missing one as `slice-doc/structured-section-malformed`, and
213
213
  `--slice-ready` refuses it). A doc written before em 1.14 has no markers; leave it as it is
214
214
  unless you are re-creating it (`em slice new … --wire --force`, carrying the prose across).
215
+ A question this version will not answer is deferred with `em slice defer <model> <key> "<question>" --until v<n> --decision "<what this version does>"` — never left `- [ ]`, never deleted, never answered by guessing.
215
216
  2. **First-time authoring:** scaffold the doc mechanically rather than hand-writing the
216
217
  frontmatter — `em slice new "<slice name>" --pattern <state-change|state-view|automation|
217
218
  translation> --swimlane "<Persona> → <Context>" --wire <model>.em` writes `slices/<slice-name>.md`
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: discover
3
- em-version: 1.14.0
3
+ em-version: 1.14.1
4
4
  description: >-
5
5
  Use when starting a brand-new event model from scratch — greenfield discovery: brainstorming
6
6
  past-tense events, storyboarding the happy path, finding the commands and read models — or when
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: engagement
3
- em-version: 1.14.0
3
+ em-version: 1.14.1
4
4
  description: >-
5
5
  Use when leading an engagement: building a named set of ratified event-modeling slices
6
6
  (`em engagement`) into a stack of PRs by dispatching the em-implementer, em-validator,
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: event-modeling
3
- em-version: 1.14.0
3
+ em-version: 1.14.1
4
4
  description: >-
5
5
  Use when the user runs `/em:event-modeling` (with or without a phase name), or wants to resume an
6
6
  event-modeling session without specifying which part of the process applies. Reads the model's
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: implement
3
- em-version: 1.14.0
3
+ em-version: 1.14.1
4
4
  description: >-
5
5
  Use when building a single ratified event-modeling slice (status: ready-to-implement) into
6
6
  merged, tested code — the one phase where the agent builds rather than facilitates. Gates on
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: review
3
- em-version: 1.14.0
3
+ em-version: 1.14.1
4
4
  description: >-
5
5
  Use when starting em's live browser viewer (`em watch --serve`) so a team can watch a model
6
6
  update in real time, or facilitating a SCHEDULED stakeholder walkthrough that steps through
@@ -57,7 +57,7 @@ review:` marker (mirrors `Last conformance:`).
57
57
  **Per-slice outcome.** A slice whose open questions are all resolved in the room →
58
58
  `em slice review <model>.em <key> --by <name>` (flips its doc to `status: reviewed` and records
59
59
  `reviewedBy:`/`reviewedOn:`). Anything still open stays `draft` — the walkthrough doesn't decide
60
- it, the next session or the open-questions list does.
60
+ it, the next session or the open-questions list does. A question this version will not answer is deferred with `em slice defer <model> <key> "<question>" --until v<n> --decision "<what this version does>"` — never left `- [ ]`, never deleted, never answered by guessing.
61
61
 
62
62
  **The facilitator never ratifies, never offers to ratify, and never suggests ratification in a
63
63
  review session. Ratification is a separate human gate after review**