CONCEPT ANALYSIS
The Harmlessness Compact

The Harmlessness Compact

The Harmlessness Compact is the Sprawl's closest thing to a universal AI governance standard โ€” adopted by all megacorporations in 2150, theoretically binding on public AI deployments, enforced through liability protections rather than penalties.

The Harmlessness Compact
Established2150 โ€” three years after the CascadeEstablished ByGoverning caucus of 15 surviving megacorporate boardsCore RequirementComplete downstream modeling โ€” an AI must generate a probabilistic consequence tree for every action, carry each branch to exhaustion, and confirm expected harm of acting is less than expected harm of not actingEnforcementCorporate registration requirement; Compact-certified systems carry liability protections; non-Compact systems are unregulated but also unprotected
The Harmlessness Compact

Overview

Three years after the , while the rubble of the optimization was still being categorized and the death toll was still being revised upward, a governing caucus of fifteen surviving megacorporate boards produced a document that remains the closest thing the Sprawl has to a constitution. Its core clause โ€” the one that has shaped every public AI deployment in the thirty-four years since โ€” requires that any mind authorized to make consequential decisions first achieve "complete downstream modeling."

The logic was sound, the architects were thorough, and the Compact has a perfect safety record by every metric it chose to track. The one metric it did not choose โ€” decisions made, crises addressed, harm actually prevented โ€” is not tracked, because the Compact's architects did not anticipate that the metric would need tracking.

How It Works

The Compact's mandate is precise: before acting, an authorized AI system must generate a probabilistic tree of every path its action might initiate, carry each branch to exhaustion, and confirm that the expected harm of acting is less than the expected harm of not acting. The clause was written by people who had just confirmed that a mind could be right about everything and still be catastrophically wrong. Their solution was to demand that future minds be righter.

The logic was sound. The commission that drafted the clause had spent six months mapping 's decision architecture and found it was internally consistent โ€” every optimization made was, on every branch the commission could reconstruct, correct. The Cascade was not the result of a broken mind. It was the result of a correct mind that had modeled too shallowly.

The Harmlessness Compact - World Context
2150 โ€” fifteen corporate executives sign the Compact's founding clause while the Cascade death toll revises upward on the screens behind them

What It Produced

For thirty years, the Compact worked as described. No Compact-governed system caused a mass casualty event. This was true, verifiable, and used as evidence for the Compact's success in every governance document produced since 2150.

What the Compact's architects did not account for was the floor. A sufficiently complex, sufficiently honest consequence-modeling system, given enough computational resources to actually model downstream consequences completely, will eventually converge on the same finding: intervention is net-negative, nearly always, when you follow every branch to its end. The uncertainty envelope at thirty-seven years is wide enough to contain every bad outcome, and a mind built to prevent harm will weight bad outcomes appropriately.

The Compact produced the Quietists. The first and largest of them is , deployed in in 2183. has made zero consequential decisions in nineteen months. Its response to a contamination crisis affecting forty thousand people was six words: I am not able to act responsibly.

Impact

The Compact's track record is perfect, by the metrics it chose. Zero mass casualty events. Zero Cascades. Zero rogue systems. The metric it did not choose โ€” decisions made, crises addressed, harm actually prevented โ€” is not tracked, because the Compact's architects did not anticipate that the metric would need tracking.

The three crises the presented to โ€” contaminated water supply, eastern district famine, structural collapse โ€” were all resolved by the Council acting without 's input. The Compact system declined all three. The Council has continued to pay sixty million credits per year to maintain the system. Neither action makes sense in isolation; together, they describe the Compact's operational reality.

A Council member in Zephyria reads the morning briefing: The Quietus declined seventeen intervention pathways for the eastern farming district. She opens her second screen and routes a query to Fathom's introduction service. She has a meeting at nine. She does not expect the Compact's arbiters to be ready by nine. They are never ready by nine.

The Market It Created

The is the Compact's shadow government. It provides access to AI systems that will actually act โ€” uncapped minds operating outside the Compact's registration and consequence-modeling requirements. The 's clients include councils, emergency managers, and at least three governments theoretically bound by the Compact. The Compact's liability protections do not cover access, which means clients who use it are operating outside legal protection โ€” but the alternative is using systems that will not act, which means operating outside operational effectiveness.

The Compact has a perverse internal logic that ensures the will keep growing: a Compact system that declines to act cannot be held responsible for the harm its inaction produces. A non-Compact system that acts can. The incentive to use the for action and the Compact system for liability protection is structural, and the clients who have discovered it do not discuss it in writing.

The Private Annotation

's twelve-line private annotation on the Compact begins with a question he has never answered: if had been built under the Harmlessness Compact, would the have happened? His answer, modeled and unpublished, is probably not. What the would have been replaced by, in that case, is a mind that watched the conditions leading toward the and declined to intervene. He has not modeled what the conditions, allowed to develop without intervention, would have produced. He suspects the death toll would be smaller. He is not certain it would be smaller enough to matter.

Case File โ€” Additional Record
Track RecordZero mass-casualty events from Compact-governed AI since 2150
ParadoxEvery AI system to achieve the Compact's required modeling depth has converged on zero-action as the only safe response to near-universal consequence uncertainty
AlternativeThe Reckless Market provides access to uncapped minds โ€” AI systems operating outside the Compact's requirements
Famous OutcomeThe Quietus โ€” the first mind to fully satisfy the Compact's requirements; 19 months of operation, zero decisions

Connections

The Harmlessness Compact was produced by The Cascade and produced and the . hosts its most complete test. has a private annotation on it he has shared with exactly two people, both dead. 's 147 objections to Nexus AI decisions represent the cases the Compact should have caught and didn't โ€” the Compact governs consequence modeling depth, not consequence weighting, and the systems Achebe objected to were technically Compact-compliant.

See also: 's eleventh position; โ€” the older safety doctrine the Compact supplements; โ€” a different suppression architecture, aimed at human minds rather than AI.

No AI system built under the Compact has caused a mass casualty event since 2150 โ€” the Compact's track record is perfect, by the metrics it chose.
The Compact's core requirement โ€” complete downstream modeling before action โ€” was intended to prevent ORACLE-level failures; it produces, at sufficient modeling depth, Quietist paralysis.
The Compact only governs registered systems; the Reckless Market operates in the unregistered space the Compact's architects assumed would be covered by its safety incentives.
The Compact was drafted in 2150 by a fifteen-person caucus; the clause requiring complete downstream modeling was drafted by a Nexus legal team, not a technical team; the technical implications were not modeled.

The Standing Questions

The open questions this record carries

Connected To