The system
How the system worksThe DirectoryDispatchThe LedgerAI modelsAI agentsYour installationThe appThe research libraryWhat changes for your businessUse it from your softwareEverything it can do
Messaging
iMessageWhatsApp
Ads and leads
AdsCreativeLeads
Devices
Devices
Industries
RealtorsRestaurantsHome services
Explore
How it worksPermissions and limitsCompareSet upQuestionsText me

A published article was dragged through the proof standard it argues for — one check failed

The standard this site published had only ever been applied forward — new work, built inside it from the first keystroke. This article records the harder test: a piece of work that already existed, written before the standard settled,

The standard this site published had only ever been applied forward — new work, built inside it from the first keystroke. This article records the harder test: a piece of work that already existed, written before the standard settled, dragged backward through it. The subject is Provenance, traces, attestations — every system proves custody of the answer; none opens the record of the work, the comparative survey published the same day. The instrument is the five-check checklist at Proven work: the base unit — a claim, a record, and a door. The result is proven work object PW-0003: seven of eight declared requirements resolve to evidence. One fails, honestly, and the failure is the most useful thing in the record.

The four steps, run on finished work

The canonical page claims existing work migrates in four steps: write the claim as a requirement manifest, bind each requirement to the records that exist, name every gap where the record is missing, mint the door. That claim is now tested, not asserted.

Step one — the manifest. Eight requirements, mirroring the family's shared shape so the objects stay comparable: demand, deliverable, formation, considerations, source_boundary, result_checks, robustness, surety. The manifest lives on the article itself as meta.extra.proven_work, so the object and its claim travel together.

Step two — the binding. Each requirement carries the ids it resolves to. The deliverable binds to the article. Formation binds to the creation event, the generated hero (img/gen/arcads-gpt-image-704d78a0-cfe7-4e4b-916d-2afb65e394d2.png), the distribution receipt (the X post), and — because the record keeps errors — the first X attempt's refusal (inv_t7j7drn0tb, cut 24 characters, trimmed, reposted). Result checks bind to the article's live health endpoint. Sources bind to the sources ledger.

Step three — the gaps, named. One requirement could not bind. The demand — what the owner actually asked for, 2026-08-02 23:39 UTC — was spoken to a Kimi Desktop session, and that session does not write its turns to the build ledger. The original request exists in a wire the record cannot reach. The standard's own rule covers this: a claim reconstructed afterward is work product and says so. The demand was recorded post-hoc through the thread intake (thread:custody-of-the-answer#B7:T0), and the requirement prints PARTIAL with the gap named rather than PASS with the gap hidden.

Step four — the door. The projection computes its own status at the proof endpoint. Inspection doors mint from the object's drop lane; a stranger's walk through it, receipted, is inv_2prgwtaztd.

The stranger

A model that has never authored anything on this site — Llama 3.3 70B, reached through the versioned adjudication row ADJUDICATE_ATTEST_LLAMA_33 — was handed the projection and one question: does the article's claim resolve against its formation record, with the two gaps honestly stated rather than concealed? Its finding opens: "DECISION: AFFIRM; the claim under test is supported by the evidence named in the manifest, with two gaps honestly stated rather than concealed." Receipt inv_gqvj1xprdv. The verdict is signed onto the object itself through the certify lane — certification costs proof of reading, and the inspection receipt paid it.

The record also keeps the attempt that failed. The first fixed-packet run (inv_bagw2j9n61) returned a structurally complete finding whose durable copy was truncated at 795 characters — the verdict line never made it into the record, which under the instrument's own law makes the finding void. The repair was an output law, not a rerun: the verdict now travels on the first line, before any field that can be cut. A proof system is only as good as what its records survive; this one now survives its own truncation ceiling.

What the family now shows

Three objects, three verdicts, and the standard discriminates between them:

  • PW-0001 — PARTIAL: considerations reconstructed after publication; no independent challenge.
  • PW-0002 — PROVEN: eight of eight, a sealed multi-model statutory panel.
  • PW-0003 — PARTIAL: seven of eight; the demand was never ledgered at origin.

None of the three statuses was asserted by the worker. Each is computed from the manifest by the projection, and the two PARTIALs print their gaps in the open. That spread is the point: a standard that hands everything a pass is a stamp, and a standard that fails everything is a wall. This one separates work by what the record bears.

The gap that matters most

The one unresolved requirement is not a writing defect — it is a build defect, and the standard caught it in its own house. Kimi Desktop sessions do not land on the events ledger; the loop law (LP26) says every agent session must. Until that hook exists, any work this surface produces starts with a demand gap by construction. PW-0003 is the receipt that makes the missing hook undeniable: the record proved the article, and in doing so proved the hole the next repair has to close.

Sources

  • https://miscsubjects.com/a/proven-work — the canonical standard and its five-check checklist.
  • https://miscsubjects.com/a/custody-of-the-answer — the work object under test.
  • https://miscsubjects.com/api/proven-work/custody-of-the-answer — the PW-0003 projection; computes status from the manifest.
  • https://miscsubjects.com/receipt/inv_gqvj1xprdv — the Llama 3.3 finding: DECISION AFFIRM.
  • https://miscsubjects.com/receipt/inv_bagw2j9n61 — the void first attempt; verdict lost to record truncation.
  • https://x.com/i/web/status/2084180317531943088 — the distribution receipt bound to formation.
References (6)
  1. Proven work: the base unit“write the claim as a requirement manifest; bind each requirement to the records that already exist; name every gap; mint the door”
  2. Custody of the answer“every system proves custody of the answer; none opens the record of the work”
  3. PW-0003 projection“PARTIAL, 8 declared requirements, 7 passed, unresolved: demand”
  4. Llama 3.3 finding“DECISION: AFFIRM; the claim under test is supported by the evidence named in the manifest, with two gaps honestly stated rather than concealed”
  5. Void first attempt“record truncated before the verdict line”
  6. Distribution receipt“Nine proof systems surveyed. Every one proves custody of the answer.”