Bind permission to the call
Receipts bind actor, tenant, action, exact arguments, and policy evidence. A mismatched or expired receipt is rejected at the governed executor.
EXECUTION KERNEL
Evaluate a proposed tool call, record the decision, and verify its receipt before execution. Add gove-zone at the point where your application calls a tool.
For engineers integrating agent tools, custom executors, and CI gates.
WHERE IT FITS
Use this when a specific side effect must pass a policy and receipt check before the registered function runs.
Supply an actor, tenant, tool, and exact arguments.
Evaluate policy and append audit evidence before issuing a receipt.
The governed executor checks the receipt before invoking the registered tool.
INSIDE THE PRODUCT
Follow each behavior to its implementation or maintained documentation.
Receipts bind actor, tenant, action, exact arguments, and policy evidence. A mismatched or expired receipt is rejected at the governed executor.
Policy failures deny the request. Failure to append required audit evidence prevents a completed governed execution path.
Keep hash-chained JSONL audit records and verify their integrity. Re-deriving a decision also requires retained inputs and the original policy.
Python, MCP, runtime-hook, and CI examples have documented coverage. SDK patterns and roadmap integrations carry separate labels.
LOCAL EVALUATION
From a Python 3.11+ environment, using the published 1.0.0rc2 pre-release on PyPI.
Install Python 3.11+, then install the published gove-zone package. Installation requires network access.
Run gove-zone doctor to confirm the package imports and the local audit path is writable.
Request evaluation access at evaluation@acgs.ai for the receipt-gated execution guide before wiring your own function and trusted verifier.
python -m pip install "gove-zone==1.0.0rc2"
# Optional Ed25519 receipt signing extra:
python -m pip install "gove-zone[crypto]==1.0.0rc2"
gove-zone doctorLocal evaluation commands. No external business action is demonstrated here.
Copy the example or select the code manually.
DESIGN AROUND THE BOUNDARY
The integration and operating conditions are part of the product decision.
gove-zone 1.0.0rc2 is published on PyPI under Apache-2.0, which permits production and commercial use. Releases after rc2 are planned under ACGS evaluation terms, and kernel source is not publicly available. Production use and commercial embedding of those later releases will require a separate written agreement.
Only paths wired through the governed executor or a documented adapter reaching it. An in-process library cannot contain a compromised host or prevent tools called outside that path.
Issuance needs an explicit signer; the executor requires a matching trusted verifier by default. One-time use additionally needs a ReceiptConsumptionLedger shared by every relevant executor. Stateless verification alone does not stop replay.
Identity and key management, runtime containment, operational monitoring, and external audit anchoring. A local hash chain can retain a valid prefix after tail truncation.
It is a Python kernel. An ESCALATE decision is non-executable. Approval interfaces, deployment operations, and regulatory assessment need their own integration and evidence.
SOURCE, RELEASE, AND CHECKS
PyPI lists 1.0.0rc2, uploaded August 23. The inspected monorepo uses a 1.0.0rc1 fallback. These are different artifacts; release reconciliation remains open.
Reviewed 2026-09-08. Source version and published release are tracked separately.
At the inspected monorepo commit, python-gove-zone failed its Python 3.11 test step; the Python 3.12 test job was cancelled. Packaging smoke and platform-lock jobs passed. No tests were rerun for this review.
FROM READING TO EVALUATION
Follow one example. Inspect the result. Decide whether it fits your workflow.