Which Agent-native responsibilities remain after strong classical baselines?
Use mature workflow, retrieval, idempotency, and provider systems to delete any shared abstraction that does not own a distinct failure.
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 meaning belongs in Host, physical execution truth in Runtime, and correlated external interaction may belong in World; durable workflow mechanics, generalized Context state, and provider-specific lifecycle can remain in mature systems or owning applications.
Answered within the Round 1 boundary. LangGraph and Temporal carried durable work state; current-revision retrieval matched the tested Context need; single-backend Effect machinery shrank to identity, UNKNOWN, correlation, reconciliation, and no blind redispatch; live provider replacement preserved Task state without proving model equivalence.
02 / Decision boundary
What keeps this Question alive?
A proposed core becomes permanent inheritance. It should contain only responsibilities that survive strong alternatives, multiple workloads, cost measurement, and a deletion test.
Use the result as an admission test in World W1 and Harness H4–H5. Reopen the shared-core boundary only when a materially different workload exposes an unowned non-bypassable responsibility.
A future workload repeatedly fails because a stable responsibility cannot remain in Host, Runtime, World, a mature workflow engine, or a provider-faithful adapter.
03 / Supporting publications
Complete arguments connected to this Question.
3 dated publications currently document this research line.
Creation, Judgment, and Recoverable Systems
The canonical public statement of Ordivon's project intent: creation, capability externalization, judgment, changing implementation costs, low governance, high recoverability, and participant freedom.
31 July 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 noteA Transcript Is Not a Task Database
Why transcripts and summaries remain useful cognitive evidence but should not become the authoritative database of durable agent work.
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.