Which World responsibilities still earn permanent ownership after deletion pressure?
Archive stale active-history material, delete research-only APIs, replay the same mixed failures, and retain only cross-owner reality relations whose absence recreates a current failure.
01 / Current position
A hypothesis is not the current judgment.
The dossier preserves the live research position. Dated articles preserve the complete evidence and argument that changed it.
A narrow cross-owner relation and reconciliation boundary survives while routing, network mechanics, provider truth, and physical execution remain owner-native.
Answered for the current HP0–HP8 boundary. Current retrieval improved 7/9→9/9 after historical contraction, research-only ForeignEgress/EffectPath machinery was deleted, and the same 96 mixed-failure invocations passed after deletion.
02 / Decision boundary
What keeps this Question alive?
A broad World layer can duplicate Provider, Host, Runtime, Workstation, and domain truth while also making old research easier for an Agent to mistake for current authority.
Keep the boundary demand-triggered. Reopen only when a named current workload reproduces a cross-owner failure the remaining direct owners cannot preserve cleanly.
A real remote or multi-owner workload repeatedly loses necessary observation, transfer, currentness, or consequence continuity despite Provider-native evidence plus Host, Runtime, Workstation, and domain ownership.
03 / Supporting publications
Complete arguments connected to this Question.
5 dated publications currently document this research line.
The Command Succeeded. Did Anything Happen?
A concrete guide to the boundary between local execution, external consequence, and semantic completion, using Runtime's effect kernel and Security's interrupted-consequence experiment.
12 August 2026 ↗Research reportThe Evidence Is Real. It Is Still Too Old.
Why authentic evidence can become stale without becoming false, how Security EC1 and World experiments tested current applicability, and why TTLs or generation numbers are weaker than exact dependency revalidation for the tested cases.
12 August 2026 ↗Engineering reportWorld Got Smaller—and Got Clearer
How the World HP6–HP8 survival audit treated every retained abstraction as guilty until a current workload proved its value—and why historical knowledge had to stop competing with current authority.
12 August 2026 ↗Architecture guideFrom Tokens to Work: Five Questions an Agent System Must Answer
A Feynman-style guide to Ordivon's current work trajectory: domain meaning, one Agent Run, physical execution, durable responsibility, external consequence, and current revalidation.
12 August 2026 ↗Design argumentWhy Ordivon Exists
A first-principles explanation of Ordivon: why model intelligence, durable work responsibility, physical execution, external reality, domain meaning, research, and public expression need different owners.
12 August 2026 ↗04 / Source discipline
The dossier is an index, not the evidence authority.
Owns the current judgment, next test, and deletion condition.
Own complete dated arguments, limitations, comparisons, and source links.
Own exact code, tests, releases, receipts, and machine evidence.