A useful answer.
A source you can inspect.

ACGS is a family of components for different governance jobs. gove-zone checks receipts at an integrated execution boundary. ACGS-Lite adds Python policy checks and wrappers. Swarm coordinates agents; Agent Bus exposes messaging and workflow services. Choose the component whose contract matches your integration.

A receipt records a policy decision bound to a request and its context. The governed executor must verify it against the actual call before execution. A receipt alone does not establish that an external action succeeded, that every host tool was mediated, or that a deployment is compliant.

The inspected gove-zone single-action executor requires trusted signature verification by default. Issuing a signed receipt still needs an explicit signer, and the executor needs the matching trusted verifier. A missing verifier prevents execution. Unsigned development mode is an explicit opt-out.

Stateless receipt verification does not consume a receipt. One-time use requires the configured ReceiptConsumptionLedger to be shared by every relevant executor. Design the storage and failure behavior for the operating environment; receipt consumption is not proof of exactly-once external effects.

A hash chain can reveal internal edits, but a shortened prefix may remain internally consistent. Detecting tail removal requires an independently protected event count, head hash, or checkpoint. Storage access, retention, and external anchoring are separate controls. Lite also requires explicit full audit configuration for chain evidence.

DENY and ESCALATE receipts are non-executable. An escalation is a recorded stop, not a fourth kind of permission. A later approval must use the documented integration and fresh executable authorization; the original escalation receipt cannot simply become an execution grant.

The source documents an optional static signing-key-ID revocation list on supported runtime and offline verification paths. That is narrower than a managed identity or key-lifecycle service. Follow the security model for the exact surface you use, including key custody and update distribution.

No. The bus’s default message endpoint accepts work for processing. The validate_and_route mode also returns HTTP 202, with its governance result in the response body. Read that contract explicitly; a transport status is not a gove-zone execution receipt.

Review the exact artifact, integration scope, current tests, identity, trusted keys, storage, and operational dependencies. A source version and a green selected test suite answer different questions. The evidence index records known failed and missing checks without presenting them as production assurance.