Taxonomy / Contestatory constitutionalism
A written specification still binds the AI, but any application of it can be appealed, and each appeal's outcome enters a public record.
Scroll the diagram sideways to see all of it.
Limitation
The appeals channel can be captured: well-resourced or highly motivated actors learn to work it in their favor. It can also simply be swamped: if every decision can be contested, every decision may be. Either way, resolving disputes starts to cost more time and effort than the decisions themselves are worth.
The person on the receiving end of an automated decision gets a standing channel that takes their objection and puts it in front of a human who has to answer, with the exchange written down. Some members are design frameworks setting out the features such a route needs — covering mechanisms built in ahead of time and ones bolted on afterward alike; others are working systems, from a ban-appeal channel on a Reddit community of millions to a clinical dashboard where a doctor files structured disagreement with the model's reading, plus one speculative concept for a municipal camera car. Notice of the decision and a statement of its grounds belong to the fuller designs but not to all of them; what every member shares is that the object of dispute is one decision and the remedy is a reply plus a trail of what happened.
Instead of arguing with an output after it lands, the people governed write and rewrite the norms the system applies to them, and the system is built to defer to that authored profile rather than to one fixed inside the model. The interface is the mechanism: it exposes the profile so it can be inspected, challenged and revised, which is what makes the standard itself contestable rather than only its applications. The wager is that pluralism is won at the interface layer, by handing the standard to its subjects, not by picking a better standard centrally.
Takes a specification that already exists and disciplines what its words mean: it names the interpretive choices the text leaves open, shows that several equally defensible readings of one principle drive model behavior apart, and imports the machinery courts and agencies use to contain that — a pipeline that rewrites ambiguous rules the way an agency reworks a regulation, and prompt-level canons that constrain how the remaining ambiguity gets applied, tested across 5,000 real user scenarios. The strand's internal argument is the old jurisprudential one: bind a powerful decider with rules, or with accumulated cases. This is drafting and reading hygiene on the developer's side; nothing in it touches who wrote the text or who authorized it.
Leaves the wording of the rules alone and works instead on where the authority to make them comes from and whether the people under it can push back. The proposal is a constitution ratified in public rather than written privately inside a lab, with individual applications accumulating into a public body of case law that anyone can cite against the next decision; the yardstick applied to such an arrangement is a six-part test from republican political theory — legitimacy, accountability, corrigibility, non-domination, subsidiarity, institutional resilience — run first over existing non-majoritarian institutions and then over a hypothetical bounded superintelligent authority. The test is the instrument that grades this strategy, not a strategy standing beside it.
Opens a route for someone who was not in the room when the system was built to report that it failed in the world, and builds the plumbing that carries the report to whoever can act on it: standard machine-readable formats with rules of engagement, disclosure programs borrowed from bug bounties with legal safe harbor for the reporter, and a conduit that fans a single submission out to the several developers, coordinators and registries it concerns. Design frameworks in this group also cover schemes where the submitter is the deployer rather than an outsider, specifying enforcement, anonymity and what happens after a report. At the far end sit open, searchable archives of real-world failures and the editorial problem of indexing incidents whose cause, severity or technical detail is unclear.
The record is written as a matter of course rather than in answer to any particular complaint, and its audience is whoever reads it back later in bulk. Two different records are kept here: a voluntary tamper-evident ledger held inside the developer, logging models, data, training and evaluation runs, deployments and the approvals, waivers and attestations that authorized each one; and a legally compelled public register into which platforms file a statement of reasons for every individual adverse action against a user — 353 million of them in a hundred days, comparable across platforms. What unites them is the move rather than the object recorded or who is forced to record it: write it down by default so that the exercise of authority can be reconstructed and compared afterward.
The decision is represented formally as a network of claims supporting and undercutting one another, so a challenger can see which grounds actually carried the outcome. Because the links carry weights, one can compute how sensitive the conclusion is to each of them and work out exactly what would have to change for it to come out differently. Contestation here is machinery rather than interface: an exchange the system itself can hold, step by step, and revise when a challenge succeeds.
Anyone subject to a decision must have a real route to challenge it — to inspect the grounds it was made on, to contest the outcome, and to have that challenge answered. Legitimacy is not settled once by an election or an act of consent; it is held open by that route staying available. The test of a free system is not that its rulers are kind, but that their decisions can be contested by the people they affect.
Freedom here is not the absence of interference. You are unfree if someone holds unchecked power over you — even if they never misuse it and mean well. A benevolent master is still a master, and so is an authority whose workings you cannot see. Legitimacy requires that power be checked, not merely well-intentioned.
Rulings on challenges are written down, published and citable, so the system's interpretation of its own rules accumulates in the open, where it can be studied, invoked and criticized. The record is what makes the system predictable as well as legitimate: nothing is settled in private, and every decision leaves its reasoning behind it.