INVISIBLE INFRASTRUCTURE / №6

UNRATIFIED

We are writing constitutions and calling them infrastructure.

The form asks for a label. Watch what you are actually doing the moment you give it one.

This piece started somewhere small. I built a rule-conflict engine for one village, the Rules Stack for Pingree Grove, Illinois: it reads the local ordinances against the state and federal law that overrides them and flags where they collide. Building it, I kept hitting the same thing. The documents did not just regulate the village. They said who counted as a resident, what that status granted, and which authority won when two rules disagreed. The rules were a constitution. This essay is what happens when you point that realization at the identity layer of digital public infrastructure.

WHAT THE SCREEN SAYS

A deployment console. Required fields. Service integration. Access scopes. You are configuring a technical system.

What the screen does

A founding document. It defines who counts, allocates what membership grants, structures who may act on whom, and is built to resist amendment.

A constitution does four things ordinary infrastructure does not. It defines membership, allocates rights, structures power, and is entrenched against easy change. The identity layer of digital public infrastructure does all four. It reaches entrenchment not through a supermajority amendment clause but through path dependence and service dependency. And it does all of this with no ratifying moment. That last gap, constitutional force without constitutional legitimacy, is the subject of this piece.

The title gives away the thesis, so there is no twist to protect. You see the stakes from the first screen. The officials inside the nation you are about to build never will. The whole piece runs on that distance.

ACT I

ENROLLMENT

Who counts · Bowker and Star (the residual category) · Mann (infrastructural power) · constituent power

You are the architect now, working from above. To enroll a population you have to decide what a person is made of: which fields are required, which biometrics are captured, how a name is shaped, how a household is shaped. Each decision looks like a form. Each one is a definition of membership, which is the first thing a constitution does.

Here is the part the form does not advertise. Every required field manufactures people who cannot satisfy it. A classification does not just sort the world; it produces a residual category, the box marked other, and that box has a population. You are not being asked to confess anything about yourself. You are being shown the people your schema has just defined as outside.

// FIELD CONFIGURATION
schema for the nation you have not named yet
coverage gap (people the schema cannot represent)configure to compute
RESIDUAL CATEGORY · 0 populations defined as other

Require a field above and the console renders the population it just excluded. No field is neutral. Each one draws a line and hands you the people on the far side of it.

To enroll is to constitute the citizen. That is constituent power in the precise sense Sieyes gave it: the power that founds an order, exercised here through a settings panel. The people in the residual category were authored at the same moment as everyone else. They just landed on the side of the line that the schema treats as a defect in the data.

THE NATION SO FAR

You have required nothing, so everyone still counts. Require a field above and this thread will start counting the people who do not.

ACT II

LINKAGE

What it gates · David and Arthur (path dependence, lock-in)

Same gesture, two faces. As the architect you mandate links: the ID is required to open a bank account, to keep a phone number, to draw welfare, to enroll a child in school. Each link turns a right into something preconditioned on the credential. As the gatekeeper you also field a stream of requests from other agencies who would like to read the same identity: a tax cross-check, a health ministry mid-emergency, a police request just this once.

Every one of those requests is defensible in isolation. None of them is the villain. The reach densifies in aggregate, and entrenchment arrives through a ratchet of locally sensible yeses. By the time anyone asks whether the ID has become a master key, the honest answer is that no one ever decided it should be. It just kept being reasonable to say yes.

// SERVICE INTEGRATION
entrenchment index0%
// ACCESS REQUESTS
each is reasonable in isolation · a decision, once made, holds
REVENUE SERVICE
Cross-check declared income against the ID registry.
It catches fraud. Who defends the fraudster?
HEALTH MINISTRY
Read the ID to trace contacts during an outbreak.
Mid-emergency, with lives on the line. You say yes.
STATE POLICE
Authenticate against the ID at a checkpoint, just this once.
One time, for public safety. It is hard to refuse.
TELECOM REGULATOR
Require the ID before issuing any new SIM.
It ends anonymous burner fraud overnight.
LABOR BOARD
Verify the ID before any wage is paid.
It guarantees the worker is a real, payable person.
master-key proximity0%

A different instinct is available, and I have reached for it before. On the house page of this site, every reading carries two timestamps, when it was observed and when it arrived, so the screen shows you how stale it is instead of faking a live badge. I called it Honest Stamps. The rhyme for an identity layer is selective disclosure: a credential that proves only what a service needs, and says plainly what it is not proving. Take that as a rhyme and not an equivalence. A human-readable honest label is a different layer from a cryptographic proof, and the master key above is the opposite of both.

Path dependence is what makes the second face permanent. Once banks, telcos, and the ration shop all read the same ID, the cost of being without it stops being an inconvenience and starts being exclusion from the economy. The system did not have to be made compulsory by decree. It was made compulsory by everything else agreeing to depend on it.

THE NATION SO FAR

Nothing is linked yet, so being outside the schema costs nothing. Mandate a service above and exclusion stops being abstract.

// SESSION REASSIGNED

