Ordivon Runtime
Commit one Agent action to local reality without losing what happened.
The deterministic boundary between an agent decision and local machine execution. Runtime binds exact source and operation identity to durable jobs, process trees, bounded evidence, cancellation, reconciliation, and recovery.
- Maturity
- Production-tested local runtime
- Built for
- Developers who need reliable local execution without turning the runtime into a workflow engine or semantic task owner.
- Latest proof
- Thirteen public tools supported Host correlation, replay, fresh-client recovery, and terminal evidence with no new Runtime semantic objects.
Question this project must answer
Which execution facts cannot safely be reconstructed after interruption?
Working model
proposalnot committed
dispatchphysical boundary
evidenceretained facts
completionseparate claim
Where it stands now
Production-tested local runtime
Production Runtime remains at thirteen public tools. Host H2/R2 proved cross-layer correlation, replay, recovery, and terminal evidence through existing request identity and opaque foreign references without adding Host Task semantics to Runtime.
Capability evidence
13public tools
4opaque Host references
0new Runtime semantic objects
What this project owns
Facts it must preserve and may commit.
- Workspaces
- Jobs and Attempts
- Process trees
- Artifacts
What it leaves elsewhere
Responsibilities another owner or mature system should retain.
- Trusted-local, not a sandbox
- No Goal ownership
- No invented exactly-once claims
Questions that can still change the project