{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"proven-work-failed-task-object","urls":{"read":"https://miscsubjects.com/api/articles/proven-work-failed-task-object/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/proven-work-failed-task-object/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/proven-work-failed-task-object/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/proven-work-failed-task-object/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/proven-work-failed-task-object/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/proven-work-failed-task-object/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/proven-work-failed-task-object/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"proven-work-failed-task-object","title":"A failed AI task with its receipts beats a claim of success — the proof standard that prosecuted its own flagship","register":"standard","tags":[],"updated_at":"2026-08-03T17:35:01.680Z","body_excerpt":"*This page argues one point, with the build's own public ledger as the exhibit: a complete, receipted record of an AI task that failed — the wall it hit and the lineage of repairs that followed — is worth more than an assertion of success, because only the failure record shows exactly where the wall is, and because every repair against the wall is itself proven work. Every term is defined where used, every receipt named can be opened, and this page's own status is computed by the machinery it describes.*\n\n## The claim, stated exactly\n\nAn 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.\n\nThe 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.\n\nThe machinery that keeps the map honest is [[proven-work|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.\n\n## The specimen: the standard prosecuted its own flagship\n\nThe strongest failure record on this site belongs to the standard's own flagship object, PW-0002 — [[three-models-deliberate-one-statutory-question|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.\n\nWhen 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.\n\nThen 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 ","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"PW-0002 read PROVEN, 10 of 10, when its live projection was fetched for this page.","tier":"primary","section":"The claim, stated exactly","interaction_risk":false,"status":"active","source_ids":["s1"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"The sealed chain head is anchored to drand round 6343866 and Bitcoin block 960842 — anchor fbf9bdbc890eb000…, verifiable by anyone.","tier":"primary","section":"The claim, stated exactly","interaction_risk":false,"status":"active","source_ids":["s2"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"The audit-trail template this extends is 29 years old: FDA Part 11 requires secure, computer-generated, time-stamped audit trails whose record changes shall not obscure previously recorded information.","tier":"primary","section":"The lineage","interaction_risk":false,"status":"active","source_ids":["s3"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"EU AI Act Article 12 mandates lifetime event logging for high-risk systems — logs held for the authority, not doors open to strangers.","tier":"primary","section":"The lineage","interaction_risk":false,"status":"active","source_ids":["s6"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"An assertion of success carries one bit; a complete failure record carries the map — the requirement that failed, the record ids on either side of the wall, and every receipted repair against it.","tier":"primary","section":"The claim, stated exactly","interaction_risk":false,"status":"active","source_ids":["s1","s5"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"s1","url":"https://miscsubjects.com/api/proven-work/three-models-deliberate-one-statutory-question","title":"the live PW-0002 projection; PROVEN, 10 of 10, when read for this page.","claim_ids":[],"hash":"3cd3543c176b25a65b1f632294dc99da4a6c05ade4c2f15212add82fa1fedad9"},{"id":"s2","url":"https://miscsubjects.com/api/anchor/fbf9bdbc890eb0004d166790252b96b9c6bfaa7af68bf75fdfc81f8bd7400154","title":"the anchor binding the sealed chain head to drand round 6343866 (https://api.drand.sh/public/6343866) and Bitcoin block 960842 (https://memp","claim_ids":[],"hash":"c1f468c5156ad6578e2807bda22ba4bd27e3f8f65101dc6646d7da3092dae6dd"},{"id":"s3","url":"https://www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-11/subpart-B","title":"FDA 21 CFR Part 11 §11.10: the 1997 audit-trail template; inspection runs to the agency.","claim_ids":[],"hash":"60d51ef9df530fa6be12a9d9a6ac8dcb49eb22a08d2d4be23103c977cd471820"},{"id":"s4","url":"https://www.law.cornell.edu/cfr/text/17/242.613","title":"SEC Rule 613, the Consolidated Audit Trail: complete order-lifecycle recording, regulator-only access.","claim_ids":[],"hash":"1d8d8d9ea4d985372dac39c9ff25b634f8c15b47397422fbcb7b4f54a098c5e0"},{"id":"s5","url":"https://datatracker.ietf.org/doc/draft-sharif-agent-audit-trail/","title":"the IETF agent-audit-trail draft: hash-chained signed agent logs; a format, not a verdict.","claim_ids":[],"hash":"2e34c185959343afccb47888c818ed8d4272bef4299114f1627111e1dffc2632"},{"id":"s6","url":"https://artificialintelligenceact.eu/article/12/","title":"EU AI Act Article 12: mandatory event logging for high-risk systems, to authorities on request.","claim_ids":[],"hash":"61d67752a0084b5db844bb0429a1db84861c9e55d99a438d6f0cb932c0d5f3a3"},{"id":"s7","url":"https://provenrail.com/","title":"the closest commercial record product: hash capture and hosted proof links; no claim binding, no verdict, no inspector receipts.","claim_ids":[],"hash":"bd4af72e8cd6b477ac145388cd1f81eb08ad5b895053ee2fc5a90247af6718c7"}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"proven-work-failed-task-object","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":5,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":5,"claims_total":5,"sources":7,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}