canon-inspect-invocations

Inspecting Canon run invocation decisions requires a valid RUN_ID to trace request-level policy outcomes. This process exposes what Canon allowed, denied, or constrained, providing detailed context needed for compliance reviews and debugging.

You need to audit Canon run invocation outcomes when conducting compliance reviews, debugging request-level policy failures, or verifying traceability. It validates exactly what Canon allowed, denied, or constrained at the request level for a specific run.

Tracing Canon policy decisions during an audit requires a specific RUN_ID. By running canon inspect invocations --run <RUN_ID>, you retrieve the invocation decisions and outcomes necessary to ensure full traceability and compliance.

Yes, you can see what Canon denied or constrained at the request level by inspecting invocation decisions. Running canon inspect invocations --run <RUN_ID> exposes these policy outcomes for traceability and debugging.

Inspecting Canon invocations requires no external dependencies, but it does require a valid RUN_ID. The skill provides command syntax, preflight checks, and follow-up actions to help you trace invocation decisions.