Skip to main content

Module journal

Module journal 

Source
Expand description

The run journal: the audit record of one conversation with a forge.

It answers, after the fact and from another session, what ran, with what arguments, against what, and what came back. Per run: meta.json, events.jsonl, transcript.txt, and the materialized scripts — removed on clean completion, kept on failure. Retention is bounded: a run count cap enforced at the start of each new run, oldest pruned first. The journal is audit evidence and never resumable state.

Structs§

Journal
One open journal.
Meta
The meta.json document.
ScriptRecord
One materialized script, proven by digest.
SecretHandling
How a secret was handled: the fact of the handling, never the value and never a fingerprint of one.

Constants§

META_SCHEMA
The version of the meta.json shape.
RUNS_KEPT
How many runs the journal root keeps; run N+1 prunes the oldest.

Functions§

list_run_ids
Every run directory name, oldest first. The id opens with the UTC timestamp, so lexical order is age order.
prune_to
Remove the oldest runs past keep; the count removed.
runs_root
The journal root: <state root>/runs.