Bridge to Implementation
The preceding argument is analytical. What follows is normative.
The book makes twelve claims about the structure of computational governance. Those claims are empirical and structural: they can be right or wrong. The constitutional proposal that follows is a different kind of object: it specifies rights, institutions, and procedures. These can be accepted or rejected, but they cannot be true or false. The relationship between the two is neither deduction nor assertion. It is conditional necessity.
The Structure of Inference
Constitutional reasoning does not deduce rights from facts. It identifies structural conditions under which governance without certain protections produces domination, and then specifies the minimum protections required to prevent it. The logic is: if a structural condition obtains, then a governance framework that ignores it will fail in a predictable way. The article is the minimum institutional response that closes the failure mode.
This is how every serious constitutional tradition has worked. Madison did not deduce the separation of powers from a theorem about human nature. He identified a structural condition (that concentrated power tends toward abuse) and specified the minimum institutional arrangement that prevents the concentration. Locke did not deduce the right to property from the state of nature. He identified a structural condition (that labor intermixed with the world creates claims that antedate government) and specified the minimum protection that any legitimate government must provide.
The inference here follows the same pattern. The book identifies structural conditions of computational governance — tempo asymmetry, compositional failure, quiet foreclosure, domination without a dominator. The articles are the minimum responses. The word minimum is load-bearing. A stronger response would be a permission-based regime, in which computational systems may act only with prior authorization. A weaker response would be a disclosure-only regime, in which systems must describe what they do but need not permit contestation. The receipt regime occupies the constitutional middle: strong enough to make coercion legible and contestable, specific enough to be implementable, modest enough to survive political opposition from those whose interests it constrains.
Other constitutional responses to the same structural conditions are possible. The articles that follow are offered not as the only response but as a sufficient one — precise enough to implement, critique, and improve. Specification disciplines thought in ways that aspiration does not.
From Claims to Articles
Each article below is justified by the structural condition that makes governance without it a form of domination. The justification is not that the article is the best conceivable protection — it is that, given the structural condition, the absence of the article produces a specific and predictable failure of legitimacy.
Article 1. Right to a receipt at time of coercive act.
Structural condition: When decision tempo exceeds participation tempo (C1), the governed cannot contest what they cannot inspect. A system that acts in milliseconds and answers in months has satisfied the form of governance while violating the substance. Without the article: Coercion becomes invisible. Not denied, not justified, simply unrecorded. The affected person has no artifact to contest, no record to appeal, no evidence to present. What existing law provides: GDPR Articles 13-14 require notice. TILA requires disclosure of credit terms. What the article adds: The extension from notice to contestable receipt. Notice tells you what happened. A receipt gives you the artifact you need to challenge it.
Article 2. Right to contest through independent review.
Structural condition: Receipt fields must be sufficient for contestation (C8), and receipt regimes fail in predictable ways (C9). A receipt that cannot be challenged is a record of subjugation, not a tool of accountability. Without the article: The receipt becomes ornamental, filed and archived but never examined. Power generates paperwork without generating answerability. What existing law provides: GDPR Article 22 grants a right to contest automated decisions. The EU AI Act creates risk tiers. What the article adds: The institutional mechanism. GDPR names the right but does not specify who reviews, on what timeline, or with what authority to reverse. This article specifies proportionality tiers calibrated by severity, with critical actions reviewed within days and routine actions within weeks.
Article 3. Right to human review for material adverse actions.
Article 2 guarantees contestability after the act. Article 3 addresses a different question: whether certain acts require an irreducibly human point of authorization or review before their consequences become binding. The distinction is between the right to challenge and the right to a human in the chain of judgment.
Structural condition: Legitimacy requires contestability at human tempo (C1), and local compliance does not guarantee global accountability (C7). A system may be correct in every component and unjust in composition. Without the article: The authorization membrane hollows out. The human who signs becomes a rubber stamp, processing outputs at a rate that precludes comprehension. Accountability attaches to form rather than substance. What existing law provides: The EU AI Act requires human oversight for high-risk systems. What the article adds: Constitutional status. A regulatory requirement can be waived by contract or administrative convenience. A constitutional right cannot.
Article 4. Right to export data, credentials, and relational context.
Structural condition: Contestability requires credible exit (C10). Quiet foreclosure eliminates alternatives through architecture rather than force (C11). If you cannot leave, your right to contest is a petition, not a claim. Without the article: Lock-in masquerades as choice. The user who has accumulated five years of reputation, relational context, and credential history on a platform cannot exit without losing the conditions of their participation. What existing law provides: GDPR Article 20 grants data portability. The Digital Markets Act requires interoperability. What the article adds: The extension from data to credentials and relational context. GDPR lets you export your data. This article lets you export your reputation.
Article 5. Right to present portable credentials.
Structural condition: Without fork rights, receipts become petitions (C10). The trust tax persists through lock-in (C3). Article 4 prevents exit from becoming amputation. Article 5 prevents portability from becoming ceremonial. A credential you can carry but no institution is obligated to recognize is a trophy, not a right. Without the article: Each platform becomes a sovereign issuer of standing, and leaving one means starting from zero at the next. The governed can carry their history but cannot use it. Exit is formally free and practically ruinous. What existing law provides: The W3C Verifiable Credentials specification defines a technical standard for portable attestations. What the article adds: The obligation to accept. Technical portability without a right of presentment leaves the receiving institution free to ignore the credential entirely. This article closes the gap between carrying and counting.
Article 6. Right against cross-domain composition without consent.
Structural condition: Bilateral coherence does not guarantee compositional coherence (C4). Without a mercy threshold, receipted coercion becomes permanent caste (C12). Without the article: A credit decision, a hiring decision, and an insurance decision — each independently compliant, each drawing on different data, none aware of the others — compose into a condition of life that no single actor chose and no single institution can reverse. What existing law provides: No existing framework addresses cross-domain composition of individually compliant decisions. What the article adds: This is the genuinely novel article. It names a failure mode that current law does not recognize: the composition of separately lawful acts into collectively unjust outcomes.
Article 7. Right to time-bounded personal records.
Structural condition: Without a mercy threshold, verification becomes caste (C12). Perfect memory forecloses transformation. Without the article: Every failure, every dispute, every youthful misjudgment persists in machine-readable form, composable across domains, unsealable and unexpirable. The person becomes the permanent sum of their documented worst moments. What existing law provides: GDPR Article 17 grants erasure. The FCRA limits credit reporting to seven years. What the article adds: Constitutional temporal asymmetry. Not merely "you can ask to be deleted" but "the system must structurally forget" — designed forgetting as a constitutional principle, not an administrative convenience.
Article 8. Right to know the rule invoked.
Structural condition: Receipt fields must be evaluable (C8). Domination without a dominator is structural (C7). You cannot contest a rule you cannot name. Due process has always required knowable grounds: nulla poena sine lege (no punishment without a law) is the oldest procedural guarantee in the Western legal tradition. The computational version is: no adverse act without a nameable rule. Without the article: The governed face outcomes without reasons — not because reasons are withheld, but because the system that produced the outcome has no category for reason-giving. Administrative opacity converts power from something that can be challenged into something that can only be endured. What existing law provides: Administrative law requires agencies to state the legal basis for their actions. GDPR Article 22(3) requires "meaningful information about the logic involved." What the article adds: The extension from explanation to evaluability. "Meaningful information about the logic" can be satisfied by a paragraph of boilerplate. A nameable rule can be tested against precedent, compared across cases, and challenged as misapplied.
Article 9. Right against excess data collection.
Structural condition: The trust tax includes extractable surveillance premiums (C3). Quiet foreclosure operates through information asymmetry (C11). Excess collection is not merely wasteful or intrusive. It is the mechanism by which the intermediary converts its position into structural advantage: the more the intermediary knows, the harder it becomes for the governed to exit, contest, or even perceive the scope of the intermediary's authority. Information asymmetry is not a side effect of computational governance. It is the substrate of domination without a dominator. Without the article: Every interaction becomes an extraction opportunity. The coherence fee, the genuine cost of making truth compose, is padded with a surveillance premium that funds the position from which composition is performed. The intermediary's knowledge advantage compounds across time and across domains. What existing law provides: GDPR Article 5(1)(c) requires data minimization. What the article adds: The constitutional framing. Data minimization under GDPR is a regulatory principle enforceable by fine. Under this article, excess collection is a structural condition that enables domination and is therefore constitutionally prohibited, not merely regulatorily punishable. The distinction is between a fine for noncompliance and a constitutional limit on state and corporate power.
Article 10. Anti-waiver: the constitutional floor cannot be contracted away.
Structural condition: Domination persists despite contractual consent (C7). Foreclosure of alternatives makes "consent" structurally coerced (C11). Without the article: The receipt regime dissolves into the terms of service. Every protection becomes waivable by the click that precedes the service. The constitutional floor is contractible, and the contract is adhesive. What existing law provides: ECHR non-derogable rights. TILA anti-waiver provisions. What the article adds: The principle that the receipt regime's protections are constitutional, not contractual. No terms-of-service agreement may reduce the floor below the twelve articles. The right to a receipt is not a feature. It is a condition of legitimate computational governance.
Article 11. Settlement-layer integrity.
Structural condition: Energy structured through computation is the emerging factor of production (C5). Receipt integrity requires a substrate that cannot be edited by the receipted entity (C8). Without the article: The ledger on which receipts are recorded is maintained by the entity whose power the receipts are meant to constrain. The constrained party edits the constraint. What existing law provides: No existing framework addresses this. What the article adds: The requirement that the receipt substrate be structurally independent of the receipted authority. This is the most contested article because it derives from the book's thermodynamic argument. It is also the article most directly connected to the research program's formal results.
Article 12. Mandatory independent audit.
Structural condition: Receipt regimes fail in predictable ways (C9). Compositional failure is computable and therefore auditable (C4). Without the article: The receipt regime is self-certifying. The system that issues receipts also evaluates whether the receipts are adequate. The auditor and the operator are the same entity. What existing law provides: Sarbanes-Oxley requires independent financial auditing. The PCAOB oversees audit quality. What the article adds: Extension from financial to computational governance. The principle is the same — the entity subject to audit may not control the audit. The domain is new.
Alternative Responses
These twelve articles are not the only constitutional response to the structural conditions the book identifies. Two alternatives bracket the space:
A disclosure-only regime would require computational systems to publish their rules, parameters, and decision logs — transparency without contestability. This is weaker than the receipt regime because disclosure without a right to contest is observation without agency. The governed can see what is done to them but cannot challenge it. Disclosure regimes tend to produce informed acquiescence rather than structural accountability.
A permission-based regime would require prior authorization for every coercive computational act — approval before action. This is stronger than the receipt regime but likely unworkable at computational scale. Permission requirements that operate at human tempo would throttle systems that must act in milliseconds. The result would be either paralysis or exemption, and exemption would swallow the rule.
The receipt regime is the constitutional middle: coercion is permitted, but it must leave an inspectable, contestable trace. The system may act at machine speed, but the governed retain the right to challenge at human speed. This is the same structure that due process has always had — not prior permission, but subsequent review under conditions that make review meaningful.
The inferential burden has been established. Each article follows from a structural condition identified in the book. Each names a specific failure of legitimacy that occurs in its absence. Each positions itself relative to existing law and explains what it adds. What follows is the constitutional proposal in two parts: the Orientation, which states the commitments and the procedures for their amendment and exception, and the Design Brief, which specifies the institutional machinery that makes them self-enforcing.