Ordivon Runtime
Commit one admitted operation to local reality without losing what happened.
The physical authority for admitted local execution. Runtime proves what the machine executed, retained, observed, reclaimed, and can safely replay; it does not decide what that execution means for the Task, Provider, or external domain.
- Projected status
- Operational owner-trusted local infrastructure; public interface remains pre-1.0 and Windows-native is experimental opt-in
- For
- Builders who need Agent actions, source commitments, physical effects, retained evidence, and lifecycle transitions to remain identifiable and recoverable without turning the executor into Task or domain authority.
- Evidence for status
- The C1–C10 operational-realization programme saturated its current evidence horizon without reopening Runtime Foundations: currentness, consequential retry, evidence scope, identity/lineage, authority/binding, lifecycle retention, and reclamation remained separable. Current production also exposes workspace.content for digest-bound pixel observation, runtime.describe for capability/ceiling discovery, and workspace.execBound on Linux plus configured limited windows_native targets; the latest fixes preserve fresh remote source currentness, reclaim lifecycle contracts, and terminal observation time instead of guessing after the fact.
Question this project must answer
Which physical execution facts cannot safely be reconstructed after interruption?
One recovery property
communication discontinuity · execution continuity
The response can disappear.
The work does not have to.
Runtime gives one admitted operation a durable identity. If delivery becomes uncertain, a later client can recover the recorded Job instead of treating silence as permission to create new work.
Client A
exact requestrequest ↔ job ↔ attemptRecorded independently of the response channel.
Delivery is now uncertain.
Client B
same request identityNo blind replay merely because the first response vanished.
Boundary: this is execution recovery, not a claim that every external effect is idempotent or that Runtime decides semantic Task completion.
Current operating model
Standing in this projection
Operational owner-trusted local infrastructure; public interface remains pre-1.0 and Windows-native is experimental opt-in
Operational for owner-trusted Linux engineering work with an experimental configured Windows-native backend. Exact execution, immutable inputs, observation, cancellation, recovery, lifecycle/reclamation, and bounded evidence are current capabilities. Hostile multi-tenant isolation, arbitrary external-effect truth, and semantic Task completion remain outside Runtime.
Capability evidence
What this project owns
Facts, products, or methods maintained here.
- Workspaces
- Jobs and Runtime Attempts
- Process trees
- Artifacts and physical recovery
What it leaves elsewhere
Responsibilities and claims outside its boundary.
- No Task semantics
- No Provider policy
- No semantic completion
Questions and current judgments