About ACGS

Useful answers are a beginning.What happens next matters.

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

Why ACGS exists

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 narrative

From the founder narrative

The principles that carry through.

Explore the project

Build the boundary. Then examine it.

The components have different contracts and levels of maturity. Their setup, evidence, and operating conditions should remain visible.

Trust and responsibility

Look beyond the artifact.

Source code, tests, and decision receipts each establish something specific. Deployment controls and independent assurance require their own evidence.

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