Tool execution
gove-zone
Require a valid decision receipt before an integrated tool call can run.
Only tool paths routed through the governed executor are covered.
For developers
Start with one action.Make the boundary explicit.
Choose the contract your integration needs. A Python policy check, an executable decision receipt, and a messaging response establish different things.
Your evaluation starting point
Documentation & setup
Product-specific setup instructions, integration references, and source evidence.
Follow the product-specific setup and inspect the expected result before expanding the integration.
Open the documentationChoose an evaluation
What needs a check?
Begin with a single tool call, proposed Python action, or cloud plan. Keep the execution path and evidence configuration in scope.
Beta · release candidate
Python policy checks
ACGS-Lite
Start with configurable policy checks and governed Python wrappers.
A successful validation alone does not authorize an external action. Inspect the separate execution gate and audit configuration.
Cloud-plan checks
CFT Governance Pack
Check Google Cloud Terraform plan JSON and retain control evidence.
Evaluate Google Cloud Terraform plan JSON. Your pipeline enforces the result before apply.
Connect the workflow
Coordination has its own contract.
Inspect the responsibilities of each component and the hooks your host actually invokes.
Multi-agent coordination
ACGS Swarm
Coordinate task ownership, peer validation, and governance evidence.
Self-hosted messaging
Enhanced Agent Bus
Operate governed messaging and workflow endpoints as a separate service.
A bus acceptance response is not approval to execute a tool call.
Integration reference
Hermes integration
Inspect pre-tool checks, output screening, final-response holds, and optional evidence capture.
Connect middleware hooks to the actual runtime. The reference panel uses fixture traces; its replay and export buttons do not call a backend.
Inspect and learn
Build with the limits in view.
Use the reference material to define authority, investigate risks, and review the evidence your integration should retain.
Framework and task brief
For agents
Copy a governance framework and a blank task brief for agent workflows.
Source-backed answers
Governance Q&A
Search source-backed answers about receipts, signatures, audit evidence, and product scope.
Risks and warning signs
Failure modes
A practical catalogue of agent-workflow risks, warning signs, and integration controls.
Operating arrangements
Governance patterns
Choose operating modes and controls appropriate to an agent task.
Source, release, and CI review
Claims & Evidence
A dated source, release, CI, and limitations index for the product family.
Keep the evidence in view
Understand the scope.
Then evaluate.
Components have different contracts and levels of maturity. Review the setup, source evidence, and operating conditions for the path you choose.
Review Claims & Evidence