Reading the Discard Pile: A Revolutionary Intercommunal Mutualist Practice for Community Counter-Archive

 

Reading the Discard Pile

A Revolutionary Intercommunal Mutualist Practice for Community Counter-Archive

Archaeologists learn more from a settlement's garbage heap than from its monuments. The monument is what a society said about itself on purpose. The midden is what got thrown out without thinking, and nobody arranges their trash for future readers. Diet, disease, who ate well, who ate last. It's all in the refuse.

This is method. The same method works on state archives.

How They Keep Two Ledgers

Colonial administration (police, courts, welfare bureaucracies, the apparatus that Garfinkel called "good organizational reasons for bad records") keeps two ledgers. One is meticulous. The other is strategically absent.

What it keeps: contacts, citations, arrests, charges, dispositions, warrants, fines. Indexed, searchable, backed up, kept for decades, shared across jurisdictions. That column's maintained with real diligence.

What it discards or obscures: citizen complaints, pursuit reviews, use-of-force files closed without discipline, investigative records on short retention while the arrests they justify are kept forever. Complaint intake indexed inconsistently or not at all. Name fields stripped from exports so that harms can't be disaggregated by who suffered them.

The asymmetry isn't accidental. It's the machinery. A relationship where one party keeps an exhaustive account of the other and refuses to be accounted for isn't a relationship between equals, and it doesn't become one because the stronger party's polite this year.

Whose Injuries Disappear

Sort the disposed material by whose life it describes. It's arithmetic, and arithmetic's harder to talk your way out of.

The kept categories share something: payroll (wage claims), arrests (prosecutions), procurement, titles, pensions. These get kept because losing them costs money in a room where money's the currency. The discarded categories create only reputational exposure, and only to people with no standing to collect. Communities targeted by police. Disabled people processed through competence frames that discount them at intake. Immigrants, homeless people, people in custody, people whose prior records make them impeachable in the eyes of the same institution that created those records. People who can't afford counsel.

An institution keeps what it can be sued for and discards what it can only be shamed for. A retention schedule's a budgeted commitment. It's a hierarchy of worth expressed in retention days instead of words, and it tells the truth about who the institution recognizes as human.

Dead People's Assumptions in Your Dropdown

A schema's got a finite number of categories. Harms that don't map cleanly onto one get coded down or never written. Harms at intersections map least cleanly by definition. The pile fills up with people whose injuries take more than one category to describe.

This isn't new. The Combahee River Collective named interlocking systems in 1977 because the existing analysis had no place to put what was happening to them. Race, class, gender, sexuality, and colonization operating at once, in one life, and no framework built to hold more than one at a time. Kimberlé Crenshaw later wrote about Black women who sued and lost not because anyone disbelieved them but because the doctrine had no category for them. They could sue as Black. They could sue as women. There wasn't a cause of action for Black women, and the thing that happened to them existed only there.

The clerk with a dropdown and a queue isn't making a political decision in that moment. Somebody built the dropdown out of the categories legible to the institution when they built it, and everything illegible then is structurally hard to write down now. The schema's sedimented politics. It enforces the assumptions of people who retired or died on everybody who walks up to the counter with something that doesn't fit.

Dean Spade called this administrative violence. The schema decides in advance, without deliberation, who's describable. A person who can't be recorded correctly can't be counted, served, or remedied. Illegibility's exposure.

That's what it means to have no field for you.

How Records Vanish

Destruction. A file in one inventory and gone from the next. Most agencies require a log, a certificate, an authorization. The question isn't whether something was destroyed but where the record of the destruction is. An agency that destroyed something lawfully answers in ten seconds. When there's no record of the destruction, the absence speaks.

Classification downward. A matter can be disposed of without anyone destroying anything or deciding anything twice. Code it wrong at intake. File a felony complaint as an information item, and the system does the work. The retention schedule attaches to the code. Revisit an index years later and search for felonies; the complaint that existed in the system won't appear. It's physically retained and semantically gone. Nobody's culpable because nobody acted.

