oz0 incident verify

Usage and flags for oz0 incident verify.

For: Operators and developers looking up a command.

Check an incident's timeline without the cluster: the checkpoint's signature by an audit key (pin it with --key, the fingerprint oz0 audit key prints), the hash of everything else in the document, and every audit entry's hashes and links from each piece's start to its end.

A timeline exported without the content permission holds blinded entries, whose hashes cannot be checked: only the signature covers them, so it fails without --key unless --unpinned says that showing the file is whole is enough. Exit status 1 when a check fails, 2 when the file cannot be read.

Usage

oz0 incident verify FILE [flags]

Flags

FlagTypeDefaultDescription
--jsonboolprint JSON instead of a table
--keystringthe audit key's fingerprint (hex) or public key (base64) to pin
--unpinnedboolcheck a timeline with blinded entries without --key, which shows only that it is whole: whoever edited it could have signed it again

Inherited flags

FlagTypeDefaultDescription
--contextstring$OZ0_CONTEXT or <config dir>/orchestrator-zero/context.jsonCLI context file written by server init
--log-levelstringinfolog level: debug, info, warn or error
--tenantstringdefaultthe tenant

See all oz0 commands and the global flags.

On this page
Copyright © 2026