Capabilities and permissions

Overview

Verified permissions use exact tool-scoped values such as tool:read_record. Capability checks should be narrow enough to explain and revoke.

• Name the specific tool or operation.
• Bind permissions to the owning organization and project.
• Use short expiry for elevated authority.
• Separate read, propose, approve, and execute powers.
• Revoke on mission completion or compromise.

Production checklist

• Keep credentials in a server-side secret store.
• Set explicit cost, latency, privacy, provider, and regional constraints.
• Capture route and evaluation evidence for incident review.
• Test timeouts, cancellation, fallback, and denied-policy paths before rollout.