oz0 incident
For: Operators and developers looking up a command.
An incident is a tenant's record of something that went wrong. It links the jobs, audit ranges, kill switches, receipts, egress denials, findings and other incidents that tell what happened; linking a job tags it incident:<id>. Its clocks are computed from the regimes the tenant says apply (oz0 incident regimes): the built-in GDPR, NIS2, DORA and AI Act Art. 73 clocks are defaults to be confirmed, which a tenant edits.
The incident's owner and the tenant's admins are reminded before each deadline. Marking a stage notified records what you entered in OZ; it does not say that a notification was made or was enough.
Every change takes a reason (--reason, default $OZ0_REASON) and is in the audit log. The timeline export (oz0 incident export) verifies offline (oz0 incident verify). The tenant's admins may; once roles are data, incidents.read and incidents.manage (the auditor reads, the privacy officer manages).
Usage
oz0 incident [command]
Subcommands
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--tenant | string | default | the tenant |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.