Using SRR API: A Complete Developer Guide

Good API surfaces make states obvious: queued, running, waiting for approval, completed, failed, and verified.

Designing with those states first keeps clients predictable and makes automation easier to debug.

SRR's future API work should preserve the same operator contract shown in the product surfaces: visible intent, clear permissions, and evidence after execution.