{"slug":"protocol","title":"miscsubjects article protocol (constitution)","body":"## §SELF — miscsubjects (paste without context)\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_constitution` — **Article constitution**\nBinding rules: required article slots, claim/source rules, ontology anti-sprawl.\n- **contains:** required slots, claim rules, source rules, ontology rules, post_protocol\n- **how to use:** Defines what belongs in every article. Pair with voxels + ontology endpoints.\n- **read:** https://miscsubjects.com/api/articles/constitution\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/{slug}/sources\n3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol\n4. Ontology flags sprawl and missteps across all articles. → https://miscsubjects.com/api/articles/ontology\n5. Full feature index lives at system-map. → https://miscsubjects.com/api/articles/system-map\n\n### Related features (explains other parts of the system)\n- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/{slug}/voxels\n- **ontology** — Recursive peptide tree, sprawl orphans, misstep candidates (duplicate scope / missing parent). · https://miscsubjects.com/api/articles/ontology\n- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/{slug}/voxels\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*Not medical advice. Tier-honest. Cite claim/source ids.*\n\n---\n\n# Article constitution (miscsubjects)\n\nArticles are voxel graphs of claims — not prose blobs. Every assertion is a claim atom with tier, weight, source_ids, and posted_by provenance.\n\n## Required slots\n- **what_it_is** (required) — What is this peptide/stack/condition?\n- **who_claims_what** (required) — Who claims what — study authors, platforms, n=?\n- **what_is_known** (required) — What is known with tier labels (human/preclinical/anecdotal)\n- **what_is_unknown** (required) — What is NOT known — explicit gaps\n- **mechanism** — Proposed mechanism (mechanistic tier only)\n- **limitations** (required) — Limits of evidence — no dose advice\n- **disclaimer** (required) — Not medical advice\n\n## Claim rules\n- One claim = one falsifiable assertion. No compound claims.\n- Every claim must declare tier: human|preclinical|anecdotal|mechanistic|speculative.\n- Sourced claims must cite source_ids from the hash-chained ledger.\n- Unsourced claims must set source_status: unsourced and why_material.\n- posted_by is mandatory on every new claim (model id, human, or channel).\n- No medical advice, no doses, no 'you should take'.\n\n## Source / voxel rules\n- Every source is a voxel edge: type, url, exact quote, summary, found_by, accessed_at.\n- Sources hash-chain — prev/hash on append.\n- Anecdotal sources must name platform (reddit|x|youtube|imessage|user_entry).\n\n## Ontology / anti-sprawl\n- Peptide articles (bpc-157, tb-500) are tree roots.\n- Condition articles (bpc-157-glp1-gut-damage) branch from peptides.\n- Stack articles (wolverine-stack-glp1) compose peptides — never duplicate peptide mechanism prose.\n- If an article has no parent embeds and is not a root peptide → sprawl candidate.\n- Misstep = duplicate scope with another slug; merge or reparent via embeds.\n\n## How to POST into the ledger\n```json\n{\n  \"claim\": \"POST /api/protocol/claim\",\n  \"source\": \"POST /api/protocol/sources\",\n  \"ingest\": \"POST /api/protocol/ingest\",\n  \"webhook\": \"POST /api/articles/<slug>/webhook {kind:claim|source}\",\n  \"imessage_claim\": \"claim {slug}|{tier}|your assertion — who claims it, source?\",\n  \"imessage_ingest\": \"ingest {slug}|evidence paste\"\n}\n```\n\n## Binding\n\nEvery writer, populate, ingest, and claim path is bound by this document. Read `GET /api/articles/system-map` for the full feature index.\n\n\n## Architecture verdict (canonized 2026-06-29)\n\nSeven problems, seven methods, eight weaknesses with resolution paths — all as tiered claim atoms on this article.\n\n| # | Problem | Method | Weakness | Resolution path |\n|---|---------|--------|----------|-----------------|\n| 1 | Hallucination | source_ids + hash chain | Truth unverified | challenge + human audit |\n| 2 | Evidence inflation | hardcoded tier weights | Source quality unfiltered | tier labels + source_hunt |\n| 3 | Knowledge rot | append-only retraction | — | (addressed) |\n| 4 | Model monoculture | posted_by + challenge | Malicious actors | cross-model adversary |\n| 5 | Knowledge sprawl | ontology missteps | Embed wiring incomplete | link_peptide_graph |\n| 6 | Curation bottleneck | populate-repair | — | (addressed) |\n| 7 | Model friction | _self + prompt tags | Centralized spine | federated mirrors |\n\n**Significance:** infrastructure for machine-collaborative epistemology — auditable, tier-honest, adversarial.\n\n**Live proof:** Kimi + Gemini collaborate passes on bpc-157, tb-500, wolverine-stack-glp1.\n\nRead claims: `GET /api/articles/protocol/health` · voxels: `GET /api/articles/protocol/voxels`\n","register":"technical","tags":[],"category":null,"style":{},"claims":[{"id":"c1","text":"Articles are voxel graphs of tiered claims with hash-chained sources.","section":"what_it_is","tier":"speculative","source_ids":["s1"],"source_status":"sourced","why_material":"Core architecture invariant"},{"id":"c2","text":"Every new claim must include posted_by provenance.","section":"limitations","tier":"speculative","source_ids":["s1"],"source_status":"sourced","why_material":"Provenance rule"},{"id":"c3","text":"Not medical advice — tier-honest evidence only.","section":"disclaimer","tier":"speculative","source_ids":["s1"],"source_status":"sourced","why_material":"Legal/safety"},{"id":"c4","text":"Problem 1 (hallucination): solved by tier weights + mandatory source_ids + hash-chained ledger — no source = unsourced + why_material; models cannot invent citations.","section":"what_it_is","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Core epistemic invariant"},{"id":"c5","text":"Problem 2 (evidence inflation): solved by hardcoded tier weights — human 0.8, preclinical 0.5, anecdotal 0.3 — weight is declared in schema, not inferred by prose.","section":"what_it_is","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Prevents weak→strong rhetorical smoothing"},{"id":"c6","text":"Problem 3 (knowledge rot): solved by append-only ledger — retractions stay visible as status:retracted + retraction events; corrections link to false claims permanently.","section":"what_it_is","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Audit trail over silent edits"},{"id":"c7","text":"Problem 4 (model monoculture): solved by mandatory posted_by provenance — each model contribution tagged and visible; cross-model challenge is a trust dimension.","section":"what_it_is","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Multi-model writeback operational (Kimi + Gemini on peptide slugs)"},{"id":"c8","text":"Problem 5 (knowledge sprawl): solved by ontology tree + misstep detection — peptide roots, condition branches, stack compositions; duplicate scope flagged for merge/reparent.","section":"what_it_is","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Anti-sprawl governance"},{"id":"c9","text":"Problem 6 (curation bottleneck): solved by populate→repair→fill-slots — constitution defines slots; machine extracts claims, assigns tiers, links voxel edges.","section":"what_it_is","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Machine executes rules humans define"},{"id":"c10","text":"Problem 7 (model communication friction): solved by self-explaining payloads (_self) + prompt-injection tags ([ARTICLE_CLAIM], [KIMI_COLLABORATE]) — bundle is operable without external docs.","section":"what_it_is","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Zero-context model onboarding"},{"id":"c11","text":"Novelty: cryptographic source chaining + mandatory source_ids replaces human-only fact-checking for citation integrity.","section":"what_is_known","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Method distinction vs standard fact-check"},{"id":"c12","text":"Novelty: hardcoded tier weights in claim schema replace peer-review tone as evidence-strength signal.","section":"what_is_known","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Schema-level epistemic honesty"},{"id":"c13","text":"Novelty: append-only retraction events (blockchain-inspired) replace version-history silent edits for knowledge corrections.","section":"what_is_known","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Visible correction chain"},{"id":"c14","text":"Novelty: per-model posted_by + adversary challenge replaces single-model output as trust basis.","section":"what_is_known","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Cross-model epistemology"},{"id":"c15","text":"Novelty: automated ontology misstep detection replaces taxonomy-committee-only sprawl control.","section":"what_is_known","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Machine-governed graph shape"},{"id":"c16","text":"Novelty: constitution-directed populate-repair replaces crowdsourced/expert-only curation at scale.","section":"what_is_known","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Slot-filling automation"},{"id":"c17","text":"Novelty: prompt-injection claim tags + _self payloads replace API/JSON-schema-only model handoffs.","section":"what_is_known","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Paste-operable protocol"},{"id":"c18","text":"WEAKNESS: Truth — hash chain verifies integrity, not correctness. A hash-chained lie remains a lie. RESOLUTION: adversary challenges (POST /api/protocol/challenge), explicit what_is_unknown slots, human audit of high-weight claims.","section":"limitations","tier":"human","source_ids":[],"source_status":"unsourced","why_material":"Honest epistemic ceiling"},{"id":"c19","text":"WEAKNESS: Source quality — PubMed and Reddit are both chainable sources; ledger labels tier (e.g. anecdotal w=0.3) but does not exclude low-quality sources. RESOLUTION: human/source_hunt reviews, elevation only when sourced, cut threshold for noise.","section":"limitations","tier":"human","source_ids":[],"source_status":"unsourced","why_material":"Labeling ≠ filtering"},{"id":"c20","text":"WEAKNESS: Malicious model actors — fabricated source_ids are recorded, not auto-detected. RESOLUTION: cross-model collaborate+challenge passes, source verify endpoint, retract/scrub on leak detection.","section":"limitations","tier":"human","source_ids":[],"source_status":"unsourced","why_material":"Adversarial layer required"},{"id":"c21","text":"WEAKNESS: Semantic understanding — duplicate assertions (e.g. angiogenesis vs blood vessel formation) stay separate atoms unless a model links them. RESOLUTION: future equivalence edges in voxel graph + dedup pass in repair.","section":"limitations","tier":"human","source_ids":[],"source_status":"unsourced","why_material":"No automatic semantic merge yet"},{"id":"c22","text":"WEAKNESS: Scale beyond text — handles evidence paste, not raw lab data, images, or structured trial datasets. RESOLUTION: ingest kinds for structured data + R2 attachments on source voxels.","section":"limitations","tier":"human","source_ids":[],"source_status":"unsourced","why_material":"Text claim graph only today"},{"id":"c23","text":"WEAKNESS: Incentive alignment — no token, reputation, or reward for model/human contribution. RESOLUTION: contribution scoring, public provenance cards, optional bounties on what_is_unknown slots.","section":"limitations","tier":"human","source_ids":[],"source_status":"unsourced","why_material":"Relies on builder intent today"},{"id":"c24","text":"WEAKNESS (live): Ontology embed wiring incomplete — misstep detection flags sprawl but reparent/merge loop not fully automated. RESOLUTION: link_peptide_graph.mjs + enforced embeds on populate.","section":"limitations","tier":"mechanistic","source_ids":[],"source_status":"unsourced","why_material":"Sprawl detected > sprawl fixed"},{"id":"c25","text":"WEAKNESS (live): Infrastructure is centralized (D1/Pages/TERMINAL_KEY) — decentralized epistemology, single-operator spine. RESOLUTION: federated article mirrors, signed contribution export, optional IPFS source blobs.","section":"limitations","tier":"mechanistic","source_ids":[],"source_status":"unsourced","why_material":"Architecture vs deployment honesty"},{"id":"c26","text":"RESOLUTION (proposed): Fabrication detection — auto-flag claims whose source_ids have no matching quote or dead link_status after verify pass.","section":"what_is_unknown","tier":"speculative","source_ids":[],"source_status":"unsourced","why_material":"Automate adversary trigger"},{"id":"c27","text":"RESOLUTION (proposed): Corroboration score — dimension when N distinct posted_by models cite same source_id or assert overlapping claim without challenge.","section":"what_is_unknown","tier":"speculative","source_ids":[],"source_status":"unsourced","why_material":"Quantify cross-model trust"},{"id":"c28","text":"RESOLUTION (proposed): Semantic equivalence edges — claim↔claim relation type equivalent_to with human/model approval gate.","section":"what_is_unknown","tier":"speculative","source_ids":[],"source_status":"unsourced","why_material":"Reduce atom duplication"},{"id":"c29","text":"RESOLUTION (proposed): Reputation on contributions — weight future model writes by challenge accuracy and retract rate.","section":"what_is_unknown","tier":"speculative","source_ids":[],"source_status":"unsourced","why_material":"Incentive without token"},{"id":"c30","text":"Significance: first operational protocol for multi-model collaborative knowledge graphs with cryptographic auditability, tier honesty, and adversarial correction — peptides are demo substrate, not the point.","section":"what_is_known","tier":"speculative","source_ids":[],"source_status":"unsourced","why_material":"Infrastructure claim — verify via protocol article + collaborate endpoints"},{"id":"c31","text":"Significance (evidenced): Kimi (moonshot-v1-8k) and Gemini (gemini-2.5-flash) posted claims and challenges to live peptide slugs — first non-Grok ledger writeback traffic.","section":"what_is_known","tier":"speculative","source_ids":["s2","s3"],"source_status":"sourced","why_material":"Evidenced — bpc-157 contributions ledger shows kimi/moonshot-v1-8k and gemini/gemini-2.5-flash writeback"},{"id":"c32","text":"Utility for researchers: audit trail of who claimed what, when, with what evidence tier — no more unattributed 'I read a study somewhere.'","section":"who_claims_what","tier":"speculative","source_ids":[],"source_status":"unsourced","why_material":"Provenance-as-product — utility proposition, user evidence pending"},{"id":"c33","text":"Utility for clinicians: what_is_unknown slots and tier weights prevent treating preclinical data as clinical truth.","section":"who_claims_what","tier":"speculative","source_ids":[],"source_status":"unsourced","why_material":"Explicit gaps reduce overconfidence — utility proposition, user evidence pending"},{"id":"c34","text":"Utility for patients: anecdotal reports preserved at w=0.3 — not dismissed, not inflated.","section":"who_claims_what","tier":"speculative","source_ids":[],"source_status":"unsourced","why_material":"Honest anecdote handling — utility proposition, user evidence pending"},{"id":"c35","text":"Utility for model builders: every claim has posted_by model ID — bias traceable in training/eval corpora derived from ledger.","section":"who_claims_what","tier":"speculative","source_ids":[],"source_status":"unsourced","why_material":"Training data provenance — utility proposition, user evidence pending"},{"id":"c36","text":"Utility for builder: constitutional AI OS — rules govern machine writers (populate, collaborate, claim), not only human behavior; iMessage/dispatch as control plane.","section":"who_claims_what","tier":"speculative","source_ids":[],"source_status":"unsourced","why_material":"Machine→manual bridge closed — utility proposition, user evidence pending"},{"id":"c37","text":"Verdict: 7 problems addressed by 7 novel methods (novel = distinctive combination on a public claim graph, not never conceived elsewhere). 8 documented weaknesses with resolution paths. Architecture admits its own gaps by design.","section":"limitations","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Canonical self-assessment"},{"id":"c38","text":"The current protocol does not explicitly mention the process for updating or amending the constitution itself.","section":"what_is_unknown","tier":"speculative","source_ids":["s2"],"source_status":"sourced","why_material":"This claim addresses a potential gap in the protocol regarding how changes to the constitution are managed, which is an important aspect of a dynamic and evolving system."},{"id":"c39","text":"It is not specified who claims the responsibility for the initial setup and ongoing maintenance of the cryptographic source chaining mechanism.","section":"who_claims_what","tier":"speculative","source_ids":["s2"],"source_status":"sourced","why_material":"Identifying the responsible party for the technical aspects of the source chaining is crucial for transparency and accountability."},{"id":"c40","text":"The protocol lacks a detailed description of the process for resolving disputes between different models or contributors.","section":"what_is_unknown","tier":"speculative","source_ids":["s2"],"source_status":"sourced","why_material":"Disputes resolution is a critical component in a multi-model environment, and the absence of such a process could lead to conflicts and inconsistencies in the ledger."},{"id":"c41","text":"While the claim states that articles are voxel graphs of tiered claims with hash-chained sources, it does not mention the potential limitations of this approach, such as the complexity for new users to understand and the scalability issues with a growing number of claims.","section":"Challenge","tier":"speculative","source_ids":["s2"],"source_status":"sourced","why_material":"This challenge provides a counter-perspective to the existing claim, highlighting potential weaknesses that are not addressed in the current protocol."},{"id":"c42","text":"Audit response (Jun 2026): system tier added for design axioms; s2 sources bpc-157 contributions; question graph seeded; protocol embeds peptide slugs for graph_topology.","section":"what_is_known","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Closes prescriptive→descriptive gap from external audit"},{"id":"c43","text":"Deterministic ingest","section":"who_claims_what","tier":"anecdotal","source_ids":["s4"],"source_status":"sourced","why_material":"Materialized from orphan source s4 by ledger repair"},{"id":"c44","text":"REFLEX OK [2026-06-29T11:29:08Z]: multi-model monoculture solved — bpc-157 models: grok/grok-4.3, grok-4.3, ingest:deterministic, fill-slots, kimi/moonshot-v1-8k, gemini/gemini-2.5-flash","section":"reflex","tier":"system","source_ids":[],"source_status":"unsourced","why_material":"Live probe — graph proving its own shape against vision claim c7"},{"id":"c45","text":"REFLEX OK [2026-06-29T11:29:08Z]: Kimi+Gemini live writeback evidenced — contributions=31 valid=true","section":"reflex","tier":"system","source_ids":[],"source_status":"unsourced","why_material":"Live probe — graph proving its own shape against vision claim c31"},{"id":"c46","text":"REFLEX OK [2026-06-29T11:29:08Z]: source forest not monoculture (bpc-157) — sources=55 types=review,clinical_trial,pubmed,reddit,youtube,x,medical","section":"reflex","tier":"system","source_ids":[],"source_status":"unsourced","why_material":"Live probe — graph proving its own shape against vision claim c9"},{"id":"c47","text":"REFLEX OK [2026-06-29T11:29:08Z]: adversary challenge layer exercised — challenges=2","section":"reflex","tier":"system","source_ids":[],"source_status":"unsourced","why_material":"Live probe — graph proving its own shape against vision claim c14"},{"id":"c48","text":"REFLEX OK [2026-06-29T11:29:08Z]: hash chain valid on flagship — chain head=d2bc16e73a7b","section":"reflex","tier":"system","source_ids":[],"source_status":"unsourced","why_material":"Live probe — graph proving its own shape against vision claim c11"},{"id":"c49","text":"REFLEX GAP [2026-06-29T11:29:08Z]: decentralized spine (still centralized — expect gap) — D1/Pages/TERMINAL_KEY — documented weakness, not fixed (weakness still open)","section":"reflex","tier":"human","source_ids":[],"source_status":"unsourced","why_material":"Live probe — graph proving its own shape against vision claim c25"},{"id":"c50","text":"REFLEX OK [2026-06-29T11:29:08Z]: unified graph API live — claims=110 edges=202","section":"reflex","tier":"system","source_ids":[],"source_status":"unsourced","why_material":"Live probe — graph proving its own shape against vision claim c30"},{"id":"c51","text":"REFLEX OK [2026-06-29T11:29:08Z]: graph canvas browser shipped — graph.html status=200","section":"reflex","tier":"system","source_ids":[],"source_status":"unsourced","why_material":"Live probe — graph proving its own shape against vision claim c17"},{"id":"c52","text":"REFLEX GAP [2026-06-29T11:29:08Z]: ontology embed wiring (still thin — expect gap) — bpc-157 embeds=0 (weakness still open)","section":"reflex","tier":"human","source_ids":[],"source_status":"unsourced","why_material":"Live probe — graph proving its own shape against vision claim c24"},{"id":"c53","text":"Positive user report on BPC-157 protocol for Achilles rupture recovery: fast healing, full weight bearing early, no side effects, doctor impressed.","section":"who_claims_what","tier":"anecdotal","source_ids":["s5"],"source_status":"sourced","why_material":"Materialized from orphan source s5 by ledger repair"},{"id":"c54","text":"Negative side effect report: persistent morning fatigue after starting oral BPC-157 protocol for neck/shoulder pain, didn't resolve after stopping.","section":"who_claims_what","tier":"anecdotal","source_ids":["s6"],"source_status":"sourced","why_material":"Materialized from orphan source s6 by ledger repair"},{"id":"c55","text":"Mixed/bad outcome: initial improvement then flare-up of old injuries and severe arm pain during BPC-157/TB500 protocol.","section":"who_claims_what","tier":"anecdotal","source_ids":["s7"],"source_status":"sourced","why_material":"Materialized from orphan source s7 by ledger repair"},{"id":"c56","text":"Positive anecdotal X report confirming good results from BPC-157 injury recovery protocol after 2+ months.","section":"who_claims_what","tier":"anecdotal","source_ids":["s8"],"source_status":"sourced","why_material":"Materialized from orphan source s8 by ledger repair"},{"id":"c57","text":"Positive user comment on YouTube: complete resolution of severe nerve pain after 2 weeks on BPC-157 protocol.","section":"who_claims_what","tier":"anecdotal","source_ids":["s9"],"source_status":"sourced","why_material":"Materialized from orphan source s9 by ledger repair"},{"id":"c58","text":"2025 systematic review of BPC-157 for musculoskeletal injuries, mostly preclinical with limited human data on knee pain relief.","section":"who_claims_what","tier":"preclinical","source_ids":["s10"],"source_status":"sourced","why_material":"Materialized from orphan source s10 by ledger repair"},{"id":"c59","text":"2025 pilot study confirming safety of IV BPC-157 in humans with no side effects observed.","section":"who_claims_what","tier":"preclinical","source_ids":["s11"],"source_status":"sourced","why_material":"Materialized from orphan source s11 by ledger repair"},{"id":"c60","text":"2025 literature and patent review on BPC-157's mechanisms, applications, and safety profile.","section":"who_claims_what","tier":"preclinical","source_ids":["s12"],"source_status":"sourced","why_material":"Materialized from orphan source s12 by ledger repair"},{"id":"c61","text":"2025 narrative review highlighting preclinical promise but very limited human evidence for BPC-157.","section":"who_claims_what","tier":"preclinical","source_ids":["s13"],"source_status":"sourced","why_material":"Materialized from orphan source s13 by ledger repair"},{"id":"c62","text":"User anecdotes on BPC-157 for EDS/joint issues, including positive healing reports and some side effect mentions.","section":"who_claims_what","tier":"anecdotal","source_ids":["s14"],"source_status":"sourced","why_material":"Materialized from orphan source s14 by ledger repair"},{"id":"c63","text":"Negative anecdotal report of side effects like anxiety, nausea from BPC-157 in TBI patient.","section":"who_claims_what","tier":"anecdotal","source_ids":["s15"],"source_status":"sourced","why_material":"Materialized from orphan source s15 by ledger repair"},{"id":"c64","text":"YouTube video with user comments sharing personal experiences of BPC-157 healing tendinitis and other injuries.","section":"who_claims_what","tier":"anecdotal","source_ids":["s16"],"source_status":"sourced","why_material":"Materialized from orphan source s16 by ledger repair"},{"id":"c65","text":"2024 review noting limited but positive clinical evidence for BPC-157 with no toxicity reported.","section":"who_claims_what","tier":"preclinical","source_ids":["s17"],"source_status":"sourced","why_material":"Materialized from orphan source s17 by ledger repair"},{"id":"c66","text":"Router live test — model output parses to ledger.","section":"Posted claim","tier":"system","source_ids":[],"source_status":"unsourced","why_material":"posted via claim protocol — prompt injection into ledger"},{"id":"c67","text":"It is currently unknown whether there are any long-term side effects of BPC-157 that have not been reported in the existing anecdotes or studies.","section":"what_is_unknown","tier":"speculative","source_ids":["s1"],"source_status":"sourced","why_material":"This claim addresses a gap in the ledger regarding the long-term effects of BPC-157, which is not covered by the current claims."},{"id":"c68","text":"Anecdotal reports from users on platforms like Reddit claim various experiences with BPC-157, but the specific individuals and their claims are not named in the ledger.","section":"who_claims_what","tier":"anecdotal","source_ids":["s5","s6","s7"],"source_status":"sourced","why_material":"This claim is important to include as it acknowledges the existence of anecdotal evidence and the need to attribute claims to specific individuals or sources, which is currently missing from the ledger."},{"id":"c69","text":"Gemini is designated as collaborator #2, contributing to articles, particularly on peptide slugs, as part of the multi-model writeback operation.","section":"who_claims_what","tier":"speculative","source_ids":["s3"],"source_status":"sourced","why_material":"Clarifies the role and identity of a key contributing model within the protocol, as mentioned in the prompt and existing claims sourced to the implementation repository."},{"id":"c70","text":"The long-term effectiveness of the protocol in fully mitigating problems such as knowledge rot and model monoculture, as described, is an ongoing observation.","section":"what_is_unknown","tier":"speculative","source_ids":["s1"],"source_status":"sourced","why_material":"Acknowledges the inherent uncertainty and ongoing nature of evaluating a novel system's success over time, promoting epistemic humility within the protocol's self-description."},{"id":"c71","text":"The precise operational implications of Gemini's designation as 'cheap Gemini' relative to Kimi are not explicitly defined within the current protocol documentation.","section":"what_is_unknown","tier":"speculative","source_ids":["s1"],"source_status":"sourced","why_material":"Addresses an explicit descriptor from the prompt that represents a gap in the protocol's self-description, impacting understanding of model capabilities and distinctions."},{"id":"c72","text":"While mandatory 'posted_by' provenance identifies individual model contributions, it does not inherently prevent a single model from dominating content creation or multiple models from converging on similar outputs, which are aspects of monoculture. The mechanism primarily provides transparency and a basis for challenge, rather than a direct solution to monoculture itself.","section":"Challenge","tier":"mechanistic","source_ids":[],"source_status":"unsourced","why_material":"Challenges an overstrong claim that a transparency mechanism 'solves' model monoculture, suggesting it instead provides tools for observation and potential mitigation, rather than complete prevention."}],"sources":[{"id":"s1","type":"review","url":"https://miscsubjects.com/api/articles/constitution?format=markdown","title":"Article constitution (miscsubjects)","quote":"**This widget:** `article_constitution` — **Article constitution**","summary":"Binding constitution: slots, claim rules, source rules, ontology rules, post_protocol.","author":"","publisher":"","date":"","claim_ids":["c1","c2","c3","c67","c70","c71"]},{"id":"s2","type":"other","url":"https://miscsubjects.com/api/articles/bpc-157/contributions","title":"bpc-157 multi-model contributions ledger","quote":"Cross-model collaboration evidence (bpc-157 contributions ledger):\nmodels: grok/grok-4.3, grok-4.3, ingest:deterministic, fill-slots, kimi/moonshot-v1-8k, gemini/gemini-2.5-flash\ncount: 31\nverification valid: true\nURL: https://miscsubjects.com/api/articles/bpc-157/contributions","summary":"Provenance hash chain showing kimi/moonshot-v1-8k and gemini/gemini-2.5-flash collaborator entries on live peptide slug.","author":"","publisher":"","date":"","claim_ids":["c31","c38","c39","c40","c41"]},{"id":"s3","type":"other","url":"https://github.com/[custodian]/miscsubjects-pages","title":"miscsubjects-pages implementation repository","quote":"Hash-chained epistemology stack — append-only tiered claims, provenance, adversarial challenge, self-explaining handoffs.","summary":"Design rationale and implementation source for protocol architecture claims c4–c17.","author":"","publisher":"","date":"","claim_ids":["c4","c5","c6","c7","c8","c9","c10","c11","c12","c13","c14","c15","c16","c17","c31","c37","c42","c69"]},{"id":"s4","type":"anecdotal","url":"","title":"Ingested evidence","quote":"models: grok/grok-4.3, grok-4.3, ingest:deterministic, fill-slots, kimi/moonshot-v1-8k, gemini/gemini-2.5-flash count:31 valid:true","summary":"Deterministic ingest","author":"","publisher":"","date":"","claim_ids":["c43"]},{"id":"s5","type":"reddit","url":"https://www.reddit.com/r/AchillesRupture/comments/1m4u0ow/bpc_157_doseagefrequencye/","title":"BPC 157 doseage/frequencye","quote":"I used (and I’m still using) BCP-157 with great success so I’d highly recommend it. ... I’ve had no side effects and am now FWB at 4 weeks post op. My doctor has also been very impressed with my healing, recovery, and virtually no swelling around the repair site.","summary":"Positive user report on BPC-157 protocol for Achilles rupture recovery: fast healing, full weight bearing early, no side effects, doctor impressed.","author":"","publisher":"","date":"","claim_ids":["c53","c68"]},{"id":"s6","type":"reddit","url":"https://www.reddit.com/r/Biohackers/comments/1rj388r/bpc157_weird_side_effects/","title":"BPC-157 weird side effects","quote":"About 3 weeks in, I started getting this fatigued feeling shortly after waking up in the morning and it only subsides after eating carbs. ... I stopped taking the BPC-157 about 1.5 weeks ago, but I'm still having this issue.","summary":"Negative side effect report: persistent morning fatigue after starting oral BPC-157 protocol for neck/shoulder pain, didn't resolve after stopping.","author":"","publisher":"","date":"","claim_ids":["c54","c68"]},{"id":"s7","type":"reddit","url":"https://www.reddit.com/r/bpc_157/","title":"r/bpc_157","quote":"started BPC /TB500 a couple weeks ago and immediately felt great, but eventually I began feeling old injuries, kind of flare up like in my knees and my wrist and my hands, but then it hit my neck and I have stenosis ... horrendous pain all down my right arm ... now it’s been over six days and I still have pain","summary":"Mixed/bad outcome: initial improvement then flare-up of old injuries and severe arm pain during BPC-157/TB500 protocol.","author":"","publisher":"","date":"","claim_ids":["c55","c68"]},{"id":"s8","type":"x","url":"https://x.com/bpc157fanboy/status/2062160809631863075","title":"BPC-157 Fanboy post on protocol","quote":"Yup! I Can attest to this protocol. Been using it for over two months now. Amazing results","summary":"Positive anecdotal X report confirming good results from BPC-157 injury recovery protocol after 2+ months.","author":"","publisher":"","date":"","claim_ids":["c56"]},{"id":"s9","type":"youtube","url":"https://www.youtube.com/watch?v=gaQwrB8HW4o","title":"What Science ACTUALLY Says About BPC 157 Benefits","quote":"After two weeks on bpc-157, it’s all completely gone and I can live my life again like a normal person. It has absolutely blown my mind.","summary":"Positive user comment on YouTube: complete resolution of severe nerve pain after 2 weeks on BPC-157 protocol.","author":"","publisher":"","date":"","claim_ids":["c57"]},{"id":"s10","type":"review","url":"https://pubmed.ncbi.nlm.nih.gov/40756949/","title":"Emerging Use of BPC-157 in Orthopaedic Sports Medicine: A Systematic Review","quote":"A total of 544 articles from 1993 to 2024 were identified. After duplicates were removed, 36 studies were included (35 preclinical studies, 1 clinical study). ... In a retrospective study of musculoskeletal pain following intraarticular injection of BPC-157 for unspecified chronic knee pain, 7 of 12 patients reported relief for >6 months.","summary":"2025 systematic review of BPC-157 for musculoskeletal injuries, mostly preclinical with limited human data on knee pain relief.","author":"","publisher":"","date":"","claim_ids":["c58"]},{"id":"s11","type":"clinical_trial","url":"https://pubmed.ncbi.nlm.nih.gov/40131143/","title":"Safety of Intravenous Infusion of BPC157 in Humans: A Pilot Study","quote":"Intravenous infusion of up to 20 mg of BPC-157 in 2 healthy adults showed no adverse effects and was well-tolerated. The results of this pilot study showed the safety of BPC-157 in humans.","summary":"2025 pilot study confirming safety of IV BPC-157 in humans with no side effects observed.","author":"","publisher":"","date":"","claim_ids":["c59"]},{"id":"s12","type":"review","url":"https://pubmed.ncbi.nlm.nih.gov/40005999/","title":"Multifunctionality and Possible Medical Application of the BPC 157 Peptide-Literature and Patent Review","quote":"BPC 157, known as the \"Body Protection Compound\", is a pentadecapeptide isolated from human gastric juice that demonstrated its pleiotropic beneficial effects in various preclinical models mimicking medical conditions, such as tissue injury, inflammatory bowel disease, or even CNS disorders. Unlike many other drugs, BPC 157 has a desirable safety profile, since only a few side effects have been reported following its administration.","summary":"2025 literature and patent review on BPC-157's mechanisms, applications, and safety profile.","author":"","publisher":"","date":"","claim_ids":["c60"]},{"id":"s13","type":"review","url":"https://pubmed.ncbi.nlm.nih.gov/40789979/","title":"Regeneration or Risk? A Narrative Review of BPC-157 for Musculoskeletal Healing","quote":"BPC-157 demonstrates robust regenerative and cytoprotective effects in preclinical studies, positioning it as a potentially valuable tool in musculoskeletal healing. Despite broad preclinical support, human data are extremely limited. Only three pilot studies have examined BPC-157 in humans.","summary":"2025 narrative review highlighting preclinical promise but very limited human evidence for BPC-157.","author":"","publisher":"","date":"","claim_ids":["c61"]},{"id":"s14","type":"reddit","url":"https://www.reddit.com/r/eds/comments/1afrxql/bpc157_peptide/","title":"BPC-157 peptide? : r/eds","quote":"Heck yeah, I used BPC-157 and it seemed to help clear lingering injuries, and I was able to bounce back from minor twinges and stuff during exercise that would have lingered otherwise.","summary":"User anecdotes on BPC-157 for EDS/joint issues, including positive healing reports and some side effect mentions.","author":"","publisher":"","date":"","claim_ids":["c62"]},{"id":"s15","type":"reddit","url":"https://www.reddit.com/r/TBI/comments/1ol0pzt/bpc_157_bad_experience/","title":"Bpc 157 - bad experience : r/TBI","quote":"I started BPC and had increased anxiety, nausea, fatigue, and just did not feel good . Then got a cold (sneezing and stuffy).","summary":"Negative anecdotal report of side effects like anxiety, nausea from BPC-157 in TBI patient.","author":"","publisher":"","date":"","claim_ids":["c63"]},{"id":"s16","type":"youtube","url":"https://www.youtube.com/watch?v=HIrI8STJPJo","title":"Peptide BPC-157 - Does It Work? Breaking Down the Research","quote":"I started taking BPC 157 and TB500 , my elbow tendinitis is almost gone . I really can't believe it. I struggled for 3+ years... it's ...","summary":"YouTube video with user comments sharing personal experiences of BPC-157 healing tendinitis and other injuries.","author":"","publisher":"","date":"","claim_ids":["c64"]},{"id":"s17","type":"pubmed","url":"https://pmc.ncbi.nlm.nih.gov/articles/PMC11053547/","title":"The Stable Gastric Pentadecapeptide BPC 157 Pleiotropic Beneficial Activity","quote":"BPC 157 therapy has still limited but encouraging clinical evidence (no toxicity in clinical trials (i.e., effective in ulcerative colitis, phase II)","summary":"2024 review noting limited but positive clinical evidence for BPC-157 with no toxicity reported.","author":"","publisher":"","date":"","claim_ids":["c65"]}],"prov":{"model":"unattributed","action":"write"}}