Receipt Templates
Aa
These four examples give concrete form to the duties developed in Chapter 11: Act, Authority, Bounds, Evidence, and Contest. They show what a record can make available to a person facing an adverse decision. The named networks, deadlines and policy references are illustrative; they do not describe existing services or state current law.
Template 1: Account Restriction
Context. A payment platform restricts a user's ability to send outbound transfers.
| Field | Content |
|---|---|
| Act | Outbound transfer capability suspended for account #[hash]. All pending transfers held. Inbound transfers continue. Balance viewable but not withdrawable. |
| Authority | Platform Policy §7.3.2 (Unusual Activity Protocol), effective [date]. Applicable regulatory requirement: [jurisdiction] Anti-Money Laundering Regulation §[section]. |
| Bounds | Suspension effective [timestamp]. Duration: 72 hours or until review completion, whichever is sooner. Scope: outbound transfers only. Inbound deposits, balance viewing, and account history access are unaffected. If review is not completed within 72 hours, the restriction is automatically lifted and may be reimposed only with a new receipt citing the results of the review. |
| Evidence | Three transactions within 48 hours matching pattern [pattern-ID] in the platform's anomaly-detection model (version [v], deployed [date]). Pattern confidence: [percentage]. The specific transactions flagged: [transaction hashes]. Supporting records available to the affected person or an authorized advocate, and to an independent auditor under audit protocol [ID]. |
| Contest | (1) Self-service identity verification via [URL], estimated time 15 minutes. If identity is confirmed and no further anomalies detected, restriction is lifted automatically. (2) Human review request via [URL], guaranteed response within 48 hours. (3) Escalation to Credential Arbitration Network, case filing via [URL], independent arbiter assigned within 5 business days. |
Template 2: Content Removal
Context. A social platform removes a user's post.
| Field | Content |
|---|---|
| Act | Post [content-hash] removed from public view. Post remains in user's archive (visible to user only). Engagement metrics preserved. |
| Authority | Community Guidelines §4.1 (Harmful Misinformation), version [date]. Specific sub-rule: §4.1.3 (Health Claims Contradicted by Verified Sources). |
| Bounds | Removal effective [timestamp]. Duration: indefinite unless overturned on appeal. Scope: public visibility only; the post is not deleted and remains in the user's personal archive. Account standing is not affected by this removal. |
| Evidence | Post contains claim: [extracted claim]. Claim contradicted by [N] verified sources: [source-1], [source-2], [source-3]. Claim evaluated by content-review model (version [v]) with confidence [percentage]. The specific elements of the post that triggered the removal are highlighted in the user's archive view. |
| Contest | (1) User may request human review via [URL], guaranteed response within 7 days. (2) If human review upholds removal, user may request independent review through platform's Content Review Board, response within 30 days. (3) If Content Review Board upholds removal, user may file with external Content Arbitration Network via [URL]. |
Template 3: Credential Rejection
Context. An employer's credentialing system rejects a professional license (the Elena scenario).
| Field | Content |
|---|---|
| Act | Professional credential [credential-hash] presented by [holder-ID] rejected by [employer] credentialing system. Employment eligibility status set to "pending review." |
| Authority | Employer Policy §[section] (Credentialing Requirements), requiring verification through approved credentialing sources. Approved sources: [list]. |
| Bounds | Rejection effective [timestamp]. Duration: until discrepancy is resolved. Scope: the specific credential only; other credentials and employment history are unaffected. If discrepancy is not resolved within 15 business days, the employer must either accept the credential based on the issuing authority's direct attestation or provide a new receipt citing specific grounds for continued rejection. |
| Evidence | Credential contradicted by record in [aggregator-name]: [specific claim from aggregator, including case number, date, and nature of claim]. The direct attestation from the issuing authority ([issuing authority name]) shows: [attestation content]. The discrepancy between the two sources is: [specific discrepancy]. |
| Contest | (1) Holder may present direct attestation from issuing authority. If attestation contradicts aggregator record, employer must accept credential unless employer can cite independent grounds for rejection. (2) Holder may file dispute with Credential Arbitration Network via [URL], arbiter assigned within 3 business days. (3) If arbitration finds aggregator record erroneous, aggregator must correct record within 5 business days and issue a correction receipt to all parties that received the erroneous record. |
Template 4: Algorithmic Scoring Adjustment
Context. A credit-scoring system adjusts a person's score past a threshold that affects their eligibility for financial services.
| Field | Content |
|---|---|
| Act | Credit score for [person-ID-hash] adjusted from [previous-range] to [new-range], crossing threshold [threshold-value] for [service-type] eligibility. Adjustment effective [timestamp]. |
| Authority | [Responsible institution] acting under [applicable authority and delegated scope], using scoring model [model-ID], version [v], deployed [date]. Model parameters last audited [audit-date] by [auditor-name]. |
| Bounds | Score adjustment affects eligibility for: [list of affected services/products]. Score adjustment does not affect: [list of unaffected services]. The score is recalculated [frequency]. The adjustment will be reflected in the next recalculation cycle. |
| Evidence | Score adjustment driven by [N] factors, listed in order of contribution: (1) [Factor, contribution weight, data source], (2) [Factor, contribution weight, data source], (3) [Factor, contribution weight, data source]. Full factor decomposition available to person via [URL] and to independent auditor under audit protocol [ID]. |
| Contest | (1) Person may request factor decomposition via [URL], provided within 5 business days. (2) Person may dispute any factor by providing contradicting evidence via [URL]. If evidence is accepted, score is recalculated within 10 business days. (3) Person may request independent audit of the scoring model's application to their case via [URL], auditor assigned within 15 business days. |
Implementation Notes
The information needed varies with the action and the institution. A completed form is inadequate if its evidence cannot be examined, its declared authority does not cover the act, or its contest route cannot alter an unjustified consequence. Different implementations can discharge these duties through different records and procedures. The information must concern the actual case; generic entries can leave a person with nothing usable to challenge (see Chapter 12, Failure Mode One: Semantic Deception).
The receipt format should be machine-readable (structured data) as well as human-readable (natural language summary). A machine-readable representation supports automated audit, comparison and pattern detection. A readable account must also make the act and the available challenge intelligible to the affected person.
Signatures, timestamps and independently held copies can protect the record against unilateral revision. Affected people need access to evidence whose preservation does not depend entirely on the authority they challenge. The assurance must fit the power constrained; a shared settlement layer is one possible means, not a universal requirement. Integrity of the record remains distinct from the truth of its contents and the legitimacy of its use.