@milehimikey/em 1.6.1 → 1.7.1

package/.claude/skills/event-modeling/reference/implement.md

@@ -0,0 +1,172 @@
+# Implementing a ratified slice
+
+The contract for the implementation half of the workflow: an agent (or engineer) turning **one
+ratified slice** into merged, verified code. The facilitation phases (`discover`/`extract` →
+`model` → `slice`) produce the inputs; this document governs consuming them. It applies to any
+implementing agent, whether or not the session started from `/event-modeling`.
+
+**The contract in one paragraph:** the slice doc is the spec — nothing between it and the code
+is a source of truth. Verify readiness mechanically before writing any code; implement exactly
+what the doc says; put every gap in front of a human instead of deciding it silently; never
+edit the ratified doc except the two lifecycle fields at merge; prove the work with tests
+traceable to the doc's invariants and scenarios.
+
+Why the rules are shaped this way: **agents propose, humans ratify.** Everything in the model
+and its slice docs is there because a human decided it on purpose — that is what makes the
+model authoritative. An implementing agent that silently patches a gap, or edits a ratified
+doc outside a session, converts the model into just another generated artifact and voids the
+whole methodology. (The full human/agent partition is `docs/process.md` in the
+[em repository](https://github.com/milehimikey/em/blob/main/docs/process.md) — not vendored
+with this skill.)
+
+## 1. Gate: verify readiness before starting
+
+```bash
+em validate <model>.em --slice-ready <slice-key>
+```
+
+`<slice-key>` is the slice's export key — the kebab-case slug of its name (`"Place Order"` →
+`place-order`). Exit 0 means: the slice has a doc bound via `note "slices/<key>.md"`, its
+frontmatter is usable, `status: ready-to-implement`, every `## Open Questions` checkbox is
+checked, and no status/version/link incoherence is flagged.
+
+**Non-zero exit means stop.** Report which checks failed and hand the slice back to the humans.
+Never make the gate pass yourself — checking an open-question box, flipping `status`, or
+editing frontmatter are ratification decisions, and ratification happens in a facilitated
+session, not in an implementation branch.
+
+## 2. Read the spec
+
+Read `slices/<slice-key>.md` end to end — every section is load-bearing:
+
+| Section | What it is to the implementer |
+|---|---|
+| frontmatter `pattern:` | Which of the four patterns' implementation shapes to build (State Change / State View / Automation / Translation) |
+| Command / Event field tables | The contracts — names, types, validation rules, immutable-fact markers |
+| `## Invariants / Business Rules` (INV-n IDs) | The non-negotiable rules; every one needs a test citing its ID |
+| `## Scenarios (Given / When / Then)` | The acceptance tests, already written — compile them, don't reinvent them |
+| `## Alternate & Error Flows` | Retries, idempotency, compensations — real requirements, not appendix |
+| `## Non-Functional Requirements` | Authz, PII, performance — implement or consciously surface, never skip |
+| `## Dependencies & Read Models Affected` | The blast radius — what else to check before and after |
+
+For timeline context, read the slice's surroundings in the `.em` (what triggers it, what
+consumes its output) — the slice's own diagram (`slices/<slice-key>.svg`) shows its canonical
+pattern shape. For machine-readable facts, use `em export <model>.em` rather than parsing the
+DSL or the doc's frontmatter yourself: it carries the slice's `pattern`, element refs, fields,
+and the joined doc metadata (`slice.doc.status`, `version`, `driftSignal`).
+
+If the project ships pattern-specific implementation skills (for example an Axon/DCB skill
+set keyed on a slice doc's `pattern:` frontmatter), route by the slice's pattern and follow
+those.
+
+## 3. Two modes: first version vs. ratified delta
+
+Check the doc's `version:` and `## Delta` section (or `em export`'s `slice.doc.driftSignal`):
+
+- **First implementation** (`version: 1`, no `## Delta`, `driftSignal: never-implemented`):
+  green-field slice implementation. Build the whole pattern shape the doc specifies.
+- **Ratified delta** (`version` > 1, `## Delta` present, `status: ready-to-implement` while
+  `implementedIn` still names the prior version's PR — `driftSignal: unpropagated-delta`):
+  this is a **change to existing, owned code**. The `## Delta` section's typed operations
+  (Added/Modified/Removed/Renamed, each with scenarios) scope the work precisely — which
+  invariants, which scenarios, which tests change. Touch what the delta names; leave the rest.
+  **Never regenerate merged code wholesale from the model** — after merge, code is owned by
+  the people who've edited it (generated-then-owned); regeneration is legal only for slices
+  whose code never merged.
+
+## 4. Gaps: propose, never decide
+
+Mid-implementation you will hit things the doc doesn't answer — a field's edge case, an
+undocumented ordering, a contradiction with adjacent code. The discipline:
+
+- **Stop that thread and surface it.** State precisely what's unspecified, the options, and
+  your recommendation. The human resolves it — at the model, where the resolution lands as an
+  answered open question or a small ratified delta alongside your fix, so the decision is
+  recorded instead of buried in an implementation diff.
+- **Never edit the ratified doc to record your own answer**, and never quietly pick a behavior
+  a business person could have an opinion on. Silent divergence is the failure mode the whole
+  conformance loop exists to catch — don't manufacture it.
+- Purely technical choices with no behavioral surface (private naming, idiomatic structure,
+  which assertion library) are yours; anything observable in behavior, data, or contract is not.
+
+## 5. Definition of done
+
+- Every `INV-n` invariant has at least one test that cites its ID.
+- Every scenario in `## Scenarios (Given / When / Then)` exists as a passing test; rejection
+  scenarios assert the doc's named rejection reason.
+- Alternate/error flows (idempotency included) are covered by tests.
+- The build and full test suite are green; the model still validates (`em validate` in CI —
+  you didn't touch the `.em`, so this only fails if something else broke).
+- Nothing between the slice doc and the code was committed as a source of truth (see §7 —
+  work containers are ephemeral; generated or symlinked specs are renderings).
+
+## 6. At merge: the lifecycle flip
+
+When the PR merges, exactly **two** frontmatter fields change on the slice doc:
+
+```yaml
+status: implemented
+implementedIn: <PR or commit URL>
+```
+
+This is supply-loop mechanics, not ratification — it's the one edit an implementing agent makes
+to a slice doc, and it's why `em ledger` deliberately excludes these two fields from what
+counts as content. **Do not bump `version:`** — versions bump only when a delta is ratified;
+a bump here is a ledger defect. In bridge-equipped projects,
+`npx -p em-sdd-bridge em-sdd-mark-implemented <slice-key> <pr-url>` does the flip for you.
+
+Then update the model's `README.md` slice index if the project keeps one, so the one canonical
+slice table reflects the new status and link. The `implementedIn` link is what the `conform`
+phase later uses to anchor drift-checking — leaving it empty blinds the loop.
+
+## 7. Spec-kit projects: the SDD adapter
+
+If the repository uses spec-kit (a `.specify/` directory exists), do not hand-author spec-kit
+artifacts — allocate through **em-sdd-bridge**, redirect mode preferred:
+
+```bash
+npx em-sdd-bridge@<pinned-version> <slice-key> --symlink
+```
+
+That allocates the feature branch and `specs/NNN-slug/` dir, runs the same readiness gates,
+and drops `spec.md` as a **symlink to the slice doc** — the slice doc itself travels through
+plan/tasks as FEATURE_SPEC. The rules that keep redirect mode safe:
+
+- **Never run `/speckit.specify`.** The ratified slice *is* the spec; an interactive specify
+  session against a defined slice creates a second, unratified source of truth.
+- **`/speckit.clarify` must never write into a slice doc.** Open questions resolve at the
+  model (that's what the readiness gate enforced); a ratified slice has nothing to clarify.
+  Projects using em-sdd-preset's overlays carry a mechanical guard for this — respect the
+  rule even where the guard isn't installed.
+- `/speckit.plan` and `/speckit.tasks` may run against the slice doc directly; the preset's
+  redirect preambles map spec-kit's section vocabulary onto the slice doc's sections.
+- **Emission fallback**: where redirect can't work (Windows checkouts without symlink
+  privileges, two-doc pattern-pair bundles, a toolchain that mutates its spec files), run the
+  bridge without `--symlink` to render `spec.md` from the slice doc. The generated file is a
+  rendering — never hand-edit it; regenerate it from the slice doc instead.
+- Everything under `specs/NNN-*/` is an **ephemeral work container** — one per change effort,
+  discardable; the PR is the durable record of the effort, the slice doc the durable
+  definition of the behavior.
+
+No spec-kit (or any SDD tool)? Implement straight from the slice doc — it already contains
+everything a spec holds. Don't introduce an intermediate spec document of your own.
+
+## 8. Never do
+
+| Rule | Because |
+|---|---|
+| Never implement from a slice that fails `--slice-ready` | The gate is the handoff contract; bypassing it hands you unratified decisions |
+| Never edit a ratified slice doc, except the two §6 fields at merge | Doc content is ratified; edits outside a session are unratified decisions |
+| Never edit the `.em` model | Model edits are ratified decisions — propose, don't write |
+| Never bump `version:` | Versions move only with ratified deltas; see `em ledger` |
+| Never silently decide unspecified behavior | Silent divergence is the disease the conformance loop exists to catch |
+| Never regenerate merged code from the model | Generated-then-owned: post-merge code belongs to its owners |
+| Never commit an authored intermediate spec | The slice is the spec; anything between it and the code is a rendering |
+
+## 9. Afterward: the loop closes
+
+Implementation isn't the end of the slice's story. On a cadence — or whenever someone asks —
+the `conform` phase checks implemented slices against the code, using the `implementedIn` link
+you recorded, and reports drift for humans to rule on (see `reference/conform.md`). Your two
+duties to that future loop are already behind you if you followed this doc: an accurate
+lifecycle flip, and zero silent decisions.

package/.claude/skills/event-modeling/reference/methodology.md

@@ -25,16 +25,16 @@ tempting shortcuts:
 - **`command → read model`** — the CQRS violation. A write is only ever visible to a reader
   through the event it recorded. Put the event between them.
 - **`read model → command`** — reads never drive a write directly. A processor or translation
-  watches the read model and issues the command, across two slices.
+  watches the read model and issues the command that sits in the same slice.
 
 If you find yourself wanting an arrow the patterns don't allow, the model is missing an
 **element**, not an arrow.
 
 **Automations and translations are not exceptions to rule 1.** They are *reactions* — a processor
 or an adapter that wakes up, decides something must change, and **issues a command** to do it. They
-never record an event themselves. A reaction box always points at a **command** (in the next
-slice), and that command produces the event. If you ever see a translation or automation wired
-straight to an event, the model is wrong.
+never record an event themselves. A reaction box always points at a **command in its own slice** —
+the same shape a `ui` already uses in State Change — and that command produces the event. If you
+ever see a translation or automation wired straight to an event, the model is wrong.
 
 Events are **immutable past-tense facts** ("Order Placed", "Payment Captured"). They are the
 spine of the model. Everything else hangs off the events.
@@ -52,8 +52,8 @@ Every slice is exactly one of these. In `em`, each maps to a specific shape (see
 **UI → Command → Event.** A user (or automation) submits a command; the system validates it
 against invariants and records one or more events.
 - **A State Change never travels alone, and it's joined at both ends.** Something must *trigger*
-  the command — the `ui` it's issued from, or (patterns 3 and 4) the reaction in the slice before
-  it — and its event needs a read model that projects it. So the unit of work is a State Change
+  the command — the `ui` it's issued from, or (patterns 3 and 4) the reaction that triggers it,
+  also in this slice — and its event needs a read model that projects it. So the unit of work is a State Change
   slice *plus* the State View slice that reads its event. Write them together; a command nothing
   points at is a write nobody can start, an unread event is a write nobody can see, and
   `em validate` warns on each.
@@ -114,16 +114,17 @@ displays. Read-only; changes no state.
   expectation?"*
 
 ### 3. Automation (Processor pattern)
-**Read Model → Processor → (next slice) Command → Event.** The system reacts on its own: a
-processor watches a read model (a "to-do list" of work) and **issues a command** — it never
-records an event directly.
-- `em` shape: **two slices**, then the read slice that consumes the event — three in all:
+**Read Model → Processor → Command → Event, the last three together in one slice.** The system
+reacts on its own: a processor watches a read model (a "to-do list" of work) and **issues a
+command** — it never records an event directly.
+- `em` shape: the read model in the slice before, then the reaction with its command and event —
+  plus the read slice that consumes the event — three slices in all:
   ```em
   slice "Todo" {
     view Todo from "..."
-    processor P
   }
-  slice "Do It" {           # the triggered command goes in the NEXT slice
+  slice "Do It" {           # processor, command, and event all share this slice
+    processor P from "Todo"
     command C
     event E @Context
   }
@@ -132,9 +133,10 @@ records an event directly.
     ui Work Board @Persona     # ...and every read model needs a consumer
   }
   ```
-  The processor band holds no event; the command in the next slice produces it. Keeping the
-  triggered command in the same slice as the processor is a validation warning — always split it.
-  Forgetting the third slice leaves `E` unread, which is also a warning.
+  The processor never records the event directly — the command it triggers does, and that event
+  happens to live in the processor's own slice now because the command does. A processor with no
+  command in its slice (and no explicit arrow to one) is a validation warning: a decision the
+  system never acts on. Forgetting the third slice leaves `E` unread, which is also a warning.
 - **Naming:** name the read model after the pending work — `Payments To Process`,
   `Orders To Fulfill`, `Pending Approvals` — never after the triggering event. The event is what
   happened; the view is what's left to do. Reusing the event's name also collides in the shared
@@ -144,10 +146,11 @@ records an event directly.
   list does the processor watch? What command does it fire? What if it fails or retries?"*
 
 ### 4. Translation
-**Boundary crossing → command → event.** An adapter translates data across a boundary (an external
-system, or another bounded context) into the model's own language. Like an automation, a
-translation is a *reaction*: it **triggers a command**, never records an event directly. Two
-independent questions shape which form it takes — don't conflate them:
+**Boundary crossing → command → event, the reaction and what it triggers together in one slice.**
+An adapter translates data across a boundary (an external system, or another bounded context) into
+the model's own language. Like an automation, a translation is a *reaction*: it **triggers a
+command**, never records an event directly. Two independent questions shape which form it takes —
+don't conflate them:
 - **Trigger source:** does the input come from outside the model, or from the model's own state
   pushed back out?
 - **Durable artifact:** is there a queryable, persisted thing behind the trigger (a queue, topic,
@@ -167,13 +170,14 @@ The `em` shape only tracks the second question — trigger source doesn't change
   it's scoped to the context/lane whose fact it represents, not by who committed it — the same
   move as an Anti-Corruption-Layer boundary event in DDD — and stays legitimate as long as it
   doesn't leak into the model's own domain vocabulary.
-- `em` shape: **two slices**, exactly like an automation, plus the read slice for the event:
+- `em` shape: exactly like an automation — the read model (durable-artifact form only) in the
+  slice before, then the reaction with its command and event, plus the read slice for the event:
   ```em
   slice "Boundary" {
     view Source from "..."     # durable-artifact form only; omit if there's nothing persisted
-    translation T from "Source"
   }
-  slice "Record It" {
+  slice "Record It" {          # translation, command, and event all share this slice
+    translation T from "Source"   # omit `from` entirely for the no-durable-artifact form
     command C
     event E @Context
   }
@@ -182,7 +186,7 @@ The `em` shape only tracks the second question — trigger source doesn't change
     ui Status Screen @Persona    # ...and every read model needs a consumer
   }
   ```
-  The translation band never carries an event.
+  The translation never records the event directly — the command it triggers does.
 - Socratic prompts: *"What boundary are we crossing, and which way? What outside system or context
   feeds us (or do we feed)? In what format? How do we know its data is trustworthy/complete? What
   internal **command** does it trigger, and what event does that command record?"*
@@ -237,9 +241,9 @@ each view to the events that feed it.
 ### Step 5 — Swimlanes & Apply the Patterns  *(model)*
 Organize elements into swimlanes: one **persona** row per actor, one **context** (bounded
 context / aggregate) row per event family. Classify every slice as one of the **4 patterns** and
-wire them correctly — especially **split both automations and translations across two slices**
-(the reaction in one, the command + event in the next). A translation or automation never records
-an event directly; it triggers a command.
+wire them correctly — especially **share the slice between every automation or translation and the
+command it triggers** (the read model it watches, if any, stays in the slice before). A translation
+or automation never records an event directly; it triggers a command.
 - Prompts: *"Which events belong together as one consistency boundary (aggregate)? Who owns this
   data? Is this slice a state change, a view, an automation, or a translation?"*
 - Output: a structurally complete model with swimlanes and pattern-correct slices.
@@ -258,8 +262,9 @@ dedicated `slice` phase writes the full rich spec (see `templates/slice.md`).
 
 ### Step 7 — Evaluate Completeness  *(model)*
 Walk the whole model with stakeholders and check for loose ends:
-- Every **command** has something that **triggers** it — a `ui` in its slice, or a reaction in the
-  slice before it. A command nothing points at is a write nobody can start. `em validate` warns.
+- Every **command** has something that **triggers** it — a `ui` in its slice, or the reaction that
+  triggers it, also in its slice. A command nothing points at is a write nobody can start.
+  `em validate` warns.
 - Every **command** produces at least one **event**.
 - Every **view** has at least one source event, **and a consumer** — a `ui` (headless: the `ui`
   tagged to the API-caller persona), or a reaction watching it. Every *instance* of a repeated
@@ -273,11 +278,13 @@ Walk the whole model with stakeholders and check for loose ends:
 - Every connection is one of the six legal pairs (`ui → command`, `command → event`,
   `event → read model`, `read model → ui`, `read model → reaction`, `reaction → command`). No
   arrow between two instances of one read model.
-- Automations **and** translations are split correctly (reaction → command → event, never a
-  reaction wired straight to an event); translations cover every external input.
-- Run `em validate` and resolve all errors and warnings. It now catches illegal `arrow` kind pairs
-  (error) and unread events (warning), but it still does **not** catch a translation/automation that
-  emits an event directly — verify the two-slice split by hand.
+- Automations **and** translations are wired correctly (reaction → command → event, all in one
+  slice — never a reaction wired straight to an event, and never a reaction with no command at
+  all); translations cover every external input.
+- Run `em validate` and resolve all errors and warnings. It catches illegal `arrow` kind pairs
+  (error), unread events (warning), and a reaction with no command in its slice (warning) — a
+  reaction wired straight to an event with no command anywhere is exactly what that last check
+  catches, so a clean `em validate` run does cover this case.
 - Prompts: *"Is there any event nobody reads — and if the business genuinely never looks at it, why
   are we recording it? Any command that just happens, with nobody and nothing asking for it? Any
   screen with no way in or out? Any command that records nothing? Any

package/.claude/skills/event-modeling/templates/conformance-report.md

@@ -16,11 +16,15 @@ Replace bracketed placeholders; delete guidance comments before finishing.
 
 ## Summary
 
-| Surface | Real drift | Model gap | Internal inconsistency | Accepted divergence | Uncertainty |
-|---|---|---|---|---|---|
-| Structural | {{n}} | {{n}} | — | {{n}} | {{n}} |
-| Spec | {{n}} | {{n}} | — | {{n}} | {{n}} |
-| Internal | — | — | {{n}} | {{n}} | {{n}} |
+| Surface | Real drift | Model gap | Internal inconsistency | Accepted divergence | Unpropagated delta | Uncertainty |
+|---|---|---|---|---|---|---|
+| Structural | {{n}} | {{n}} | — | {{n}} | {{n}} | {{n}} |
+| Spec | {{n}} | {{n}} | — | {{n}} | {{n}} | {{n}} |
+| Internal | — | — | {{n}} | {{n}} | — | {{n}} |
+
+**Unpropagated delta** — a slice re-ratified past its shipped version (`slice.doc.driftSignal:
+"unpropagated-delta"` in `em export --json`): a known state, not a code defect. See
+`reference/conform.md` step 4.
 
 {{One or two sentences: overall read — clean, mostly clean with N items, or notably drifted.}}
 
@@ -32,15 +36,17 @@ Replace bracketed placeholders; delete guidance comments before finishing.
 ### {{n}}. {{Short finding title}}
 
 - **Surface:** {{structural | spec | internal}}
-- **Classification:** {{real drift | model gap | internal inconsistency | accepted divergence}}
+- **Classification:** {{real drift | model gap | internal inconsistency | accepted divergence | unpropagated delta}}
 - **Slice:** {{slice name}}
 - **Evidence:** {{file path(s) and line/symbol, or the `em diff --json` entry (type + name) —
-  for accepted divergence, the `divergence "..."` annotation text itself}}
+  for accepted divergence, the `divergence "..."` annotation text itself; for unpropagated
+  delta, `slice.doc.driftSignal` and `slice.doc.version` from `em export --json`}}
 - **Claim:** {{what the model/doc says vs. what the code/doc shows — the actual disagreement}}
 - **Proposed red note:** `issue "conformance: {{text}}"` on {{element}} (slice "{{slice}}")
   <!-- Omit this line entirely for internal-inconsistency findings with no clear side to flag,
-       for any accepted-divergence finding (already ratified — don't propose re-ratifying it),
-       or when the finding doesn't warrant a red note (say why instead). -->
+       for any accepted-divergence or unpropagated-delta finding (already ratified, or already
+       a known pending-ship state — don't propose re-ratifying either), or when the finding
+       doesn't warrant a red note (say why instead). -->
 
 ## Scenario / invariant coverage
 

package/.claude/skills/event-modeling/templates/model-readme.md

@@ -18,14 +18,14 @@ Static render: `em render {{model-name}}.em -o {{model-name}}.svg`
 ## Patterns legend
 - **State Change** — UI → Command → Event
 - **State View** — Event(s) → Read Model → UI
-- **Automation** — Read Model → Processor → (next slice) Command → Event
-- **Translation** — External input (or Read Model) → Translation → (next slice) Command → Event
+- **Automation** — Read Model (slice before) → Processor + Command → Event, together
+- **Translation** — External input (or Read Model, slice before) → Translation + Command → Event, together
 
 Between them these are the only legal connections: `ui → command`, `command → event`,
 `event → read model`, `read model → ui`, `read model → reaction`, `reaction → command`. A command
 never reaches a read model directly — the event goes between them. Every slice is joined up at
-both ends: something triggers each command (the screen it's issued from, or the reaction in the
-slice before it), and every event a command records is read by some read model — so each State
+both ends: something triggers each command (the screen it's issued from, or the reaction that
+triggers it, also in this slice), and every event a command records is read by some read model — so each State
 Change slice is paired with the State View slice that projects its event. A read model repeated
 along the timeline (`view X again`) shows the same projection at a later point; the instances are
 never connected to one another.
@@ -34,9 +34,9 @@ never connected to one another.
 <!-- The canonical slice index — the ONE place slices are enumerated (the state file
      points here rather than keeping its own copy). Keep it in sync as slice docs are
      written and as statuses move. -->
-| # | Slice | Pattern | Status | Design doc |
-|---|-------|---------|--------|------------|
-| 1 | {{Slice Name}} | {{Pattern}} | {{none / draft / reviewed / ready-to-implement / implemented}} | [slices/{{slice-name}}.md](slices/{{slice-name}}.md) |
+| # | Slice | Pattern | Status | Implemented in | Design doc |
+|---|-------|---------|--------|----------------|------------|
+| 1 | {{Slice Name}} | {{Pattern}} | {{no doc yet / draft / reviewed / ready-to-implement / implemented}} | {{PR/commit link once implemented, else —}} | [slices/{{slice-name}}.md](slices/{{slice-name}}.md) |
 
 ## Status
 See [`.event-modeling.md`](.event-modeling.md) for current phase, decisions, and open questions.

package/.claude/skills/event-modeling/templates/slice.md

@@ -4,18 +4,84 @@ linked from the .em model with:  note "slices/<slice-name>.md"  on the slice's d
 Fill every section through Socratic questioning. Leave "Open Questions" rather than guessing.
 Replace the bracketed placeholders; delete guidance comments before finishing.
 
+The frontmatter below is the canonical, machine-read metadata dialect — `em`'s own parser
+(src/catalog/sliceDoc.ts) reads `status:`, `version:`, `pattern:`, and the lineage keys
+(`split-from:`/`merged-from:`/`superseded-by:`) from it. `pattern` is kebab-case
+(state-change/state-view/automation/translation) even though the skill's prose always says
+"State Change"/"State View"/etc. — the frontmatter value is a machine key, not a display label.
+Older docs using a `- **Status:** ...` bullet line instead of frontmatter still parse (legacy/
+accepted input), but new docs should always use this frontmatter form; `version` and lineage
+have no legacy form — frontmatter-only from day one.
+
+`version` is this slice's own ratified-content version — starts at `1`, bumps when a delta is
+ratified — distinct from `schemaVersion`, which versions the frontmatter dialect itself, not
+this slice. When a ratified change lands on an already-`implemented` slice: bump `version`,
+flip `status` back to `ready-to-implement` (it tracks the CURRENT version's implementation
+state — `implementedIn` legitimately keeps naming the PRIOR version's PR until the new version
+ships; that mismatch is an intended drift signal, not a bug), and fill in the `## Delta` section
+below with this hop's change, replacing whatever it held before (it always shows only the latest
+hop — full history lives in git, same-commit-ratification convention). Full grammar — the fixed
+heading, the four operation subsections, why the heading never varies, the replace-not-accumulate
+lifecycle — is documented in docs/slice-doc-schema.md#delta-section-grammar-and-lifecycle; treat
+it the same Socratic way as every other section here, don't generate it mechanically.
+
+The three lineage keys only apply when this doc was produced by a split, merge, or rename —
+delete them otherwise; most slices never carry them. Grammar: `<slice-key>@v<N>`, where
+`<slice-key>` is the referenced slice's kebab-case filename stem.
+
+Full machine schema — required-vs-optional keys per `status`, value types/enums, the
+unknown-key policy — is documented in docs/slice-doc-schema.md.
+
 The diagram below is generated, not hand-drawn: `em render <model>.em --slice "{{Slice Name}}"
 -o slices/{{slice-name}}.svg` (kebab-case the slice name to match this doc's own filename).
 -->
 
+---
+schemaVersion: 1
+pattern: {{state-change | state-view | automation | translation}}
+swimlane: {{Persona/Actor}} → {{Context/Aggregate}}
+status: {{draft | reviewed | ready-to-implement | implemented}}
+version: 1
+implementedIn: {{PR/commit link — fill in once status is `implemented`}}
+# Lineage — only when this doc exists because of a split, merge, or rename (delete these three
+# lines otherwise). Grammar: <slice-key>@v<N>. See
+# docs/slice-doc-schema.md#lineage-grammar-and-cardinality.
+# split-from: <slice-key>@v<N>
+# merged-from: <slice-key>@v<N>, <slice-key>@v<N>
+# superseded-by: <slice-key>@v<N>, <slice-key>@v<N>
+---
 # Slice: {{Slice Name}}
 
 ![Diagram](./{{slice-name}}.svg)
 
-- **Pattern:** {{State Change | State View | Automation | Translation}}
-- **Swimlane:** {{Persona/Actor}} → {{Context/Aggregate}}
-- **Status:** {{draft | reviewed | ready-to-implement | implemented}}
-- **Implemented in:** {{PR/commit link — fill in once status is `implemented`}}
+<!-- Only on re-ratification of an already-`implemented` slice — omit this whole section on a
+     slice's first version (v1 has no delta yet). The heading is always the literal `## Delta`,
+     never `## Delta: vX → vY` — hop metadata is a display line inside the section instead (see
+     docs/slice-doc-schema.md#delta-section-grammar-and-lifecycle for why). Replace this
+     section's content wholesale on the next re-ratification — it shows only the latest hop, not
+     an accumulating log. Omit any of the four subsections below with no entries this hop; keep
+     the remaining ones in this order (Added/Modified/Removed/Renamed). `Renamed` is for a
+     requirement/invariant renamed within this slice, not a substitute for the frontmatter
+     `split-from`/`merged-from`/`superseded-by` lineage keys above, which record the slice-doc
+     itself splitting, merging, or being renamed. -->
+## Delta
+**v{{X}} → v{{Y}}, ratified {{date}}** — {{one-line summary of the ratified change}}
+
+### Added
+#### Requirement: {{title}} ({{stable ID, e.g. an INV-n from Invariants below}})
+{{requirement text — same voice as an Invariants entry}}
+##### Scenario: {{name}}
+- **GIVEN** {{...}} **WHEN** {{...}} **THEN** {{...}}
+
+### Modified
+<!-- Same shape as Added — the stable ID names the requirement that changed. -->
+
+### Removed
+#### Requirement: {{title}} ({{stable ID}})
+{{why it was removed}}
+
+### Renamed
+- {{old title}} ({{old ID}}) → {{new title}} ({{new ID}})
 
 ## Intent
 {{Why this slice exists — the user or business goal it serves, in one or two sentences. Note the
@@ -30,7 +96,7 @@ an event directly.}}
 
 ## Command / Input
 <!-- For State Change, and the command half of an Automation or Translation (reactions trigger a
-     command in the next slice). Omit for pure State View slices. -->
+     command in this same slice). Omit for pure State View slices. -->
 **Command:** `{{Command Name}}`
 
 | Field | Type | Required | Rules / Validation |
@@ -40,8 +106,8 @@ an event directly.}}
 ## Trigger
 <!-- What issues this slice's command. Required: a command nothing points at is a write nobody
      can start. Either the screen the user acts on (a `ui` in this slice), or the reaction that
-     issues it (an automation/processor/translation in the PREVIOUS slice). -->
-**Triggered by:** {{screen `X` @Persona | processor `Y` in slice "Z"}}
+     issues it (an automation/processor/translation, also in this slice). -->
+**Triggered by:** {{screen `X` @Persona | processor `Y`, also in this slice}}
 
 ## Event(s) Emitted
 <!-- The immutable facts recorded. List each event and its payload. -->

package/.claude/skills/event-modeling/templates/state.md

@@ -7,7 +7,7 @@ Keep it current at the end of every working session.
 # Event Modeling Progress — {{Model Name}}
 
 - **Model file:** `{{model-name}}.em`
-- **Current phase:** {{extract | discover | model | slice}}
+- **Current phase:** {{discover | extract | model | slice | implement | conform | review | validate}}
 - **Current step:** {{1–7, see methodology; or extraction round R1–R7}}
 - **Last updated:** {{YYYY-MM-DD}}
 - **Last conformance:** {{YYYY-MM-DD @ <target-repo revision> — report: conformance/<date>-report.md | never}}
@@ -30,7 +30,7 @@ Keep it current at the end of every working session.
 - [ ] R2. Timeline order (as-is narrative, actors/callers, first render)
 - [ ] R3. Commands / inputs
 - [ ] R4. Read models / outputs (validate from here)
-- [ ] R5. Boundaries & reactions (two-slice splits)
+- [ ] R5. Boundaries & reactions (reaction shares its slice with the command it triggers)
 - [ ] R6. Gap & TBD reconciliation
 - [ ] R7. Convergence (render + validate clean, user confirmed as-is)
 
@@ -50,10 +50,11 @@ Keep it current at the end of every working session.
 
 ## Usage log
 <!-- The team's only usage signal today (see docs/usage-data.md) — cheap and coarse on purpose.
-     One line per session: phase(s) touched, and validate diagnostic *categories* hit (the rule
-     name from docs/validation.md's tables, e.g. "read model nothing consumes" — never the full
-     instance message or any domain content). Append, never edit past entries. -->
-- {{YYYY-MM-DD}}: phases: {{discover | extract | model | slice | conform | review | validate | watch, ...}} — validate: {{diagnostic category (docs/usage-data.md#categories), ... | none}}
+     One line per session: phase(s) touched, and validate diagnostic *categories* hit (one of
+     the exact fixed strings in docs/usage-data.md#categories, e.g. "read model has no
+     consumer" — never the full instance message or any domain content). Append, never edit
+     past entries. -->
+- {{YYYY-MM-DD}}: phases: {{discover | extract | model | slice | implement | conform | review | validate | watch, ...}} — validate: {{diagnostic category (docs/usage-data.md#categories), ... | none}}
 
 ## Open questions / parking lot
 <!-- Unresolved items to bring back to the user. Never guess these. Metadata is optional and

package/README.md

@@ -84,6 +84,7 @@ built this way.
 |---|---|
 | [docs/tutorial.md](docs/tutorial.md) | Learn the tool by building a model from scratch |
 | [docs/workflow.md](docs/workflow.md) | The model lifecycle: specify, gate, hand off, track change, detect drift |
+| [docs/process.md](docs/process.md) | Who does what: where humans are required, where agents work with review |
 | [docs/patterns.md](docs/patterns.md) | The four Event Modeling patterns and their DSL shapes |
 | [docs/dsl.md](docs/dsl.md) | Full DSL reference: keywords, `from`, `again`, fields, notes |
 | [docs/cli.md](docs/cli.md) | Every command and flag |

package/dist/catalog/build.d.ts

@@ -1,5 +1,6 @@
 import { NormalizedModel } from "../model/model.js";
 import { Grid } from "../layout/grid.js";
+import { RefsResult } from "../model/refs.js";
 import { Diagnostic } from "../model/validate.js";
 export interface CatalogModelInput {
     /** The .em file as given on the command line — used for the doc-discovery path and display. */
@@ -7,6 +8,10 @@ export interface CatalogModelInput {
     model: NormalizedModel;
     grid: Grid;
     dot: string;
+    /** Already-computed by the same `compile()` call that produced `model`/`grid` (MIL-91) —
+     *  never recomputed here, so its ref-collision diagnostics (already in `compile()`'s own
+     *  `diagnostics`) aren't emitted a second time. */
+    refs: RefsResult;
 }
 export interface CatalogOptions {
     outDir: string;

package/dist/catalog/build.js

@@ -15,7 +15,6 @@ import { copyFile, mkdir, writeFile } from "node:fs/promises";
 import { basename, dirname, extname, join } from "node:path";
 import { layoutDot, composeSvg, writeRendered } from "../render/render.js";
 import { buildSliceDiagram } from "../render/sliceDiagram.js";
-import { computeRefs } from "../emit/json.js";
 import { dedupe, kebabSlug } from "../util/slug.js";
 import { classifySlicePattern } from "./classify.js";
 import { parseSliceDoc } from "./sliceDoc.js";
@@ -29,7 +28,7 @@ export async function buildCatalog(inputs, opts) {
     const modelSummaries = [];
     const diagnostics = [];
     let sliceCount = 0;
-    for (const { file, model, grid, dot } of inputs) {
+    for (const { file, model, grid, dot, refs } of inputs) {
         const modelKey = dedupe(kebabSlug(basename(file, extname(file))), usedModelKeys, "~");
         const modelDir = join(outDir, modelKey);
         const slicesDir = join(modelDir, "slices");
@@ -40,7 +39,6 @@ export async function buildCatalog(inputs, opts) {
         const raw = await layoutDot(dot);
         const mainSvg = composeSvg(raw, model, grid, dirname(file), modelDir);
         await writeRendered(mainSvg, join(modelDir, diagramFile), format);
-        const refs = computeRefs(model);
         if (refs.diagnostics.length > 0)
             diagnostics.push({ file, diagnostics: refs.diagnostics });
         const sliceSummaries = [];

package/dist/catalog/build.js.map

@@ -1 +1 @@
-{"version":3,"file":"build.js","sourceRoot":"","sources":["../../src/catalog/build.ts"],"names":[],"mappings":"AAAA,+BAA+B;AAC/B,kEAAkE;AAClE,0EAA0E;AAC1E,4EAA4E;AAC5E,EAAE;AACF,cAAc;AACd,iBAAiB;AACjB,mBAAmB;AACnB,8BAA8B;AAC9B,gBAAgB;AAChB,2BAA2B;AAC3B,2FAA2F;AAE3F,OAAO,EAAE,UAAU,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AACnD,OAAO,EAAE,QAAQ,EAAE,KAAK,EAAE,SAAS,EAAE,MAAM,kBAAkB,CAAC;AAC9D,OAAO,EAAE,QAAQ,EAAE,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAG7D,OAAO,EAAE,SAAS,EAAE,UAAU,EAAE,aAAa,EAAE,MAAM,qBAAqB,CAAC;AAC3E,OAAO,EAAE,iBAAiB,EAAE,MAAM,2BAA2B,CAAC;AAC9D,OAAO,EAAE,WAAW,EAAE,MAAM,iBAAiB,CAAC;AAE9C,OAAO,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,iBAAiB,CAAC;AACpD,OAAO,EAAE,oBAAoB,EAAE,MAAM,eAAe,CAAC;AACrD,OAAO,EAAE,aAAa,EAAE,MAAM,eAAe,CAAC;AAC9C,OAAO,EAAE,eAAe,EAAE,eAAe,EAA4C,MAAM,YAAY,CAAC;AA+BxG,MAAM,CAAC,KAAK,UAAU,YAAY,CAChC,MAA2B,EAC3B,IAAoB;IAEpB,MAAM,MAAM,GAAG,IAAI,CAAC,MAAM,IAAI,KAAK,CAAC;IACpC,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,IAAI,qBAAqB,CAAC;IAClD,MAAM,MAAM,GAAG,IAAI,CAAC,MAAM,CAAC;IAE3B,MAAM,KAAK,CAAC,MAAM,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;IAEzC,MAAM,aAAa,GAAG,IAAI,GAAG,EAAU,CAAC;IACxC,MAAM,cAAc,GAA0B,EAAE,CAAC;IACjD,MAAM,WAAW,GAAkD,EAAE,CAAC;IACtE,IAAI,UAAU,GAAG,CAAC,CAAC;IAEnB,KAAK,MAAM,EAAE,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE,GAAG,EAAE,IAAI,MAAM,EAAE,CAAC;QAChD,MAAM,QAAQ,GAAG,MAAM,CAAC,SAAS,CAAC,QAAQ,CAAC,IAAI,EAAE,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,aAAa,EAAE,GAAG,CAAC,CAAC;QACtF,MAAM,QAAQ,GAAG,IAAI,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC;QACxC,MAAM,SAAS,GAAG,IAAI,CAAC,QAAQ,EAAE,QAAQ,CAAC,CAAC;QAC3C,MAAM,KAAK,CAAC,SAAS,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;QAE5C,MAAM,WAAW,GAAG,WAAW,MAAM,EAAE,CAAC;QACxC,mFAAmF;QACnF,sFAAsF;QACtF,MAAM,GAAG,GAAG,MAAM,SAAS,CAAC,GAAG,CAAC,CAAC;QACjC,MAAM,OAAO,GAAG,UAAU,CAAC,GAAG,EAAE,KAAK,EAAE,IAAI,EAAE,OAAO,CAAC,IAAI,CAAC,EAAE,QAAQ,CAAC,CAAC;QACtE,MAAM,aAAa,CAAC,OAAO,EAAE,IAAI,CAAC,QAAQ,EAAE,WAAW,CAAC,EAAE,MAAM,CAAC,CAAC;QAElE,MAAM,IAAI,GAAG,WAAW,CAAC,KAAK,CAAC,CAAC;QAChC,IAAI,IAAI,CAAC,WAAW,CAAC,MAAM,GAAG,CAAC;YAAE,WAAW,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,WAAW,EAAE,IAAI,CAAC,WAAW,EAAE,CAAC,CAAC;QAC3F,MAAM,cAAc,GAA0B,EAAE,CAAC;QAEjD,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,KAAK,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE,CAAC;YAC7C,MAAM,KAAK,GAAG,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC;YAC9B,MAAM,QAAQ,GAAG,IAAI,CAAC,SAAS,CAAC,CAAC,CAAC,CAAC;YACnC,MAAM,OAAO,GAAG,oBAAoB,CAAC,KAAK,CAAC,CAAC;YAE5C,mFAAmF;YACnF,oFAAoF;YACpF,mFAAmF;YACnF,sFAAsF;YACtF,qFAAqF;YACrF,6EAA6E;YAC7E,MAAM,UAAU,GAAG,IAAI,CAAC,QAAQ,EAAE,GAAG,QAAQ,KAAK,CAAC,CAAC;YACpD,MAAM,OAAO,GAAG,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,EAAE,UAAU,CAAC,CAAC;YAChD,MAAM,GAAG,GAAG,UAAU,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC,aAAa,CAAC,YAAY,CAAC,OAAO,EAAE,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC;YAEtF,8EAA8E;YAC9E,+EAA+E;YAC/E,0EAA0E;YAC1E,0EAA0E;YAC1E,8DAA8D;YAC9D,MAAM,eAAe,GAAG,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,EAAE,QAAQ,EAAE,GAAG,QAAQ,MAAM,CAAC,CAAC;YACzE,MAAM,gBAAgB,GAAG,GAAG,QAAQ,MAAM,CAAC;YAC3C,IAAI,UAAU,CAAC,eAAe,CAAC,EAAE,CAAC;gBAChC,MAAM,QAAQ,CAAC,eAAe,EAAE,IAAI,CAAC,SAAS,EAAE,gBAAgB,CAAC,CAAC,CAAC;YACrE,CAAC;iBAAM,CAAC;gBACN,+EAA+E;gBAC/E,8EAA8E;gBAC9E,6EAA6E;gBAC7E,8EAA8E;gBAC9E,4EAA4E;gBAC5E,sEAAsE;gBACtE,MAAM,EAAE,KAAK,EAAE,UAAU,EAAE,IAAI,EAAE,SAAS,EAAE,GAAG,EAAE,QAAQ,EAAE,GAAG,iBAAiB,CAAC,KAAK,EAAE,CAAC,EAAE;oBACxF,cAAc,EAAE,IAAI,CAAC,cAAc;iBACpC,CAAC,CAAC;gBACH,MAAM,QAAQ,GAAG,MAAM,SAAS,CAAC,QAAQ,CAAC,CAAC;gBAC3C,MAAM,QAAQ,GAAG,UAAU,CAAC,QAAQ,EAAE,UAAU,EAAE,SAAS,EAAE,OAAO,CAAC,IAAI,CAAC,EAAE,SAAS,CAAC,CAAC;gBACvF,MAAM,SAAS,CAAC,IAAI,CAAC,SAAS,EAAE,gBAAgB,CAAC,EAAE,QAAQ,EAAE,MAAM,CAAC,CAAC;YACvE,CAAC;YAED,MAAM,WAAW,GAAG,IAAI,GAAG,EAAkB,CAAC;YAC9C,KAAK,MAAM,EAAE,IAAI,KAAK,CAAC,QAAQ,EAAE,CAAC;gBAChC,MAAM,GAAG,GAAG,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,EAAE,CAAC,EAAE,CAAC,CAAC;gBACpC,IAAI,GAAG;oBAAE,WAAW,CAAC,GAAG,CAAC,EAAE,CAAC,EAAE,EAAE,GAAG,CAAC,CAAC;YACvC,CAAC;YAED,MAAM,IAAI,GAAG,eAAe,CAAC;gBAC3B,SAAS,EAAE,KAAK,CAAC,IAAI;gBACrB,WAAW,EAAE,MAAM,WAAW,EAAE;gBAChC,gBAAgB;gBAChB,KAAK;gBACL,QAAQ;gBACR,OAAO;gBACP,WAAW;gBACX,GAAG;gBACH,eAAe,EAAE,UAAU;aAC5B,CAAC,CAAC;YACH,MAAM,SAAS,CAAC,IAAI,CAAC,SAAS,EAAE,GAAG,QAAQ,OAAO,CAAC,EAAE,IAAI,EAAE,MAAM,CAAC,CAAC;YAEnE,cAAc,CAAC,IAAI,CAAC;gBAClB,GAAG,EAAE,QAAQ;gBACb,IAAI,EAAE,KAAK,CAAC,IAAI;gBAChB,OAAO;gBACP,MAAM,EAAE,GAAG,KAAK,IAAI;gBACpB,MAAM,EAAE,GAAG,EAAE,MAAM,IAAI,IAAI;aAC5B,CAAC,CAAC;YACH,UAAU,EAAE,CAAC;QACf,CAAC;QAED,cAAc,CAAC,IAAI,CAAC,EAAE,GAAG,EAAE,QAAQ,EAAE,IAAI,EAAE,KAAK,CAAC,IAAI,EAAE,IAAI,EAAE,WAAW,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC,CAAC;IACtG,CAAC;IAED,MAAM,SAAS,GAAG,eAAe,CAAC,cAAc,EAAE,KAAK,EAAE,MAAM,CAAC,CAAC;IACjE,MAAM,SAAS,CAAC,IAAI,CAAC,MAAM,EAAE,YAAY,CAAC,EAAE,SAAS,EAAE,MAAM,CAAC,CAAC;IAE/D,OAAO,EAAE,MAAM,EAAE,cAAc,CAAC,MAAM,EAAE,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,CAAC;AAC5E,CAAC"}
+{"version":3,"file":"build.js","sourceRoot":"","sources":["../../src/catalog/build.ts"],"names":[],"mappings":"AAAA,+BAA+B;AAC/B,kEAAkE;AAClE,0EAA0E;AAC1E,4EAA4E;AAC5E,EAAE;AACF,cAAc;AACd,iBAAiB;AACjB,mBAAmB;AACnB,8BAA8B;AAC9B,gBAAgB;AAChB,2BAA2B;AAC3B,2FAA2F;AAE3F,OAAO,EAAE,UAAU,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AACnD,OAAO,EAAE,QAAQ,EAAE,KAAK,EAAE,SAAS,EAAE,MAAM,kBAAkB,CAAC;AAC9D,OAAO,EAAE,QAAQ,EAAE,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAG7D,OAAO,EAAE,SAAS,EAAE,UAAU,EAAE,aAAa,EAAE,MAAM,qBAAqB,CAAC;AAC3E,OAAO,EAAE,iBAAiB,EAAE,MAAM,2BAA2B,CAAC;AAG9D,OAAO,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,iBAAiB,CAAC;AACpD,OAAO,EAAE,oBAAoB,EAAE,MAAM,eAAe,CAAC;AACrD,OAAO,EAAE,aAAa,EAAE,MAAM,eAAe,CAAC;AAC9C,OAAO,EAAE,eAAe,EAAE,eAAe,EAA4C,MAAM,YAAY,CAAC;AAmCxG,MAAM,CAAC,KAAK,UAAU,YAAY,CAChC,MAA2B,EAC3B,IAAoB;IAEpB,MAAM,MAAM,GAAG,IAAI,CAAC,MAAM,IAAI,KAAK,CAAC;IACpC,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,IAAI,qBAAqB,CAAC;IAClD,MAAM,MAAM,GAAG,IAAI,CAAC,MAAM,CAAC;IAE3B,MAAM,KAAK,CAAC,MAAM,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;IAEzC,MAAM,aAAa,GAAG,IAAI,GAAG,EAAU,CAAC;IACxC,MAAM,cAAc,GAA0B,EAAE,CAAC;IACjD,MAAM,WAAW,GAAkD,EAAE,CAAC;IACtE,IAAI,UAAU,GAAG,CAAC,CAAC;IAEnB,KAAK,MAAM,EAAE,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,MAAM,EAAE,CAAC;QACtD,MAAM,QAAQ,GAAG,MAAM,CAAC,SAAS,CAAC,QAAQ,CAAC,IAAI,EAAE,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,aAAa,EAAE,GAAG,CAAC,CAAC;QACtF,MAAM,QAAQ,GAAG,IAAI,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC;QACxC,MAAM,SAAS,GAAG,IAAI,CAAC,QAAQ,EAAE,QAAQ,CAAC,CAAC;QAC3C,MAAM,KAAK,CAAC,SAAS,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;QAE5C,MAAM,WAAW,GAAG,WAAW,MAAM,EAAE,CAAC;QACxC,mFAAmF;QACnF,sFAAsF;QACtF,MAAM,GAAG,GAAG,MAAM,SAAS,CAAC,GAAG,CAAC,CAAC;QACjC,MAAM,OAAO,GAAG,UAAU,CAAC,GAAG,EAAE,KAAK,EAAE,IAAI,EAAE,OAAO,CAAC,IAAI,CAAC,EAAE,QAAQ,CAAC,CAAC;QACtE,MAAM,aAAa,CAAC,OAAO,EAAE,IAAI,CAAC,QAAQ,EAAE,WAAW,CAAC,EAAE,MAAM,CAAC,CAAC;QAElE,IAAI,IAAI,CAAC,WAAW,CAAC,MAAM,GAAG,CAAC;YAAE,WAAW,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,WAAW,EAAE,IAAI,CAAC,WAAW,EAAE,CAAC,CAAC;QAC3F,MAAM,cAAc,GAA0B,EAAE,CAAC;QAEjD,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,KAAK,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE,CAAC;YAC7C,MAAM,KAAK,GAAG,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC;YAC9B,MAAM,QAAQ,GAAG,IAAI,CAAC,SAAS,CAAC,CAAC,CAAC,CAAC;YACnC,MAAM,OAAO,GAAG,oBAAoB,CAAC,KAAK,CAAC,CAAC;YAE5C,mFAAmF;YACnF,oFAAoF;YACpF,mFAAmF;YACnF,sFAAsF;YACtF,qFAAqF;YACrF,6EAA6E;YAC7E,MAAM,UAAU,GAAG,IAAI,CAAC,QAAQ,EAAE,GAAG,QAAQ,KAAK,CAAC,CAAC;YACpD,MAAM,OAAO,GAAG,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,EAAE,UAAU,CAAC,CAAC;YAChD,MAAM,GAAG,GAAG,UAAU,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC,aAAa,CAAC,YAAY,CAAC,OAAO,EAAE,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC;YAEtF,8EAA8E;YAC9E,+EAA+E;YAC/E,0EAA0E;YAC1E,0EAA0E;YAC1E,8DAA8D;YAC9D,MAAM,eAAe,GAAG,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,EAAE,QAAQ,EAAE,GAAG,QAAQ,MAAM,CAAC,CAAC;YACzE,MAAM,gBAAgB,GAAG,GAAG,QAAQ,MAAM,CAAC;YAC3C,IAAI,UAAU,CAAC,eAAe,CAAC,EAAE,CAAC;gBAChC,MAAM,QAAQ,CAAC,eAAe,EAAE,IAAI,CAAC,SAAS,EAAE,gBAAgB,CAAC,CAAC,CAAC;YACrE,CAAC;iBAAM,CAAC;gBACN,+EAA+E;gBAC/E,8EAA8E;gBAC9E,6EAA6E;gBAC7E,8EAA8E;gBAC9E,4EAA4E;gBAC5E,sEAAsE;gBACtE,MAAM,EAAE,KAAK,EAAE,UAAU,EAAE,IAAI,EAAE,SAAS,EAAE,GAAG,EAAE,QAAQ,EAAE,GAAG,iBAAiB,CAAC,KAAK,EAAE,CAAC,EAAE;oBACxF,cAAc,EAAE,IAAI,CAAC,cAAc;iBACpC,CAAC,CAAC;gBACH,MAAM,QAAQ,GAAG,MAAM,SAAS,CAAC,QAAQ,CAAC,CAAC;gBAC3C,MAAM,QAAQ,GAAG,UAAU,CAAC,QAAQ,EAAE,UAAU,EAAE,SAAS,EAAE,OAAO,CAAC,IAAI,CAAC,EAAE,SAAS,CAAC,CAAC;gBACvF,MAAM,SAAS,CAAC,IAAI,CAAC,SAAS,EAAE,gBAAgB,CAAC,EAAE,QAAQ,EAAE,MAAM,CAAC,CAAC;YACvE,CAAC;YAED,MAAM,WAAW,GAAG,IAAI,GAAG,EAAkB,CAAC;YAC9C,KAAK,MAAM,EAAE,IAAI,KAAK,CAAC,QAAQ,EAAE,CAAC;gBAChC,MAAM,GAAG,GAAG,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,EAAE,CAAC,EAAE,CAAC,CAAC;gBACpC,IAAI,GAAG;oBAAE,WAAW,CAAC,GAAG,CAAC,EAAE,CAAC,EAAE,EAAE,GAAG,CAAC,CAAC;YACvC,CAAC;YAED,MAAM,IAAI,GAAG,eAAe,CAAC;gBAC3B,SAAS,EAAE,KAAK,CAAC,IAAI;gBACrB,WAAW,EAAE,MAAM,WAAW,EAAE;gBAChC,gBAAgB;gBAChB,KAAK;gBACL,QAAQ;gBACR,OAAO;gBACP,WAAW;gBACX,GAAG;gBACH,eAAe,EAAE,UAAU;aAC5B,CAAC,CAAC;YACH,MAAM,SAAS,CAAC,IAAI,CAAC,SAAS,EAAE,GAAG,QAAQ,OAAO,CAAC,EAAE,IAAI,EAAE,MAAM,CAAC,CAAC;YAEnE,cAAc,CAAC,IAAI,CAAC;gBAClB,GAAG,EAAE,QAAQ;gBACb,IAAI,EAAE,KAAK,CAAC,IAAI;gBAChB,OAAO;gBACP,MAAM,EAAE,GAAG,KAAK,IAAI;gBACpB,MAAM,EAAE,GAAG,EAAE,MAAM,IAAI,IAAI;aAC5B,CAAC,CAAC;YACH,UAAU,EAAE,CAAC;QACf,CAAC;QAED,cAAc,CAAC,IAAI,CAAC,EAAE,GAAG,EAAE,QAAQ,EAAE,IAAI,EAAE,KAAK,CAAC,IAAI,EAAE,IAAI,EAAE,WAAW,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC,CAAC;IACtG,CAAC;IAED,MAAM,SAAS,GAAG,eAAe,CAAC,cAAc,EAAE,KAAK,EAAE,MAAM,CAAC,CAAC;IACjE,MAAM,SAAS,CAAC,IAAI,CAAC,MAAM,EAAE,YAAY,CAAC,EAAE,SAAS,EAAE,MAAM,CAAC,CAAC;IAE/D,OAAO,EAAE,MAAM,EAAE,cAAc,CAAC,MAAM,EAAE,MAAM,EAAE,UAAU,EAAE,WAAW,EAAE,CAAC;AAC5E,CAAC"}