Run event stream

Automax records run events in SQLite and mirrors them to an append-only JSONL stream beside the run state database:

.automax/runs/<run-id>/events.jsonl

Each line is a standalone JSON object with a stable schema identifier:

{
  "schema": "automax.event.v1",
  "sequence": 1,
  "run_id": "20260601-120000-abcdef",
  "timestamp": "2026-06-01 12:00:00",
  "event_type": "job_started",
  "node_id": null,
  "target": null,
  "payload": {
    "job": "deploy"
  }
}

The stream is designed for release evidence, CI summaries, dashboards and audit collectors that need a simple append-only contract without coupling to the internal SQLite schema.

Export events

Use automax runs events to print or write the event stream for a stored run:

automax runs events RUN_ID --state-dir .automax/runs
automax runs events RUN_ID --state-dir .automax/runs --format=json
automax runs events RUN_ID --state-dir .automax/runs --output dist/events.jsonl

The JSONL output is the preferred integration format. JSON output is useful for local inspection and tests.

Evidence bundles

automax runs bundle includes the event stream in two forms:

events/events.jsonl
events/events.json

Both files use the same redaction policy as stored run state. Event payloads must not contain raw secret values.

Existing runs

For runs created before events.jsonl existed, automax runs events reconstructs the stream from the SQLite events table. New runs append events to the JSONL stream as they are recorded.