EXECUTION KERNEL

A decision before
every governed action.

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.

Illustrative receipt fields

One call. Bound to its decision.

Actor
research-assistant
Action
documents.read
Arguments
exact values bound
Tenant
project-workspace
Policy
version + evidence
Verdict
ALLOW
The executor verifies the receipt against the call. This illustration is not a signed artifact.
Beta · release candidatePyPI 1.0.0rc2Python 3.11+Apache-2.0View evidence

WHERE IT FITS

A clear place in your stack.

Use this when a specific side effect must pass a policy and receipt check before the registered function runs.

  1. 01

    Propose

    Supply an actor, tenant, tool, and exact arguments.

  2. 02

    Decide + record

    Evaluate policy and append audit evidence before issuing a receipt.

  3. 03

    Verify + execute

    The governed executor checks the receipt before invoking the registered tool.

Four decisions. Two executable paths.

ALLOW
Run the approved call.
TRANSFORM
Run only the approved rewritten arguments.
DENY
Refuse execution.
ESCALATE
Stop execution; the escalation receipt grants no permission.

INSIDE THE PRODUCT

Capabilities you can inspect.

Follow each behavior to its implementation or maintained documentation.

01

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.

Inspect the source
02

Stop when governance cannot decide

Policy failures deny the request. Failure to append required audit evidence prevents a completed governed execution path.

Inspect the source
03

Inspect local evidence

Keep hash-chained JSONL audit records and verify their integrity. Re-deriving a decision also requires retained inputs and the original policy.

Inspect the source
04

Choose a documented integration

Python, MCP, runtime-hook, and CI examples have documented coverage. SDK patterns and roadmap integrations carry separate labels.

Inspect the source

LOCAL EVALUATION

Inspect the boundary locally.

From the ACGS monorepo checkout. These are maintained source commands; they have not been executed by this website.

  1. Prepare the runtime

    Install Python 3.11+ and uv, then open the pinned source checkout. Dependency setup may require network access.

  2. Run the local smoke example

    Exercise the documented allow, deny, and audit-verification path. The source example returns a nonzero exit code if its assertions fail.

  3. Review the signed example

    Follow the receipt-gated execution guide before wiring your own function and trusted verifier.

Open full setup instructions Open the pinned checkout
Monorepo root · shell
uv sync --package gove-zone --extra crypto
uv run --package gove-zone gove-zone doctor
uv run --package gove-zone gove-zone smoke

Local evaluation commands. No external business action is demonstrated here.

Copy the example or select the code manually.

DESIGN AROUND THE BOUNDARY

Know the scope.

The integration and operating conditions are part of the product decision.

Which calls are covered?

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.

Are receipts signed and single-use?

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.

What must the operator provide?

Identity and key management, runtime containment, operational monitoring, and external audit anchoring. A local hash chain can retain a valid prefix after tail truncation.

Is this a managed approval or compliance service?

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

Evidence with a reference.

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.

INSPECTED SOURCEMonorepo fallback: 1.0.0rc181de59eabacd

Reviewed 2026-09-08. Source version and published release are tracked separately.

CI SNAPSHOT · 2026-09-08Kernel test run failed

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.

Read the workflow evidence

FROM READING TO EVALUATION

Start with the source.

Follow one example. Inspect the result. Decide whether it fits your workflow.