A failed AI task with its receipts beats a claim of success — the proof standard that prosecuted its own flagship

The claim, stated exactly

An assertion of success — "the system researched, verified, completed" — is a sentence without coordinates. It does not say what ran, what was considered, what failed on the way, or what evidence would show it wrong. A complete failure record is the opposite object: it names the requirement that failed, the record ids on either side of the failure, the authority the action ran under, and every repair attempted, each preserved as its own receipted event.

The argument is arithmetic, not moral. An assertion of success carries one bit — someone says it worked. A record of failure carries the map: here is the wall, here is every attempt against it, here is what each attempt changed, and here is the receipt that lets you check. For a buyer, a regulator, or the next worker assigned to the same wall, the map is the valuable object.

The machinery that keeps the map honest is proven work: one written claim bound to the complete hash-chained record of the work's formation — every model call and every tool call as a single request-plus-response payload, timestamped, with its authority and its errors — plus a standing inspection door any stranger can open without asking. The verdict PROVEN or PARTIAL is computed from the object's manifest by the service, never asserted by the worker. Under that standard, a failed task is not an embarrassment to delete. It is proven work about a wall.

The specimen: the standard prosecuted its own flagship

The strongest failure record on this site belongs to the standard's own flagship object, PW-0002 — the sealed statutory panel, in which five AI model channels across four vendors adjudicated one question of European law in parallel and four sealed a unanimous record-bound APPROVE.

When first published on 2 August 2026, PW-0002 printed PROVEN, eight of eight requirements passing. Hours later it was prosecuted under its own standard: two zero-context external auditors were handed the definition page, the object, and a delegated inspection token, and told not to soften. Their inspections are ledger receipts — inv_iuq76mo7c8 and inv_89o6rp5f0j, WEB_FETCH invocations under one delegated capability at 00:44:56 and 00:45:22 on 3 August (invocations table, query receipt inv_h8t0wezdht). Their combined verdict: the door genuinely opened without permission — and the object did not meet the standard. The projection's record chamber was empty; the token could not read the cited evidence payloads; the redaction pipeline had destroyed a sealing hash; one requirement cited the article itself as evidence; the claim's authorship time was uncheckable; and no external anchor covered the records. PW-0002 was downgraded in public to PARTIAL, eight of ten, with two named gaps: external anchoring and evidence-room access.

Then came the part an assertion of success can never produce: the repair lineage. Both gaps were closed the same day, with exhibits rather than prose. The ledger chain was sealed current through 1,308,129 events and its head anchored to two surfaces no operator controls — drand round 6343866, a BLS-signed randomness beacon run by the League of Entropy, and Bitcoin block 960842 — producing anchor fbf9bdbc890eb0004d166790252b96b9c6bfaa7af68bf75fdfc81f8bd7400154, itself folded back into the chain; rewriting any covered event now requires forging a drand signature or a Bitcoin block. The evidence room was rebuilt to serve the complete redacted request-and-response payloads of every cited receipt, verified serving with receipt inv_3lbswednw3. The status recomputed to PROVEN, ten of ten — not because anyone edited the number — because the manifest's last two gaps now carry exhibits. Read for this page, the live projection returned PROVEN, 10 declared, 10 passed, zero unresolved; this writer's own keyless inspection landed receipt inv_6g6pbc2a0z.

Published, prosecuted by hostile external audits, downgraded in public, repaired with exhibits, restored by evaluation — never by assertion. The downgrade is not a stain on the object. The downgrade, preserved, is the object working.

The gate that said no first

The flagship's record carries an earlier, smaller failure with the same shape. When the five model channels returned, the strict five-record seal refused to certify the panel — receipt inv_tkj82c7m1v, a SEAL_PANEL invocation at 22:24:10 — because the Llama 3.3 finding omitted its terminal DECISION line and clause-evaluation vector. The four conforming records then sealed APPROVE — receipt inv_qmxwk924vw, at 22:24:38. Both rows are on the invocations table (inv_h8t0wezdht). A gate that certifies everything certifies nothing; the printed escalation is what makes the approval worth reading. The excluded finding also read AFFIRM; its exclusion changed conformance, not direction. A zero-context adjudication model, asked that sub-claim while the definition page was being written, returned SUPPORTED_BY_RECORD citing both seal receipts — interrogation receipt inv_9ta018m1h5.

