mex-statechart

1# MEX statechart
2 
3Make behavior easier for a human to understand. Generate only on user intent. If a diagram would obscure the explanation, use a better explanation. A prior agent answer identifies the subject; verify it independently against current code.
4 
51. Identify the bounded subject, reader, and implemented/proposed/agreed-model scope. Read current source and useful tests. Query `mex wiki query "<subject>" --limit 5 --json` before broad knowledge discovery; inspect matched terms and grounding health, then read live records. Fall back to Router-directed Markdown if unavailable. Use bounded `mex timeline --query "subject" --file known/path --limit 10 --json` only when history might matter. Verify historical applicability. Fresh Graph may locate evidence; call edges are not state transitions. Never refresh indexes on a read.
62. Retain context only when it changes or explains a state, event, condition, rule, exception, recovery, or abstraction. Record the precise connection and provenance. Keep source/requirement conflicts visible. Omit irrelevant context; do not manufacture a MEX contribution.
73. Read [the baseline modeling workflow](references/upstream-workflow.md) and [runtime instructions](references/toolchain.md). Preserve TLA+ and real TLC checks in normal generation. Reuse agreed rules with provenance; seek agreement only for new inferred rules or material conflicts. Never weaken a rule to get a passing result.
8…