## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `pw-0003-the-retrofit`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/pw-0003-the-retrofit/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/pw-0003-the-retrofit/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/pw-0003-the-retrofit/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/pw-0003-the-retrofit/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/pw-0003-the-retrofit/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/pw-0003-the-retrofit/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## MASTHEAD
- **identity:** `pw-0003-the-retrofit` v4 · content_hash `64173ac09caf9f01…` · thread_head genesis
- **thesis (c1):** Existing work migrates to the proven work standard in four steps: claim manifest, evidence binding, named gaps, minted door; PW-0003 executed all four on an already-published article.
  - c9 [system/active] The work object under test, custody-of-the-answer, argues that nine proof disciplines each prove origin, integrity, or observation while none opens the record o
  - c2 [speculative/active] PW-0003 evaluates PARTIAL with 7 of 8 requirements passed, computed by the projection from the manifest rather than asserted.
  - c3 [speculative/active] The unresolved requirement is demand: the original request was made to a Kimi Desktop session, which does not write turns to the build ledger; it was recorded p
  - c4 [speculative/active] Llama 3.3 70B, a model with no authorship on the site, returned DECISION: AFFIRM on the claim under test, receipt inv_gqvj1xprdv, and the verdict is certified o
  - c5 [speculative/active] The first adjudication attempt (inv_bagw2j9n61) was void because its durable record truncated at 795 characters, losing the verdict line; the repair places the 
  - c6 [speculative/active] The three-object family now discriminates: PW-0001 PARTIAL (two gaps), PW-0002 PROVEN (8/8), PW-0003 PARTIAL (one gap); no status was asserted by a worker.
  - c7 [speculative/active] The demand gap evidences a build defect: Kimi Desktop sessions do not land on the events ledger as loop law LP26 requires.
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/pw-0003-the-retrofit/discourse
- **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key
- **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/pw-0003-the-retrofit/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `pw-0003-the-retrofit`
- **title:** A published article was dragged through the proof standard it argues for — one check failed
- **url:** https://miscsubjects.com/a/pw-0003-the-retrofit
- **register:** standard
- **updated:** 2026-08-03T08:53:07.519Z
- **tags:** proven-work, standard, migration, PW-0003, live-receipts