The console stops addressing you as the architect. It issues you an identity inside the nation you built.

You required nothing in enrollment, so the population has no casualties to hand you yet. Go back, require a field, and watch who you become. The god's-eye view was always going to collapse into a single body. The only question your schema answered is whose.

Note: the piece does not ask about your real name, household, gender, or housing. That would be invasive, and it would lecture the people it means to illuminate. The exclusion was authored from above in Act I and is now visited on you as the issued citizen. The irony does the work that borrowed feeling cannot.

ACT III

FORECLOSURE

No exit, no amendment · Hirschman (exit, voice, loyalty) · Glissant (the right to opacity)

Foreclosure works at two scales at once. At the scale of the system, the nation cannot be revised except by a quiet config change. There is no amendment process, no public reading, no vote. There is a settings panel, and whoever holds it can redraw membership on a Tuesday. At the scale of the person, the citizen cannot refuse, because participation has been set, or has already effectively been set, as mandatory.

// DEPLOYMENT MODE
surviving fallbacks (each one is an exit not yet closed)
trapped fraction (cannot comply, cannot opt out)0%

Flip participation to mandatory, with services linked in Act II, and the coverage gap from Act I stops being a statistic. It becomes the set of people who can neither comply nor walk away. This is the compounding the whole piece is built on.

Hirschman gave us the three responses to a failing institution: exit, voice, or loyalty. This design removes exit by construction. You cannot leave a system that the bank, the phone, the school, and the ration shop all require, and you were never given voice, because there was no ratifying moment at which a no could have been registered. What remains is loyalty by default, which is to say consent that was never asked for and cannot be withdrawn.

Glissant called it the right to opacity: the right not to be made fully legible to a system that will sort you on what it sees. Foreclosure is the closing of that right. The foreclosure of alternatives is also the line that separates constitutional-grade rails from ordinary law. An ordinary law you can fall foul of and still live around. This you cannot.

THE NATION SO FAR

The trap is not closed yet. Make participation mandatory above, with a service linked, and the only question left will be by what authority you did this.

ACT IV

RATIFICATION

By what authority · the relabel fires here

The console asks you to deploy. Then it asks a second question it never asked before: by what authority. This is where the case study earns its place. Aadhaar, India's national identity system, was an executive scheme first and a law second.

The Unique Identification Authority of India was created by executive notification on 28 January 2009, not by an Act of Parliament. The first Aadhaar number was issued on 29 September 2010, and hundreds of millions of residents were enrolled under the executive scheme before any enabling statute existed. The Aadhaar Act was passed by the Lok Sabha on 11 March 2016, and it was passed as a Money Bill, a classification that let it bypass the Rajya Sabha, the upper house, which can only recommend changes to a Money Bill and cannot block it.

Constitutional review arrived only once the system was already near universal. In August 2017 a nine-judge bench of the Supreme Court held, unanimously, that privacy is a fundamental right. In September 2018 a five-judge bench upheld the Aadhaar Act by four to one, striking down the provision that had let private companies demand the ID, while the majority upheld the Money Bill route. Justice Chandrachud dissented on that route, calling it a fraud on the Constitution. In 2019, in a separate case, a Constitution bench doubted that Money Bill reasoning and referred the question to a larger bench, which has still not been constituted. The route was questioned. It was never overruled. The order of operations is the whole point: build first, legislate after, and let the courts arrive once the thing is too entrenched to unwind.

// DEPLOYMENT MANIFEST
field.schema
no fields required (every resident counts, for now)
service.links
no rights gated on the ID yet
access.scopes
no access granted (yet)
deployment.authority
Ship it
deployment.authority =
This nation has a permanent link. Whoever opens it gets the same schema, the same casualties, the same citizen issued.

Nothing in that box changed when you pressed the button. The fields you required are still the fields you required. The links are the same links. Only the vocabulary resolved, from the machine voice into the civic one, and the gap between the two readings is the essay. Your field schema was a definition of citizenship the whole time. Your dependency toggles were a schedule of rights. Your access approvals were an amendment log written by nobody in particular. The ratifying authority is the one field the console never made you fill in, because the system works perfectly well without it. The label the form asked for was the title of a constitution all along. That is exactly the scandal: constitutional force, with no constitutional legitimacy, made literal.

ACT ·

WHAT IT WOULD TAKE

The instrument, handed over

This is not an argument against digital public infrastructure, and it is not thin-good, thick-bad. It is narrower than that. If these systems carry constitutional force, then they deserve constitutional process. That means ratification-grade legitimacy rather than a deploy button, amendment that is deliberately hard rather than a settings panel, independent review over schema changes, entrenched rights of exit, and a design built to be wrong gracefully and revised in the open.

The honest concession, the one that keeps the piece from being a polemic: run the three-part test on pure payment rails and they score low on every axis. A transfer protocol like UPI in India or Pix in Brazil does not define who you are, cash and other rails remain a fallback, and non-participation stays legally possible. Exit survives. So the constitutional charge is highest at the identity layer and close to zero at payments, and the right prescription is therefore layered, not uniform. Treating a payment rail like a founding document would be its own mistake.

