Expand description
Session transcripts.
One JSONL file per run: a header line describing the session, then one line
per message. Append-only, so a crashed run still leaves a readable
transcript, and mecha sessions resume can pick it back up.
Structs§
- RunConfig
- What a run was configured with, recorded so it can be replayed.
- RunStats
- How a run went, in numbers a machine can compare across sessions.
- Session
- Session
Meta - Taint
Timeline - Where each taint checkpoint sits relative to the messages — built by
Session::taint_timeline, consumed by provenance classification inlearning.