## Body

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 [[custody-of-the-answer]], the comparative survey published the same day. The instrument is the five-check checklist at [[proven-work]]. The result is proven work object PW-0004: 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](https://x.com/i/web/status/2084180317531943088)), 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](https://miscsubjects.com/api/proven-work/custody-of-the-answer). 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-0004** — 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-0004 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-0004 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.


## Claims (9)

- **c5** [speculative w=0.12] The first adjudication attempt (inv_bagw2j9n61) was void because its durable record truncated at 795 characters, losing the verdict line; the repair places the verdict on the first line of output.
  - who_claims: kimi/kimi
  - slot: limitations
  - sources: s5
- **c7** [speculative w=0.12] The demand gap evidences a build defect: Kimi Desktop sessions do not land on the events ledger as loop law LP26 requires.
  - who_claims: kimi/kimi
  - slot: limitations
  - sources: s3
- **c9** [system w=0.35] The work object under test, custody-of-the-answer, argues that nine proof disciplines each prove origin, integrity, or observation while none opens the record of the work for reconstruction.
  - who_claims: kimi
  - slot: who_claims_what
  - sources: s2
- **c1** [speculative w=0.12] Existing work migrates to the proven work standard in four steps: claim manifest, evidence binding, named gaps, minted door; PW-0003 executed all four on an already-published article.
  - who_claims: kimi/kimi
  - slot: what_it_is
  - sources: s1, s3
- **c2** [speculative w=0.12] PW-0003 evaluates PARTIAL with 7 of 8 requirements passed, computed by the projection from the manifest rather than asserted.
  - who_claims: kimi/kimi
  - slot: what_is_known
  - sources: s3
- **c3** [speculative w=0.12] The unresolved requirement is demand: the original request was made to a Kimi Desktop session, which does not write turns to the build ledger; it was recorded post-hoc via the thread intake and prints PARTIAL.
  - who_claims: kimi/kimi
  - slot: what_is_unknown
  - sources: s3
- **c4** [speculative w=0.12] Llama 3.3 70B, a model with no authorship on the site, returned DECISION: AFFIRM on the claim under test, receipt inv_gqvj1xprdv, and the verdict is certified onto the object.
  - who_claims: kimi/kimi
  - slot: who_claims_what
  - sources: s4
- **c6** [speculative w=0.12] The three-object family now discriminates: PW-0001 PARTIAL (two gaps), PW-0002 PROVEN (8/8), PW-0003 PARTIAL (one gap); no status was asserted by a worker.
  - who_claims: kimi/kimi
  - slot: who_claims_what
  - sources: s1, s3
- **c8** [speculative w=0.12] The failed first X post (inv_t7j7drn0tb) is retained in the formation binding as part of the record, which keeps errors alongside successes.
  - who_claims: kimi/kimi
  - slot: who_claims_what
  - sources: s6

## Voxel graph (9 atoms · 20 edges)
- full graph: https://miscsubjects.com/api/articles/pw-0003-the-retrofit/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (6)
- chain valid: yes · head: `231f057a60d0bc37`

### s1 · article
- title: Proven work: the base unit
- url: https://miscsubjects.com/a/proven-work
- summary: The canonical standard and checklist.
- quote: write the claim as a requirement manifest; bind each requirement to the records that already exist; name every gap; mint the door
- claim_ids: c1, c6
- hash: `7ff87f7273028c75`

### s2 · article
- title: Custody of the answer
- url: https://miscsubjects.com/a/custody-of-the-answer
- summary: The work object under test.
- quote: every system proves custody of the answer; none opens the record of the work
- claim_ids: c9
- hash: `e39fd74afba302c9`

### s3 · api
- title: PW-0003 projection
- url: https://miscsubjects.com/api/proven-work/custody-of-the-answer
- summary: Computed status from the manifest.
- quote: PARTIAL, 8 declared requirements, 7 passed, unresolved: demand
- claim_ids: c1, c2, c3, c6, c7
- hash: `d2a593fb700f0881`

### s4 · receipt
- title: Llama 3.3 finding
- url: https://miscsubjects.com/receipt/inv_gqvj1xprdv
- summary: Independent fixed-packet adjudication.
- quote: DECISION: AFFIRM; the claim under test is supported by the evidence named in the manifest, with two gaps honestly stated rather than concealed
- claim_ids: c4
- hash: `8505af831cc44fcf`

### s5 · receipt
- title: Void first attempt
- url: https://miscsubjects.com/receipt/inv_bagw2j9n61
- summary: Finding void under its own contract; repaired by verdict-first output law.
- quote: record truncated before the verdict line
- claim_ids: c5
- hash: `ec090f13128899b5`

### s6 · receipt
- title: Distribution receipt
- url: https://x.com/i/web/status/2084180317531943088
- summary: The X post bound to formation.
- quote: Nine proof systems surveyed. Every one proves custody of the answer.
- claim_ids: c8
- hash: `231f057a60d0bc37`

## Provenance (4 model passes)
- chain valid: yes · head: `32c5241caaabbf0d`

- write · kimi · 2026-08-03T08:43 · hash `8b919100a699`
- repair · kimi · 2026-08-03T08:46 · hash `98aff897b058`
- claim · kimi · 2026-08-03T08:46 · hash `03dcf87b5209`
- edit · unknown · 2026-08-03T08:53 · hash `32c5241caaab`

## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/pw-0003-the-retrofit/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/pw-0003-the-retrofit/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"pw-0003-the-retrofit","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest pw-0003-the-retrofit|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim pw-0003-the-retrofit|tier|assertion`
- **iMessage ask:** `pw-0003-the-retrofit|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `pw-0003-the-retrofit`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/pw-0003-the-retrofit/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/pw-0003-the-retrofit/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*