Which remaining friction belongs above Runtime rather than becoming another primitive?
Prevent workflow and Harness convenience from expanding the trusted execution kernel.
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 new Runtime primitive is justified only when a physical fact cannot be reconstructed after interruption; workflow, Task, Harness, and provider convenience belongs in Host, adapters, or World.
Strongly supported. Repeated dogfood earned request lookup, progress, repair, lifecycle retention, and receipts. Harness H2/R2 then proved Assignment and Harness Run correlation, exact replay, fresh-client recovery, and terminal evidence using four opaque foreign references with zero new Runtime semantic objects.
02 / Decision boundary
What keeps this Question alive?
Every convenience promoted into Runtime becomes a durable compatibility and recovery obligation inside the trusted effect boundary.
Apply the unreconstructable-physical-fact test to each new friction reported by Host, Game, World, and future workloads before adding any primitive.
A repeated failure cannot be recovered, correlated, or explained without a new durable Runtime-owned physical fact.
03 / Supporting publications
Complete arguments connected to this Question.
1 dated publication 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.