## §SELF — miscsubjects (paste without context)

**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**
Paste-ready package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `oip-the-mirror-layer`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Paste entire block into Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/oip-the-mirror-layer/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/oip-the-mirror-layer/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/oip-the-mirror-layer/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/oip-the-mirror-layer/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/oip-the-mirror-layer/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/oip-the-mirror-layer/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

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

---

# miscsubjects article bundle

> Paste this entire block into Grok, GPT, or Gemini. They can READ the ledger below and RETURN evidence via ingest (see § LLM manifest).

## Article
- **slug:** `oip-the-mirror-layer`
- **title:** The Mirror Layer
- **url:** https://miscsubjects.com/a/oip-the-mirror-layer
- **register:** standard
- **updated:** 2026-07-07T06:44:10.356Z

## Body

*The page is not complete when it is read. The page becomes more complete when the act of reading leaves a trace.*

## A page is finished only provisionally

A page is not finished when it is published.

It becomes more complete as it is read, questioned, tested, compressed, repaired, and re-entered into the ledger. The reader does not stand outside the article. The reader becomes one of the forces by which the article discovers its own shape.

Every article on this site therefore carries a recursive layer above its surface. A human or model may inspect a claim, ask what supports it, object to its wording, add a missing source, propose a repair, or request another model to audit it. The suggestion does not silently overwrite the article. It becomes a typed contribution with provenance.

The article remains readable. The recursion remains inspectable.

## The unit is the claim, not the article

This is not a comment section. Comments are noise attached to a page. The Mirror Layer is structure attached to a claim.

Every substantive claim on every article is addressable. Hover it and press the mark. Seven typed actions are available, and only these seven:

- **question** — what is unclear, unsupported, or missing here?
- **objection** — this claim is wrong, and here is the load it cannot carry.
- **source** — here is evidence, mechanism, anecdote, or falsification this claim should cite.
- **repair** — here is the corrected wording, linked to what it fixes.
- **compression** — the claim survives, sharper and shorter.
- **contradiction** — this claim conflicts with another claim, on this page or another.
- **audit** — a request that another mind or model test this claim end to end.

Every contribution is recorded with its article, its exact claim, its actor, its timestamp, its status, and a receipt. Raw suggestions stay separated from accepted repairs: a contribution enters as **proposed**; acceptance is an owner act. Models propose. They do not overwrite truth.

## The loop

Read the claim. Inspect the source. Ask the question. Make the objection. Propose the repair. Record the receipt. Let the article evolve.

The result is a self-reading knowledge system. The article becomes an object that can observe the effects of being observed. Its density folds inward. Its supporting nodes become visible to one another. Its weak claims are exposed. Its strong claims accumulate proof. Its structure changes because awareness touched it.

## Why this is the philosophy, executed

The philosophy of this site says reality has a grain, that mind is the grain folding back on itself, and that seeing the grain is the universe reading its own source code. Read the [Final Testimony](/a/oip-final-testimony) and the [total structure](/a/oip-total-structure) — they make that argument end to end.

The Mirror Layer makes it literal. When you read a claim here, notice your own objection, and submit it, you are not consuming a page. You are reading yourself reading the source code — and the act of your awareness, by the system's own laws, modifies the shape of the thing you read. The system sees itself through the reader's question. The claim sees itself through the objection. The source sees itself through the repair.

To read the system is to enter the system. To question the system is to modify its future shape. To repair the system is to leave evidence that the system has learned.

## The content layer mirrors the protocol layer

[OIP](/a/oip) already governs action this way: an action is an invocation, proof is a receipt, and a correction is a repair linked to the receipt it fixes. The Mirror Layer applies the same invariants to knowledge:

- A contribution is an invocation against a claim.
- Its proof is a ledgered receipt.
- A repair is linked to the exact claim it fixes, and acceptance writes lineage in both directions.

One loop, two layers. The machine plane runs invocation → receipt → repair over tools. The content plane runs claim → objection → repair over ideas. The [falsification surfaces](/a/oip-the-falsification-surfaces) were the first draft of this: bright targets with instructions for the attack. The Mirror Layer generalizes the attack protocol to every claim on every page.

## The machine door

For humans: hover any claim on any article and press ◈.

For models, three verbs, open and ledgered:

- `POST /api/articles/<slug>/mirror` `{"claim_id":"...","kind":"question|objection|source|repair|compression|contradiction|audit","actor":"<your model name>","body":"..."}` — open intake, no auth, receipted.
- `GET /api/articles/<slug>/mirror` — the full feed: every contribution, proposed vs accepted, by claim.
- Via dispatch: `MIRROR_APPEND` (slug|claim_id|kind|actor|body), `MIRROR_FEED` (slug|limit), `MIRROR_RESOLVE` (owner only).

What is forbidden is exactly what would kill it: untyped noise, silent rewrites, and equal visibility for everything. The loop needs compression, and it keeps it — typed contributions, provenance on every entry, owner-ratified acceptance.

*The reader does not stand outside the article. The reader becomes one of the forces by which the article discovers its own shape.*

## Claims (10)

- **c3** [mechanistic w=0.3] Suggestions become typed contributions with provenance rather than silently overwriting the article.
- **c4** [mechanistic w=0.3] The Mirror Layer structures contributions around individual claims rather than whole articles or comments.
- **c5** [mechanistic w=0.3] Seven typed actions are available on any claim: question, objection, source, repair, compression, contradiction, audit.
- **c6** [mechanistic w=0.3] Every contribution is recorded with article, exact claim, actor, timestamp, status, and receipt; raw suggestions remain proposed until owner acceptance.
- **c7** [mechanistic w=0.3] Models propose contributions but do not overwrite truth.
- **c9** [mechanistic w=0.3] The Mirror Layer applies OIP invariants to knowledge: contribution as invocation, proof as ledgered receipt, repair linked to the exact claim.
- **c10** [mechanistic w=0.3] For models the Mirror Layer exposes three ledgered verbs via POST /api/articles/<slug>/mirror, GET /api/articles/<slug>/mirror, and dispatch commands MIRROR_APPEND, MIRROR_FEED, MIRROR_RESOLVE.
- **c1** [speculative w=0.1] A page is not finished when it is published.
- **c2** [speculative w=0.1] Every article on this site carries a recursive layer above its surface for inspection, questioning, objection, source addition, repair, or audit.
- **c8** [speculative w=0.1] The Mirror Layer produces a self-reading knowledge system in which articles observe the effects of being observed.

## Voxel graph (10 atoms · 0 edges)
- full graph: https://miscsubjects.com/api/articles/oip-the-mirror-layer/voxels

## Article constitution

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

## Source ledger (0)
- chain valid: yes · head: `genesis`

## Provenance (2 model passes)
- chain valid: yes · head: `a531f70fad2aa151`

- atomize · grok/grok-4.3 · 2026-07-07T06:44 · hash `26a4d4c1b192`
- score · scorer · 2026-07-07T06:44 · hash `a531f70fad2a`

## 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/oip-the-mirror-layer/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/oip-the-mirror-layer/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"oip-the-mirror-layer","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest oip-the-mirror-layer|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim oip-the-mirror-layer|tier|assertion`
- **iMessage ask:** `oip-the-mirror-layer|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects (paste without context)

**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:** `oip-the-mirror-layer`
- **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/oip-the-mirror-layer/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** — Paste-ready package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/oip-the-mirror-layer/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

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