Can this decision be challenged?

Standing turns “that’s wrong” into something the system has to answer: a decision with reasons, a deadline, a named person who can change it, and a route to reversal.

• Does the person receive a receipt with the reasons, the date, and what the decision covers?

  If not. “Contact support” is a queue. Without a receipt, a deadline, and a named person who can decide, it is only a request for help.

• Can a named person change or reverse the decision?

  If not. The route is for show: it hides who decides. A challenge changes the outcome only when it reaches someone who can reverse the decision, and the evidence the person sends is weighed.

• Is there a deadline by which the person must get an answer?

  If not. Requests sit in the queue and are never reversed. Due process needs a deadline and escalation that has to happen.

• Can the person challenge the decision without asking permission or meeting hidden conditions first?

  If not. The case never reaches a state the system has to answer. The person has no standing, even if there is a form or a hotline.

• If the challenge is upheld, is there a set way to reverse the decision or repair the harm?

  If not. Winning changes nothing. Due process needs a decision that binds.

• Is there a record that challenges have been upheld, not only that they were processed?

  If not. The route may be for show, ending in a queue no one can trace. A working route publishes how often challenges are upheld, names who can reverse outcomes, and shows where the evidence is weighed.

• Are upheld challenges counted against the rule that produced them, and is the count sent to the rule's owner?

  If not. The rule keeps running. When challenges to one rule keep being upheld, the rule is wrong. The count goes to the rule's owner, who changes the rule.

The questions come from the glossary definition. The contestability standard, STD-02, sets the obligations behind them, including clear appeal paths.