Deterministic replay IS the durability mechanism: every transition re-runs a
self-contained flow program (defflow source + flow/start + replay of all
recorded resume values), so the only durable state is {:flow :input :resumes}
in persist kv — restart-safe by construction (fresh space handles over the
same backend resume mid-flight runs). fork-an-agent-run = copy the record;
the two replays diverge independently. Effects are data (suspend tags +
typed request envelopes surface as plain SX); transitions ride the Phase-3
trace buffer so session history travels with the next commit. Guest numeric
results compared with = per house convention. 43/43 (196/196 total).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
12 lines
288 B
Markdown
12 lines
288 B
Markdown
# agentic-sx Conformance Scoreboard
|
|
|
|
_Generated by `lib/agentic/conformance.sh`_
|
|
|
|
| Suite | Pass | Fail | Total |
|
|
|-------|-----:|-----:|------:|
|
|
| schema | 65 | 0 | 65 |
|
|
| branch | 53 | 0 | 53 |
|
|
| trace | 35 | 0 | 35 |
|
|
| durable | 43 | 0 | 43 |
|
|
| **Total** | **196** | **0** | **196** |
|