Contest before consequence

As state agents initiate adverse action at machine speed, the review that answers a contest will keep running at human speed, and the gap between the two clocks will be borne by the person: repaying a debt while disputing it, accruing interest while a review queue clears, losing a service while an error is examined. A dispute path that opens only after the consequence lands does not close that gap; nothing in it stops the demand while the question is decided.

Where a pause exists today it is granted on request, which converts a safeguard into a knowledge test: the person must know a pause exists, ask for it correctly, and ask in time. As initiating fleets scale, a request-based pause guarantees that the people who never learn to ask absorb the consequences of every error that review would have caught.

Services Australia review and repayment pause. A person can ask for an explanation or formal review of a Centrelink debt decision, with an explanation call targeted within 14 days and a formal review at 49 days, and can ask for repayments to be paused, generally for six months, while it runs. The suspensive step exists and operates at service scale. It is a discretionary grant the person must know to request, and not a default consequence of lodging the contest.

GDPR Article 22, the contest triad and its law-authorized carve-out. Article 22 grants human intervention, the right to express a view, and the right to contest, but only where the decision rests on contract or explicit consent; for decisions authorized by law the triad does not attach, and the authorizing law need only provide 'suitable measures' of its own. In Case C-634/21, SCHUFA the CJEU pulled upstream scoring engines into the Article 22 regime. A state can legislate itself out of the contest right, and where the regime does apply it reaches the engine upstream of the officer who signs.

Regulation Z billing-error resolution. A billing-error dispute must be acknowledged within 30 days and resolved within 90, and the disputed amount is not collectible while the investigation runs. The burden shifts to the provider and the consequence is suspended for exactly as long as a bounded clock runs.

Colorado SB 24-205, the stalled statutory route. The act legislated notice of consequential decisions, an opportunity to correct the data relied on, and 'an opportunity to appeal, via human review if technically feasible, an adverse consequential decision'. It never operated: its compliance date was postponed, and it was repealed and reenacted by SB 26-189, which kept the notice and a request-based human review. It is a design precedent for the contest-and-correction bundle, never citable as operating practice.

The pause primitive already runs inside a high-volume payments agency, so the operational objection (that recovery systems cannot tolerate suspension) is answered by an existing deployment. The chargeback model supplies the missing spine: anchor the contest to the identified action, shift the investigation burden to the operator, suspend collection for the life of a bounded clock.

What breaks in transit is the trigger and the incentive. The operating pause is discretionary and knowledge-gated where this pattern needs it automatic on lodgment. The card issuer investigating a chargeback is institutionally separate from the merchant it investigates; an agency reviewing its own agent's action is not, so the burden-shift and the clock have to be designed in and externally auditable rather than inherited from market structure. And the undesigned core is the default itself: no jurisdiction has yet balanced default suspension against revenue protection, urgency carve-outs, and the gaming risk of contest-as-denial-of-recovery. The card claims the duty is designable, and says plainly that nobody has designed it yet.