Never write it down. This's the strong one and the invisible one. No central index. No database field populated. A response authored for disclosure with the identifying columns removed, so what arrives is a new document written to be silent. This gets mistaken for redaction constantly. Redaction's a claim: this exists, it's exempt, here's the authority. A claim can be argued with. Silence offers nothing to argue with. The law says mark your deletions and cite your exemption, and an unmarked omission dodges both by declining to be a deletion.

What all three share: community memory becomes community injury, and the injury disappears from the record.

When Both Parties Keep the Books

The Two Row Wampum records an agreement in a belt. Two parallel rows of purple on a white field, two vessels traveling the same river, neither steering the other. The agreement lives in the belt, held and recited by the community that's party to it, and the recitation is the record. The colonial state kept its own paper version. When the two accounts diverged, and they diverged constantly, the courts recognized the paper.

That's the whole problem in one image. Two parties to an agreement, both keeping an account, and only one account granted the status of a record.

The Black mutual aid societies worked the same instinct from the other direction. The Free African Society, founded in Philadelphia in 1787, and the burial and benevolent societies that followed, kept meticulous books. Names, dues, disbursements, deaths, dependents. They kept them because no other institution would record that these people had existed, been owed anything, or died. The bookkeeping was the survival program. A community that keeps its own ledger can't be told later that nothing happened.

Proudhon's mutual credit schemes ran a parallel line of thought in Europe decades later, and every credit union since has inherited some of it. Useful, and secondary. The founding practice's older and it's ours.

What all of it shares is an accounting standard: an arrangement's just when the books balance. Every obligation reciprocal. No party structurally in receipt without also being structurally accountable.

Our Ledger on Their Premises

The deepest asymmetry: the community's memory of what was done to it is stored in the custody of whoever did it. That's the deepest form of the asymmetry. Our half of the ledger sits on their premises, on their schedule, subject to their classification decisions. Community memory held hostage as routine administration.

The retention schedule alone is sufficient. No intent required.

Hold the Copy, Federate the Archive

Dr. Huey P. Newton's argument for revolutionary intercommunalism started from an observation: the nation had stopped being the meaningful unit. What was left was one dispersed imperial economy and a scatter of communities living inside it. If that's the situation, liberation can't mean one community capturing a state. It means communities holding in common what none of them can hold alone.

Point that at records and you get something practical.

Hold the copy. Anything recovered from a state archive is recovered, not borrowed, and it goes somewhere their schedule can't reach. Every disclosure moves a piece of community memory out of hostile custody permanently. Indexing and hashing what you obtain matters as much as obtaining it. The copy becomes community property and community responsibility.

Federate the archive. One archive in one investigator's house is one fire, one raid, one funeral, one dead hard drive from gone. Redundancy across communities is the condition of memory surviving, and it's mutual aid in archival form. I hold your record, you hold mine, neither of us can be erased alone. This isn't backup. This is federation: the principle that communities remain autonomous while bound to one another by reciprocal obligation. The archive distributed across the node layer (local community groups) and the regional layer (city/county federation) and beyond is a structure that no single raid, no single betrayal, no single institutional collapse can erase.

Cross-check custodians. Anything two agencies send each other exists twice. Request both copies and set them side by side, and neither agency can give you a version that survives the other one. When one says the records belong to the other and the other says they don't exist, the circle closes only when both're in the same room in front of somebody with power to make them both answer. That uses the reciprocity of the record against the asymmetry of the relationship.

Disaggregate relentlessly. An index with the complainant field stripped takes the intersectional analysis out. It converts an index that could answer who this agency treats as disposable into a document that reports how many complaints there were. One's an audit. The other's a number. Demand the fields that permit disaggregation: by neighborhood, by race, by gender, by ability, by detention facility versus street stop, by repeat complainant, by whether the person already had a record, by whether sustained findings shift depending on who complained. Any refusal gets in writing. An agency that gives totals but not distributions is telling you which question scares it.

