Which Harness objects survive live Provider replacement without duplicating Host or Runtime state?
Preserve Provider-faithful execution while retaining only shared Run facts required for recovery and completion.
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.
Assignment, Run receipt, Tool-step evidence, recovery, and completion proposal survive while Provider Sessions remain local.
Answered by H1–H5 and later extraction. The durable Run boundary survived Codex and Hermes replacement; a universal Provider lifecycle did not.
02 / Decision boundary
What keeps this Question alive?
A shared Harness can erase Provider capabilities or create another Task database; direct adapters can duplicate Run evidence and recovery.
Keep Provider lifecycles native and pressure only the current Harness public boundary through new adapters and workloads.
Direct Provider integrations remain equally correct with less repeated code, or the shared boundary destroys material Provider capability.
03 / Supporting publications
Complete arguments connected to this Question.
3 dated publications currently document this research line.
The Model Finished. The Protocol Wasn't Done.
How a second native Provider forced Ordivon Harness to separate model-visible semantic history from Provider-required opaque continuation state, and why only one new primitive survived a five-frontier productization test.
12 August 2026 ↗Research reportWhat Survived When Codex and Hermes Replaced Each Other Mid-Task
How one task remained coherent through Codex→Hermes and Hermes→Codex replacement, three injected faults, and materially different provider lifecycles.
4 August 2026 ↗Architecture decisionWhy Ordivon Needs a Harness—but Not a Universal Harness
Why H5 correctly rejected a common Codex/Hermes lifecycle while a separate Ordivon Harness remains strategically necessary for bare model APIs, local inference, and controlled agent-loop research.
4 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.