Confirmation Gates
Prepare a reviewable operation, check authorization for its concrete consequences, then execute and verify its state.
Prepare a reviewable operation, check authorization for its concrete consequences, then execute and verify its state.
Keep externally supplied instructions inside the data trust boundary.
Exclude sensitive values from reports and generated fixtures.
Declare a read-only operating scope before investigation.
Create and verify a recovery artifact before destructive state changes.
Classify actions into permitted, approval-required and forbidden tool policies.
Map data classes to approved destinations and allowed transformations.
Review the complete shipped skill payload before trusting its loaded entrypoint.
Delegate raw data access to bounded roles and keep the orchestrator focused on coordination and minimal results.
Assess effect reach and recoverability while honoring the actual authorization scope.
Enforce capability boundaries across every available execution route.
Check whether credential flow stays within its authorized service and destination.
Encode untrusted text for the exact output context that receives it.
Preserve originals or record reversible source-to-destination moves before reorganizing files.
Select the intended organization explicitly instead of accepting a first-account default.
Derive a cache key from every input that affects the visible response.
A well-formed derived path is a candidate target, not permission to delete it.
A unit under validation cannot grant itself an exemption from that validation.
Preserve artifact text as data when invoking an external reviewer.
Bound authorized edits to the requested behavior and only clean up orphans created by those edits.
Require a source or visible mock status for factual-looking metrics and specifications.
Verify that an export is scrubbed and independently verify that its remaining evidence still supports its claims.
Use consistent substitutions across an export while retaining safe identity and evidence structure.
Keep audience trust, permission to participate and permission to deliver as separate checks.
Bind approval to the exact draft bytes, destination and current revision so stale decisions cannot release rewritten text.
Narrow an existing agent grant without leaving its old broader credential usable.