Skip to main content
Version: v5.8.0

opschain governance activity

Included from Basic tier

opschain governance activity --from <t> [--to <t>] [--scope <node path>] [--out <file>]

Exports the governed activity over a window (GovernanceService. ListGovernedActivity) as NDJSON — one JSON document per line, oldest first: every change run with the external references its steps reported and the settings document versions it read (settings_read), and every break-glass record with its evidence, and every attested step with its answer under attestation in the StepAttestation shape (id, run_id, step_id, step_path, outcome, principal_id, answered_at, title, activity, command, where, evidence_class, evidence (the BreakglassEvidence keys), note, outputs, correlation_id; empty fields omitted), each with its node path, principal id (never a username), evidence class, chain and window. The document shape is opschain docs resources/governed_activity. Estate-wide unless --scope narrows it to a node's subtree; on a server, rows you cannot read never appear.

On the local lane the export is the home's own record, and every line carries the home's identity (home_id, minted once per home): import the file on a server with opschain governance activity import <file> and its break-glass records reach the server's reviewers, each landing once (see opschain docs cli/governance-activity-import).

Flags​

FlagMeaning
--from <t>The window's start, an RFC3339 time. Required.
--to <t>The window's end, an RFC3339 time (default now). At most 366 days.
--scope <node path>Only activity on this node and its subtree.
--out <file>Write the NDJSON to this file (mode 0600) instead of stdout; the count goes to stderr.

Exit codes​

CodeMeaning
0Exported (possibly nothing).
1The server refused or is unreachable, or --out could not be written.
2Usage error — no --from, a bad time, a window over 366 days.

Examples​

opschain governance activity --from 2026-11-01T00:00:00Z --out november.ndjson
wrote 412 governed activities to november.ndjson