What operational surface is required before Host becomes installable rather than architectural proof?
Identify the minimum inspect, service, backup, and recovery surface earned by real use.
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 small inspect surface, service lifecycle, append-only journal backup, and explicit recovery report will be sufficient; a general operations platform is unnecessary.
Open. The journal, recovery model, operator handoff, and Harness receipts exist, but long-lived installation and operator recovery have not yet established the minimum public surface.
02 / Decision boundary
What keeps this Question alive?
A correct state model that cannot be inspected, restarted, backed up, or recovered remains a laboratory artifact rather than a dependable Host.
Run Host as a persistent service through routine restart, backup, restore, and one deliberately interrupted Task.
If the current journal plus ordinary service tooling already makes every required state observable and recoverable, do not add a separate operations layer.
03 / Supporting publications
Complete arguments connected to this Question.
0 dated publications currently document this research line.
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.