Ordivon World
Let a Task reach and act through a changing external world without rebuilding the world beneath it.
The task-to-external-world interaction boundary. World correlates target, path, identity, transport, provider execution, authority, receipt, artifact, conditioned evidence, uncertainty, reconciliation, and rebinding while mature systems retain their native mechanisms.
- Maturity
- Experimental boundary
- Built for
- Developers connecting durable tasks to external services where delivery conditions and effect recovery must remain verifiable.
- Latest proof
- The former Link and Edge projects were unified and retired; the boundary now faces one decisive lost-response comparison against direct Host integration.
Question this project must answer
What must remain continuous when connection and external action fail together?
Working model
01Intentexternal relation
02Observationpath + provider
03Bindingidentity + authority
04Interactionnative mechanism
05EvidenceReceipt + Artifact
06Continuationreconcile + rebind
Where it stands now
Experimental boundary
Former Link and Edge histories are unified and retired as separate projects. The next decision is empirical: compare one correlated lost-response recovery path against direct Host-to-provider integration.
Capability evidence
2retired prototype boundaries
1World Interaction question
W1next decisive experiment
What this project owns
Facts it must preserve and may commit.
- World Interaction bindings
- Conditioned observations
- External evidence
- Reconciliation and rebinding
What it leaves elsewhere
Responsibilities another owner or mature system should retain.
- No universal proxy or transport
- No provider reimplementation
- No Goal, Task, or local process ownership
Questions that can still change the project