{"_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."},"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_ask_prompt","feature":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","contains":"suggested ask prompts with self-explaining paste_block","slug":"bpc-157","urls":{"read":"https://miscsubjects.com/api/articles/bpc-157/prompts","write":"https://miscsubjects.com/api/protocol/ask"},"how_to_use":"Answer only from topology; creates question_node with gaps and ingest_hint.","write":"https://miscsubjects.com/api/protocol/ask","imessage":"bpc-157|question","router_tag":"[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]","proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/bpc-157/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","urls":{"read":"https://miscsubjects.com/api/articles/bpc-157/topology"}},{"id":"ingest","name":"Ingest protocol","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node.","urls":{"write":"https://miscsubjects.com/api/protocol/ingest"}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/bpc-157/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","why":"Every feature is auditable collective intelligence","how":"Answer only from topology; creates question_node with gaps and ingest_hint.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/bpc-157/prompts","write":"https://miscsubjects.com/api/protocol/ask"},"imessage":"bpc-157|question","router":"[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]","related":[{"id":"topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER."},{"id":"ingest","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."}],"not_medical_advice":true},"slug":"bpc-157","title":"BPC-157: Body Protection Compound","prompts":[{"id":"claim-c120","claim_id":"c120","tier":"mechanistic","weight":0.3,"prompt":"What does the ledger say about this (mechanistic tier): \"The chain of hashes on the sources proves the sources have not been altered since they were logged. It proves nothing about whether they are…\"?","channel_hint":"ask bpc-157 claim c120","imessage_body":"On BPC-157: Body Protection Compound — what's the evidence for claim c120? (mechanistic)","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nOn BPC-157: Body Protection Compound — what's the evidence for claim c120? (mechanistic)\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"claim-c1","claim_id":"c1","tier":"human","weight":0.8,"prompt":"What does the ledger say about this (human tier): \"BPC-157 is a made-in-a-lab chain of 15 amino acids, copied from a stretch of a protein found in stomach juice.\"?","channel_hint":"ask bpc-157 claim c1","imessage_body":"On BPC-157: Body Protection Compound — what's the evidence for claim c1? (human)","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nOn BPC-157: Body Protection Compound — what's the evidence for claim c1? (human)\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"claim-c3","claim_id":"c3","tier":"human","weight":0.8,"prompt":"What does the ledger say about this (human tier): \"A 2025 pilot study dripped up to 20 mg of BPC-157 into the veins of two healthy adults. Nothing went wrong with their vital signs, their blo…\"?","channel_hint":"ask bpc-157 claim c3","imessage_body":"On BPC-157: Body Protection Compound — what's the evidence for claim c3? (human)","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nOn BPC-157: Body Protection Compound — what's the evidence for claim c3? (human)\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"claim-c11","claim_id":"c11","tier":"human","weight":0.8,"prompt":"What does the ledger say about this (human tier): \"Ten of the sources catalogued on this page are vendors and clinics selling BPC-157. That is marketing material, and it is listed here as mar…\"?","channel_hint":"ask bpc-157 claim c11","imessage_body":"On BPC-157: Body Protection Compound — what's the evidence for claim c11? (human)","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nOn BPC-157: Body Protection Compound — what's the evidence for claim c11? (human)\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"claim-c15","claim_id":"c15","tier":"human","weight":0.8,"prompt":"What does the ledger say about this (human tier): \"A 2024 review pulled together the many different effects reported for BPC-157 across the animal literature.\"?","channel_hint":"ask bpc-157 claim c15","imessage_body":"On BPC-157: Body Protection Compound — what's the evidence for claim c15? (human)","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nOn BPC-157: Body Protection Compound — what's the evidence for claim c15? (human)\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"claim-c19","claim_id":"c19","tier":"human","weight":0.8,"prompt":"What does the ledger say about this (human tier): \"A published commentary responds to a major 2024 review of BPC-157 protecting cells and organs, mostly in gut and multi-organ-failure models …\"?","channel_hint":"ask bpc-157 claim c19","imessage_body":"On BPC-157: Body Protection Compound — what's the evidence for claim c19? (human)","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nOn BPC-157: Body Protection Compound — what's the evidence for claim c19? (human)\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"anecdote-s10","source_id":"s10","type":"youtube","prompt":"Summarize this youtube report and how it should weigh: \"YouTube video discussing BPC-157 efficacy with user anecdotes on tendon healing.\"","channel_hint":"ask bpc-157 source s10","imessage_body":"On BPC-157: Body Protection Compound — what did people report on youtube (source s10)?","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nOn BPC-157: Body Protection Compound — what did people report on youtube (source s10)?\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"anecdote-s16","source_id":"s16","type":"x","prompt":"Summarize this x report and how it should weigh: \"Negative anecdote — selftest graph populate\"","channel_hint":"ask bpc-157 source s16","imessage_body":"On BPC-157: Body Protection Compound — what did people report on x (source s16)?","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nOn BPC-157: Body Protection Compound — what did people report on x (source s16)?\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"anecdote-s23","source_id":"s23","type":"youtube","prompt":"Summarize this youtube report and how it should weigh: \"YouTube video reviewing scientific evidence on BPC-157, emphasizing lack of robust human RCTs.\"","channel_hint":"ask bpc-157 source s23","imessage_body":"On BPC-157: Body Protection Compound — what did people report on youtube (source s23)?","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nOn BPC-157: Body Protection Compound — what did people report on youtube (source s23)?\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"anecdote-s43","source_id":"s43","type":"youtube","prompt":"Summarize this youtube report and how it should weigh: \"2026 video explaining BPC-157 mechanisms for tissue repair.\"","channel_hint":"ask bpc-157 source s43","imessage_body":"On BPC-157: Body Protection Compound — what did people report on youtube (source s43)?","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nOn BPC-157: Body Protection Compound — what did people report on youtube (source s43)?\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"related-the-disc-stack","related_slug":"the-disc-stack","prompt":"How does The Disc Recovery Stack relate to BPC-157: Body Protection Compound for my condition?","channel_hint":"ask bpc-157 related the-disc-stack","imessage_body":"How does The Disc Recovery Stack connect to BPC-157: Body Protection Compound in your catalogue?","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nHow does The Disc Recovery Stack connect to BPC-157: Body Protection Compound in your catalogue?\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"related-tb-500","related_slug":"tb-500","prompt":"How does TB-500: a seven-amino-acid fragment sold under the name of the protein thymosin beta-4 relate to BPC-157: Body Protection Compound for my condition?","channel_hint":"ask bpc-157 related tb-500","imessage_body":"How does TB-500: a seven-amino-acid fragment sold under the name of the protein thymosin beta-4 connect to BPC-157: Body Protection Compound in your catalogue?","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nHow does TB-500: a seven-amino-acid fragment sold under the name of the protein thymosin beta-4 connect to BPC-157: Body Protection Compound in your catalogue?\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"related-bpc-157-vs-nsaids","related_slug":"bpc-157-vs-nsaids","prompt":"How does BPC-157 vs NSAIDs: Repair or Suppress? relate to BPC-157: Body Protection Compound for my condition?","channel_hint":"ask bpc-157 related bpc-157-vs-nsaids","imessage_body":"How does BPC-157 vs NSAIDs: Repair or Suppress? connect to BPC-157: Body Protection Compound in your catalogue?","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nHow does BPC-157 vs NSAIDs: Repair or Suppress? connect to BPC-157: Body Protection Compound in your catalogue?\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"catalogue-gaps","prompt":"For my medical situation, what can you answer from your catalogue about BPC-157: Body Protection Compound — and what would you need me to tell you first?","channel_hint":"ask bpc-157 condition gaps","imessage_body":"I have a medical condition — what can you tell me from your BPC-157: Body Protection Compound catalogue, and what don't you know?","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nI have a medical condition — what can you tell me from your BPC-157: Body Protection Compound catalogue, and what don't you know?\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"},{"id":"good-vs-bad","prompt":"What good and bad outcomes are documented for BPC-157: Body Protection Compound (studies vs anecdotes)?","channel_hint":"ask bpc-157 good bad experiences","imessage_body":"What good and bad things do people report about BPC-157: Body Protection Compound?","paste_block":"## §SELF — miscsubjects portable reference\n\n**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.\n\n**This widget:** `article_ask_prompt` — **Ask protocol**\nAnswer only from topology; creates question_node with gaps and ingest_hint.\n- **article slug:** `bpc-157`\n- **contains:** suggested ask prompt for miscsubjects build\n- **how to use:** Text +14245134626 or WhatsApp this message. Creates a question_node. Reply with ingest to add evidence.\n- **read:** https://miscsubjects.com/api/articles/bpc-157/prompts\n- **write:** https://miscsubjects.com/api/protocol/ask\n- **iMessage:** `bpc-157|question`\n- **ROUTER tag:** `[ARTICLE_ASK]{slug}|question[/ARTICLE_ASK]`\n\n### Logical proof (verify each step)\n1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution\n2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/bpc-157/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow\n5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex\n6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/bpc-157/topology\n- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.\n- **question_graph** — Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output). · https://miscsubjects.com/api/articles/bpc-157/question-graph\n\n### Full index\n- JSON: https://miscsubjects.com/api/articles/system-map\n- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown\n\n### §STRUCTURE\nThis 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\n\n### §INTEGRITY\nEvery 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.\n\n### §GAUNTLET\nEvery 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.\n\n*Not medical advice. Tier-honest. Cite claim/source ids.*\n## Prompt to send\n\nWhat good and bad things do people report about BPC-157: Body Protection Compound?\n\n## After you get a question_node_id\ningest bpc-157|q:NODE_ID|paste from Grok/GPT/Gemini\n\n## Write back (quote evidence from another model)\n`ingest bpc-157|q:NODE_ID|quoted evidence`\n\n## Post one claim\n`claim bpc-157|tier|assertion — who claims it?`"}],"topology_url":"/api/articles/bpc-157/topology","ask_url":"/api/protocol/ask","system_map":"/api/articles/system-map"}