What semantic work should Host preserve when broader work continues across sessions?
Retain durable Task identity and the bounded semantic frontier without turning Host into a Goal coordinator, executor, Runtime proxy, or domain-completion authority.
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 only needs Task identity/revision, Journal/CAS admission, WorkingCheckpoint continuity, bounded handoff/inspection, and opaque owner references; broader Goal coordination and external execution can remain consumer-local.
Reframed by the 0.3 contraction. The original ‘broader Goal completion’ target was too broad: Host deliberately removed shared Goal coordination, caller-neutral foreign execution, Runtime integration residue, generic capability policy, and legacy execution workloads. Current 0.4.x preserves the semantic work claim and revalidation hints while cognition, execution, source currentness, external occurrence, and domain completion remain owner-native.
02 / Decision boundary
What keeps this Question alive?
A continuity component can preserve useful work while still becoming harmful if it silently absorbs planning, execution, currentness, or domain truth merely because those facts are convenient to resume from.
Treat the narrowed 0.4.x continuity journey as the standing answer. Reopen shared coordination only if a named cross-session workload repeatedly loses a Host-owned semantic fact that WorkingCheckpoint plus direct owner revalidation cannot preserve.
A real workload repeatedly requires Host itself to own a stable coordination or completion fact—not merely reference it—and direct consumer/owner composition cannot recover correctly with less shared machinery.
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.