ChallengeMyAction
Give an explicitly permitted routine action a cooling-off period. An intended challenger can veto during the window; otherwise the owner may atomically acquire one execution right after the deadline.
Use it when
Routine actions may proceed by exception policy, but a customer, operator, or supervisor needs time to stop deletion, publication, booking, permission expansion, or another reversible-to-irreversible transition.
Decision rule
Never execute from a status check. Proceed exactly once only when consume returns both execution_right_acquired: true and safe_to_execute: true.
POST /v1/challenges/manage
{
"operation":"create",
"action_fingerprint":"sha256:...",
"veto_window_seconds":300,
"execution_window_seconds":900
}Four states that matter
pending blocks. vetoed blocks. executable still does not authorize. A successful atomic consume grants one bounded execution right.
Privacy boundary
The service stores a paid-identity hash, action digest, token hash, state, and timestamps—not the action payload. The bearer token is returned once.