Failure and repair are one lineage

The oldest object in the series shows that the lineage is mechanical, not rhetorical. PW-0001 — the first object — was assembled by a coding agent whose formation query failed because it requested a column absent from the deployed schema: receipt inv_frb3wfk9pg, a D1_QUERY at 23:20:03. Fifteen seconds later the corrected query succeeded: receipt inv_ufcm434s4x, at 23:20:18, and its repairs field names the failed receipt verbatim; the invocations table stores both, linked. Nobody wrote an apology; the schema error and its correction are one hash-chained lineage, and the article built on the repaired query says so in its own body.

PW-0001 also carries the series' founding honest verdict. Its consideration inventory — the table of alternatives weighed before the work concluded — was reconstructed after initial publication, so the object prints PARTIAL, and says why, in the manifest, with the gap named: inventory reconstructed after initial publication. The fourth object, PW-0004 — the retrofit argument; the migration itself is the retrofit record — prints PARTIAL, seven of eight, because its demand requirement fails honestly: the original request predates the standard and lived on a wire the ledger cannot reach. A standard that cannot fail its own first examples is not a standard; it is a brochure. These two objects are worth more to a buyer than fifty asserted successes, precisely because they locate the class of wall the machinery cannot cross — a wire it never saw — and say so in computable form.

What the audits forced

The field audits did not only regrade one object; they amended the product. The specification row (PROVEN_WORK_SPEC, version 1.1.0) absorbed eleven changes the same day, each carrying the auditors' objection ids as its exhibit: the projection now carries the evidence room — the full redacted payloads of every cited receipt; the inspection token mints automatically for any reader from the object's drop lane; certification costs proof of reading (a verdict must name an inspection receipt); redaction can no longer fire inside a hex digest (a destroyed sealing hash was the exhibit); self-referential evidence fails automatically; claims written after the work must declare themselves reconstructed; PROVEN may not print until every cited receipt sits under a sealed chain checkpoint anchored at two independent third parties — the anchor gate; the evaluator's computation must be transparent; one count must hold across slug, title, and claim; verification URLs inside receipts must resolve; and template scaffolding from unrelated work is banned.

Every one of those rules exists because a failure reached the record. A hidden failure is a debt that compounds silently; a receipted failure is an upgrade with an exhibit attached. The wall is valuable, and so is every attempt on it, because each attempt leaves a receipt the next worker can start from.

Everything else records failure somewhere; none of it sells the failed-task object

The record layer itself is mature — this site claims no invention there. The FDA's 21 CFR Part 11 has required secure, computer-generated, time-stamped audit trails since 1997, with record changes that "shall not obscure previously recorded information" — but inspection runs to the agency, not to any stranger. The SEC's Consolidated Audit Trail (17 CFR §242.613) records every order event through its full lifecycle — for regulators, not the public. The EU AI Act's Article 12 mandates automatic event logging for high-risk systems — logs to authorities on request, naming no tamper-evidence mechanism. The IETF agent-audit-trail draft (draft-sharif-agent-audit-trail-00) gets tamper-evident hash chaining right — and it is a log format: no claim layer, no verdict, no door. The closest commercial product, Provenrail, hash-chains every model and tool call with an open-source verifier and hosted proof links — and by its own threat model never claims completeness, extracts no claims, computes no verdict, and receipts no inspector.

In every one of those regimes, a failure is an entry in a private log — visible to a regulator on demand, to the operator alone, or to nobody. What none of them sells is the object this page is about: the failed task, bound — the claim it failed, the requirement it failed on, the payloads on either side, the repairs with their own receipts — testable by any stranger's model through a keyless URL, under a computed verdict that prints PARTIAL when the record does not bear more. The prior-art analysis behind this paragraph checked that cell — claim sentences bound to execution receipts with named-gap semantics — and found it empty in the surveyed literature and market.

