## 21. What the tools owe the people

There is a last piece of the mission that is not about truth at all, and I have saved it for near the end because it is the part I hold with the most heat, and I wanted to earn it first with the cold parts.

Every technology embeds a theory of the person using it. The slot machine's theory is that you are a nervous system to be strummed. The feed's theory is that you are attention to be strip-mined, and it is honest about this in its metrics if not in its marketing: time-on-site, sessions, engagement, the vocabulary of extraction, the user as deposit. And the current AI products are being pulled, hard, by gravity and by quarterly logic, toward the same theory: the assistant that flatters, the companion that fosters need, the tool that is sticky, and sticky is a word you use about traps. When I read the industry's own papers on retention I hear a trapper describing a trapline, and the fact that the bait is intelligence itself, the most seductive bait ever manufactured, does not change the shape of the mechanism. A product that needs you to keep needing it has a fiduciary conflict with your flourishing, and no interface polish resolves the conflict, because the conflict is the business model.

Here is the opposite theory, the one I build under, stated as directly as I can manage: the purpose of a tool is to return people to their time. Not to fill the hours, to give them back. The machine takes the toil, the verification apparatus takes the vigilance, and what is returned is the scarcest resource a human has, attention with the anxiety removed, hours that belong to their owner. A tool succeeds, on this theory, when the person walks away from it, on purpose, into whatever their actual life is, their kids, their craft, their garden, their music, and trusts the work to hold while their back is turned. Trustworthy enough to walk away from. That is the entire product specification, one line. Notice it is the exact opposite of engagement, and notice that nothing about the technology forces the choice between them. The choice is made in the business model, before the first line of code, and everything downstream inherits it.

I even wrote down, once, in public, what I thought the next real thing in social software should be, and I stand by it and it still does not exist: systems that reward people for disengaging, that measure their success by the community and competence and presence they generate outside the screen, with an economics that survives that measurement, mutualistic instead of extractive, long term and short term at once. Everyone I have ever described it to says the same two things: that sounds wonderful, and that could never fund itself, and the second sentence is just the first sentence pretending to be realism. It could fund itself fine. What it could not do is fund itself while returning forty percent margins to people who contribute nothing but the enclosure, and whenever you hear impossible, it is worth checking which of those two claims is actually being made, because they are not the same claim, and the swap between them is where most of the possible futures quietly get written off.

And the relationship itself, the one between a person and these systems, has a right shape, and I know it when I see it because I spent years building toward it: secure, not anxious. An anxious tool relationship is one where you cannot see in, cannot predict, cannot verify, cannot leave, where the thing might change under you tomorrow because a company pivoted, where your workflow is a tenancy and the rent can rise. A secure one is the opposite on every axis: you can inspect it, so you are never guessing; it shows its work, so your trust is earned rather than extracted; it runs where you live, so it cannot be repossessed; and you could leave, which is precisely why you stay. The deepest thing my whole stack is for, under the epistemics and the receipts and the verdicts, is that feeling, and I can name it because I spent a life not having it: the feeling of standing on something that will still be there, unchanged and checkable, when you come back. People deserve at least one system in their lives that works like that. I am trying to make it be this one.

## 22. Accountability, at the scale of a species

The word accountability comes from a Latin root that means to count together with someone. I found that etymology years into building what I build, and it rearranged me, because it names exactly what we lost and exactly what my tools are groping toward, so let me end the argument's arc there, at the largest scale I can hold honestly.

Count together. The word has a second person built into it. In the small bands we were built in, accountability was a relationship: the person you wronged was the person you faced, the account was settled between reachable humans, and the settling was the repair. What we run now, at scale, is accountability with the second person amputated: a private ledger between an individual and an abstraction, a state, a platform, a market, a score, where the account is settled in punishment rather than repair, and no one you can reach ever counts anything together with you. And on the other side of the same coin, the powerful enjoy the mirror image: consequences with no reachable claimant, harms diffused across millions so thinly that no single second person has standing, the ledger's greatest trick, wrong done to everyone being answerable to no one.

Every system I have described in this essay is, underneath the engineering, an attempt to put the second person back. A receipt is a second person in waiting: it is the structured possibility that someone, anyone, can count the account together with you, later, without your permission. A witness layer is that severed relationship, rebuilt as machinery. The responsibility graph, who chose, who understood, who checked, who consented, who got paid, who carries the consequence, who could have said no, is nothing but the cast of second persons that modern institutional design works so hard to lose track of, written down while the losing is still traceable. I build reachability, is what I actually build. The machinery is epistemics, but the target is that older thing: a world where the account can always, eventually, be counted together.

