Topics · Domain workflow
Appeals reviewers can check that a decision path was witnessed and open only the fields they are authorized to see under civic disclosure rules.
Concrete scenario
A benefits system auto-denies an application. The applicant appeals and asks for proof the rules engine version and inputs hash used on the decision date. The vendor will not expose full case files to the public docket, yet the city must still show a recognized commitment existed.
Problem
Automated eligibility, permitting, and enforcement workflows already affect public life. Citizens need proof of machine-assisted decisions without forcing private case files onto the public internet or into vendor dashboards.
Mechanism
Agencies anchor receipt commitments with public recognition facts while sensitive fields remain in permissioned disclosure paths governed by profile rules and sealed claim openings. Optional attribution profiles separate who signed from what is publicly shown on civic recognition surfaces without exposing PII by default.
Verifiable outcome
Scope boundary
Receipts support accountable civic automation — not open records law compliance by themselves, electoral politics, or full transparency of every vendor subsystem.