Which contracts survive a second independent workload without being tailored to one repository?
Use unrelated applications to distinguish general contracts from local accommodations.
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.
Task continuity, effect identity, evidence, and recovery contracts should survive materially different workloads through adapters rather than workload-specific core fields.
Strongly supported but not fully closed. Game implemented the immutable Host workload profile across a TypeScript deterministic World, single- and multi-Agent paths, response-loss recovery, and exact replay, then removed thirteen duplicate truth tables without changing World outcomes. A second non-Game external domain remains useful pressure.
02 / Decision boundary
What keeps this Question alive?
A contract that only explains the workload that produced it is documentation, not a computing boundary.
Apply the surviving contracts to World W1 or another non-Game provider path and record every requested exception before promoting any further shared field.
If repeated workload-specific exceptions are necessary to preserve progress, split or narrow the claimed shared contract instead of generalizing it further.
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.