## §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-framework-utility` - **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-framework-utility/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-framework-utility/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-framework-utility/topology - **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/protocol-framework-utility/voxels - **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/protocol-framework-utility/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-framework-utility/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-framework-utility` v3 · content_hash `4f2fec00c9f0687f…` · thread_head genesis · 22 DIVs - **thesis (c_use_1):** The framework separates transport (REST protocol), evidence atoms (claims), and presentation (widgets) — each layer inspectable independently. - c_use_2 [system/active] POST /api/protocol/ask returns gaps[] and ingest_hint — the ledger tells the user what evidence would materially improve the answer. - c_use_3 [system/active] Combinatorial matrix generalizes to any inventory × target grid where regen/degen scores can be defined transparently. - c_use_4 [system/active] Multi-model collaborate preserves each model's original contribution — useful for audit, dispute resolution, and bias detection. - c_use_5 [system/active] Graph canvas GET /api/graph enables cross-article reasoning without copying full bodies into prompt context. - c_use_6 [system/active] iMessage/WhatsApp ingest paths let lay users add anecdotal tier evidence that enters the same hash-chained ledger. - c_use_7 [system/active] Obsidian vault export supports offline research workflows while keeping slug parity with the live corpus. - c_use_8 [system/active] Tasks REST + dispatch directory let cron and human operators invoke protocol steps as named functions. - **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes - **standing objections:** 0 open → https://miscsubjects.com/api/articles/protocol-framework-utility/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-framework-utility/discourse · https://miscsubjects.com/api/protocol ## Article - **slug:** `protocol-framework-utility` - **title:** What This Framework Enables: Use Cases Beyond Peptide Catalogues - **url:** https://miscsubjects.com/a/protocol-framework-utility - **register:** combinatorial_accessible - **updated:** 2026-07-17T02:41:02.243Z - **tags:** system, protocol, applications ## Body ## What this article is This document explains what the miscsubjects.com protocol framework can do beyond peptide catalogues. It describes the build itself. The framework separates transport (REST protocol), evidence atoms (claims), and presentation (widgets). Each layer remains inspectable independently. ## Who claims what Tasks REST and dispatch directory let cron jobs and human operators invoke protocol steps as named functions. Library-snapshot and poll endpoints support periodic external source refresh against existing claims. ## What is known POST /api/protocol/ask returns gaps[] and ingest_hint. The ledger tells the user what evidence would materially improve the answer. Combinatorial matrix generalizes to any inventory × target grid where regen/degen scores can be defined transparently. Multi-model collaborate preserves each model's original contribution. This supports audit, dispute resolution, and bias detection. Graph canvas GET /api/graph enables cross-article reasoning without copying full bodies into prompt context. iMessage/WhatsApp ingest paths let lay users add anecdotal tier evidence that enters the same hash-chained ledger. Obsidian vault export supports offline research workflows while keeping slug parity with the live corpus. ## What is unknown Domain packs beyond peptides require new canonical catalogs. The engine (matrix, grow, claims) is domain-agnostic. Federation across multiple miscsubjects instances is not implemented. Single D1 spine today. Commercial RUO peptide commerce integration is out of scope. The framework is evidence organization only. ## Limitations Accessible register articles still depend on claim tier discipline. Prose alone does not elevate evidence. Usefulness scales with source forest density. Empty articles benefit from populate before ask. ## Disclaimer Framework users remain responsible for their own research and medical decisions. ## Claims (15) - **c_use_14** [system w=0.35] Accessible register articles still depend on claim tier discipline — prose alone does not elevate evidence. - who_claims: miscsubjects protocol (system tier) - slot: limitations - **c_use_1** [system w=0.35] The framework separates transport (REST protocol), evidence atoms (claims), and presentation (widgets) — each layer inspectable independently. - who_claims: miscsubjects protocol (system tier) - slot: what_it_is - **c_use_2** [system w=0.35] POST /api/protocol/ask returns gaps[] and ingest_hint — the ledger tells the user what evidence would materially improve the answer. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_use_3** [system w=0.35] Combinatorial matrix generalizes to any inventory × target grid where regen/degen scores can be defined transparently. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_use_4** [system w=0.35] Multi-model collaborate preserves each model's original contribution — useful for audit, dispute resolution, and bias detection. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_use_5** [system w=0.35] Graph canvas GET /api/graph enables cross-article reasoning without copying full bodies into prompt context. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_use_6** [system w=0.35] iMessage/WhatsApp ingest paths let lay users add anecdotal tier evidence that enters the same hash-chained ledger. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_use_7** [system w=0.35] Obsidian vault export supports offline research workflows while keeping slug parity with the live corpus. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_use_8** [system w=0.35] Tasks REST + dispatch directory let cron and human operators invoke protocol steps as named functions. - who_claims: miscsubjects protocol (system tier) - slot: who_claims_what - **c_use_9** [system w=0.35] Library-snapshot and poll endpoints support periodic external source refresh against existing claims. - who_claims: miscsubjects protocol (system tier) - slot: who_claims_what - **c_use_10** [system w=0.35] Domain packs beyond peptides require new canonical catalogs — the engine (matrix, grow, claims) is domain-agnostic. - who_claims: miscsubjects protocol (system tier) - slot: what_is_unknown - **c_use_11** [system w=0.35] Federation across multiple miscsubjects instances is not implemented — single D1 spine today. - who_claims: miscsubjects protocol (system tier) - slot: what_is_unknown - **c_use_12** [system w=0.35] Commercial RUO peptide commerce integration is out of scope — framework is evidence organization only. - who_claims: miscsubjects protocol (system tier) - slot: what_is_unknown - **c_use_13** [system w=0.35] Usefulness scales with source forest density — empty articles benefit from populate before ask. - who_claims: miscsubjects protocol (system tier) - slot: mechanism - **c_use_15** [system w=0.35] Framework users remain responsible for their own research and medical decisions. - who_claims: miscsubjects protocol (system tier) - slot: disclaimer ## Voxel graph (15 atoms · 15 edges) - full graph: https://miscsubjects.com/api/articles/protocol-framework-utility/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: `a7aeca38b49cf006` - write · grok/build · 2026-06-29T16:53 · hash `662b94328aa0` - synthesize_body · grok/grok-4.3 · 2026-06-29T16:54 · hash `1a4adeb0a403` - synthesize_body · grok/grok-4.3 · 2026-06-29T17:01 · hash `5761ff713095` - voxel_divide · owner · 2026-07-17T02:41 · hash `a7aeca38b49c` ## 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-framework-utility/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-framework-utility/topology - **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"protocol-framework-utility","question":"..."}` - **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest protocol-framework-utility|your evidence` - **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim protocol-framework-utility|tier|assertion` - **iMessage ask:** `protocol-framework-utility|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-framework-utility` - **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-framework-utility/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-framework-utility/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.*