## §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:** `protocol-widgets`
- **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/protocol-widgets/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/protocol-widgets/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/protocol-widgets/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/protocol-widgets/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/protocol-widgets/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/protocol-widgets/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:** `protocol-widgets` v3 · content_hash `3982c1fdf885ddd2…` · thread_head genesis · 12 DIVs
- **thesis (c_wid_1):** Every attachSelf() response includes _self.what, _self.how_to_use, and _self.related URLs — widgets are self-explaining payloads, not static HTML.
  - c_wid_2 [system/active] FEATURES in self_explain.js is the canonical feature index; system-map article exposes it for humans and LLMs.
  - c_wid_3 [system/active] sourceToWidget() maps hash-chained ledger sources to native platform cards (reddit, x, pubmed, youtube, imessage) on the reader page.
  - c_wid_4 [system/active] buildInlineEmbedMap() resolves [[embed:slug]] markers in article body to horizontal native cards without external iframes.
  - c_wid_5 [system/active] normalizeWidget() in vault_widgets.js unifies directory rows, tasks, events, and claims into vault-card rails with shortHash ids.
  - c_wid_6 [system/active] meta.widgets[] supports imessage|quote|stat|note|gallery types as JSON series independent of the source ledger.
  - c_wid_7 [system/active] Graph canvas widgets come from GET /api/graph — nodes are claims/sources, edges are supported_by, posted_by, challenges, embeds.
  - c_wid_8 [system/active] explainGrowStep() returns human-readable why/how for each grow-queue step — operational widget for cron operators.
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/protocol-widgets/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/protocol-widgets/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `protocol-widgets`
- **title:** Protocol Widgets: Self-Explanation, Vault Cards, and Native Embeds
- **url:** https://miscsubjects.com/a/protocol-widgets
- **register:** technical
- **updated:** 2026-07-17T02:41:02.828Z
- **tags:** system, protocol, widgets

## Body

## What this article is

Protocol Widgets document the rendering system on miscsubjects.com.  
It explains how evidence appears as self-contained cards and embeds.  
The audience is operators who maintain the site, models that consume the API, and readers who view articles.

## Who claims what

Widgets are self-explaining.  
Every attachSelf() response returns _self.what, _self.how_to_use, and _self.related URLs.  
explainGrowStep() returns human-readable why/how text for each grow-queue step.  
Platform logos and rail styling live in widgets/platform_logos.js and widgets/social.js.

## What is known

FEATURES in self_explain.js is the canonical feature index.  
sourceToWidget() maps ledger sources to native cards for reddit, x, pubmed, youtube, and imessage.  
buildInlineEmbedMap() turns [[embed:slug]] markers into horizontal native cards.  
normalizeWidget() unifies directory rows, tasks, events, and claims into vault-card rails with shortHash ids.  
meta.widgets[] supports imessage, quote, stat, note, and gallery types as JSON series.  
Graph canvas widgets come from GET /api/graph with nodes as claims or sources and edges as supported_by, posted_by, challenges, or embeds.  
Widget rendering is deterministic from ledger JSON.  
Third-party oEmbed iframes are avoided for Reddit and X.

## What we do not know

Not all admin pages yet consume _self blocks.  
Widget accessibility with ARIA on rails remains partial.

## Limitations

Widgets display evidence only.  
They do not score or elevate claims.  
Weighting stays in claim.weight from /score.

## Disclaimer

This is not medical advice.  
Social anecdote widgets are anecdotal tier by definition.

## Claims (15)

- **c_wid_14** [system w=0.35] Widgets display evidence; they do not score or elevate claims — weighting remains in claim.weight from /score.
  - who_claims: miscsubjects protocol (system tier)
  - slot: limitations
- **c_wid_1** [system w=0.35] Every attachSelf() response includes _self.what, _self.how_to_use, and _self.related URLs — widgets are self-explaining payloads, not static HTML.
  - who_claims: miscsubjects protocol (system tier)
  - slot: what_it_is
