oz0 receipt

Usage and flags for oz0 receipt.

For: Operators and developers looking up a command.

A kill switch, a revoked grant, a removed plugin, a revoked API key or a person who lost their last path to start jobs records a revocation; revocations that land together are one batch, one step of the tenant's authority epoch.

The edges refuse every call of a job the batch reaches, an edge stops exactly those jobs, and the batch ends in a receipt: per carrier (each stopped job, waiting approvals, routines, start sites, remote sessions, model calls at each edge, streams, deliveries in flight) its final state, closed, parked, refused_at_fence or indeterminate with the reason. Management signs it with the audit key (oz0 audit key). Reading receipts is the audit trail's permission: a tenant's admins.

Usage

oz0 receipt [command]

Subcommands

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

See all oz0 commands and the global flags.

Copyright © 2026