How it works · durable work trajectory22 August 2026
One piece of semantic work can outlive the model Run and process that carried it.
Ordivon does not require every project to run through one platform. When durable semantic continuity, replaceable cognition, and physical execution are all needed, Host, Harness, and Runtime can compose without turning any one of them into the owner of the caller's domain truth.
This is a supported path, not a mandatory platform pipeline. The domain begins and ends the trajectory; Host, Harness, and Runtime own different interruption-sensitive facts in the middle, and World appears only when a cross-owner relationship cannot be reconstructed safely by either endpoint alone.
01
Current boundary
A participant or application defines the work
A real goal, repository, game state, external service, budget, or human decision creates work whose meaning belongs to its domain.
02
Current boundary
Host preserves the semantic work frontier
Task identity/revision, Host Journal/CAS admission, and the current WorkingCheckpoint survive client replacement while Runtime, Git, Provider, and domain facts remain references that must be revalidated with their native owners.
03
Current boundary
Harness runs replaceable intelligence
Provides independent Journal/CAS Run authority plus Agent-selected WorkingSet cognition, caller interaction and attempt-local Tool context, request-bound action capabilities, Provider/Tool response-loss recovery, bounded cognition history, exact cross-Run source admission, and the supported HarnessAgentRun Python composition surface.
04
Current boundary
Runtime commits local physical work
Exact source and request identity become observable Jobs, process state, structured patches, Artifacts, cancellation, and reconciliation evidence.
05
Current boundary
Current consequence returns to the owner
External providers keep native truth; World preserves only the cross-owner relation when needed. The caller or domain then revalidates current applicability, accepts or rejects completion, and decides what the evidence means next.
Explore the architecture
Inspect ownership, execution, and research connections.
The explorer is a curated orientation. Exact implementation state remains in the linked repositories.
State ownership
Structure view
Three durable work boundaries, one independent research plane, and the repositories that implement or pressure them. No edge makes Computing a runtime authority, and World appears only where a cross-owner relation is needed.
8 visible nodes6 visible connectionsHover or focus to inspect
Core work system
Three boundaries preserve facts interruption makes expensive to reconstruct.
Host, Harness, and Runtime preserve different interruption-sensitive facts while leaving caller and domain authority outside the execution layers.
01tested
Host
The durable semantic Task-continuity boundary: exact Task identity/revision, Host Journal/CAS admission, WorkingCheckpoint handoff, and bounded Host-local integrity across replaceable Agent sessions.
No universal coordinator or scheduler · No model–Tool/cognition execution · No Runtime proxy or source mutation · No foreign currentness or domain-world truth
02tested
Harness
The durable cognitive execution boundary for one bounded Agent Run: canonical history, Agent-selected cognition, interaction/attempt context, request-bound action authority, Provider/Tool recovery, receipts, and completion proposals.
Preserves
Canonical bounded-Run history and immutable Run authority · Durable WorkingSet/WorkingView cognition mechanics · Interaction and attempt-local cognition reconstruction · Request-bound Harness/Tool action authority · Provider/Tool effect fencing, recovery, receipts, and CompletionProposal
Leaves elsewhere
No generic Task/domain database or final acceptance · No Runtime Workspace/Job/Attempt ownership · No semantic ranking, Memory/RAG truth, or automatic knowledge promotion · No generic Provider-opaque continuation or Mandate scheduler
03tested
Runtime
The physical execution boundary that owns durable local operation identity, process state, retained evidence, cancellation, and reconciliation.
Preserves
Workspaces · Jobs and Runtime Attempts · Process trees · Artifacts and physical recovery
Leaves elsewhere
No Task semantics · No Provider policy · No semantic completion
Research and conformance
Computing observes the trajectory; it is not another execution layer.
The research plane compares boundaries against mature alternatives, promotes only cross-project contracts with consumers, and records deletions as results.
Ractive
Computing
The research, specification, and conformance root that tests which shared contracts deserve to survive.
Owns
Shared theory · Research portfolio · Promoted protocol · Conformance evidence
Stays outside
No production Tasks · No physical Jobs · No product maturity claims
Public model
Formal objects appear only after the work trajectory is understood.
The site distinguishes current ownership, unresolved questions, and dated argument without becoming another implementation database.
Object types
boundaryCore boundary
A durable responsibility whose facts cannot safely be reconstructed by another layer.
research-planeResearch plane
A comparison, specification, and conformance role outside the execution path.
projectRepository
A product, capability carrier, or research line with its own source of truth.
questionQuestion
A falsifiable uncertainty that can change priorities, scope, or architecture.
articlePublication
A dated argument that records evidence, limitations, and the judgment at that time.
Curated connections
depends on
One owner requires capability or evidence owned by another without copying its truth.
implements
A repository realizes one tested boundary or shared contract.
explores
A project applies pressure to an active research question.
documents
A publication records the complete dated argument around a question.