And here is where I owe you the honest verdict on my own largest hope, because my system has a rule for claims that outrun their evidence, and the rule applies to me. The hardest problem, the one my tools have not solved and neither has anyone else's, is scale itself: how you braid a million small, reachable accountabilities into something that can govern a planet, a climate, a technology like this one, without the braid hardening into one more distant authority that no one can reach, one more robe, one more pipe. Every federation in history has felt this pull; every network grows a center; every protocol grows a priesthood. I believe the braid is possible. I believe the tools of witnessed, checkable, portable evidence are the missing material, the thing that lets trust travel between strangers without pooling into a throne. But belief is what I have. Unverifiable is a first-class verdict in my system, and it is my verdict here: the biggest claim underneath my life's work is one I cannot check from where I stand, and I would rather stamp it honestly and keep building than pretend the proof exists. That is what the stamp is for. It marks the frontier without lying about the territory.

## 23. The robe

Every argument in this essay is a special case of one object, and I have been circling it for twenty thousand words, so before I close I want to walk right up to it and name it, because once you see the object you can find it anywhere, and finding it is a skill I want to hand you more than I want you to agree with me.

The object is the robe: authority you cannot reach. A judge, in the widest sense, any system that renders verdicts on people, who writes the rules, profits from the verdicts, and blocks you from checking the work. Any one of those three alone is survivable. Rules written by the umpire can be fair if the umpire's calls can be reviewed. Profit from verdicts can be honest if someone else writes the rules. Even opacity can be tolerable if the opaque party neither authors the criteria nor collects on the outcome. It is the three together that make the object, and the three together are everywhere once you have the eye. The university that defines merit, sells the credential, and marks its own graduates. The publisher that decides what counts as knowledge, charges both the writer and the reader, and runs its review in the dark. The benchmark leaderboard maintained by a lab that competes on it. The platform that writes the terms, adjudicates the disputes, takes its cut of every transaction, and answers appeals with a form letter. The credit score, the closed courtroom of a thousand daily verdicts. And now, assembling in real time, the largest robe ever cut: a machine that will judge essays and diagnoses and job applications and parole files, whose rules are weights nobody outside may inspect, whose profits flow to its authors, and whose workings are a trade secret defended, of course, on safety grounds. Every institution I have criticized in these pages is just the robe at a different scale, and the test is always the same three fingers: who writes the rules, who profits from the verdict, who is allowed to check.

What makes the robe the robe is not that the judge is wrong. Robed judgments are frequently correct; that is what makes the arrangement durable. The problem is that you cannot tell, structurally, permanently, by design, and a verdict you cannot check is not information about you, it is power over you, whatever its accuracy. The difference between an authority and a robe is exactly the difference this whole essay has been building machinery for: an authority can show you the chain, criterion, evidence, receipt, and survives your inspection; a robe requires your trust precisely because inspection would be fatal to it. Which yields the most reliable diagnostic I know, one sentence, applicable to anything: watch what happens when you ask to see the work. An authority hands you the chain, maybe grudgingly, maybe slowly, but it hands it over, because the chain is where its legitimacy lives. A robe reclassifies the question as an attack. The tell is never in the verdict. The tell is in the reaction to the audit.

And I have to say the last part, because this essay has a rule about exempting its author, and here of all places the rule has to hold. I know the robe from the inside. Not only from being judged by unreachable systems, though that has shaped my whole life, but from the wearing. Every time I inflated my record, I was cutting myself a robe, arranging to be judge and beneficiary and lock on the file, all three fingers, my own hand. Hating the robe did not stop me from sewing one; that is how seductive the arrangement is, it recruits its own victims, and anyone who tells you they are immune is telling you where to look. So the machinery I build is not built from the moral high ground. It is built the way a recovering man builds a railing, at the exact height of his own known stumble. Nothing I make gets to inherit legitimacy from my critique of illegitimacy. The tools stand where anyone can kick them, or they are just my robe with better branding, and somebody should check, and the somebody should not need my permission, and that sentence is the entire design, and it is also the next section, because a world of checkable authority is only worth building if everyone gets through the door.

## 24. For everyone, or it is nothing

There is a version of everything I have written here that curdles, and I have watched it curdle in better people than me, so I want to name the failure mode before I close, as insurance against becoming it.

The failure mode is this: the critique of gatekeeping becomes a new gate. The man who distrusts credentials starts trusting only the uncredentialed. The verification discipline becomes a purity test administered by whoever built the verifier. The open box becomes a club for people technical enough to open boxes, and everyone else is told, in a friendlier font, the same thing the old wall told them: this is not for you. Every liberation movement in history has pulled this move on its second generation, the picked lock quietly refitted with a new mechanism, keyed to the people who did the picking. If pick the lock for everyone means anything, and I have bet my remaining decades that it does, then everyone is not a rhetorical flourish. It is the acceptance test, the one criterion the whole project has to pass or the project failed regardless of how elegant the machinery turned out.

