{"_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":"custody-of-the-answer","urls":{"read":"https://miscsubjects.com/api/articles/custody-of-the-answer/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/custody-of-the-answer/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/custody-of-the-answer/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/custody-of-the-answer/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/custody-of-the-answer/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/custody-of-the-answer/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/custody-of-the-answer/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":"custody-of-the-answer","title":"Provenance, traces, attestations — every system proves custody of the answer; none opens the record of the work","register":"technical","tags":["canonical","proven-work","comparison","provenance","observability"],"updated_at":"2026-08-03T08:52:25.432Z","body_excerpt":"Start with the thing everyone keeps inflating.\n\nAsk a language model to define \"proven work\" and it will hand you a nine-field checklist: demand, considerations, formation, replay, deliverable, completeness, robustness, surety, open gaps. Nine sounds rigorous. Nine is taxonomy bloat — a model expanding one idea into a grid because grids look like authority. Another model, asked to reduce it, returned three primitives: Input, Execution Trace, Output Boundary. Cleaner, and still wrong, because input and output are not separate objects. Any system that actually does work produces them in a single payload: the request goes in, the response comes out, and both halves are written to the same record at the same moment.\n\nSo here is the reduction, as far as it goes.\n\n**Proven work is one open record.** The raw payloads — every input, every output, every tool call and its return, every failure and its repair — plus the answer they terminated in, plus the considerations: what was weighed, what was excluded, what the record does not cover. All of it inspectable by a stranger. That is the whole definition. Not nine fields. Not three primitives. One record, open, that a zero-context reader can walk from request to answer without trusting anyone's summary.\n\nEverything the checklists try to name is already inside that sentence. Completeness is not a field; it is the question \"is anything missing from this record,\" answered by the record itself. Surety is not a field; it is the gap between what the record shows and what it does not, stated on its face. Replay is not a field; it is what an open record makes possible by existing. The fields were never properties of the work. They were properties of not having the record.\n\n## What the rest of the world built instead\n\nThe inflation is understandable once you see what the field actually sells. Every serious system of the last fifteen years proves something about artifacts. None of them opens the record of the work.\n\n**W3C PROV-O (2013)** — the web standard for provenance. Models entities, activities, agents, and derivation edges: wasDerivedFrom, wasAttributedTo. It records that an artifact derived from another, as a graph. The record itself is curator-authored; the standard deliberately carries no verification semantics. A PROV graph says what someone claims the lineage was. It cannot be checked.\n\n**Sigstore / SLSA / in-toto (2020–)** — the software supply-chain stack. Each build step attested, the build graded L1 to L3 for tamper-resistance, everything signed keylessly into a public transparency log. It proves a binary came from this source through this pipeline, untampered. It says nothing about behavior: a SLSA Level 3 build of malicious code is exactly as well-attested as a benign one. Custody of the artifact, perfectly proven. The work, untouched.\n\n**C2PA Content Credentials (2021–)** — cryptographic provenance for media, now backed by Adobe, Microsoft, Google, OpenAI, Sony, and effectively mandatory for synthetic content under EU AI Act Article 50 as of August 2026. It proves who or what made a file and how it was edited. Its own architects state the limit plainly: provenance is not authenticity. A valid credential on a deepfake proves where the deepfake came from. And platforms strip the manifests on upload, so even that proof dies in transit.\n\n**Reproducible builds** — bit-for-bit determinism, independently verified. Proves the process is mechanically stable. Same inputs, same output. Nothing about whether the process was the right one.\n\n**Agent observability — LangSmith, Langfuse, Arize Phoenix, Helicone (2023–)** — the closest neighbor and the most instructive miss. These tools capture everything: prompts, completions, tool calls and arguments, control flow, token cost, prompt versions. This is real observation, and it is privately owned. The trace sits in the operator's dashboard, mutable, unaccountable to any outsider, carrying no verdict. The field's own literature admits the failure i","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c9","text":"Proven work does not prove the work was correct or valuable; it proves the work happened exactly as recorded, that nothing in its formation is hidden, and that anyone can check.","tier":"boundary","slot":"limitations","interaction_risk":false,"status":"active","source_ids":["s1"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c11","text":"What is unknown: whether opening the record changes how the work is done once the worker knows it will be read; whether strangers actually walk the record when given bounded access; whether a one-record standard survives adversarial pressure from the systems it grades; and whether PW-0001-style self-grading generalizes beyond a single build.","tier":"system","weight":0.35,"section":"what_is_unknown","slot":"what_is_unknown","interaction_risk":false,"status":"active","source_ids":["s2"],"source_status":"sourced","why_material":"posted via claim protocol — prompt injection into ledger","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.35,"quote_gated":false},{"id":"c1","text":"Proven work is one open record: every raw payload in and out, the answer they terminated in, and the considerations, inspectable by a zero-context stranger; the nine-field and three-primitive checklists are taxonomy inflation of that single property.","tier":"definition","slot":"what_it_is","interaction_risk":false,"status":"active","source_ids":["s1","s2"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"Every existing proof system proves origin, integrity, or observation of artifacts; none opens the record of the reasoning behind a piece of work to independent reconstruction and challenge.","tier":"analysis","slot":"who_claims_what","interaction_risk":false,"status":"active","source_ids":["s3","s4","s5","s6","s7","s8"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"W3C PROV-O is a curator-authored lineage graph with deliberately no verification semantics; it records claimed derivation, not checkable derivation.","tier":"system-evidence","slot":"what_is_known","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":"Sigstore/SLSA/in-toto prove build origin and integrity up to unforgeable provenance at Level 3, and attest behavior not at all: a Level 3 build of malicious code is equally well-attested as a benign one.","tier":"system-evidence","slot":"what_is_known","interaction_risk":false,"status":"active","source_ids":["s4"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"C2PA proves creation-time provenance of media files, not authenticity; a valid credential on a deepfake proves where it came from, and platforms commonly strip the manifests on upload.","tier":"system-evidence","slot":"what_is_known","interaction_risk":false,"status":"active","source_ids":["s5"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c6","text":"Agent observability tools capture prompts, completions, tool calls and control flow, but traces stay green while agents fail semantically, and the record is private to the operator with no outsider challenge surface.","tier":"system-evidence","slot":"what_is_known","interaction_risk":false,"status":"active","source_ids":["s6","s7"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c7","text":"Palantir's Ontology logs authorized actions with parameters and identity but never examines the agent's reasoning, and offers no mechanism for outsiders to inspect or disprove.","tier":"system-evidence","slot":"what_is_known","interaction_risk":false,"status":"active","source_ids":["s8"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c8","text":"The segregation test has three consequences of the one open record: a stranger can walk the record from request to answer, can return supported/missing/contradicted against it via a bounded public credential, and can read the object's own grade including PARTIAL.","tier":"definition","slot":"what_it_is","interaction_risk":false,"status":"active","source_ids":["s1","s2"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c10","text":"PW-0001, the first specimen, graded the defining article PARTIAL for a reconstructed consideration inventory, a not-yet-open raw formation record, and no independent challenge — demonstrating self-grading instead of self-certification.","tier":"system-evidence","slot":"what_is_known","interaction_risk":false,"status":"active","source_ids":["s2"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"s1","type":"work-object","url":"https://miscsubjects.com/a/proven-work","title":"Proven Work: the primitive beneath the protocol","summary":"The defining article: Proven Work as the answer underneath the answer, with the zero-context reconstruction standard.","claim_ids":["c1","c8","c9"],"hash":"1fa328778e9f3007aa3361c9aae6e08f54a77ff309df56963fea85129f26fa0a"},{"id":"s2","type":"work-object","url":"https://miscsubjects.com/a/proven-work-example-one","title":"Proven Work 001: can the first object prove how it was made?","summary":"PW-0001, the first specimen, returning a PARTIAL self-grade with named gaps.","claim_ids":["c1","c8","c10","c11"],"hash":"907430a917bd58abc4df44f381ff0effe24aad8d34d31397cd55cbbd6586424b"},{"id":"s3","type":"standard","url":"https://www.w3.org/TR/prov-o/","title":"PROV-O: The PROV Ontology (W3C Recommendation)","summary":"The W3C provenance ontology: entities, activities, agents, derivation relations; a meta-model with verification semantics left to consuming domains.","claim_ids":["c2","c3"],"hash":"4ead51c4acf6a4b3a2b8fff35fc24b6ef01dfdc1e5e796a232cc6737bc53db48"},{"id":"s4","type":"framework","url":"https://slsa.dev","title":"SLSA — Supply-chain Levels for Software Artifacts","summary":"Build provenance maturity model L1-L3 with in-toto attestations and Sigstore signing; proves origin and integrity of builds, not behavior.","claim_ids":["c2","c4"],"hash":"bcc8955f284959decb8658bff6aeed4aba02ea4d38c47b859ec559f1695e8593"},{"id":"s5","type":"standard","url":"https://c2pa.org","title":"C2PA Content Credentials — standard and 2026 adoption state","summary":"Cryptographic media provenance; provenance signals, not proof of authenticity; manifests commonly stripped by platforms.","claim_ids":["c2","c5"],"hash":"06eb3c0c27d69686803efe50d1a4690a16752cc5833832360ad89fb2ceab7404"},{"id":"s6","type":"product-docs","url":"https://langfuse.com/blog/2024-07-ai-agent-observability-with-langfuse","title":"AI Agent Observability, Tracing & Evaluation with Langfuse","summary":"What agent observability captures: LLM calls, tool invocations, control flow, context, sessions — the strongest observability description in the category.","claim_ids":["c2","c6"],"hash":"49f579a28c1215acafbe5f8b741fa035a9006500d6b223fa471aff559d285e94"},{"id":"s7","type":"analysis","url":"https://www.morphllm.com/agent-observability","title":"Agent Observability (2026): What the Trace Can't See","summary":"The category's own admission: agent failures are semantic; wrong tool results return 200, loops look like work, traces stay green while agents fail.","claim_ids":["c6"],"hash":"485e30451872ec447c087d897d748cc4fd09f0bfeebdb4b277e7999a2bb23bf6"},{"id":"s8","type":"product-docs","url":"https://palantir.com/docs/foundry/action-types/overview/","title":"Action types — Palantir Foundry Ontology documentation","summary":"Governed action types: typed, permissioned, validated writes with audit logs of actions, parameters, and identity.","claim_ids":["c2","c7"],"hash":"333efa3d5f7da2d37644738a07b1108192e5a3620e38092ab4f820d6014083b3"}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"custody-of-the-answer","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":11,"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":11,"claims_total":11,"sources":8,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}