ORDIVON
Menu

System · durable work trajectory1 August 2026

One task can outlive the model, process, and path that carried it.

Ordivon separates task meaning, model-run cognition, local execution, and external consequences so each can be replaced or recovered without forcing another layer to invent what happened.

Read the complete execution stackSee the replacement experiment
provider-replacement orders completed
2 / 2
injected faults contained
3
production Runtime tools
13
next external recovery comparison
W1

End-to-end trajectory

The work moves; ownership does not blur.

This is the reader-facing path through the stack. Formal objects and curated architecture views follow after the consequence of each boundary is clear.

  1. 01
    Tested boundary

    Host admits the work

    The user goal, task, accepted decisions, and unresolved commitments become durable above one conversation.

  2. 02
    Tested boundary

    A harness runs replaceable intelligence

    Codex, Hermes, or a future bare-model loop can reason and use tools without becoming the owner of the task.

  3. 03
    Tested boundary

    Runtime commits local work

    Exact source and operation identity become observable jobs, process state, artifacts, cancellation, and recovery evidence.

  4. 04
    Next decisive test

    World correlates external consequences

    Paths, identities, provider requests, receipts, observations, and uncertainty remain connected when the outside environment changes.

  5. 05
    Tested boundary

    Evidence changes the frontier

    Host accepts completion or keeps the task open; Computing uses the same trajectory to retain, narrow, or delete the shared contract.

Explore the architecture

Inspect ownership, execution, and research connections.

The explorer is a curated technical view of the same trajectory—not a second source of implementation truth.

State ownership

Structure view

A curated view of three consequence boundaries, one research plane, and the repositories that implement them. This is an architecture map, not a second fact store.
8 visible nodes7 visible connectionsHover or focus to inspect

Durable boundaries

Three consequence boundaries preserve facts that interruption makes expensive to reconstruct.

Host owns task meaning, Runtime owns local execution evidence, and World tests the external consequence boundary.

01tested

Host

The semantic control boundary that keeps Goals and Tasks continuous above replaceable sessions and processes.

Preserves
Goals and Tasks · Host journal · Cognition contexts · Outcomes
Leaves elsewhere
No process ownership · No model monopoly · No Runtime mechanics
02tested

Runtime

The physical effect boundary that owns durable local execution identity, process state, and retained evidence.

Preserves
Workspaces · Jobs and Attempts · Process trees · Artifacts
Leaves elsewhere
Trusted-local, not a sandbox · No Goal ownership · No invented exactly-once claims
03experimental

World

The experimental continuity boundary for paths, identities, authority, provider actions, receipts, and external uncertainty.

Preserves
World Interaction bindings · Conditioned observations · External evidence · Reconciliation and rebinding
Leaves elsewhere
No universal proxy or transport · No provider reimplementation · No Goal, Task, or local process ownership

Research and conformance

Computing observes the trajectory; it is not another execution layer.

The research plane compares boundaries against mature alternatives, preserves shared contracts, and deletes abstractions that fail their admission test.

Ractive

Computing

The research and conformance plane that tests which shared contracts deserve to survive.

Owns
Stack model · Semantic contracts · Reference experiments · Conformance
Stays outside
No production Tasks · No physical Jobs · No place in the execution path

Formal public model

Technical objects appear only after the work trajectory is understood.

The site distinguishes stable ownership, current uncertainty, and dated argument without publishing every experiment, finding, decision, and relation as another mutable object.

Object types

boundaryConsequence boundary

A durable responsibility that preserves task meaning or execution evidence.

research-planeResearch plane

A comparison and conformance role outside the execution path.

projectRepository

An implementation or research line with its own source of truth.

questionQuestion

A falsifiable uncertainty that can change priorities or boundaries.

articlePublication

A complete dated argument with evidence links, limits, and the next test.

Curated connections

depends on

One state owner or project requires facts or capabilities owned by another.

implements

A repository realizes a stable responsibility or shared contract.

explores

A project applies pressure to an active research question.

documents

A publication records the complete argument around a question.