The product family
All products
Compare the execution kernel, Python library, multi-agent runtime, HTTP service, and infrastructure companion.
About ACGS
ACGS explores the boundary between a proposed action and its execution: who may act, which resources are in scope, when review is needed, and what evidence should remain.
The idea behind the project
The gap between a useful answer and what an agent is allowed to do next.
A useful rule must meet the actual execution path, and a completion claim must point to something a reviewer can inspect.
Read the founder narrativeFrom the founder narrative
Explore the project
The components have different contracts and levels of maturity. Their setup, evidence, and operating conditions should remain visible.
The product family
Compare the execution kernel, Python library, multi-agent runtime, HTTP service, and infrastructure companion.
Principles in practice
Choose operating modes and controls appropriate to an agent task.
Dated source review
A dated source, release, CI, and limitations index for the product family.
Trust and responsibility
Source code, tests, and decision receipts each establish something specific. Deployment controls and independent assurance require their own evidence.
Trust center
Review product claims, security boundaries, and deployment-specific data questions.
Security boundaries
Start with controls present in the source, then evaluate the environment in which they will operate.
Privacy and data handling
Review authored site behavior and deployment questions before operating a service.
Public-origin subprocessors
Processors used to serve the public origin; not a signed inventory for every product or deployment.
This is not a signed legal inventory for every ACGS product or deployment.
Keep the evidence in view
Components have different contracts and levels of maturity. Review the setup, source evidence, and operating conditions for the path you choose.
Review Claims & Evidence