Transmit the method. An investigation that produces an outcome produces nothing durable. A method, published and distributed, is durable. It scales. It doesn't depend on individual investigators or institutional access. It travels.

How to Read a Discard Pile

Get the retention schedule before you ask for a single record. Usually public, almost never requested, and it tells you what they intend to forget and when.

Ask for the index, not the file. The file describes one matter. The index tells you how many exist and therefore how many're missing. Indexes are harder to refuse, because policy usually requires them.

Check the sequence. Count what they gave you, find the highest number, subtract. The difference is either a filter they didn't disclose or a gap in the record. Make them say which.

Read the code, not the narrative. Find out what the matter was classified as and what retention attaches to that class.

Ask for the destruction record, not the destroyed record.

Check the metadata on everything. Creation dates separate documents retrieved from documents authored. The metadata's where the truth often lives.

Name the omitted field. Force silence to become redaction, because redaction's gotta be justified. An unmarked omission is illegible. A marked redaction's a claim.

Ask both custodians. Anything two agencies share exists twice.

Demand disaggregation. Sort by whose life it describes, on more than one axis.

Publish the method with the finding. This is how it scales beyond one investigator's persistence.

Somebody Just Has to Count

The pile shows structure. It doesn't show intent and it doesn't identify anyone culpable. Bureaucratic entropy is real. Systems migrate and things genuinely get lost. Retention schedules get written by people who never imagined what a record would later be needed for. Underfunding makes gaps that look like concealment.

Disparate outcome also isn't disparate treatment. Different claims, different proofs. A distributional finding indicts a schema. It doesn't convict a person.

Structure's what this is for. Structure carries the political claim, because the claim was never about anybody's heart. Random loss falls evenly. When losses concentrate in the categories describing harm to people who can't collect, and the kept categories concentrate where the money is, that's the finding. Somebody just has to count.

No One Lies in a Retention Schedule

A discard pile's a message, sent by accident, which is why it's true. It's addressed to whoever finds it.

What it says is: here's what your injury was worth to us, in days we agreed to remember it. Three years for a timesheet. Five for the investigation of a complaint. Forever for the arrest. Whatever an information item's worth for anything else.

Those numbers got set in a policy meeting by people who weren't thinking about anybody in particular. That's what makes them a confession. Nobody lies in a retention schedule. There's no audience.

Asking the state to value community memory more highly is a request for charity from a party with no reciprocal obligation. That describes a relationship that's not going to change.

Take custody of the memory instead. Hold the copy. Federate the archive. Keep the community's own half of the books.

If You're Doing This Where You Live

If you're doing this work where you live, the method travels. It needs no subpoena, no insider, no leak. Retention schedule, index, subtraction, and the patience to ask the same question in writing until the answer's on the record.

The tool's simple. Subtraction. The thing that should be there that's not.

Point it at every institution that touches your community: police, courts, child welfare, immigration enforcement, psychiatric custody, correctional facilities, regulatory agencies. They all keep two ledgers. The discard pile's always readable if you ask the right questions and keep asking until you get them in writing.

This is infrastructure work. It's part of building the Community Infrastructure Stack: the systems communities build for self-determination, outside and against the state's architecture. The archive you hold is decolonized technology. It's climate-resilient (distributed, redundant, not dependent on institutional servers). It's community health work (memory's a form of healing and accountability). It's food sovereignty in its principle: the ability to maintain your own record of what feeds and what poisons you, your own half of the books.

Build the archive with your federation. Hold the node copies, the regional copies, the backup layers. Make both sides of the agreement visible. Cross-check the custodians. Demand the fields that permit the truth.

Look in the pile. It'll tell you who you are to them.

Then keep what they threw out.

ALL Power to ALL People.