no svid, no action.
human approval isn't a checkbox. it's a cryptographic gate. without an svid issued by ackd, the agent cannot proceed — full stop.
enforcement
how enforcement works
human approval triggers SVID issuance via SPIRE
the agent must present a valid, unexpired SVID to proceed
the SVID is scoped to exactly one request_id — it cannot authorize any other action
observability
what gets logged
every authorization request stores:
stored in DynamoDB. TTL-based retention. exportable.
failure modes
what happens when things go wrong
trust model
who controls what
ackd controls
- consent flow
- SVID issuance
- audit log
- TTL enforcement
the agent controls
- what action it requests
- the justification it provides
the human controls
- the approval decision — the only thing that gates the SVID
compliance
compliance-ready from day one
SOC2 Type II
CC6.1 (logical access controls), CC6.6 (least privilege)
HIPAA
§164.312(b) audit controls, §164.312(a)(1) access control
ISO 27001
A.9.4 system and application access control
every agent action is tied to a named human, a timestamp, and a cryptographically verifiable SVID. that's your audit evidence.
coming soon
SOC2 Type II report — in progress
third-party penetration test results — scheduled