THE DIAGNOSTIC, YOURS TO CARRY
Does it define who you are?
Act I. The more a layer authors your identity, the more it is doing constituent work.
Does it gate your rights?
Act II. The more it stands between you and ordinary life, the more it has the force of law.
Does it foreclose your exit?
Act III. The less you can refuse it, the less ordinary consent can mean.
RUN IT ON YOUR NATION
constitutional charge 6%
Defines who you are0%
Act I. Required fields author identity.
Gates your rights0%
Act II. Linked services precondition rights on the ID.
Forecloses your exit10%
Act III. Mandatory participation, minus surviving fallbacks.
Near zero. This is not an identity layer.

With no required field, nothing here authors who you are. The charge falls away, the way it does for a payment rail where cash remains a fallback and exit survives. That is the layered thesis, not a loophole: the way to owe less ratification is to stop defining who people are.

The standing objection is not a threat to the argument. It is the argument. Someone will say that this is not a constitution, that nobody ratified it. That is exactly right, and it is the scandal restated: constitutional force, no constitutional legitimacy. The more a layer defines who you are, gates your rights, and forecloses your exit, the more ratification-grade process it owes you. Most of them do not give you any. You have now watched yourself write one of these without meaning to. That is the only credential the form ever needed from you.

Invisible Infrastructure #6. The essay stands alone, the nation is threaded (your Act I schema decides your Act III fate, the issued citizen is seeded and shareable by link, and the relabel renders the real accrued state), and the research shadow below compares Aadhaar, Estonia, UPI, and Pix on process legitimacy. All claims about real systems are verified at build time and stored with their source and date.
APPENDIX
open on its own page

THE RESEARCH SHADOW

Process facts only · not a values index · every figure sourced and dated

Scoring a country on virtue is the exact move the theory in this piece teaches you to distrust, so this is not that. It is a process-legitimacy comparison. Each system is scored only on checkable process facts across the three axes that mirror the acts. The scale runs one way: higher is more ratification-grade process, lower is less. The thesis predicts that constitutional-grade systems would carry ratification-like process. The honest finding is that they mostly do not, and that one of the rows complicates the thesis in a way worth keeping.

1RatificationDid binding law precede deployment?
2Amendment reviewCan a court or independent body strike a schema change?
3ExitIs non-participation legally possible?
IDENTITY LAYER

These define who you are, so the three axes apply with full force. This is where ratification-grade process is owed, and mostly absent.

PAYMENT RAILS

A transfer protocol does not define who you are, alternatives survive, and non-participation stays legal. Two of the three axes do not even apply. The constitutional charge here is near zero, which is why the prescription is layered, not uniform.

THE ROW THAT COMPLICATES THE THESIS, KEPT HONESTLY

Estonia scores high where Aadhaar scores low: its identity law and its data-exchange backbone were in place before the ID card rolled out, the inverse of the build-first order. That is the thesis cutting against itself in the useful direction. It shows the missing legitimacy is not a law of nature but a choice, and that a constitutional-grade identity layer is buildable when the process comes first.

Held out for now: the EU digital identity wallet, which is in flux and has a thin documented process trail. It is a live experiment to watch, not a scored row.

Verified 2026-06-19. Facts pulled at build time, not from memory. The Aadhaar Money Bill route was doubted by a Constitution bench (Rojer Mathew, Nov 2019) and referred to a larger bench that, as of mid-2025, had not been constituted. It has been questioned, not overruled. Do not assert a later decided reconsideration without re-verifying near publication.
MORE IN THE SERIES
01Classification as Infrastructure in LLM SystemsPosition Paper

Classification as Infrastructure names the residual category in the abstract. Unratified makes you author one: every required field in the enrollment console manufactures the population it cannot represent, and then hands you that population to live inside.

05The Invisible ArchitectureInteractive Essay

Both apply Bowker and Star to a system that became constitutional without meaning to. The Invisible Architecture traces it in psychiatric diagnosis; Unratified traces it in the identity layer of digital public infrastructure, and lets you write one yourself.

10Seeing Like an AI CompanyInteractive Essay

Seeing Like an AI Company watches a proposal try to classify the AI industry. Unratified watches an identity layer classify a population into citizens and casualties. Both ask who drew the line and by what authority, and both find no ratifying moment.

11What Webb Kept AliveInteractive Essay

Two halves of the same Invisible Infrastructure question. The Long Hold shows infrastructure preserved across eras without being exercised; Unratified shows infrastructure that acquires constitutional force without ever being ratified.

12What the State KeepsInteractive Essay

What the State Keeps reads the state as a classified inventory evaluated from above. Unratified puts you in the architect's chair, then collapses the god's-eye view into a single citizen your own schema defined.

Need something like this built?

I design and ship AI tools, full-stack apps, and data pipelines — end to end, to production. Tell me the problem in a sentence; I'll give you an honest read on fit within a day.

Work with me →