Skip to content

Accountability infrastructure for autonomous engineering

Principle 02

Least authority

Authority is granted narrowly, explicitly and in advance. Anything outside the declared envelope is refused, not negotiated.

Every component receives the narrowest authority that lets it do its job, declared before it starts and enforced at admission rather than argued about at runtime.

The envelope comes first

Before a run starts, its authority is written down: what it may touch, what it may spend, how long it may hold the lease, and what is explicitly denied. DoneState admits a run only if the requested outcome fits inside that envelope.

Declaring authority in advance changes where the argument happens. Instead of a running agent asking for more access at the moment it is most inconvenient to refuse, the scope is settled while nobody is under pressure.

Blast radius is a design input

Budget ceilings, lease expiry and scope limits are not throttles bolted on afterwards. They define the worst outcome a run can produce, which is the number that actually matters when deciding how much autonomy to grant.

An envelope that expires with the lease avoids the most common failure: authority that outlives the reason it was granted.

Authority the verifier does not have

Least authority applies hardest to the components people are most tempted to trust. OpsTruth has no write capability, so a compromised or simply wrong verifier cannot cause the damage it would otherwise be positioned to cause.

AgentProof extends the same logic to consequential actions: proposer, authority, executor, signer and verifier are separate roles, so no single component can both act and vouch for the action.

Give agents authority. Keep the proof.

Principles are only credible when the architecture makes them expensive to violate.