THE ACGS PRODUCT FAMILY
Choose your
point of control.
Start with gove-zone for receipt-gated tool calls, ACGS-Lite for Python policy checks, or CFT Governance Pack for cloud plans. Swarm and Agent Bus address coordination.
EXECUTION KERNEL
Permission belongs
at the tool boundary.
gove-zone requires a valid receipt before a tool call runs on an integrated execution path. Start here if your next question is: “May this exact action execute?”
Meet gove-zone Beta · PyPI 1.0.0rc2Verified callDENY / ESCALATE
Execution stops
Find the right building block.
Current evidencegove-zone
Require a valid decision receipt before an integrated tool call can run.
Beta · release candidate02ACGS-Lite
Start with configurable policy checks and governed Python wrappers.
Beta03ACGS Swarm
Coordinate task ownership, peer validation, and governance evidence.
Mixed maturity · optional research04Enhanced Agent Bus
Operate governed messaging and workflow endpoints as a separate service.
Evaluation · operational setup required05CFT Governance Pack
Check Google Cloud Terraform plan JSON and retain control evidence.
Early source companionDIFFERENT JOBS. EXPLICIT BOUNDARIES.
Match the product to the job.
The family shares a governance focus. Each component has its own contract, dependencies, and maturity.
| Product | Primary job | You provide |
|---|---|---|
| gove-zone | Receipt-gated tool execution | Executor wiring, trusted keys, identity, and audit anchoring |
| ACGS-Lite | Python policy checks and governed wrappers | Constitution, call integration, and full audit configuration |
| ACGS Swarm | Agent coordination and peer validation | Agent roles, validators, transport, keys, and persistence |
| Enhanced Agent Bus | Messaging and workflow HTTP service | Authentication, Redis, workflow, policy, and audit backends |
| CFT Governance Pack | Terraform plan checks and evidence | Plan JSON, controls, CI enforcement, and evidence retention |
EVALUATIONS AND WORKFLOW REFERENCES
Explore the next layer.
Additional source packages, local examples, and design references. Each page states what is implemented and what remains open.
Governance Evaluation
Source MVP for authority, policy, and evaluation evidence.
Read the referenceClinicalGuard
Healthcare assessment prototype for source evaluation.
Read the referenceLegal workflow example
Mock drafting, matter access, and review boundaries.
Read the referenceHermes integration
Source middleware around the tool-call lifecycle.
Read the referenceEU AI Act mapping
Engineering evidence mapping with explicit gaps.
Read the referenceCredential-governance concept
A design reference; implementation remains unverified.
Read the referenceDECIDE WITH EVIDENCE
Inspect before you integrate.
Source code, release metadata, and CI checks answer different questions. Review all three for your chosen product.
Read Claims & Evidence