Conformance
Normative: MODEL.md §12.
An implementation is conformant when it reproduces the scenarios below — the arbiter of MODEL.md §2–§16. Both implementations encode this list as their test suite:
| suite | run | |
|---|---|---|
| TypeScript | ts/packages/core/test | cd ts && pnpm test |
| .NET | dotnet/test/Ilmek.Core.Tests | cd dotnet && dotnet test Ilmek.sln |
The non-negotiable scenarios
| # | Scenario | Spec |
|---|---|---|
| 1 | step executes once across an interrupt/resume cycle | §5, §6 |
| 2 | Two interrupts in one node resolve independently, one resume each | §6 |
| 3 | An interrupt inside a loop with stable keys resumes at the right iteration | §5.4, §6 |
| 4 | Superstep reduce order is task order, not completion order | §2, §4 |
| 5 | A crash mid-superstep replays it with zero re-executed steps | §4, §5 |
| 6 | compile(spec) → toSpec() round-trips | §9 |
| 7 | Strict mode raises when a journaled step key vanishes on replay | §5.5 |
| 8 | Concurrent pauses resolve to their own answers; a bare answer to >1 pending is refused | §6.1 |
| 9 | A send fan-out runs the target once per payload, each with its own input; results reduce independent of scheduling | §14 |
| 10 | A node's command({goto}) overrides its static edges; command({update}) reduces before the goto is planned | §15 |
| 11 | A retried node re-runs its body but not its completed steps | §16 |
Why scenario 8 exists
The engine once shipped this bug: two nodes pausing in the same superstep each
journal interrupt#0, so answers keyed by key collapsed to one entry and both
nodes received the same answer. Nothing raised. A conformance list is worth
exactly the failures it has caught — this is the one that earned the
id vs key rule.
Companion fixtures
Some behavior is pure data in, data out. For that, both languages read one shared
fixture under conformance/
and must produce the same result:
| Fixture | Pins |
|---|---|
conformance/viz | Mermaid export (MODEL.md §9.1). Each case is a spec plus code-only extras (routers, hand-written guards) and options. The rendered text must match <case>.mmd byte for byte, both from the compiled graph and, when the case has no code, from the spec. |
conformance/skills | The SKILL.md reader: parsed skills and the level-1 prompt. |
conformance/mcp | The MCP toolbox: tool naming, result normalization, prompts as skills. |
conformance/a2a | The A2A client: how a task reduces to a result. |
Status
Green against the list in both languages: TypeScript and .NET. See the capability matrix in the repository for the current per-feature breakdown across the two ports.