fiber

The session log is the only state of record

Fiber's predecessor kept an append-only event log and, beside it, four files derived from that log: a session manifest with token totals and a checkpoint hash, a usage ledger, a commit manifest and an authority marker. They could and did disagree — 63 sessions ended up flagged projection_invalid from stale manifests, and ask could exit with an indeterminate commit status. The same failure was found independently in another harness: of 78 official Pi extensions audited, 17 held state and 2 did it correctly, the rest keeping it in closures, live maps or a rescan on restore, which is why rewind and resume lie there.

So: the log is the only authority for what happened in a session. Anything the loop, the TUI or an extension needs to know about a session after a resume is an event or a fold of events; runtime objects may cache and index but never become a second truth. What describes no single session lives in Fiber home instead: configuration, credentials, and an extension's data directories (docs/state.md). The log is append-only for the life of the session, so a compaction appends new events rather than rewriting it, and a session directory holds no file that can contradict it. The contract is docs/events.md; the rationale and the rejected alternatives are on issue #6.

Consequences