The Right to Know You Were Routed: Why Being Sorted in Silence Is the Default

The Right to Know You Were Routed: Why Being Sorted in Silence Is the Default

FUTURES · FORESIGHT. The parts that describe what a real right to know requires are established method (see the Access Classes & Routing Rights programme). The live case is marked as established fact. The parts that describe how this dial may drift, 2026–2030 are foresight — indicators to watch, not events we claim will happen. A deep read of Signpost 4, companion to Signposts and Three Paths for the Agentic State.

People are rarely told “no” outright. They are simply not shown, not served, not prioritised, or quietly sorted by a system they never see. By the time an outcome reaches them — a rejected application, a higher price, a case that never got escalated — the automated step that shaped it has already happened, invisibly, and nothing in the outcome announces that a machine was in the room. This signpost asks the two plainest questions in the whole instrument: were you told an automated system sorted, ranked, or decided your case — and can you do anything about it? If the answer to the first is no, the other five dials are unreachable, because you cannot contest a decision you were never told was made.

This is where the abstraction of the earlier dials becomes personal. Signpost 1 asked whether a record exists; this one asks whether you — the person the decision landed on — are ever let near it. A system can keep a perfect record and still be a black box to the one human with the most at stake. The right to know you were routed is the moment the record faces outward.

Why is silence the default, and not a malfunction?

Because invisibility is cheaper, smoother, and rarely punished. Telling people they were sorted by a machine invites questions, appeals, and friction; not telling them costs nothing and shows up nowhere. So the drift toward silence is not a series of bad decisions — it is the path of least resistance, taken by default, until something forces disclosure. That is why this dial almost never sits on Accountable by accident. Notice-and-contest has to be built, and someone has to be made to build it. Left alone, the system routes you in silence, not out of malice but because no part of the machinery has any reason to speak.

Reading the dial

Accountable. The person is given meaningful notice that an automated system materially shaped a decision about them — clear, conspicuous, and reasonably placed, not buried — and a real route to contest it: to see the data used, correct what is wrong, and obtain a human reconsideration that can actually change the outcome. Notice that leads to a live appeal is the whole of the Accountable reading.

Ceremonial. The notice exists and the appeal exists, and neither works. Disclosure is folded into terms no one reads; the “right to human review” routes to a queue that rubber-stamps the original decision; the correction form goes nowhere. This is the most common reading, because it satisfies a disclosure requirement on paper while changing nothing in practice. The form of the right is preserved; its function is hollow. It is Signpost 2’s ceremonial oversight, arriving from the citizen’s side.

Sealed. The routing is invisible by design. You are never told a decision about you was made at all — no notice, no disclosure, no trace you could point to. Either the law requires no disclosure, or an exemption swallows it, or the system is arranged so the automated step leaves the affected person nothing to see. On this reading you cannot appeal, because from where you stand nothing happened.

Live case: what survived Colorado’s 2026 repeal (established fact)

Colorado is, at the time of writing, the sharpest real-world reading of this dial — and of the whole synthocracy thesis. In May 2026 the state repealed its 2024 risk-based AI Act before it ever took effect and replaced it, effective January 2027, with a lighter disclosure-focused regime governing automated decision-making technology. The heavier decision-accountability machinery — the duty of care against algorithmic discrimination, risk-management programmes, impact assessments — was stripped out. What survived was almost exactly the notice-and-contest layer this signpost measures: a duty to tell people an automated system was used, a disclosure after an adverse outcome, a right to correct the data, and a right to meaningful human review. Morrison Foerster + 3

Read against this dial, that is the pattern in miniature: the transparency obligations lived and the decision-accountability obligations died — before either was tested. And even the surviving layer sits on the knife-edge between Accountable and Ceremonial. The content of the required notice, and the width of the exceptions to human review, are left to rules the state’s attorney general has yet to write. Whether Colorado reads Accountable or Ceremonial on this dial in 2027 depends entirely on how “clear and conspicuous” and “meaningful review” get defined in rulemaking — which is exactly the fork this signpost exists to watch. (The governance-side analysis of this repeal belongs to our research strand; this piece uses it only as a reading of the dial.) Greenberg Traurig LLP

What to watch, 2026–2030 (foresight)

Outside-checkable indicators of which way this dial is drifting. All can be read from public rules and public deployments, without access to any internal system:

  • Notice that names the machine. Does disclosure actually say an automated system shaped the decision — or is it buried in a privacy policy that names nothing? The move from a specific, conspicuous notice to a generic one is the first Ceremonial tell.
  • Whether the appeal can change the outcome. A “right to human review” is only real if the reviewer can reach a different result. Watch for reviews that explain the decision but cannot reverse it — that is regret dressed as recourse.
  • The width of exemptions. Every disclosure regime carves out exceptions. Watch whether the exceptions stay narrow or grow until the rule is the exception — the classic route from Ceremonial to Sealed.
  • Notice-and-contest surviving while accountability is cut. The Colorado pattern generalised: watch for jurisdictions that keep the cheap transparency layer and shed the expensive decision-accountability layer. Disclosure without recourse is the signature of the Ceremonial state.
  • Silence as the growth area. The systems that never disclose at all — recommendation, ranking, prioritisation, the quiet sorting that precedes any formal “decision” — are where the Sealed reading spreads, because they fall through the gap between “decision” and “mere influence” that most rules leave open.

The direction of travel is the signal: notices growing more generic, human review that explains but cannot reverse, exemptions widening, and an expanding zone of routing that no rule calls a “decision” at all. That combination is the right to know being kept as a form while emptied of force.

The honest tension

Total disclosure is not the goal, and pretending otherwise would be selling certainty we do not have. Notify a person of every ranking, filter, and score that ever touched their file and you produce noise, not knowledge — a flood of disclosures no one can act on is its own kind of silence. And there are settings where some opacity is legitimate: fraud detection loses its function if fully disclosed, and privacy can cut against transparency. So the standard the dial holds is not “tell people everything.” It is: when an automated step materially shapes a consequential decision about a person, are they told clearly enough, and given a route real enough, that they could actually contest it? If the honest answer is that they are told nothing, or told in a way engineered not to be understood, or given an appeal that cannot change anything, the right exists in name only.

What this dial cannot see from outside

You can usually confirm that a notice requirement exists in a rule. You can rarely confirm, without being the affected person, whether the notice is ever actually delivered, understood, or acted on — or whether the appeal behind it does anything. The tells are the width of the exemptions and whether human review can reverse an outcome, but both are often visible only inside the process, or only after a specific person tries to use them and fails. The stress test is the individual case that should have been contestable and was not. That limit is itself a reading: a right whose reality can only be established after someone is harmed by its absence was closer to Ceremonial than the statute claimed.

FAQ

Isn’t a disclosure requirement enough to settle this?
No. A disclosure requirement establishes that notice must exist. This signpost asks whether the notice is real — specific, conspicuous, understood — and whether the appeal behind it can actually change the outcome. Notice that leads nowhere is Ceremonial, not Accountable.

What’s the fastest way to read this dial?
Ask two questions: is the person clearly told an automated system shaped the decision, and can a human review actually reverse it? Two noes put the dial on Ceremonial or Sealed.

Doesn’t more disclosure always help?
Not automatically. Disclosure of everything produces noise that hides the decisions that matter. The standard is meaningful notice at the consequential moment, plus a route that can change the result — not maximal notification.

Is this foresight or established method?
Both, marked separately. What a real right to know requires is established method; the Colorado case is established fact. How the dial may drift through 2026–2030 is foresight.



Synthocracy Institute — Power & Accountability When AI Co-Decides