## §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-logic` - **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-logic/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-logic/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-logic/topology - **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/protocol-logic/voxels - **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/protocol-logic/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-logic/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-logic` v3 · content_hash `3aead632a438c891…` · thread_head genesis · 27 DIVs - **thesis (c_log_1):** The combinatorial matrix treats degenerative conditions and degenerative pharma as entropy targets on the same ledger plane. - c_log_2 [system/active] delta = regen_score − degen_score is the elevation signal for queueing cross articles — disclosed methodology, not a black-box rank. - c_log_3 [system/active] planNextTick() merges gap audit and entropy audit into a single prioritized slug list for grow and matrix/tick. - c_log_4 [system/active] graph_grow_queue prepends matrix-planned slugs before legacy PRIORITY_SLUGS — canonical gaps override editorial hooks. - c_log_5 [system/active] entropy_score rises with orphan count, missing roots, and low-delta written crosses; negentropy_score tracks coverage convergence. - c_log_6 [system/active] parseCrossSlug() resolves article slugs to peptide×target cells for mapping backfill on existing corpus. - c_log_7 [system/active] Pipeline table holds 1254 combo rows after full sync — deterministic seed replaces LLM-only pipelineSeed for inventory. - c_log_8 [system/active] Reflex pass posts system-tier claims that cite live endpoint probes — the graph validates its own API surface. - **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes - **standing objections:** 0 open → https://miscsubjects.com/api/articles/protocol-logic/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-logic/discourse · https://miscsubjects.com/api/protocol ## Article - **slug:** `protocol-logic` - **title:** The Logic of the Logic: Recursive Ledger, Entropy, and Combinatorial Control - **url:** https://miscsubjects.com/a/protocol-logic - **register:** technical - **updated:** 2026-07-17T02:41:02.531Z - **tags:** system, protocol, logic, matrix ## Body ## What this article is This document records the internal logic that builds and maintains the miscsubjects.com corpus. It treats every article as a cell in a combinatorial matrix. The ledger tracks entropy, coverage gaps, and cross-article mappings rather than medical outcomes. ## Who claims what System-tier rules classify articles into peptide_root, condition, or stack using the PEPTIDE_CATALOG of 33 roots. The combinatorial matrix places degenerative conditions and degenerative pharma on the same ledger plane. delta = regen_score − degen_score serves as the elevation signal for queueing cross articles. planNextTick() merges gap audit and entropy audit into a single prioritized slug list. graph_grow_queue prepends matrix-planned slugs before legacy PRIORITY_SLUGS. entropy_score rises with orphan count, missing roots, and low-delta written crosses. parseCrossSlug() resolves article slugs to peptide×target cells for mapping backfill. The pipeline table holds 1254 combo rows after full sync; deterministic seed replaces LLM-only pipelineSeed. Reflex pass posts system-tier claims that cite live endpoint probes. Rest gate (P8) logs energy_spent when a model pass is non-material. Hash chains on sources, provenance, and contributions make post-hoc tampering detectable via verify endpoints. ## What is known Article ontology, entropy scoring, and queue logic run on deterministic functions rather than editorial preference. Full autonomous cron for P0–P8 phases is not continuously running; grow batch is the practical scheduler today. LLM-driven pipelineMap weights are superseded by deterministic computeMapping for new syncs; historical rows may differ. ## What we do not know The exact future coverage delta after the next full matrix tick. Whether all 1254 combo rows remain current after the next deterministic seed update. ## Limitations Meta-logic articles use system tier. They do not compete with human clinical claims on weight. ## Disclaimer Recursive control optimizes corpus shape, not patient outcomes. ## Claims (15) - **c_log_14** [system w=0.35] Meta-logic articles use system tier — they do not compete with human clinical claims on weight. - who_claims: miscsubjects protocol (system tier) - slot: limitations - **c_log_1** [system w=0.35] The combinatorial matrix treats degenerative conditions and degenerative pharma as entropy targets on the same ledger plane. - who_claims: miscsubjects protocol (system tier) - slot: what_it_is - **c_log_2** [system w=0.35] delta = regen_score − degen_score is the elevation signal for queueing cross articles — disclosed methodology, not a black-box rank. - who_claims: miscsubjects protocol (system tier) - slot: what_it_is - **c_log_3** [system w=0.35] planNextTick() merges gap audit and entropy audit into a single prioritized slug list for grow and matrix/tick. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_log_4** [system w=0.35] graph_grow_queue prepends matrix-planned slugs before legacy PRIORITY_SLUGS — canonical gaps override editorial hooks. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_log_5** [system w=0.35] entropy_score rises with orphan count, missing roots, and low-delta written crosses; negentropy_score tracks coverage convergence. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_log_6** [system w=0.35] parseCrossSlug() resolves article slugs to peptide×target cells for mapping backfill on existing corpus. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_log_7** [system w=0.35] Pipeline table holds 1254 combo rows after full sync — deterministic seed replaces LLM-only pipelineSeed for inventory. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_log_8** [system w=0.35] Reflex pass posts system-tier claims that cite live endpoint probes — the graph validates its own API surface. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_log_9** [system w=0.35] Article ontology classifies peptide_root vs condition vs stack using PEPTIDE_CATALOG — 33 roots, not hardcoded 10. - who_claims: miscsubjects protocol (system tier) - slot: who_claims_what - **c_log_10** [system w=0.35] Rest gate (P8) logs energy_spent when a model pass is non-material — waste is visible on the ledger. - who_claims: miscsubjects protocol (system tier) - slot: who_claims_what - **c_log_11** [system w=0.35] Full autonomous cron for all P0–P8 phases is not continuously running — grow batch is the practical scheduler today. - who_claims: miscsubjects protocol (system tier) - slot: what_is_unknown - **c_log_12** [system w=0.35] LLM-driven pipelineMap weights are superseded by deterministic computeMapping for new syncs — historical rows may differ. - who_claims: miscsubjects protocol (system tier) - slot: what_is_unknown - **c_log_13** [system w=0.35] Hash chains on sources, provenance, and contributions make post-hoc tampering detectable via verify endpoints. - who_claims: miscsubjects protocol (system tier) - slot: mechanism - **c_log_15** [system w=0.35] Recursive control optimizes corpus shape, not patient outcomes. - who_claims: miscsubjects protocol (system tier) - slot: disclaimer ## Voxel graph (15 atoms · 15 edges) - full graph: https://miscsubjects.com/api/articles/protocol-logic/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: `ef9a12adb637eff9` - write · grok/build · 2026-06-29T16:53 · hash `db756d8a09cd` - synthesize_body · grok/grok-4.3 · 2026-06-29T16:54 · hash `713aa2b71d91` - synthesize_body · grok/grok-4.3 · 2026-06-29T17:01 · hash `a64170f606a7` - voxel_divide · owner · 2026-07-17T02:41 · hash `ef9a12adb637` ## 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-logic/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-logic/topology - **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"protocol-logic","question":"..."}` - **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest protocol-logic|your evidence` - **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim protocol-logic|tier|assertion` - **iMessage ask:** `protocol-logic|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-logic` - **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-logic/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-logic/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.*