Skip to content
C.W.K.
Stream
Lesson 02 of 04 · published

The Transcript Is a Fold

~12 min · transcript, resume, fold

Level 0Cold Stick
0 XP0/41 lessons0/14 achievements
0/100 XP to next level100 XP to go0% complete

History Is Derived

Resume is not 'load the last messages array.' There is no parallel store of history. transcript(record, dialect) is a deterministic, dialect-parameterized fold. A crash leaves an open step, marked interrupt on load, never rewritten. One shared pre-pass runs before any dialect renders: prior thinking is downgraded to text because no dialect replays unsigned thinking natively — a silent drop would lose context the operator watched. Orphan calls get synthetic error results. Opaque attachments render only to their own dialect; a cross-dialect fold drops them and records that drop once per unique item.

Every outbound request then passes a positional call/result validator before it is recorded or transported. If the model emitted three calls, the next request has to carry three results in that order. A missing positional result is not a style bug. It is how a model starts answering the wrong call.

Resume is a refold. If you have to rewrite the file to continue, you no longer have an append-only notebook. You have an editor.

Compaction Is a Marker, Not a Rewrite

When a local window fills, a summary lands once in a content-addressed artifact. A compaction marker names the summary, the first kept sequence, and the coverage. Resume refolds as summary fragment plus the retained operator suffix. Record bytes are not deleted. A marker that cannot fit its own window or does not reduce context is ignored during refold. The trailing operator prompt is excluded from the summarizer request because feeding it lets conversational momentum hijack the summary — measured, then fixed.

Code

Resume in one sentence of code·python
def resume(record, dialect):
    return transcript(record, dialect)
# No messages.json. No 'last good snapshot.'
# An open step becomes interrupt. Nothing is rewritten.

External links

Exercise

Take a conversation you have continued after a crash. Ask whether the tool you used rewrote history or appended an interrupt. If it rewrote, write the turn that is now unprovable.
Hint
The unprovable turn is the one that was on screen and never became a line.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.