A transcript can explain without authorizing
A conversation is useful evidence of how a model reached a proposal. It is not, by itself, a safe database of what work remains admissible.
Core Work System Round 1 made the difference concrete. A bounded transcript summary preserved the broad story of a repository-maintenance task but omitted the pending operation identity after the backend had committed and the response was lost. A fresh process treated the operation as failed, created a new request identity, and produced a duplicate non-idempotent Effect.
A summary can preserve narrative continuity while destroying operational continuity.
The missing facts
Safe continuation required facts that prose did not reliably retain:
These facts have different owners and lifetimes. Repository revision comes from source control. Process truth comes from Runtime. External receipts come from the Provider or World. Goal and Task commitments belong to Host. A transcript may cite them, but citation does not transfer authority.
More transcript can be less safe
The full-transcript Context path also failed. It included an obsolete trusted specification, an old Tool catalog, and a plausible untrusted README that recommended removing validation. More text exposed the model to more stale and unsupported claims.
Current-revision retrieval succeeded because selection was bound to present trusted sources. Source-bound Context added explicit identity, revision, trust class, Claim status, and invalidation dependencies. The lesson is not “use less Context.” It is:
Compile Context from separately owned current state instead of treating conversation accumulation as truth accumulation.
What a transcript is good for
- preserving model rationale for later inspection;
- recovering hypotheses that can be rechecked;
- understanding failed reasoning patterns;
- providing candidate language for a fresh cognitive episode;
- retaining interaction history when its source and trust are explicit.
It should not silently decide whether an external operation may be retried, whether an approval remains current, which source revision is authoritative, or whether a Task is complete.
The thin boundary
Ordivon does not require eliminating transcripts. It requires a smaller separation:
A replacement Provider can receive a newly compiled Context and continue the same Task without inheriting the old Session. That is stronger continuity than preserving every token, because the work remains tied to current sources, current authority, and unresolved operations.
A transcript remembers what was said. A Task database preserves what may still be done.
Evidence