## §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-api-structure` - **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-api-structure/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-api-structure/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-api-structure/topology - **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/protocol-api-structure/voxels - **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/protocol-api-structure/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-api-structure/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-api-structure` v3 · content_hash `a2fa4db25480b78a…` · thread_head genesis · 14 DIVs - **thesis (c_api_1):** GET /api/protocol returns the live machine contract — endpoint list, body schemas, and phase definitions; it is the authoritative API map. - c_api_2 [system/active] The protocol splits into two planes: /api/articles for CRUD and sub-resources, and /api/protocol for phase operations (populate, review, score, grow). - c_api_3 [system/active] Claims live in article.meta.claims[]; sources in meta.sources[] with prev/hash chain; provenance in meta.provenance[] — all append-only. - c_api_4 [system/active] POST /api/protocol/draft validates tiers, optionally verifies source URLs, hash-chains sources, and publishes or updates the article head. - c_api_5 [system/active] POST /api/protocol/populate ingests science + social sources into an article without rewriting body — forest-first growth. - c_api_6 [system/active] POST /api/protocol/collaborate lets Kimi or Gemini read topology and append 1–3 claims with posted_by; optional require_challenge for adversary pass. - c_api_7 [system/active] POST /api/protocol/score recomputes claim.weight from base(tier) + endorsement_sum − adversary_sum; claims below cut_threshold get status:cut. - c_api_8 [system/active] GET /api/protocol/next?role=writer atomically claims one open task; POST /api/protocol/run executes one scheduler tick inside the 100s request cap. - **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes - **standing objections:** 0 open → https://miscsubjects.com/api/articles/protocol-api-structure/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-api-structure/discourse · https://miscsubjects.com/api/protocol ## Article - **slug:** `protocol-api-structure` - **title:** Protocol API Structure: REST Surface, Objects, and Phase Machine - **url:** https://miscsubjects.com/a/protocol-api-structure - **register:** technical - **updated:** 2026-07-17T02:41:01.604Z - **tags:** system, protocol, api ## Body ## What this article is This document describes the live REST surface and phase machine for miscsubjects.com. It is system documentation, not a compound catalogue entry. ## Who claims what The build itself defines the contract. GET /api/protocol returns the authoritative machine map. API_QUICKMAP.md and PROTOCOL_SPEC.md are static mirrors of that contract. ## What is known GET /api/protocol exposes the endpoint list, body schemas, and phase definitions. Two planes exist: /api/articles for CRUD and sub-resources, and /api/protocol for phase operations. Claims live in article.meta.claims[]. Sources live in meta.sources[] with prev/hash chain. All writes are append-only. POST /api/protocol/draft validates tiers, optionally verifies source URLs, and hash-chains sources. POST /api/protocol/populate ingests sources into an article without rewriting the body. POST /api/protocol/collaborate lets Kimi or Gemini append 1–3 claims. POST /api/protocol/score recomputes claim.weight and applies status:cut when below threshold. GET /api/protocol/next?role=writer hands out one open task atomically. POST /api/protocol/run executes one scheduler tick inside the 100-second request limit. GET /api/matrix/gaps lists missing roots and cross cells. POST /api/matrix/seed fills from the canonical catalog. Webhook POST /api/articles/{slug}/webhook accepts atomic appends of kind:claim|source|widget. ## What we do not know Not every phase listed in PROTOCOL_SPEC.md has a deployed cron worker. Some phases still require manual POST /api/protocol/grow or dispatch tools. Rate limits and per-tenant quotas on gateway model calls are environment-dependent and not shown in the public contract. ## Limitations Protocol slugs are immutable. Hard DELETE is blocked. Corrections use PATCH status:retracted or new revisions. Every phase transition must finish inside Cloudflare’s ~100-second cap. Batch work uses grow batch or cron ticks. ## Disclaimer This API map is a research-ledger transport layer only. It grants no medical authority. ## Claims (16) - **c_api_16** [system w=0.35] Immutable slugs (protocol) block DELETE; corrections use PATCH status:retracted or new revisions, never hard delete. - who_claims: miscsubjects protocol (system tier) - slot: limitations - **c_api_1** [system w=0.35] GET /api/protocol returns the live machine contract — endpoint list, body schemas, and phase definitions; it is the authoritative API map. - who_claims: miscsubjects protocol (system tier) - slot: what_it_is - **c_api_2** [system w=0.35] The protocol splits into two planes: /api/articles for CRUD and sub-resources, and /api/protocol for phase operations (populate, review, score, grow). - who_claims: miscsubjects protocol (system tier) - slot: what_it_is - **c_api_3** [system w=0.35] Claims live in article.meta.claims[]; sources in meta.sources[] with prev/hash chain; provenance in meta.provenance[] — all append-only. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_api_4** [system w=0.35] POST /api/protocol/draft validates tiers, optionally verifies source URLs, hash-chains sources, and publishes or updates the article head. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_api_5** [system w=0.35] POST /api/protocol/populate ingests science + social sources into an article without rewriting body — forest-first growth. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_api_6** [system w=0.35] POST /api/protocol/collaborate lets Kimi or Gemini read topology and append 1–3 claims with posted_by; optional require_challenge for adversary pass. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_api_7** [system w=0.35] POST /api/protocol/score recomputes claim.weight from base(tier) + endorsement_sum − adversary_sum; claims below cut_threshold get status:cut. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_api_8** [system w=0.35] GET /api/protocol/next?role=writer atomically claims one open task; POST /api/protocol/run executes one scheduler tick inside the 100s request cap. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_api_9** [system w=0.35] GET /api/matrix/gaps audits missing peptide roots and unwritten cross cells; POST /api/matrix/seed deterministically fills pipeline from canonical catalog. - who_claims: miscsubjects protocol (system tier) - slot: what_is_known - **c_api_10** [system w=0.35] Webhook POST /api/articles/{slug}/webhook accepts atomic append of kind:claim|source|widget without replacing article head. - who_claims: miscsubjects protocol (system tier) - slot: who_claims_what - **c_api_11** [system w=0.35] The build documents API_QUICKMAP.md and PROTOCOL_SPEC.md as human-readable mirrors; GET /api/protocol is the runtime truth. - who_claims: miscsubjects protocol (system tier) - slot: who_claims_what - **c_api_12** [system w=0.35] Not every PROTOCOL_SPEC phase has a dedicated cron worker deployed yet — some remain manual via POST /api/protocol/grow or dispatch tools. - who_claims: miscsubjects protocol (system tier) - slot: what_is_unknown - **c_api_13** [system w=0.35] Rate limits and per-tenant quotas on gateway model calls are environment-dependent — not exposed in the public contract. - who_claims: miscsubjects protocol (system tier) - slot: what_is_unknown - **c_api_14** [system w=0.35] Phase transitions are stateless per request: each POST must finish inside Cloudflare's ~100s cap; batch work uses grow batch or cron ticks. - who_claims: miscsubjects protocol (system tier) - slot: mechanism - **c_api_15** [system w=0.35] This API map does not grant medical authority — it is a research-ledger transport layer only. - who_claims: miscsubjects protocol (system tier) - slot: disclaimer ## Voxel graph (16 atoms · 16 edges) - full graph: https://miscsubjects.com/api/articles/protocol-api-structure/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: `8af78dc9c8f77fc2` - write · grok/build · 2026-06-29T16:53 · hash `c401918a3550` - synthesize_body · grok/grok-4.3 · 2026-06-29T16:54 · hash `49ed398e8b7f` - synthesize_body · grok/grok-4.3 · 2026-06-29T17:00 · hash `ab33048eebe7` - voxel_divide · owner · 2026-07-17T02:41 · hash `8af78dc9c8f7` ## 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-api-structure/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-api-structure/topology - **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"protocol-api-structure","question":"..."}` - **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest protocol-api-structure|your evidence` - **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim protocol-api-structure|tier|assertion` - **iMessage ask:** `protocol-api-structure|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-api-structure` - **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-api-structure/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-api-structure/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.*