II.
Topic overview
Reference · livetopic:agent-journal
Agent Journal overview
Agent Journal as a cross-cutting topic - the append-only event log that tracks run state for agent orchestration. Journal events include RUN_CREATED, EFFECT_REQUESTED, EFFECT_RESOLVED, RUN_COMPLETED, and RUN_FAILED. The journal enables deterministic replay (rebuilding run state from the event stream), recovery after interruption (resuming from the last resolved effect), and audit trails for compliance. The state cache is derived data from the journal; if it drifts, run:rebuild-state reconstructs it. Malformed entries can be repaired via run:repair-journal.
Attributes
displayName
Agent Journal
description
Agent Journal as a cross-cutting topic - the append-only event log that
tracks run state for agent orchestration. Journal events include
RUN_CREATED, EFFECT_REQUESTED, EFFECT_RESOLVED, RUN_COMPLETED, and
RUN_FAILED. The journal enables deterministic replay (rebuilding run state
from the event stream), recovery after interruption (resuming from the
last resolved effect), and audit trails for compliance. The state cache
is derived data from the journal; if it drifts, run:rebuild-state
reconstructs it. Malformed entries can be repaired via
run:repair-journal.
Outgoing edges
applies_to1
- domain:software-engineering·DomainSoftware Engineering
Incoming edges
contains1
- domain:software-engineering·DomainSoftware Engineering