- **c_wid_2** [system w=0.35] FEATURES in self_explain.js is the canonical feature index; system-map article exposes it for humans and LLMs.
  - who_claims: miscsubjects protocol (system tier)
  - slot: what_it_is
- **c_wid_3** [system w=0.35] sourceToWidget() maps hash-chained ledger sources to native platform cards (reddit, x, pubmed, youtube, imessage) on the reader page.
  - who_claims: miscsubjects protocol (system tier)
  - slot: what_is_known
- **c_wid_4** [system w=0.35] buildInlineEmbedMap() resolves [[embed:slug]] markers in article body to horizontal native cards without external iframes.
  - who_claims: miscsubjects protocol (system tier)
  - slot: what_is_known
- **c_wid_5** [system w=0.35] normalizeWidget() in vault_widgets.js unifies directory rows, tasks, events, and claims into vault-card rails with shortHash ids.
  - who_claims: miscsubjects protocol (system tier)
  - slot: what_is_known
- **c_wid_6** [system w=0.35] meta.widgets[] supports imessage|quote|stat|note|gallery types as JSON series independent of the source ledger.
  - who_claims: miscsubjects protocol (system tier)
  - slot: what_is_known
- **c_wid_7** [system w=0.35] Graph canvas widgets come from GET /api/graph — nodes are claims/sources, edges are supported_by, posted_by, challenges, embeds.
  - who_claims: miscsubjects protocol (system tier)
  - slot: what_is_known
- **c_wid_8** [system w=0.35] explainGrowStep() returns human-readable why/how for each grow-queue step — operational widget for cron operators.
  - who_claims: miscsubjects protocol (system tier)
  - slot: who_claims_what
- **c_wid_9** [system w=0.35] Platform logos and rail styling live in widgets/platform_logos.js and widgets/social.js — presentation layer only, not ledger truth.
  - who_claims: miscsubjects protocol (system tier)
  - slot: who_claims_what
- **c_wid_10** [system w=0.35] Third-party oEmbed iframes are avoided for Reddit/X — native cards use ledger quote+url for auditability.
  - who_claims: miscsubjects protocol (system tier)
  - slot: what_is_known
- **c_wid_11** [system w=0.35] Not all admin pages yet consume _self blocks — some legacy HTML predates attachSelf.
  - who_claims: miscsubjects protocol (system tier)
  - slot: what_is_unknown
- **c_wid_12** [system w=0.35] Widget accessibility (ARIA on rails) is partial — visual cards exist before full a11y pass.
  - who_claims: miscsubjects protocol (system tier)
  - slot: what_is_unknown
- **c_wid_13** [system w=0.35] Widget rendering is deterministic from ledger JSON — same source hash always maps to same card content.
  - who_claims: miscsubjects protocol (system tier)
  - slot: mechanism
- **c_wid_15** [system w=0.35] Not medical advice — social anecdote widgets are anecdotal tier by definition.
  - who_claims: miscsubjects protocol (system tier)
  - slot: disclaimer

## Voxel graph (15 atoms · 15 edges)
- full graph: https://miscsubjects.com/api/articles/protocol-widgets/voxels

## Article constitution

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

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

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

- write · grok/build · 2026-06-29T16:53 · hash `a480a03f67ba`
- synthesize_body · grok/grok-4.3 · 2026-06-29T16:54 · hash `af98e34a0dbb`
- synthesize_body · grok/grok-4.3 · 2026-06-29T17:00 · hash `548c7a900078`
- voxel_divide · owner · 2026-07-17T02:41 · hash `ca9ea576277e`

## 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/protocol-widgets/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/protocol-widgets/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"protocol-widgets","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest protocol-widgets|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim protocol-widgets|tier|assertion`
- **iMessage ask:** `protocol-widgets|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:** `protocol-widgets`
- **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/protocol-widgets/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/protocol-widgets/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.*