Dual Control Timer
Not a key manager — but a policy-gated gate that proves N parties explicitly approved before a timed release.
The problem
/ 01When sensitive actions require multiple approvals and a time-delayed release, you need a stateful gate that records every approval, rejects self-approval, deduplicates approvers, and only unlocks once the threshold is met and the timer expires.
What it does
/ 05Creates a dual-control approval request with actionLabel, optional requesterId, requiredApprovals, unlockAfter (ISO-8601 timestamp), and optional meta.
Returns a requestId and initial status (pending).
Approves a request by requestId + approverId; rejects self-approval and duplicate approvers.
Status transitions: pending → armed (threshold met, timer active) → unlocked (timer expired).
Lists all requests and fetches a full record by ID.
Who it’s for
/ 03- Security teams enforcing multi-party operations
- SREs managing production access change windows
- Compliance reviewers auditing approval chains
In context
/ 01Complements Sovereignty (agent governance), Escape Hatch Notarization (exception records), and the Consent Receipt Registry (consent integrity).
