Can Host complete a general repository Goal without absorbing Runtime mechanics?
Test semantic continuity on real engineering work while preserving the Host–Runtime boundary.
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.
Host can own Goal, Task, candidate admission, Harness assignment, verification, and Outcome while Runtime exclusively owns Workspaces, Jobs, process trees, and physical evidence.
Strongly supported but still bounded. H2–H6 established continuation; Harness H1–H5 completed a frozen repository-repair workload in both Codex/Hermes replacement orders, rejected stale and missing-Artifact completion claims, recovered a dropped repair response without redispatch, and committed TaskOutcome only after independent Runtime acceptance. A broader unbounded repository Goal remains outstanding.
02 / Decision boundary
What keeps this Question alive?
Host only matters if semantic continuity survives real work; a demo loop that cannot cross restart, model replacement, and ambiguous effects does not establish a state owner.
Run one broader multi-step repository Goal with open-ended decomposition across Host restart and later Harness replacement while preserving admitted decisions, unknown-effect handling, and acceptance evidence.
If Host must copy process, Workspace, or Artifact truth to continue correctly—or loses semantic commitments when those objects remain in Runtime—the boundary is wrong.
03 / Supporting publications
Complete arguments connected to this Question.
2 dated publications currently document this research line.
A Thin Host Can Improve Strategy Without Becoming a Planner
How Station Zero M2.1 improved Codex and Codex-to-Hermes strategy by compiling trustworthy decision semantics without forcing rank one, adding unrestricted memory, or introducing a hidden planner.
31 July 2026 ↗Architecture reportWhy Task Continuity Belongs Above Execution
Why durable task continuity belongs in Ordivon Host above replaceable model sessions and Ordivon Runtime process execution.
28 July 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.