Existing reference receivers check bound parameters, expiry, replay, and current authority. The disposable reference credential destination couples redemption, the version change, signed effect evidence, receipt, and audit in one transaction.
Integration and verification requirements
The credential reference requires shared PostgreSQL and stable signing keys outside Development. It does not establish an externally operated receiver without issuer database access, universal customer-hosted enforcement, or exactly-once remote effects.
Use case / Protected-service engineer
Apply an authorized versioned credential change.
Illustrative integration review. These controls explain the design; they do not submit requests, grant authority, or execute an action.