I appealed it and I won it and the finding was reversed. They struck it from the register. They read it out.
Ostensible acquittal returns the accused to ordinary life with one condition: the file survives.
Kafka’s painter describes a court in which a favorable decision does not settle the matter. The documents circulate upward. A judge may revive the charge. The accused goes free under a verdict whose machinery remains intact.
Automated systems can create the same shape without a secret court. One record is corrected. Its earlier value has already traveled.
The derived record
A determination rarely stays in the table where it began. A risk flag may influence a queue. A status can determine which questions a reviewer asks. A refusal may become an outcome used in later analysis. Systems built for reuse convert decisions into inputs.
The original field might then be corrected while its descendants remain unchanged. A cached result may expire later. A downstream recipient may not receive the correction. A feature derived from several variables may carry the old value without exposing where it came from.
No exotic model behavior is required. Ordinary data engineering is enough.
The appeal process usually faces the visible determination. It asks whether the result should stand. A full remedy would also ask where the result went, what changed because of it, and which derived records must be recomputed.
A list that outlived its reasons
Between 2013 and March 2020, the Dutch Tax Administration’s Fraude Signalering Voorziening accumulated registrations concerning roughly 270,000 people, including about 2,000 minors. The press came to call it a blacklist. In 2022 the Dutch data protection authority fined the tax administration €3.7 million over it, finding that there was no legal basis for the processing and that the recorded data was often inaccurate, so that people had been wrongly registered as possible fraudsters. The tax administration itself reported that between 5,000 and 15,000 people experienced financial harm, including refused debt restructuring.
The part that matters here came afterward. The signals had been shared beyond the tax administration, and years after the list was shut down, the state was still trying to establish which bodies had received it. Closing the source register was the easy act. Finding every copy of a determination that had already traveled turned into its own investigation, run by an institution whose records of the sharing fell short of letting it reconstruct the full list of recipients.
Winning against one copy
An overturned decision has at least two histories. The official history records an adverse result followed by a successful challenge. The operational history includes everything that happened between those entries.
Some consequences can be amended. A status changes. Funds can be released. A notice can be withdrawn. Other consequences have already passed into human judgment. A reviewer saw the flag. A manager allocated attention elsewhere. Another system learned that this was the kind of case associated with an adverse outcome.
The FSV register shows the structural risk at national scale. Any workflow that exports a determination without a correction protocol can produce a reopened record, and the difficulty of the cleanup scales with everything the finding touched on its way out.
Correction custody
Evidence custody usually focuses on proving what the system did. Remedy requires custody of the correction too.
A correction needs an identifier that travels with the original determination. Recipients need a duty to accept it. Derived features need lineage sufficient to show whether recomputation is required. The organization needs evidence that each reachable copy was amended or deliberately retained under a stated rule.
Without that chain, the person receives an ostensible acquittal. The official result improves. The old determination remains available to systems that were never told the case had changed.
This is why an audit log can preserve the wrong it is meant to expose. Logs should retain evidence of the original action. Operational systems should cease treating that action as current truth. Conflating those purposes creates a choice between forgetting history and continuing the harm.
The separation has to be designed. An immutable audit record can document that a determination occurred and was overturned. A current-state system can propagate the corrected status. Access controls can prevent the historical adverse result from becoming an active feature again.
The right actor
None of this happens because an appeal form exists. Someone must have authority across the systems that received the decision. That person may need a vendor to change a product, a provider to address a model, or another institution to correct its copy.
The affected person can point to the wrong. The operator can change one record. The vendor controls the surrounding application. The provider may control the model beneath it.
Four parties stand near the undo function. Only some of them can press it.
Companions
- The regulator’s decision: Autoriteit Persoonsgegevens, Boete Belastingdienst zwarte lijst FSV.
- The contemporaneous reporting: NOS on the FSV fine.
- The search for where the list went: FSV portal, Belastingdienst.
- The custody of evidence: The Accused Writes the Log.
- The liaison office: Whom the Mechanism Reaches.
- The fiction: Kafka’s ostensible acquittal, set out in Definite Acquittal.
These notes come out of Sociable Systems, a practice that reads AI-shaped documents the way a hostile reviewer will, before a lender or a court finds the gap. The argument has an operational form: the Interim Protocol sets out four rules for AI use in environmental and social deliverables, covering disclosure at touch-point grain, evidence custody, the phrases no automated screening may settle, and a hostile read before anything ships. Free, and written to be cited or retired once institutional guidance arrives.