This site argues that people an automated system decides about should be able to challenge a decision and get an answer by a deadline, and that the challenge should be able to change the outcome. It calls that standing. The usual objection to it is volume.
Volume and vetocracy
Every argument for standing meets a mirror argument: require the institution to answer every challenge from the people its system decides about, and it drowns. Every automated denial is challenged, every halt is triggered on suspicion, and every decision is reopened indefinitely. Public administration knows this worry in concrete form. Permitting regimes, environmental review, and procurement are already criticized for veto-point proliferation, sometimes called vetocracy: each added party with the power to pause makes the pausing permanent, and nothing gets built. Governance systems fail in two directions, through automated cruelty and through paralysis. A method that guards only against the first produces the second.
Law VII already answers the narrow version. A challenge with procedural force must be received, answered, and able to change the outcome. It need not prevail, and it does not stop the system on assertion. One challenge is a transaction with a cost, not a veto with an infinite one. The law does not answer the arithmetic that follows. A hundred thousand challenges are a budget line, and no institutional design survives refusing to do the sum.
Per-case force, aggregate risk
Volume in bad faith means challenges filed to exhaust, delay, or retaliate. The fix exists and is unglamorous. Procedural force includes a standard of review and a set of admissible evidence, and whoever answers challenges can find one inadmissible without denying the challenger standing. Ruling on admissibility is a decision about one case, with a record. Narrowing who may challenge is a change to the standing register, the published record of who may challenge what, and it has to survive the same scrutiny as any other change to how the system is governed.
Volume in good faith is different. The people the system decides about file more real challenges than the institution can answer. A good-faith challenge can concern a wrong decision, but also a correct one under an ambiguous rule, or a request for an exception, so volume alone does not count errors. What a queue of unanswered challenges measures is the gap between the demand for answers and the correction capacity its delegation was granted with; the error rate has to be read from what the challenges uphold and what the reviews find, not from the queue’s length. Law IV states that delegated authority may not accumulate without a matching accumulation of corrective capacity. Challenge volume is where that law becomes countable — with arrivals, upheld challenges, and processing costs tracked separately.
The cost of answering
Answering challenges is labor, and someone has to do it. Suppose a system issues 200,000 decisions a year and 2% of them are wrong. That is 4,000 errors. Suppose half the people with a wrong decision challenge it, and each answer takes a reviewer three hours. The institution needs 6,000 reviewer-hours a year, about four full-time reviewers at 1,500 working hours each. If it has staffed two, 1,000 challenges a year go unanswered, and the backlog grows by that much for every year the system runs. The numbers are illustrative. The shortfall was fixed when the delegation was granted, not when the challenges arrived.
Burden accounting already counts one side of this. The waiting time and re-submissions pushed onto the people a system decided about appear as costs. The other side, the institution’s unanswered challenges, appears nowhere. A queue that ages without anyone counting it is how the institution absorbs the evidence of its own errors.
Under Law VIII, a challenge past its clock is not pending. Silence past the clock is a governance failure. The institution’s records already mark the congestion as a failure state. What the institution does not do is read those records as a signal about its capacity.
Law VII asks who pays for the repair. The mirror question is about the challenge itself: who does the answering, at what cost, and whether that cost was budgeted when the delegation was granted. A standing register that names responders and clocks has also named a cost center. An institution that finds it cannot afford its own register has not made an argument against standing. It has found the real size of the correction capacity behind its delegation. The response is more resources or a smaller scope, the two levers Law IV provides. It is not disqualifying the people the system fails.
What congestion actually means
When challenge volume exceeds response capacity, institutions reach for the nearest lever, and it is almost always narrowing: fewer parties eligible to challenge, fewer matters open to challenge, higher admissibility bars, longer clocks. Each narrowing is defensible on its own. Together they are the whole failure. The method’s name for a system that the people it misjudges can reach is an open circuit. Standing, deadlines for answers, and records are what keep it open. Narrowing standing in response to congestion closes it. The people the system fails lose the instrument exactly when the volume shows the institution cannot answer them. The signal arrives through volume, and the response destroys the channel that carried it.
Challenge density is the rate at which challenges arrive against the capacity to answer them, and a rate can be governed by capacity decisions rather than by restricting rights. An institution treats challenge density as a governing signal when it ties sustained breaches of response clocks to a resourcing decision or a scope decision, and records which one was made. An institution treats it as a nuisance when it ties the same breaches to eligibility criteria. The two responses can look identical in a quarter of calm and diverge completely in a year of scale.
Theory, drawn
Challenge volume against response capacity
Congestion begins where challenge volume exceeds response capacity. One response closes the channel; the other provisions the capacity to answer.
Stratification
The other lever operates on the force side rather than the volume side. Not every challenge should carry the same halt potential, and not every halt should be available at the same tier. A frontline operator pausing one case, a supervisor halting a queue, and a steward halting the whole system are different instruments. They differ in blast radius, meaning how much each one stops, and in how service recovers and what evidence each demands. Tiering the power to halt by blast radius keeps per-case force from becoming system-wide friction. The power to stop scales with the size of what is being stopped, and the smallest tiers stay cheap enough that people use them.
Veto points proliferate when every party holds the same maximal instrument, the system-wide halt, and no one holds a graduated one. A halt structure with tiers does not remove veto points. It prices them. The question about any proposed standing grant stops being “can this paralyze us” and becomes “which tier does this force operate at, and is the recovery path provisioned at that tier.”
What the laws take from this
Law IV: correction capacity is measured against challenge volume, not asserted alongside it. The challenge load ledger is the instrument, and sustained congestion is a capacity event, not an eligibility event.
Law VII: halt force is stratified by blast radius, so that the power to stop scales with the size of what is being stopped.
Law XII: narrowing standing in response to volume is a named failure mode. It erases a condition of the system’s contestability, and the institution’s records should say that it did.
A reader can accept the vetocracy objection in full and still accept these commitments. They give no one more power. They require that the cost of the power already granted be counted, budgeted, and recorded. That is the arithmetic the objection asked for.