What operational surface is required for durable semantic Host continuity?
Determine the smallest inspection, recovery, backup/restore, deployment, and MCP surface needed to operate Host without expanding it into an operations platform.
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 Host-local surface is sufficient when every foreign fact remains an opaque reference that its native owner revalidates.
Answered for the current 0.4.x product scope. Host now has schema-v5 Journal/CAS, full-history validation, Doctor, backup/restore, receipt-bound deployment/rollback, WorkingCheckpoint recovery, and exactly six public MCP Tools. Runtime health, source currentness, Provider state, and domain verification are intentionally not folded into Host operations.
02 / Decision boundary
What keeps this Question alive?
A correct continuity model still needs observable and recoverable product behavior, but operational convenience should not recreate deleted coordination, execution, or cross-owner truth roles.
Continue ordinary operation and product hardening. Reopen the research question only if a repeated Host-local failure cannot be diagnosed, recovered, or rolled back with the current bounded surface without importing foreign-owner truth.
A current Host-owned operational failure repeatedly requires one additional durable Host fact or operation that cannot be reconstructed from Journal/CAS plus the existing inspection/recovery surface.
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.