AIP-02: Capability Model

Abstract#

Defines the hierarchical capability system governing all execution authority.

Capability Structure#

Capabilities MUST follow: category.subcategory.action

Examples:

• device.file.read

• wallet.sign.transaction

• net.fetch

• storage.put

• k8s.pod.exec

Normative Requirements#

1. Every tool invocation MUST declare its required capability.

2. Capabilities MUST be validated before execution.

3. Capability validation MUST precede policy evaluation for a given tool call.

4. Unspecified capabilities MUST default to DENY.

5. Capability escalation MUST NOT occur implicitly.

6. Capability registry updates MUST be versioned and auditable.

7. Capability names MUST remain backward compatible; deprecated capabilities MUST remain resolvable.

8. Implementations SHOULD support capability scoping (domain, workspace, environment).

Legal Consideration#

Capability boundaries define explicit authority limits and reduce ambiguity about delegated authority.