Skip to main content
The 0.14.0 milestone executes its validated graph through one local JDBC runtime. One local JVM owns a store. The application supplies its constructor-injected Steps, compatible definition and deployment dependencies; recovery does not reconstruct the deployment.

​
Commit and recover

Admission saves the root input, compatibility and finite execution policy. Before each Step, the runtime saves the exact typed invocation input and provenance. Accepted results and their continuation commit before successors execute. A native Verdict commits its complete assessment, conclusion, selected route and initial executable branch input together. Recovery reuses that route and never repeats an accepted jury evaluation. Fan-out saves an immutable ordered manifest before item execution. Equal values at different indexes have distinct invocation identities. Recovery retains committed item results and repeats only unresolved work within saved attempt/deadline allowances. It does not rediscover membership or reorder results. Reopen the compatible store and explicitly call resume; no background distributed worker service is implied.

​
Bounds and settlement

Nested supported composition can progress at physical capacity one. Parallel and fan-out allSuccessful joins require every declared result. Negative business outcomes are values; execution failures prevent a successful partial join. Admitted work settles before failure is reported. Empty fan-out returns an empty typed list. Cancellation or expiry revokes acceptance authority; it does not interrupt or roll back external application calls.

​
Limits

A crash after an external effect but before accepted result commit can repeat that effect. There is no exactly-once external-effect or power-loss guarantee. Use stable invocation identity for external idempotency where supported. Known execution failures are terminal, without an engine retry/backoff policy. Terminal failed/cancelled runs cannot be reopened; a fresh run can repeat completed effects. Store format 9 refuses earlier formats, with no migration or automatic conversion. Keep earlier stores with their compatible deployment. Rolling binaries back does not downgrade store bytes. Undeclared service/configuration behavior and external responses are not made reproducible by a build identifier. Durable loops, waits/timers, committed-event Journal projection, non-routing evaluation and broader hardening remain deferred. Companion leaf-agent and in-memory graph facilities do not acquire this durable contract. See the tutorial for actual application wiring.