Run data formats
| Format | Role | Specification |
|---|---|---|
| Events | Recorded HTTP-first event format | RFC-0002 |
| Storyline | Internal normalized Run and tool-call model | RFC-0001 § Wire schema |
| ACTF | JSON Run interchange | RFC-0004 § JSON Pointer mapping |
| ATIF | Agent Run interchange | RFC-0008 § JSON Pointer mapping |
| OpenAI Messages | Row-based training and evaluation corpus | RFC-0009 § JSON Pointer mapping |
| Codex | Local Codex CLI/TUI session JSONL (~/.codex/sessions/**/rollout-*.jsonl). Decode-only. | — |
| Claude Code | Local Claude Code transcript JSONL (~/.claude/projects/**/*.jsonl). Decode-only. | — |
| AgenticMD | Human-readable live and materialized view | AgenticMD reference |
Recorded events and reconstructed projections have different fidelity and ownership. See Run storage design before choosing a format as a persistence boundary.
Each format RFC is authoritative for that format's wire contract and its mapping to Storyline. Mapping tables elsewhere are non-normative.