Tool use needs anatomy
Tool permissions are often listed as APIs. The Covenant groups them by delegated consequence: speech, value, authority, access, and harm.
Review memo
The Golem Covenant is a small control protocol for delegated agent authority. It asks systems to declare what they can do, deny what they have not declared, and prove how they can be stopped.
golem.yml.golem.yml or equivalent capability declarations in agent frameworks.Tool permissions are often listed as APIs. The Covenant groups them by delegated consequence: speech, value, authority, access, and harm.
An agent that can act outside a sandbox must have a tested shutdown and tool-revocation path before launch.
Teams need to know whether an agent can speak, spend, sign, access secrets, deploy, publish, summon humans, or escalate authority.
The point is not to make bots more like their keepers. The point is to stop bots from becoming a keeper's unbounded operational self.
It is a small protocol for naming delegated authority before an agent acts.
We are seeking review of golem.md, a v0.1 draft protocol for bounded, answerable, revocable AI agents. The core proposal is simple: no golem without a soul, no soul without declared organs, no organs without limits, and no limits without tested revocation.
The concrete review request is the five-organ model, the schema-backed manifest, and the return-to-dust test. We would like feedback on whether this pattern belongs in agent frameworks, tool permission systems, and enterprise agent preflight checks.