Appendix C
Worked Examples
Aa
The examples below show how the receipt grammar changes an existing institutional act. They do not claim that completing a form makes the underlying regime constitutional. Each example distinguishes the act, proposed record, authority, verification route, independent forum, remedy, unresolved penumbra, and principal failure mode.
Where an existing legal regime supplies part of the structure, the example identifies it. The remaining fields are proposals. Where no particular event is documented, the example is explicitly counterfactual.
1. Platform Account Suspension
Status. Counterfactual implementation under an actual regulatory baseline.
Current act. A hosting platform suspends an account after automated and human review of alleged policy violations. The European Union's Digital Services Act requires a clear and specific statement of reasons for restrictions including account suspension or termination and provides internal complaint and out-of-court dispute routes. 1
Proposed receipt. The platform issues a stable event record naming the restricted capabilities, effective time, territorial scope, duration, policy and version, material facts, source class, role of automated means, surviving principal, and next deadline. Protected complainant information is separated from the testable proposition rather than omitted without explanation.
Authority. The platform cites the specific contractual rule and any legal obligation requiring or authorizing the restriction. It distinguishes a private policy judgment from an act compelled by public law.
Verification method. The user can compare the cited content, timestamps, policy version, and account state with an exported record. If evidence must remain confidential, an independent reviewer can inspect it under a protected procedure. A signature or commitment establishes which version was issued; it does not establish that the policy was lawful or correctly applied.
Independent forum. After internal complaint, the user can reach a certified out-of-court body or competent public forum without surrendering the underlying claim. The forum discloses appointment, funding, and conflict relations with repeat platform parties.
Remedy. Available relief includes interim preservation where delay would destroy the account's value, restoration, correction of the violation record, notice to systems that received the suspension state, reimbursement where authorized, and a reasoned denial if the restriction remains.
Remaining penumbra. Context, satire, threat, harassment, and community safety cannot always be reduced to fields. The receipt should expose the interpretive judgment and responsible office rather than pretend the policy label settles the case.
Failure mode. The platform can satisfy the schema with generic text, withhold the operative evidence, or route every challenge to a reviewer unable to restore the account. The test is practical contest and remedy, not field completion.
2. Employment Screening and an Old Record
Status. Proposed receipt applied to the documented dispute in Grijalva v. ADP Screening and Selection Services.
Current act. An employment-screening report included both a continuing federal exclusion and the old license revocation from which the exclusion originated. The Ninth Circuit held in 2025 that the ongoing exclusion could be reported, treated the revocation as a separate adverse item subject to the reporting limit, and found no liability because the defendant's contrary interpretation was objectively reasonable. 2
Proposed receipt. A screening provider separates current status from historical cause. For each item it records the source, date, legal category, reporting period, current authority, last verification, dispute status, and every employer or decision system to which the item was delivered. It does not allow a current status field to carry an expired narrative invisibly.
Authority. The provider cites the reporting rule applicable to each item and identifies the permissible purpose for the employer's request. The employer separately identifies the rule under which the report may affect employment.
Verification method. The person can inspect the source record, compare identifiers, test the reporting period, and see whether a later correction or reinstatement exists. The screening provider records uncertainty where identity matching or legal classification is contested.
Independent forum. The person may use the statutory dispute process and, where available, a regulator or court able to order correction and damages. Internal customer-service review is not the only route.
Remedy. The provider corrects or suppresses the item, notifies every recent recipient required by law or contract, and records whether the employer reconsidered the adverse action. The employer remains answerable for its own decision even if the report accurately described a current exclusion.
Remaining penumbra. The lawful relevance of a present exclusion and the weight an employer may give it are distinct questions. A corrected report cannot decide whether the job, safety duty, evidence of rehabilitation, and present risk justify the final employment consequence.
Failure mode. A provider may correct its own display while copied reports, derived risk flags, or employer notes continue to reproduce the old item. Correction lineage is therefore part of the receipt.
3. Content Demotion and Statements of Reasons
Status. Operational extension of the Digital Services Act statement-of-reasons regime.
Current act. A platform removes, demotes, demonetizes, or otherwise restricts content. Article 17 of the DSA specifies information a statement of reasons must contain, and Article 24(5) supports transmission of standardized statements to the European Commission's transparency database. 3 The database creates a systemic record but does not by itself establish that every individual statement is adequate. 4
Proposed receipt. The platform provides the five-field grammar at the level of the affected item: act, authority, bounds, evidence, and contest. It adds the ranking or moderation system version, whether detection and decision were automated, the consequence for visibility or revenue, and the relationship between this item and any account-level strike.
Authority. The receipt distinguishes illegal-content action from enforcement of contractual terms. If the platform acts on a government order, the order and issuing authority are linked subject to lawful confidentiality limits.
Verification method. The creator can inspect the cited content and policy version, compare pre- and post-action distribution metrics where those metrics form part of the claim, and obtain independent review of protected signals. The public database can reveal aggregate patterns but does not replace the person's case record.
Independent forum. Internal complaint, qualified out-of-court settlement, regulator, and court remain distinct routes. The receipt says which one can review the content judgment and which can review only procedural compliance.
Remedy. Restoration, removal of an account strike, revenue correction, notice to syndication or advertising systems, and publication of an amended reason where the original statement entered a public database.
Remaining penumbra. The line between harmful context and protected expression remains interpretive. A system can make the authority and evidence visible without claiming to encode the final meaning of speech.
Failure mode. Standardization can produce boilerplate at enormous scale. A database of uninformative reasons increases countable transparency while leaving the governed person unable to contest the actual inference.
4. Automated Public-Benefit Debt
Status. Proposed receipt derived from the documented failures and recommendations of Australia's Robodebt Royal Commission.
Current act. The Robodebt scheme used income information and automation to identify apparent benefit overpayments. Where more granular information was absent, annual earnings could be averaged across benefit periods and used to raise debts. The Royal Commission recommended clear review routes, plain disclosure that automation is used, independent scrutiny of business rules and algorithms, and ongoing monitoring and audit. 5
Proposed receipt. Before collection, the agency states the benefit periods, data sources, matching method, any averaging assumption, legal basis, amount, uncertainty, human authorization, collection date, and route for supplying contrary evidence. The receipt identifies whether the amount is an observed overpayment or an inference produced because period-level evidence is missing.
Authority. The responsible public office cites the statute, regulation, and delegated instrument claimed to authorize both the calculation and collection. Software and contractors are not named as the source of legal power. An accountable official or agency remains the surviving principal.
Verification method. The recipient can reproduce the calculation from the disclosed data or appoint a representative to do so. Missing records, incompatible pay periods, and employer corrections are visible rather than converted silently into claimant error.
Independent forum. An administrative review body or court can stay collection, compel disclosure, receive new evidence, and decide legality. The original agency's automated reconsideration does not exhaust review.
Remedy. Cancellation or recalculation of the debt, cessation of collection, repayment of sums collected, correction of credit or compliance records, compensation where law permits, and systemic review if the same defect affected a class.
Remaining penumbra. A lawful overpayment calculation does not settle hardship, waiver, reliance on official advice, or the proportionality of recovery. Those issues require separately authorized judgment.
Failure mode. The agency can disclose a formula while placing the burden of disproving its unsupported inference on a person who lacks records, time, or representation. A receipt must expose burdens and uncertainty, not merely arithmetic.
5. Biometric Authentication and Food Entitlement
Status. Counterfactual receipt informed by mixed empirical evidence from Indian identity-linked benefit systems.
Current act. A ration transaction is denied or delayed after biometric or identity authentication fails. Research discussed in Chapter 2 shows unlike outcomes across implementations: compulsory Aadhaar authentication in one setting was associated with substantial transaction failure, a smartcard payment reform elsewhere improved speed and reduced leakage, and stricter identity requirements reduced corruption while imposing material transition costs on legitimate beneficiaries. 6
Proposed receipt. At the point of failure, the system records the requested entitlement, authentication method, device and software version, failure category, network state, operator action, alternative method offered, goods or payment withheld, and responsible agency. The receipt avoids exposing the biometric template itself.
Authority. The agency identifies the rule requiring authentication and the rule that guarantees fallback or exception handling. A vendor's technical response code does not become the legal authority for denying subsistence.
Verification method. An inspector can distinguish biometric mismatch, device failure, connectivity failure, database mismatch, expired credential, and operator refusal. The beneficiary or representative can prove the entitlement and the failed transaction through a protected record.
Independent forum. A local grievance office must be reachable without successful biometric authentication, with escalation to an authority independent of the dealer and authentication vendor. Emergency access should not wait for final adjudication where food or essential payment is at stake.
Remedy. Immediate alternative delivery, restoration of the entitlement, correction of identity or account records, repayment for missed benefits where authorized, and investigation of repeated failures at the device, dealer, or district level.
Remaining penumbra. The acceptable balance among fraud prevention, administrative capacity, dignity, and risk of exclusion is political and empirical. A receipt makes failure attributable; it does not choose the balance.
Failure mode. A technically accurate failure code can leave the person hungry if no fallback is funded, the grievance office is remote, or the operator is punished for honoring exceptions. Remedy capacity belongs inside the implementation.
The Five-Field Grammar and Its Limit
Across the five examples, the recurring grammar is:
| Field | Required question |
|---|---|
| Act | What changed, for whom, when, and with what practical consequence? |
| Authority | Which rule, version, mandate, and surviving principal authorized it? |
| Bounds | How far does the act reach, how long does it last, and what ends it? |
| Evidence | Which observations and inferences support the act, with what uncertainty? |
| Contest | Which forum can review it, by when, and with what remedy? |
Implementation also requires verification access, delivery, correction lineage, handback where authority was delegated, and seam jurisdiction where claims cross systems.
The grammar is successful when it makes the unresolved dispute more precise and gives the affected person a usable route to alter the consequence. It has failed when the fields are complete but the authority is unlawful, the evidence unavailable, the forum dependent, the remedy empty, or the corrected claim continues to travel.