Run receipts
For: cluster operators and plugin authors.
Run receipts record the authority a job received and the calls made under it. Use the authority and call-binding pages to understand the record, then verify an exported receipt offline.
A run receipt is what Orchestrator Zero records about a job tree so that someone who was not there can check, later and offline, on whose authority each step ran, what it was allowed to do, and that it stayed inside it. The model never writes any of it: the edge records it from what passes through it.
This page grows with each part of the receipt. It starts with the authority envelope; budgets, origin checks and the kill switch's receipt add their sections.
Related tasks and reference
Previous section links
budget charges: Read the section.
calls bound to the node: Read the section.
checking them offline: Read the section.
constraints that survive every hand off: Read the section.
each hop only narrows: Read the section.
further reading: Read the section.
origins and sequences: Read the section.
what the audit log records: Read the section.