Validate
Bundle integrity: VERIFIED
Policy check: PASSED
Restoring policy context, topology constraints, and proof pipeline metadata.
Validate
Route
Seal
Executes policy-admitted workloads through deterministic topology, bounded runtime, and verifiable output sealing.
/health -> OK
latency: low
status: deterministic runtime active
Live Engine Flow
Bundle - Admit - Fork - Sync - AnchorSimulation phase: Bundle admitted at policy gate
Runtime accepts valid transitions and terminates invalid branch states fail-closed.
Axis
Traditional Runtime
ADINKRA Engine
Failure semantics
Fail-open fallback under ambiguous states
Fail-closed termination on invalid transitions
Execution model
Dynamic path behavior at runtime
Topology-bound routing from approved graph
Verification model
Post-hoc logs and best-effort replay
Signed artifact with deterministic replay context
Bundle integrity: VERIFIED
Policy check: PASSED
Topology router: LOCKED
Path: ROOT -> FORK -> PATH_B
Execution state: ACTIVE
Budget used: 34%
Valid branches: 1
Rejected branches: 2
Signature: HSM VERIFIED
Trace state: COMPLETE
Same input -> same topology -> same output under the same policy boundary.
Invalid path transitions terminate immediately with controlled rejection.
Execution cannot leave the approved runtime graph boundaries.
Global step budget prevents runaway execution and uncontrolled loops.
Global Step Budget
Within Runtime LimitsGlobal Budget: 1000 steps
Used: 342
Remaining: 658
When remaining budget reaches zero, engine terminates execution fail-closed.
Shared budget limits branch expansion and enforces predictable fail-closed termination.
Branch Convergence Model
Only valid branches converge. Rejected branch states terminate before sync.
Branch convergence accepts only valid state transitions and drops invalid branches before SYNC.
Execution cannot escape defined topology boundaries. Off-map transitions are rejected before runtime state can drift.
Boundary state: ENFORCED
Execution Report Artifact
PendingExecution Report // Engine Trace v1
Deterministic execution correctness is a hard requirement.
Runtime must remain bounded under branch or load stress.
Outcome verification requires proof-oriented execution artifacts.
Use Citadel for admission and trust boundaries. Use API Reference for contract integration.