// Problem
Unverified execution decisions are not trustworthy
Without independent verification, teams cannot prove that an automated action was authorized under policy. That gap weakens incident response, compliance evidence, and operational trust.
Logs can be edited, policy state can drift, and audit trails can fragment across tools. Verify provides a trust layer for proving decision integrity across those boundaries.
// What Verify does
Verify cryptographic execution receipts
Verify confirms that receipts issued by TrigGuard are intact, signed by the expected key material, and bound to the decision context that authorized execution.
Capabilities
- Execution authorization
- Policy enforcement
- Receipt generation
- Audit verification
// How it works
Receipt and signature validation pipeline
System
→ POST /execute
→ TrigGuard Gate
→ PERMIT | DENY | SILENCE
→ Execution receiptVerify checks signatures using trusted key discovery and confirms the receipt remains bound to decision context.
// Example
CLI verification of a receipt
trigguard verify --receipt receipt.json --signature signature.bin// Integration
SDK, API, CI/CD, and infrastructure integration
// Related links