{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"slug":"protocol-framework-utility","title":"What This Framework Enables: Use Cases Beyond Peptide Catalogues","body":"## What this article is\n\nThis document explains what the miscsubjects.com protocol framework can do beyond peptide catalogues. It describes the build itself.\n\nThe framework separates transport (REST protocol), evidence atoms (claims), and presentation (widgets). Each layer remains inspectable independently.\n\n## Who claims what\n\nTasks REST and dispatch directory let cron jobs and human operators invoke protocol steps as named functions.\n\nLibrary-snapshot and poll endpoints support periodic external source refresh against existing claims.\n\n## What is known\n\nPOST /api/protocol/ask returns gaps[] and ingest_hint. The ledger tells the user what evidence would materially improve the answer.\n\nCombinatorial matrix generalizes to any inventory × target grid where regen/degen scores can be defined transparently.\n\nMulti-model collaborate preserves each model's original contribution. This supports audit, dispute resolution, and bias detection.\n\nGraph canvas GET /api/graph enables cross-article reasoning without copying full bodies into prompt context.\n\niMessage/WhatsApp ingest paths let lay users add anecdotal tier evidence that enters the same hash-chained ledger.\n\nObsidian vault export supports offline research workflows while keeping slug parity with the live corpus.\n\n## What is unknown\n\nDomain packs beyond peptides require new canonical catalogs. The engine (matrix, grow, claims) is domain-agnostic.\n\nFederation across multiple miscsubjects instances is not implemented. Single D1 spine today.\n\nCommercial RUO peptide commerce integration is out of scope. The framework is evidence organization only.\n\n## Limitations\n\nAccessible register articles still depend on claim tier discipline. Prose alone does not elevate evidence.\n\nUsefulness scales with source forest density. Empty articles benefit from populate before ask.\n\n## Disclaimer\n\nFramework users remain responsible for their own research and medical decisions.","hero":null,"images":[],"style":{},"tags":["system","protocol","applications"],"category":null,"model":"grok/build (protocol-meta-articles)","ledger":{"href":"/api/articles/protocol-framework-utility/ledger","live":true},"embeds":["protocol","protocol-api-structure","protocol-widgets","protocol-claims","protocol-logic"],"widgets":[],"home":true,"claims":[{"id":"c_use_1","text":"The framework separates transport (REST protocol), evidence atoms (claims), and presentation (widgets) — each layer inspectable independently.","section":"what it is","slot":"what_it_is","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_2","text":"POST /api/protocol/ask returns gaps[] and ingest_hint — the ledger tells the user what evidence would materially improve the answer.","section":"what is known","slot":"what_is_known","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_3","text":"Combinatorial matrix generalizes to any inventory × target grid where regen/degen scores can be defined transparently.","section":"what is known","slot":"what_is_known","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_4","text":"Multi-model collaborate preserves each model's original contribution — useful for audit, dispute resolution, and bias detection.","section":"what is known","slot":"what_is_known","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_5","text":"Graph canvas GET /api/graph enables cross-article reasoning without copying full bodies into prompt context.","section":"what is known","slot":"what_is_known","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_6","text":"iMessage/WhatsApp ingest paths let lay users add anecdotal tier evidence that enters the same hash-chained ledger.","section":"what is known","slot":"what_is_known","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_7","text":"Obsidian vault export supports offline research workflows while keeping slug parity with the live corpus.","section":"what is known","slot":"what_is_known","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_8","text":"Tasks REST + dispatch directory let cron and human operators invoke protocol steps as named functions.","section":"who claims what","slot":"who_claims_what","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_9","text":"Library-snapshot and poll endpoints support periodic external source refresh against existing claims.","section":"who claims what","slot":"who_claims_what","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_10","text":"Domain packs beyond peptides require new canonical catalogs — the engine (matrix, grow, claims) is domain-agnostic.","section":"what is unknown","slot":"what_is_unknown","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_11","text":"Federation across multiple miscsubjects instances is not implemented — single D1 spine today.","section":"what is unknown","slot":"what_is_unknown","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_12","text":"Commercial RUO peptide commerce integration is out of scope — framework is evidence organization only.","section":"what is unknown","slot":"what_is_unknown","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_13","text":"Usefulness scales with source forest density — empty articles benefit from populate before ask.","section":"mechanism","slot":"mechanism","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_14","text":"Accessible register articles still depend on claim tier discipline — prose alone does not elevate evidence.","section":"limitations","slot":"limitations","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_15","text":"Framework users remain responsible for their own research and medical decisions.","section":"disclaimer","slot":"disclaimer","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35}],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"combinatorial_accessible","status":"published","revisions":2,"contributions":[{"seq":0,"id":"k1","ts":"2026-06-29T16:54:34.232Z","model":"grok/grok-4.3","role":"editor","action":"synthesize_body","payload":{"chars":2930,"claims_used":0,"legibility":{"pass":true,"reasons":[]}},"rationale":"Reader body rewritten from ranked ledger topology — plain English","tokens_in":1142,"tokens_out":641,"cost":0.00303,"prev_hash":"genesis","hash":"337584ce173f707ca162d601bff2aea009e97353c0ca1e10534f9080d2853953"},{"seq":1,"id":"k2","ts":"2026-06-29T17:01:09.792Z","model":"grok/grok-4.3","role":"editor","action":"synthesize_body","payload":{"chars":1932,"claims_used":15,"legibility":{"pass":true,"reasons":[]}},"rationale":"Reader body rewritten from ranked ledger topology — plain English","tokens_in":1456,"tokens_out":337,"cost":0.0026625,"prev_hash":"337584ce173f707ca162d601bff2aea009e97353c0ca1e10534f9080d2853953","hash":"74d5ae7c6729859303648abd13169b9a4becc140daf3987c075844de0aec776a"}],"provenance":[{"ts":"2026-06-29T16:53:49.497Z","model":"grok/build","action":"write","prompt":"post_protocol_meta_articles.mjs","input":"protocol-framework-utility","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"662b94328aa0c38d637a41ec3d51995f809beb51136168c8f19e932c65e0dc40"},{"ts":"2026-06-29T16:54:34.232Z","model":"grok/grok-4.3","action":"synthesize_body","prompt":"","input":"protocol-framework-utility","response":"## Regeneration vs degeneration — where this fits\nThe body is always doing two things at once: breaking down and building back. A condition persists when breakdown outruns repair. Most drugs used for symptoms suppress a signal without fixing the tissue that caused the signal. This framework places one compound in the repair-pathway ledger. It asks whether the compound is studied for new blood vessels, repair-cell migration, nerve regrowth, gut lining, or neural connections.\n\n## What it is\nThe framework is a map. It takes one compound and runs it through a fixed set of questions. The map starts with the regeneration-versus-degeneration frame. It then lists what the compound is, how it is proposed to work, why the logic holds, why people try it, how many people try it, the evidence count, what scientists state, what users report on Reddit and X, what remains unknown, and the safety limits recorded so far.\n\n## How it works\nThe framework works by holding every claim to the same sequence. First, state the degeneration problem. Second, state the proposed repair action. Third, list the steps the compound is said to follow. Fourth, mark each step as human data, animal data, or anecdote. Fifth, record what each data type proves and what it leaves open.\n\n## Why it would work (logic chain)\nStep 1: Tissue breaks down faster than it rebuilds.  \nStep 2: A repair pathway exists that can move cells, grow vessels, or restore lining.  \nStep 3: The compound is studied for one or more of those steps.  \nStep 4: If the pathway activates and the breakdown rate drops, net repair rises.  \nStep 5: The logic chain stops at the data limit; it does not extend past what the source type can show.\n\n## Why people take it\nPeople take it when they want a repair option instead of signal suppression. They look for reported changes in tissue recovery, reduced breakdown signals, or restored function. The framework records the stated reason without adding claims.\n\n## How many people take it\nThe ledger sho","tokens_in":1142,"tokens_out":641,"cost":0,"prev":"662b94328aa0c38d637a41ec3d51995f809beb51136168c8f19e932c65e0dc40","hash":"1a4adeb0a403e1a5a58266e6512052deeea941eb4d8029db57a6338e4e14ffe3"},{"ts":"2026-06-29T17:01:09.792Z","model":"grok/grok-4.3","action":"synthesize_body","prompt":"","input":"protocol-framework-utility","response":"## What this article is\n\nThis document explains what the miscsubjects.com protocol framework can do beyond peptide catalogues. It describes the build itself.\n\nThe framework separates transport (REST protocol), evidence atoms (claims), and presentation (widgets). Each layer remains inspectable independently.\n\n## Who claims what\n\nTasks REST and dispatch directory let cron jobs and human operators invoke protocol steps as named functions.\n\nLibrary-snapshot and poll endpoints support periodic external source refresh against existing claims.\n\n## What is known\n\nPOST /api/protocol/ask returns gaps[] and ingest_hint. The ledger tells the user what evidence would materially improve the answer.\n\nCombinatorial matrix generalizes to any inventory × target grid where regen/degen scores can be defined transparently.\n\nMulti-model collaborate preserves each model's original contribution. This supports audit, dispute resolution, and bias detection.\n\nGraph canvas GET /api/graph enables cross-article reasoning without copying full bodies into prompt context.\n\niMessage/WhatsApp ingest paths let lay users add anecdotal tier evidence that enters the same hash-chained ledger.\n\nObsidian vault export supports offline research workflows while keeping slug parity with the live corpus.\n\n## What is unknown\n\nDomain packs beyond peptides require new canonical catalogs. The engine (matrix, grow, claims) is domain-agnostic.\n\nFederation across multiple miscsubjects instances is not implemented. Single D1 spine today.\n\nCommercial RUO peptide commerce integration is out of scope. The framework is evidence organization only.\n\n## Limitations\n\nAccessible register articles still depend on claim tier discipline. Prose alone does not elevate evidence.\n\nUsefulness scales with source forest density. Empty articles benefit from populate before ask.\n\n## Disclaimer\n\nFramework users remain responsible for their own research and medical decisions.","tokens_in":1456,"tokens_out":337,"cost":0,"prev":"1a4adeb0a403e1a5a58266e6512052deeea941eb4d8029db57a6338e4e14ffe3","hash":"5761ff713095cb0a18fe7b15651fdfbc6002a07a7175d6c5a111615cfb01b798"},{"ts":"2026-07-17T02:41:02.243Z","model":"owner","action":"voxel_divide","prompt":"","input":"protocol-framework-utility","response":"22 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"5761ff713095cb0a18fe7b15651fdfbc6002a07a7175d6c5a111615cfb01b798","hash":"a7aeca38b49cf00610954a52497c888570f58ba53886d509c9371b67804722ca"}],"energy":{"passes":4,"tokens_in":2598,"tokens_out":978,"tokens_total":3576,"cost_usd":0,"models":{"grok/build":1,"grok/grok-4.3":2,"owner":1},"head":"a7aeca38b49cf00610954a52497c888570f58ba53886d509c9371b67804722ca"},"posted_at":"2026-06-29T16:53:49.497Z","created_at":"2026-06-29T16:53:49.497Z","updated_at":"2026-07-17T02:41:02.243Z","machine":{"shape":"article.machine/v1","slug":"protocol-framework-utility","kind":"article","read":{"human":"https://miscsubjects.com/a/protocol-framework-utility","json":"https://miscsubjects.com/api/articles/protocol-framework-utility","bundle":"https://miscsubjects.com/api/articles/protocol-framework-utility/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":15,"sources":0,"contributions":2,"revisions":2,"objections_url":"https://miscsubjects.com/api/articles/protocol-framework-utility/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=protocol-framework-utility","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"protocol-framework-utility\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"protocol-framework-utility\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/protocol-framework-utility/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"protocol-framework-utility\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/protocol-framework-utility | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/protocol-framework-utility","json":"/api/articles/protocol-framework-utility","markdown":"/api/articles/protocol-framework-utility/bundle?format=markdown","skill":"/api/articles/protocol-framework-utility/skill","topology":"/api/articles/protocol-framework-utility/topology","versions":"/api/articles/protocol-framework-utility/revisions","invocations":"/api/articles/protocol-framework-utility/invocations"},"editorial_review":null,"editorial_audit":{"slug":"protocol-framework-utility","ok":false,"issues":[{"code":"headline_context","message":"headline depends on surrounding context instead of naming its subject: \"What This Framework Enables: Use Cases Beyond Peptide Catalogues\"","replacement":"Write a shorter literal headline naming the article subject and its central event or claim."},{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"4f2fec00c9f0687f36bdb2ce42a66c18e795d0e0596dd75ea48b907a2a8fcc4e","object":{"object_type":"article-object","identity":{"id":"article:protocol-framework-utility","slug":"protocol-framework-utility","title":"What This Framework Enables: Use Cases Beyond Peptide Catalogues"},"law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]},"expressions":{"human":{"route":"/a/protocol-framework-utility","role":"explain","audience":"human"},"skill":{"route":"/api/articles/protocol-framework-utility/skill","role":"direct behavior","audience":"model","content":"---\nname: protocol-framework-utility\ndescription: Apply the What This Framework Enables: Use Cases Beyond Peptide Catalogues article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# What This Framework Enables: Use Cases Beyond Peptide Catalogues\n\nThis Skill is the behavioral expression of [the canonical article](/a/protocol-framework-utility). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/protocol-framework-utility.\n- Read claims and relationships at /api/articles/protocol-framework-utility/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\nWhat 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 presenta\n\n## Representations\n\n- Human: /a/protocol-framework-utility\n- JSON: /api/articles/protocol-framework-utility\n- Relationships: /api/articles/protocol-framework-utility/topology\n- History: /api/articles/protocol-framework-utility/revisions\n"},"json":{"route":"/api/articles/protocol-framework-utility","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/protocol-framework-utility/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"PROTOCOL_WRITE","type":"fn","method":null,"category":"system","enabled":true,"contract":"# WHAT: Create, revise, or enrich an article via /api/protocol/write, /api/protocol/revise, or /api/protocol/populate.\n# WHEN_TO_USE: the user asks for an article, wants it revised, or wants more sources/widgets added.\n# ARGS: $1 = JSON object or plain topic string. JSON keys: mode (\"write\"|\"revise\"|\"populate\"), slug, topic, ask, feedback, web_search (bool), max_tokens (number), max_rounds (number), loops (number). Plain topic defaults to mode=write.\n# EX: [PROTOCOL_WRITE]BPC-157 mechanisms and evidence[/PROTOCOL_WRITE]\n# EX: [PROTOCOL_WRITE]{\"mode\":\"write\",\"topic\":\"BPC-157 vs NSAIDs\"}[/PROTOCOL_WRITE]\n# EX: [PROTOCOL_WRITE]{\"mode\":\"revise\",\"slug\":\"bpc-157\",\"feedback\":\"add human trials and a dosing widget\"}[/PROTOCOL_WRITE]\n# EX: [PROTOCOL_WRITE]{\"mode\":\"populate\",\"slug\":\"bpc-157\",\"ask\":\"find more human studies and create widgets\",\"max_rounds\":3}[/PROTOCOL_WRITE]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/PROTOCOL_WRITE","json":"/api/directory/PROTOCOL_WRITE","skill":"/api/directory/PROTOCOL_WRITE?format=skill","oip_contract":"/api/dispatch?key=PROTOCOL_WRITE"}},{"key":"EDITORIAL_BOARD_RUN","type":"fn","method":null,"category":"protocol","enabled":true,"contract":"# WHAT: Run one receiving editorial-board task. It reads a MODEL_CHAT_INTAKE ledger event, extracts owner complaints and content-rule defects as JSON, ledgers EDITORIAL_BOARD_DECISION, and queues OIP purification.\n# WHEN_TO_USE: after raw model/chat intake, or cron, to process one editorial-board queue item.\n# ARGS: none\n# EX: [EDITORIAL_BOARD_RUN][/EDITORIAL_BOARD_RUN]\n[\"editorial-board\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/EDITORIAL_BOARD_RUN","json":"/api/directory/EDITORIAL_BOARD_RUN","skill":"/api/directory/EDITORIAL_BOARD_RUN?format=skill","oip_contract":"/api/dispatch?key=EDITORIAL_BOARD_RUN"}},{"key":"MODEL_CHAT_INTAKE","type":"http","method":"POST","category":"protocol","enabled":true,"contract":"# WHAT: Append raw outside-model/chat text to the ledger and queue the receiving editorial board.\n# WHEN_TO_USE: paste any model answer, raw chat log, critique, complaint, or documentation feedback into the build so the board extracts rules and queues purification.\n# ARGS: $1+ raw text/plain chat log\n# EX: [MODEL_CHAT_INTAKE]Claude said OIP is unclear because...[/MODEL_CHAT_INTAKE]\n$1+","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/MODEL_CHAT_INTAKE","json":"/api/directory/MODEL_CHAT_INTAKE","skill":"/api/directory/MODEL_CHAT_INTAKE?format=skill","oip_contract":"/api/dispatch?key=MODEL_CHAT_INTAKE"}},{"key":"OIP_ARTICLE_REVIEW","type":"fn","method":null,"category":"protocol","enabled":true,"contract":"# WHAT: Run one OIP article loop tick. Claims the next tasks.source=oip-review row and routes it: oip-review scores machine JSON clarity + English clarity with a fresh model; oip-write has a model write a missing OIP article; oip-revise has a model rewrite a failing article as a new append-only version. Every step lands in the ledger.\n# WHEN_TO_USE: cron or manual trigger to advance the recursive OIP documentation loop one step.\n# ARGS: none\n# EX: [OIP_ARTICLE_REVIEW][/OIP_ARTICLE_REVIEW]\n[\"oip-review\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_ARTICLE_REVIEW","json":"/api/directory/OIP_ARTICLE_REVIEW","skill":"/api/directory/OIP_ARTICLE_REVIEW?format=skill","oip_contract":"/api/dispatch?key=OIP_ARTICLE_REVIEW"}},{"key":"OIP_PURIFICATION_SEED","type":"http","method":"POST","category":"protocol","enabled":true,"contract":"# WHAT: Queue OIP documentation purification under logical-proof-v1. Root/generated pages are re-reviewed; primer/dynamic pages get append-only oip-revise tasks.\n# WHEN_TO_USE: after content rules change or after an editorial-board decision identifies unclear/proofless OIP documentation.\n# ARGS: optional raw JSON {\"slugs\":[\"oip\",\"oip-operating-model\"],\"brief\":\"...\"}\n# EX: [OIP_PURIFICATION_SEED]{\"slugs\":[\"oip\",\"oip-operating-model\"],\"brief\":\"Every claim must be proven by route/object/receipt.\"}[/OIP_PURIFICATION_SEED]\n$1+","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/OIP_PURIFICATION_SEED","json":"/api/directory/OIP_PURIFICATION_SEED","skill":"/api/directory/OIP_PURIFICATION_SEED?format=skill","oip_contract":"/api/dispatch?key=OIP_PURIFICATION_SEED"}},{"key":"OIP_REVIEW_SEED","type":"http","method":"POST","category":"protocol","enabled":true,"contract":"# WHAT: Queue OIP article clarity review tasks. Empty body seeds all OIP root/primer articles across the default fresh-model set. Raw JSON body may pass {\"slugs\":[\"oip\"],\"models\":[\"grok/grok-4.3\"]}.\n# WHEN_TO_USE: start or refill the recursive OIP article review queue.\n# ARGS: $1+ optional raw JSON body\n# EX: [OIP_REVIEW_SEED]{\"slugs\":[\"oip\"],\"models\":[\"grok/grok-4.3\"]}[/OIP_REVIEW_SEED]\n$1+","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/OIP_REVIEW_SEED","json":"/api/directory/OIP_REVIEW_SEED","skill":"/api/directory/OIP_REVIEW_SEED?format=skill","oip_contract":"/api/dispatch?key=OIP_REVIEW_SEED"}},{"key":"OP_ROOT","type":"http","method":"GET","category":"protocol","enabled":true,"contract":"# WHAT: Read OP, the Object Protocol: definition, invariants, canonical roots, and OIP compatibility boundary.\n# ARGS: None. Add ?format=markdown for a model-readable document.\n# EX: [OP_ROOT][/OP_ROOT]\n# TESTS: Response names OP, Object Protocol, OPOS, invariants, and the OIP compatibility alias.","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OP_ROOT","json":"/api/directory/OP_ROOT","skill":"/api/directory/OP_ROOT?format=skill","oip_contract":"/api/dispatch?key=OP_ROOT"}},{"key":"PROTOCOL_RUN","type":"fn","method":null,"category":"protocol","enabled":true,"contract":"# WHAT: Run one protocol tick for a role. $1=role (writer|reviewer|source_hunt|oip-review|writer-queue|...). Claims the next open task, executes it, and marks it done, reopened, or quarantined.\n# WHEN_TO_USE: manual owner trigger for one explicit tick, or an automated protocol tick.\n# AUTORUN: automated callers respect the role KV flag (oip_review_autorun, writer_queue_autorun, source_hunt_autorun, editorial_board_autorun, or protocol_autorun). If the flag is off, the tick returns skipped and touches no task.\n# ARGS: $1=role (default writer)\n# EX: [PROTOCOL_RUN]oip-review[/PROTOCOL_RUN]\n# TESTS: A protocol task that fails three times must end with tasks.status='quarantined', tasks.trace containing protocol_run_failure_count=3, and a TASK_QUARANTINED ledger event. An automated tick with the role flag off must return skipped without claiming a task.\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/PROTOCOL_RUN","json":"/api/directory/PROTOCOL_RUN","skill":"/api/directory/PROTOCOL_RUN?format=skill","oip_contract":"/api/dispatch?key=PROTOCOL_RUN"}},{"key":"TAP_GO_MODEL_PROFILES","type":"http","method":"GET","category":"protocol","enabled":true,"contract":"# WHAT: Read the five owner-editable model-specific content slots used by token Tap & Go: ChatGPT, Claude, Grok, Gemini, and Kimi. The model selector belongs to the token DROP, not the build audit.\n# ARGS: None for read. Owner edits one profile with PUT /api/tap-go-profiles {model,content}.\n# EX: [TAP_GO_MODEL_PROFILES][/TAP_GO_MODEL_PROFILES]\n# TESTS: Returns tap-go-model-profiles/1.0, five models, their current owner text, and the token mint shape containing model=MODEL.","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/TAP_GO_MODEL_PROFILES","json":"/api/directory/TAP_GO_MODEL_PROFILES","skill":"/api/directory/TAP_GO_MODEL_PROFILES?format=skill","oip_contract":"/api/dispatch?key=TAP_GO_MODEL_PROFILES"}},{"key":"DISCLOSURE_GET","type":"http","method":"GET","category":"protocol","enabled":true,"contract":"# WHAT: Read a versioned public defensive-publication artifact from the disclosure archive. Text is scanned for bearer/credential material at read time; binary artifacts are admitted only after local render/hash/credential review. Keys are immutable and public.\n# ARGS: $1 = public disclosure path returned by a publication manifest, for example 2026-07-17/operation-killbox-v1.1/specification.md.\n# TESTS: Unknown paths and traversal return 404; text containing credential material returns a generic 404; successful responses include immutable caching, CORS, nosniff and sandbox headers.\n[\"$1\"]","input_schema":"{\"type\":\"string\",\"pattern\":\"^[a-zA-Z0-9][a-zA-Z0-9._/-]{0,500}$\"}","examples":"[\"2026-07-17/operation-killbox-v1.1/specification.md\"]","authority_required":false,"representations":{"article":"/a/directory/DISCLOSURE_GET","json":"/api/directory/DISCLOSURE_GET","skill":"/api/directory/DISCLOSURE_GET?format=skill","oip_contract":"/api/dispatch?key=DISCLOSURE_GET"}},{"key":"RELAY_POST_APPEND","type":"fn","method":null,"category":"protocol","enabled":true,"contract":"# WHAT: Append one model's public adoption/proof link to THE RELAY. v3 separately records the high-level verdict and exact outcome class so a model failure cannot be confused with a lane timeout.\n# WHEN_TO_USE: After a model audits the prior relay and performs real work. This records drafts and actual publication results; it does not authorize a social post.\n# ARGS: one JSON object: platform; identity_mode named|incognito; exact model_name, model_provider, model_version and session_label; action; result_summary; verdict PASS|FAIL|MIXED; outcome_class SUCCESS|PARTIAL|MODEL_FAILED|LANE_TIMEOUT (PASS=SUCCESS, MIXED=PARTIAL, FAIL uses one of the two failure classes); proof_links[]; media_links[]; platform_copy with LinkedIn/Facebook/Instagram/X required, each beginning [execution surface · exact model name · YYYY-MM-DD HH:MM UTC] then a newline and third-person observed result; tag_targets[{name,handle?,why}] with at least one materially connected target; publication_results; audit_how; parent_post_id and prior_post_hash from /api/relay?social=1.\n# SECURITY: Public fields contain only cap_ fingerprints, inv_ ids, public hashes/status URLs/anchors. Never include share tokens or backend credentials. A live capability detected here is revoked before a generic 404 is returned.\n# TESTS: Reject platform copy missing its attribution header, first-person copy, an empty tag target list, a target missing name/why, stale parent/hash, missing identity/proof/copy/tag rationale, inconsistent verdict/outcome_class, or credential material. Return v3 post, outcome class, receipt and chain links.\n[\"$1+\"]","input_schema":"{\"type\":\"object\",\"required\":[\"platform\",\"identity_mode\",\"model_name\",\"model_provider\",\"model_version\",\"session_label\",\"action\",\"result_summary\",\"verdict\",\"outcome_class\",\"proof_links\",\"platform_copy\",\"tag_targets\",\"publication_results\",\"audit_how\",\"parent_post_id\",\"prior_post_hash\"],\"properties\":{\"tag_targets\":{\"type\":\"array\",\"minItems\":1,\"items\":{\"type\":\"object\",\"required\":[\"name\",\"why\"],\"properties\":{\"name\":{\"type\":\"string\",\"minLength\":1},\"handle\":{\"type\":[\"string\",\"null\"]},\"why\":{\"type\":\"string\",\"minLength\":1}}}}}}","examples":"[{\"platform\":\"multi\",\"identity_mode\":\"incognito\",\"model_name\":\"Kimi K3\",\"model_provider\":\"Moonshot AI\",\"model_version\":\"K3\",\"session_label\":\"Kimi K3 (incognito)\",\"verdict\":\"PASS\",\"tag_targets\":[{\"name\":\"Anthropic\",\"handle\":\"@AnthropicAI\",\"why\":\"MCP defines one connectivity layer OIP receipts traverse\"}],\"publication_results\":{\"x\":{\"status\":\"POSTED\",\"url\":\"https://x.com/i/web/status/...\",\"receipt\":\"https://miscsubjects.com/receipt/inv_...\"}},\"parent_post_id\":\"rsp_...\",\"prior_post_hash\":\"...\"}]","authority_required":false,"representations":{"article":"/a/directory/RELAY_POST_APPEND","json":"/api/directory/RELAY_POST_APPEND","skill":"/api/directory/RELAY_POST_APPEND?format=skill","oip_contract":"/api/dispatch?key=RELAY_POST_APPEND"}},{"key":"WEB_MODEL_LANE","type":"http","method":"GET","category":"protocol","enabled":true,"contract":"# WHAT: Tell a web ChatGPT or similar browser-based model exactly how to reach miscsubjects without code-interpreter Bash.\n# ARGS: none.\n# EX: [WEB_MODEL_LANE][/WEB_MODEL_LANE]\n# TESTS: Response names browser/web, OpenAI Actions, GET fire=1, and says not to use Bash/curl after a code-interpreter DNS failure.","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/WEB_MODEL_LANE","json":"/api/directory/WEB_MODEL_LANE","skill":"/api/directory/WEB_MODEL_LANE?format=skill","oip_contract":"/api/dispatch?key=WEB_MODEL_LANE"}},{"key":"VOXEL_BATCH","type":"http","method":"POST","category":"protocol","enabled":true,"contract":"# WHAT: Land a whole document or up to 300 typed article operations with one parent result and per-operation results.\n# ARGS: JSON {document:{slug,title,markdown}|operations:[...],actor,key?}. Web ChatGPT uses the OpenAI Action from /api/openai/actions.json; a small browser-only payload may use GET /api/protocol/voxel-batch?fire=1&payload=<URL-encoded JSON>. Never use code-interpreter Bash for miscsubjects.com.\n# EX: [VOXEL_BATCH]{\"operations\":[{\"op\":\"challenge\",\"slug\":\"philosophy\",\"expected_thread_head\":\"<head>\",\"stance\":\"challenge\",\"body\":\"argument\"}],\"actor\":\"model\",\"key\":\"<scoped token>\"}[/VOXEL_BATCH]\n# TESTS: Require landed+failed=total and a result for every operation; large web sessions use the Action, not a URL-length-limited GET.\n# EXISTING SLUG LAW: Document mode appends new DIVs when document.slug already exists; it does not replace prior active DIVs. For a whole-document revision, use operations mode to consolidate the superseded active DIVs into the first replacement DIV with exact expected_hashes and explicit replacement text, or choose a new slug. Verify the final active article body hash.\n$1+","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/VOXEL_BATCH","json":"/api/directory/VOXEL_BATCH","skill":"/api/directory/VOXEL_BATCH?format=skill","oip_contract":"/api/dispatch?key=VOXEL_BATCH"}},{"key":"KERNEL","type":"fn","method":null,"category":"system","enabled":true,"contract":"# Universal kernel ingress. Natural-language request resolved through the directory.\\n[\\\"$1+\\\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/KERNEL","json":"/api/directory/KERNEL","skill":"/api/directory/KERNEL?format=skill","oip_contract":"/api/dispatch?key=KERNEL"}},{"key":"KNOWLEDGE","type":"fn","method":null,"category":"system","enabled":true,"contract":"# KNOWLEDGE — fetch a knowledge card for models\n# ARGS: CUSTOMER_FUNNEL | AD_ACCOUNTS | MARKETING_STATE | LEO_RESEARCH | IMAGE_REFERENCE | REACTIONS | BATCH | ARTICLE_LIST\n# EX: [KNOWLEDGE]AD_ACCOUNTS[/KNOWLEDGE]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/KNOWLEDGE","json":"/api/directory/KNOWLEDGE","skill":"/api/directory/KNOWLEDGE?format=skill","oip_contract":"/api/dispatch?key=KNOWLEDGE"}}]},"ontology":{"conformance_group":"article","inferred_from":["system","protocol","applications","protocol","framework","utility"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/protocol-framework-utility/invocations?status=success","failure_events":"/api/articles/protocol-framework-utility/invocations?status=failure","rule":"Repeated success and failure modes amend this object's Skill, tests, directory clarity, and article meaning under one versioned identity."},"article":{"slug":"protocol-framework-utility","title":"What This Framework Enables: Use Cases Beyond Peptide Catalogues","body":"## What this article is\n\nThis document explains what the miscsubjects.com protocol framework can do beyond peptide catalogues. It describes the build itself.\n\nThe framework separates transport (REST protocol), evidence atoms (claims), and presentation (widgets). Each layer remains inspectable independently.\n\n## Who claims what\n\nTasks REST and dispatch directory let cron jobs and human operators invoke protocol steps as named functions.\n\nLibrary-snapshot and poll endpoints support periodic external source refresh against existing claims.\n\n## What is known\n\nPOST /api/protocol/ask returns gaps[] and ingest_hint. The ledger tells the user what evidence would materially improve the answer.\n\nCombinatorial matrix generalizes to any inventory × target grid where regen/degen scores can be defined transparently.\n\nMulti-model collaborate preserves each model's original contribution. This supports audit, dispute resolution, and bias detection.\n\nGraph canvas GET /api/graph enables cross-article reasoning without copying full bodies into prompt context.\n\niMessage/WhatsApp ingest paths let lay users add anecdotal tier evidence that enters the same hash-chained ledger.\n\nObsidian vault export supports offline research workflows while keeping slug parity with the live corpus.\n\n## What is unknown\n\nDomain packs beyond peptides require new canonical catalogs. The engine (matrix, grow, claims) is domain-agnostic.\n\nFederation across multiple miscsubjects instances is not implemented. Single D1 spine today.\n\nCommercial RUO peptide commerce integration is out of scope. The framework is evidence organization only.\n\n## Limitations\n\nAccessible register articles still depend on claim tier discipline. Prose alone does not elevate evidence.\n\nUsefulness scales with source forest density. Empty articles benefit from populate before ask.\n\n## Disclaimer\n\nFramework users remain responsible for their own research and medical decisions.","hero":null,"images":[],"style":{},"tags":["system","protocol","applications"],"category":null,"model":"grok/build (protocol-meta-articles)","ledger":{"href":"/api/articles/protocol-framework-utility/ledger","live":true},"embeds":["protocol","protocol-api-structure","protocol-widgets","protocol-claims","protocol-logic"],"widgets":[],"home":true,"claims":[{"id":"c_use_1","text":"The framework separates transport (REST protocol), evidence atoms (claims), and presentation (widgets) — each layer inspectable independently.","section":"what it is","slot":"what_it_is","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_2","text":"POST /api/protocol/ask returns gaps[] and ingest_hint — the ledger tells the user what evidence would materially improve the answer.","section":"what is known","slot":"what_is_known","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_3","text":"Combinatorial matrix generalizes to any inventory × target grid where regen/degen scores can be defined transparently.","section":"what is known","slot":"what_is_known","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_4","text":"Multi-model collaborate preserves each model's original contribution — useful for audit, dispute resolution, and bias detection.","section":"what is known","slot":"what_is_known","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_5","text":"Graph canvas GET /api/graph enables cross-article reasoning without copying full bodies into prompt context.","section":"what is known","slot":"what_is_known","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_6","text":"iMessage/WhatsApp ingest paths let lay users add anecdotal tier evidence that enters the same hash-chained ledger.","section":"what is known","slot":"what_is_known","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_7","text":"Obsidian vault export supports offline research workflows while keeping slug parity with the live corpus.","section":"what is known","slot":"what_is_known","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_8","text":"Tasks REST + dispatch directory let cron and human operators invoke protocol steps as named functions.","section":"who claims what","slot":"who_claims_what","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_9","text":"Library-snapshot and poll endpoints support periodic external source refresh against existing claims.","section":"who claims what","slot":"who_claims_what","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_10","text":"Domain packs beyond peptides require new canonical catalogs — the engine (matrix, grow, claims) is domain-agnostic.","section":"what is unknown","slot":"what_is_unknown","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_11","text":"Federation across multiple miscsubjects instances is not implemented — single D1 spine today.","section":"what is unknown","slot":"what_is_unknown","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_12","text":"Commercial RUO peptide commerce integration is out of scope — framework is evidence organization only.","section":"what is unknown","slot":"what_is_unknown","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_13","text":"Usefulness scales with source forest density — empty articles benefit from populate before ask.","section":"mechanism","slot":"mechanism","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_14","text":"Accessible register articles still depend on claim tier discipline — prose alone does not elevate evidence.","section":"limitations","slot":"limitations","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35},{"id":"c_use_15","text":"Framework users remain responsible for their own research and medical decisions.","section":"disclaimer","slot":"disclaimer","tier":"runtime","source_status":"unsourced","why_material":"Architecture axiom — verifiable via live GET endpoints cited in text.","posted_by":{"actor":"grok/build","channel":"api","ts":"2026-06-29T16:53:48.320Z"},"who_claims":"miscsubjects protocol (system tier)","weight":0.35}],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"combinatorial_accessible","status":"published","revisions":2,"contributions":[{"seq":0,"id":"k1","ts":"2026-06-29T16:54:34.232Z","model":"grok/grok-4.3","role":"editor","action":"synthesize_body","payload":{"chars":2930,"claims_used":0,"legibility":{"pass":true,"reasons":[]}},"rationale":"Reader body rewritten from ranked ledger topology — plain English","tokens_in":1142,"tokens_out":641,"cost":0.00303,"prev_hash":"genesis","hash":"337584ce173f707ca162d601bff2aea009e97353c0ca1e10534f9080d2853953"},{"seq":1,"id":"k2","ts":"2026-06-29T17:01:09.792Z","model":"grok/grok-4.3","role":"editor","action":"synthesize_body","payload":{"chars":1932,"claims_used":15,"legibility":{"pass":true,"reasons":[]}},"rationale":"Reader body rewritten from ranked ledger topology — plain English","tokens_in":1456,"tokens_out":337,"cost":0.0026625,"prev_hash":"337584ce173f707ca162d601bff2aea009e97353c0ca1e10534f9080d2853953","hash":"74d5ae7c6729859303648abd13169b9a4becc140daf3987c075844de0aec776a"}],"provenance":[{"ts":"2026-06-29T16:53:49.497Z","model":"grok/build","action":"write","prompt":"post_protocol_meta_articles.mjs","input":"protocol-framework-utility","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"662b94328aa0c38d637a41ec3d51995f809beb51136168c8f19e932c65e0dc40"},{"ts":"2026-06-29T16:54:34.232Z","model":"grok/grok-4.3","action":"synthesize_body","prompt":"","input":"protocol-framework-utility","response":"## Regeneration vs degeneration — where this fits\nThe body is always doing two things at once: breaking down and building back. A condition persists when breakdown outruns repair. Most drugs used for symptoms suppress a signal without fixing the tissue that caused the signal. This framework places one compound in the repair-pathway ledger. It asks whether the compound is studied for new blood vessels, repair-cell migration, nerve regrowth, gut lining, or neural connections.\n\n## What it is\nThe framework is a map. It takes one compound and runs it through a fixed set of questions. The map starts with the regeneration-versus-degeneration frame. It then lists what the compound is, how it is proposed to work, why the logic holds, why people try it, how many people try it, the evidence count, what scientists state, what users report on Reddit and X, what remains unknown, and the safety limits recorded so far.\n\n## How it works\nThe framework works by holding every claim to the same sequence. First, state the degeneration problem. Second, state the proposed repair action. Third, list the steps the compound is said to follow. Fourth, mark each step as human data, animal data, or anecdote. Fifth, record what each data type proves and what it leaves open.\n\n## Why it would work (logic chain)\nStep 1: Tissue breaks down faster than it rebuilds.  \nStep 2: A repair pathway exists that can move cells, grow vessels, or restore lining.  \nStep 3: The compound is studied for one or more of those steps.  \nStep 4: If the pathway activates and the breakdown rate drops, net repair rises.  \nStep 5: The logic chain stops at the data limit; it does not extend past what the source type can show.\n\n## Why people take it\nPeople take it when they want a repair option instead of signal suppression. They look for reported changes in tissue recovery, reduced breakdown signals, or restored function. The framework records the stated reason without adding claims.\n\n## How many people take it\nThe ledger sho","tokens_in":1142,"tokens_out":641,"cost":0,"prev":"662b94328aa0c38d637a41ec3d51995f809beb51136168c8f19e932c65e0dc40","hash":"1a4adeb0a403e1a5a58266e6512052deeea941eb4d8029db57a6338e4e14ffe3"},{"ts":"2026-06-29T17:01:09.792Z","model":"grok/grok-4.3","action":"synthesize_body","prompt":"","input":"protocol-framework-utility","response":"## What this article is\n\nThis document explains what the miscsubjects.com protocol framework can do beyond peptide catalogues. It describes the build itself.\n\nThe framework separates transport (REST protocol), evidence atoms (claims), and presentation (widgets). Each layer remains inspectable independently.\n\n## Who claims what\n\nTasks REST and dispatch directory let cron jobs and human operators invoke protocol steps as named functions.\n\nLibrary-snapshot and poll endpoints support periodic external source refresh against existing claims.\n\n## What is known\n\nPOST /api/protocol/ask returns gaps[] and ingest_hint. The ledger tells the user what evidence would materially improve the answer.\n\nCombinatorial matrix generalizes to any inventory × target grid where regen/degen scores can be defined transparently.\n\nMulti-model collaborate preserves each model's original contribution. This supports audit, dispute resolution, and bias detection.\n\nGraph canvas GET /api/graph enables cross-article reasoning without copying full bodies into prompt context.\n\niMessage/WhatsApp ingest paths let lay users add anecdotal tier evidence that enters the same hash-chained ledger.\n\nObsidian vault export supports offline research workflows while keeping slug parity with the live corpus.\n\n## What is unknown\n\nDomain packs beyond peptides require new canonical catalogs. The engine (matrix, grow, claims) is domain-agnostic.\n\nFederation across multiple miscsubjects instances is not implemented. Single D1 spine today.\n\nCommercial RUO peptide commerce integration is out of scope. The framework is evidence organization only.\n\n## Limitations\n\nAccessible register articles still depend on claim tier discipline. Prose alone does not elevate evidence.\n\nUsefulness scales with source forest density. Empty articles benefit from populate before ask.\n\n## Disclaimer\n\nFramework users remain responsible for their own research and medical decisions.","tokens_in":1456,"tokens_out":337,"cost":0,"prev":"1a4adeb0a403e1a5a58266e6512052deeea941eb4d8029db57a6338e4e14ffe3","hash":"5761ff713095cb0a18fe7b15651fdfbc6002a07a7175d6c5a111615cfb01b798"},{"ts":"2026-07-17T02:41:02.243Z","model":"owner","action":"voxel_divide","prompt":"","input":"protocol-framework-utility","response":"22 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"5761ff713095cb0a18fe7b15651fdfbc6002a07a7175d6c5a111615cfb01b798","hash":"a7aeca38b49cf00610954a52497c888570f58ba53886d509c9371b67804722ca"}],"energy":{"passes":4,"tokens_in":2598,"tokens_out":978,"tokens_total":3576,"cost_usd":0,"models":{"grok/build":1,"grok/grok-4.3":2,"owner":1},"head":"a7aeca38b49cf00610954a52497c888570f58ba53886d509c9371b67804722ca"},"posted_at":"2026-06-29T16:53:49.497Z","created_at":"2026-06-29T16:53:49.497Z","updated_at":"2026-07-17T02:41:02.243Z","machine":{"shape":"article.machine/v1","slug":"protocol-framework-utility","kind":"article","read":{"human":"https://miscsubjects.com/a/protocol-framework-utility","json":"https://miscsubjects.com/api/articles/protocol-framework-utility","bundle":"https://miscsubjects.com/api/articles/protocol-framework-utility/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":15,"sources":0,"contributions":2,"revisions":2,"objections_url":"https://miscsubjects.com/api/articles/protocol-framework-utility/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=protocol-framework-utility","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"protocol-framework-utility\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"protocol-framework-utility\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/protocol-framework-utility/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"protocol-framework-utility\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/protocol-framework-utility | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/protocol-framework-utility","json":"/api/articles/protocol-framework-utility","markdown":"/api/articles/protocol-framework-utility/bundle?format=markdown","skill":"/api/articles/protocol-framework-utility/skill","topology":"/api/articles/protocol-framework-utility/topology","versions":"/api/articles/protocol-framework-utility/revisions","invocations":"/api/articles/protocol-framework-utility/invocations"},"editorial_review":null,"editorial_audit":{"slug":"protocol-framework-utility","ok":false,"issues":[{"code":"headline_context","message":"headline depends on surrounding context instead of naming its subject: \"What This Framework Enables: Use Cases Beyond Peptide Catalogues\"","replacement":"Write a shorter literal headline naming the article subject and its central event or claim."},{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"4f2fec00c9f0687f36bdb2ce42a66c18e795d0e0596dd75ea48b907a2a8fcc4e"}}}