// Problem
Uncontrolled automation creates irreversible risk
CI/CD pipelines, infrastructure changes, data exports, and payment execution can cause permanent impact when they run without explicit authorization. Gate exists to stop accidental or unauthorized execution before systems commit side effects.
Common examples include deploying infrastructure, exporting sensitive data, triggering payment operations, and running production database migrations.
// What Gate does
Gate evaluates execution before action occurs
Gate intercepts execution requests and runs them through TrigGuard policy and safety evaluation before work is performed. Gate is the decision point for whether execution may proceed.
Capabilities
- Execution authorization
- Policy enforcement
- Receipt generation
- Audit verification
// How Gate works
Execution request to deterministic decision
System
→ POST /execute
→ TrigGuard Gate
→ PERMIT | DENY | SILENCE
→ Execution receiptFlow steps: (1) request received, (2) signals aggregated, (3) safety engine evaluates policy, (4) decision returned to the execution adapter.
// Example
Terraform deployment approval
terraform apply
↓
POST /execute
↓
TrigGuard evaluates request
↓
PERMIT or DENY
// Integration
SDK, API, CI/CD, and infrastructure integration
// Related links
Protocol · Runtime docs · Arbiter · Verify · Pricing