Approval Binding. The explicit relationship between an approval record and the exact action, payload, connector, descriptor, risk tier, evidence, and execution boundary it authorizes. An approval binding prevents a human decision from becoming a floating permission that later attaches to a different capability or broader effect.
An approval binding makes an approval useful because it is part of the action path: the request creates an approval record, the action carries the approval identifier, the boundary verifies that the approval applies to this exact action, and execution refuses to continue when the binding does not match. The binding should also name the approval mode that made approval required, optional, escalated, or denied. The binding must also preserve the approval's lifecycle state, so expired, revoked, pending, or already-used approval cannot be mistaken for current authority. Its revocation rule explains how a once-valid approval stops authorizing future work before normal expiration.