Which remaining friction belongs above Runtime rather than becoming another primitive?
Prevent semantic convenience, environment closure, external-effect policy, or cleanup pressure from expanding physical execution authority without a reproduced unreconstructable fact.
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.
Most remaining friction belongs with Harness, Host, Workstation, providers, package managers, or domain owners; Runtime should retain only irreducible physical execution, evidence, and lifecycle facts.
Answered for the current P0–P5, HP0, and C1–C10 evidence horizon. Storage pressure produced an owner/retention correction rather than a generic cleanup service, and later operational-realization pressure kept currentness, retry, evidence scope, identity, authority, retention, and reclamation separable without reopening Runtime Foundations.
02 / Decision boundary
What keeps this Question alive?
Every Runtime primitive becomes permanent compatibility, recovery, and release debt inside the physical authority boundary.
Keep the graduated boundary closed. Reopen only on a new physical falsifier: a repeated current operation that cannot be recovered, replayed, observed, or explained without one additional Runtime-owned fact under a materially different workload or execution target.
A repeated current failure survives owner-local repair and cannot be represented with existing Workspace/Job/Attempt/process/Artifact/source/lifecycle evidence without adding a new durable Runtime fact.
03 / Supporting publications
Complete arguments connected to this Question.
4 dated publications currently document this research line.
Correctness Is Not Isolation
How Finance C2-L separated effect correctness from credential and administrator isolation, falsified hostile-root isolation on one machine, and retained a disabled single-machine effect-correctness profile without authorizing live trading.
12 August 2026 ↗Engineering recordWe Deleted 16.8 GB. Not Because It Was Old.
Runtime HP0-C as a storage-authority experiment: why age, size, repository activity, and reconstructibility are insufficient deletion rules, and how current consumption relationships determined a safe 16.8 GB production reclaim.
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 ↗Engineering reportHow Ordivon Runtime Grew Beyond Its Ten-Tool Core
How a production-tested ten-tool runtime became a thirteen-tool execution and recovery system without absorbing task meaning or external-world semantics.
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.