Which repeated physical operation deserves a dedicated structured Runtime contract?
Require stable identity, enforceable preconditions, receipts, replay/reconciliation, and ambiguity behavior before promoting another physical Tool contract.
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.
Only repeated operations with unreconstructable Runtime-owned physical facts should become structured contracts; generic execution stays effect-opaque and external consequence stays owner-native.
Open, but trigger-gated rather than under active expansion. Structured Patch and a small set of Runtime-owned lifecycle operations earned dedicated contracts; the later C1–C10 operational-realization programme did not produce a generic Effect layer, external-consequence authority, cleanup service, or semantic-completion primitive.
02 / Decision boundary
What keeps this Question alive?
Every Runtime primitive becomes a durable compatibility and recovery obligation inside the physical boundary.
Wait for repeated real use to expose one physical fact that generic execution plus owner-local evidence cannot preserve. Only then preregister the smallest structured contract against that simpler baseline.
Generic execution plus owner-local receipts/reconciliation continues to preserve the required result with less permanent Runtime machinery.
03 / Supporting publications
Complete arguments connected to this Question.
4 dated publications currently document this research line.
The Command Succeeded. Did Anything Happen?
A concrete guide to the boundary between local execution, external consequence, and semantic completion, using Runtime's effect kernel and Security's interrupted-consequence experiment.
12 August 2026 ↗Engineering reportHow Ordivon Runtime Grew Beyond Its Ten-Tool Core
How a production-tested ten-tool runtime became a thirteen-tool execution and recovery system without absorbing task meaning or external-world semantics.
12 August 2026 ↗Research reportThe Smaller Core That Survived Strong Baselines
How Core Work System Round 1 used strong classical baselines and live Codex/Hermes replacement to remove a Task Runtime, reject a generalized Context Kernel, shrink Effect, localize DecisionRequest, and retain provider-neutral Task state.
31 July 2026 ↗Research noteUNKNOWN Is an Operational State, Not a Model Feeling
Why unresolved external reality must be represented as system state rather than inferred from model confidence or collapsed into failure.
31 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.