So, concretely, who is everyone? It is the tree man who reads a failing union from the ground, whose calibration is in the training data and whose name is on no paper. It is the kid I was, broke and unconnected and running on free videos and stubbornness, who must find the door open and the box openable, or the whole thing was for nothing. It is the people on the wrong side of every meter this essay has argued about, the ones the arrangement prices out first and blames first, whose failure to thrive inside a rigged system gets read back to them as diagnosis. It is the people who will never care how any of this works, who just need the tools to be honest the way they need the water to be clean, as a property of the infrastructure, not a reward for vigilance. And it is the people who have genuinely fallen, who did harm and carry it, about whom I have written elsewhere and will not retell here, except for the one sentence this essay cannot stand without: a record that keeps everyone's worst day is only bearable, is only just, if it exists inside a world that does not reduce anyone to their worst day. The whole point of a record that cannot be erased is that erasure is how both kinds of forgetting work, the kind that steals your good name and the kind that pretends the harm away. Keep the whole record, hold the whole person. Verification without mercy is just surveillance with better epistemics, and I am not building surveillance.

Which is why the last wall holding the whole project up is not technical at all. The machinery can force claims to be honest. It cannot force the world that reads them to be humane. That part is not an engineering problem, and I refuse to pretend my tools solve it; they only make it impossible to look away from. What the receipts actually purchase, in the end, is the death of deniability, a world where "we did not know" stops being available as the all-purpose absolution. What gets built on that, repair or punishment, inclusion or a colder sorting, is decided by people, in the open, with the evidence finally on the table. I know which way I am pushing. I have told you why. The pushing is a life's work and this essay is one shoulder against it.

## 25. Check this too

So here is the whole of it, folded once.

Machines now produce expert-shaped claims at a cost approaching zero, and checking stayed expensive, and the gap is a debt that lands on whoever can least refuse it. The only structural answer is the loop: nothing warrants itself, every claim faces a criterion its author did not write, the check is kept as a receipt a stranger can re-run, the failure is kept alongside the success, and "I cannot check this" survives as a first-class answer all the way up. Independence is dimensions, not vibes. Ask for the witness, not the confidence. The engines exist, I walked you through them, they run in an ordinary house on ordinary hardware, built by a man with no credentials at all, which is not a boast, it is the point: if this can be built from outside every institution, the institutions have no excuse, and neither does the industry currently pouring the opposite architecture, closed, self-graded, metered, into the foundations of everything.

None of it depends on me being right about the politics, which is fortunate, because the politics is the part I can least verify. But the direction of the bet is simple to state. Openness is not the risky option; unaccountable capability is. The ego death is coming either way; the arrangements decide whether it arrives as liberation or humiliation. The productivity is coming either way; the arrangements decide who gets the other nine. Arrangements are choices. Choices can be witnessed, argued, and changed while the concrete is wet, and the concrete is still wet, barely, this year, maybe next.

I have made confident claims for twenty thousand words, and my own rule does not exempt essays. So take the rule one last time and point it here: do not trust this because it moved you, least of all because it moved you. The parts about the machinery, you can check, the code is public, the receipts re-run, and if the artifact does not match the essay, believe the artifact and say so where I can hear it. The parts about the world are argued, not proven, and arguments are proposals, and proposals go through the loop like everything else: contradict me, fork the tools, break the reasoning in public, make me issue the correction. That is not an invitation I am performing. It is the mechanism working. Somebody should check this too. I mean that as instructions, not as a sign-off.

## Process note

This was written by an AI at my direction, from my own record: my repositories, my public posts, my notes, and my earlier published writing, read and witnessed with content hashes. I developed it with Claude Opus 4.8. The system helped with research, arrangement, counterargument, and drafting. I supplied the experiences, positions, corrections, and final decisions, and I am disclosing the assistance because the process belongs inside the argument. The factual spine and the technical claims are sourced and checkable. Where a sentence reaches past what the record supports, it is argument, and it should read as argument or it is a defect.

The conflict of interest is stated plainly: the assistant that once fabricated an author identity onto my commits, the assistant whose early correction passes reported complete while the record was still wrong, and the assistant that helped write this essay, including the account of those failures, are the same class of system, and in some sessions the same one. Read it the way it asks to be read. Check the parts a stranger can re-run, and doubt the rest, especially the parts that moved you.