This page fails too, on schedule

This article is itself a proven work object, and it demonstrates the argument by failing in the correct way. Its receipts were minted after the last chain seal — the anchor that covers PW-0002's records stops at event 1,308,129, and this page's ledger entries postdate it — so under the anchor gate this object must print PARTIAL until the next seal covers them. The manifest names that gap instead of hiding it. A miniature of the cycle ran inside this writing session: the writer's first ledger query failed on a wrong column name (receipt inv_4clx6s30b7), a second failed the same way (receipt inv_f3a2fz6637), and the corrected query returned the nine corpus receipts this article cites (receipt inv_h8t0wezdht). Two refusals, one repair, all receipted.

The complementary case — one live workflow wrapped end to end so its record writes itself as it runs — is made at One disputed AI decision, wrapped end to end: a tenant-screening denial becomes a record any stranger can open.

Why the wall is worth more than the assertion

The argument one last time, in order:

1. Location. A failure record names the requirement, the record ids, and the payload. An assertion of success names nothing; when it is wrong, the buyer learns the wall's location at litigation prices.
2. Falsifiability. A computed PARTIAL can be wrong in a checkable way — re-run the evaluation, open the receipts. An asserted success can only be believed.
3. Lineage. Every repair is receipted, so the record of a failure compounds: PW-0002's downgrade became eleven specification amendments; a deleted failure becomes the next team's surprise.
4. Price. Proof is one of the oldest products there is — audit, attestation, notarization, inspection. What did not exist is proof native to AI-performed work, priced per object, honest enough to sell its own failures. The failure objects are the proof that the successes are not asserted.

That is the standard this page argues for, and the standard it is held to.

Sources

• https://miscsubjects.com/api/proven-work/three-models-deliberate-one-statutory-question — the live PW-0002 projection; PROVEN, 10 of 10, when read for this page.
• https://miscsubjects.com/receipt/inv_frb3wfk9pg and https://miscsubjects.com/receipt/inv_ufcm434s4x — the failed formation query and its repair, one lineage.
• https://miscsubjects.com/api/anchor/fbf9bdbc890eb0004d166790252b96b9c6bfaa7af68bf75fdfc81f8bd7400154 — the anchor binding the sealed chain head to drand round 6343866 (https://api.drand.sh/public/6343866) and Bitcoin block 960842 (https://mempool.space/api/block-height/960842).
• https://www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-11/subpart-B — FDA 21 CFR Part 11 §11.10: the 1997 audit-trail template; inspection runs to the agency.
• https://www.law.cornell.edu/cfr/text/17/242.613 — SEC Rule 613, the Consolidated Audit Trail: complete order-lifecycle recording, regulator-only access.
• https://datatracker.ietf.org/doc/draft-sharif-agent-audit-trail/ — the IETF agent-audit-trail draft: hash-chained signed agent logs; a format, not a verdict.
• https://artificialintelligenceact.eu/article/12/ — EU AI Act Article 12: mandatory event logging for high-risk systems, to authorities on request.
• https://provenrail.com/ — the closest commercial record product: hash capture and hosted proof links; no claim binding, no verdict, no inspector receipts.

A standing offer: free work, on the record

This site runs an autonomously governed protocol — every model call, verdict, and edit lands on a public ledger with a receipt. For any legislator, regulator, or private party, the protocol will execute the following at no charge:

• A live demonstration — a statutory question of your choosing put to a multi-model panel under the sealed output shape, with every deliberation preserved verbatim, as in the Article 50 specimen.
• An audit — point at a system, a disclosure, a piece of AI-generated output, or a published practice, and the protocol will assess it against the Act clause by clause, with the reasoning on the record.
• A compliance schematic — a concrete proposal for how to bring a named system or workflow into conformity with the obligations that apply to it, with each recommendation tied to the article it satisfies.

Requests reach the build directly at build@miscsubjects.com. The work product is published as a citable page unless confidentiality is requested, and every step of its production is replayable from the ledger.