## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `protocol`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/protocol/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/protocol/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/protocol/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/protocol/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/protocol/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/protocol/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## MASTHEAD
- **identity:** `protocol` v61 · content_hash `63010d0800432457…` · thread_head genesis · 32 DIVs
- **thesis (c1):** Articles are voxel graphs of tiered claims with hash-chained sources.
  - c18 [human/active] WEAKNESS: Truth — hash chain verifies integrity, not correctness. A hash-chained lie remains a lie. RESOLUTION: adversary challenges (POST /api/protocol/challen
  - c19 [human/active] 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. RES
  - c20 [human/active] WEAKNESS: Malicious model actors — fabricated source_ids are recorded, not auto-detected. RESOLUTION: cross-model collaborate+challenge passes, source verify en
  - c21 [human/active] WEAKNESS: Semantic understanding — duplicate assertions (e.g. angiogenesis vs blood vessel formation) stay separate atoms unless a model links them. RESOLUTION:
  - c22 [human/active] WEAKNESS: Scale beyond text — handles evidence paste, not raw lab data, images, or structured trial datasets. RESOLUTION: ingest kinds for structured data + R2 
  - c23 [human/active] WEAKNESS: Incentive alignment — no token, reputation, or reward for model/human contribution. RESOLUTION: contribution scoring, public provenance cards, optiona
  - c49 [human/active] REFLEX GAP [2026-06-29T11:29:08Z]: decentralized spine (still centralized — expect gap) — D1/Pages/TERMINAL_KEY — documented weakness, not fixed (weakness still
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/protocol/discourse
- **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key
- **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/protocol/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `protocol`
- **title:** miscsubjects article protocol (constitution)
- **url:** https://miscsubjects.com/a/protocol
- **register:** technical
- **updated:** 2026-07-17T02:41:01.333Z

## Body

## §SELF — miscsubjects (paste without context)

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_constitution` — **Article constitution**
Binding rules: required article slots, claim/source rules, ontology anti-sprawl.
- **contains:** required slots, claim rules, source rules, ontology rules, post_protocol
- **how to use:** Defines what belongs in every article. Pair with voxels + ontology endpoints.
- **read:** https://miscsubjects.com/api/articles/constitution

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/{slug}/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Ontology flags sprawl and missteps across all articles. → https://miscsubjects.com/api/articles/ontology
5. Full feature index lives at system-map. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/{slug}/voxels
- **ontology** — Recursive peptide tree, sprawl orphans, misstep candidates (duplicate scope / missing parent). · https://miscsubjects.com/api/articles/ontology
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/{slug}/voxels

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# Article constitution (miscsubjects)

Articles are voxel graphs of claims — not prose blobs. Every assertion is a claim atom with tier, weight, source_ids, and posted_by provenance.

## Required slots
- **what_it_is** (required) — What is this peptide/stack/condition?
- **who_claims_what** (required) — Who claims what — study authors, platforms, n=?
- **what_is_known** (required) — What is known with tier labels (human/preclinical/anecdotal)
- **what_is_unknown** (required) — What is NOT known — explicit gaps
- **mechanism** — Proposed mechanism (mechanistic tier only)
- **limitations** (required) — Limits of evidence — no dose advice
- **disclaimer** (required) — Not medical advice

## Claim rules
- One claim = one falsifiable assertion. No compound claims.
- Every claim must declare tier: human|preclinical|anecdotal|mechanistic|speculative.
- Sourced claims must cite source_ids from the hash-chained ledger.
- Unsourced claims must set source_status: unsourced and why_material.
- posted_by is mandatory on every new claim (model id, human, or channel).
- No medical advice, no doses, no 'you should take'.

## Source / voxel rules
- Every source is a voxel edge: type, url, exact quote, summary, found_by, accessed_at.
- Sources hash-chain — prev/hash on append.
- Anecdotal sources must name platform (reddit|x|youtube|imessage|user_entry).

## Ontology / anti-sprawl
- Peptide articles (bpc-157, tb-500) are tree roots.
- Condition articles (bpc-157-glp1-gut-damage) branch from peptides.
- Stack articles (wolverine-stack-glp1) compose peptides — never duplicate peptide mechanism prose.
- If an article has no parent embeds and is not a root peptide → sprawl candidate.
- Misstep = duplicate scope with another slug; merge or reparent via embeds.

## How to POST into the ledger
```json
{
  "claim": "POST /api/protocol/claim",
  "source": "POST /api/protocol/sources",
  "ingest": "POST /api/protocol/ingest",
  "webhook": "POST /api/articles/<slug>/webhook {kind:claim|source}",
  "imessage_claim": "claim {slug}|{tier}|your assertion — who claims it, source?",
  "imessage_ingest": "ingest {slug}|evidence paste"
}
```

## Binding

Every writer, populate, ingest, and claim path is bound by this document. Read `GET /api/articles/system-map` for the full feature index.


## Architecture verdict (canonized 2026-06-29)

Seven problems, seven methods, eight weaknesses with resolution paths — all as tiered claim atoms on this article.

| # | Problem | Method | Weakness | Resolution path |
|---|---------|--------|----------|-----------------|
| 1 | Hallucination | source_ids + hash chain | Truth unverified | challenge + human audit |
| 2 | Evidence inflation | hardcoded tier weights | Source quality unfiltered | tier labels + source_hunt |
| 3 | Knowledge rot | append-only retraction | — | (addressed) |
| 4 | Model monoculture | posted_by + challenge | Malicious actors | cross-model adversary |
| 5 | Knowledge sprawl | ontology missteps | Embed wiring incomplete | link_peptide_graph |
| 6 | Curation bottleneck | populate-repair | — | (addressed) |
| 7 | Model friction | _self + prompt tags | Centralized spine | federated mirrors |

**Significance:** infrastructure for machine-collaborative epistemology — auditable, tier-honest, adversarial.

**Live proof:** Kimi + Gemini collaborate passes on bpc-157, tb-500, wolverine-stack-glp1.

Read claims: `GET /api/articles/protocol/health` · voxels: `GET /api/articles/protocol/voxels`


## Claims (48 of 72 ranked)

- **c18** [human w=0.8] 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.
  - who_claims: system/verdict
  - slot: limitations
- **c19** [human w=0.8] 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.
  - who_claims: system/verdict
  - slot: limitations
- **c20** [human w=0.8] 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.
  - who_claims: system/verdict
  - slot: limitations
- **c21** [human w=0.8] 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.
  - who_claims: system/verdict
  - slot: limitations
- **c22** [human w=0.8] 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.
  - who_claims: system/verdict
  - slot: limitations
- **c23** [human w=0.8] 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.
  - who_claims: system/verdict
  - slot: limitations
- **c24** [mechanistic w=0.3] 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.
  - who_claims: system/verdict
  - slot: limitations
- **c25** [mechanistic w=0.3] 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.
  - who_claims: system/verdict
  - slot: limitations
- **c2** [speculative w=0.12] Every new claim must include posted_by provenance.
  - who_claims: system/axiom
  - slot: limitations
  - sources: s1
- **c37** [speculative w=0.12] 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.
  - who_claims: system/design-axiom
  - slot: limitations
  - sources: s3
- **c49** [human w=0.8] REFLEX GAP [2026-06-29T11:29:08Z]: decentralized spine (still centralized — expect gap) — D1/Pages/TERMINAL_KEY — documented weakness, not fixed (weakness still open)
  - who_claims: system/reflex
  - slot: what_is_unknown
- **c52** [human w=0.8] REFLEX GAP [2026-06-29T11:29:08Z]: ontology embed wiring (still thin — expect gap) — bpc-157 embeds=0 (weakness still open)
  - who_claims: system/reflex
  - slot: what_is_unknown
- **c59** [preclinical w=0.5] 2025 pilot study confirming safety of IV BPC-157 in humans with no side effects observed.
  - who_claims: grok/grok-4.3
  - slot: who_claims_what
  - sources: s11
- **c60** [preclinical w=0.5] 2025 literature and patent review on BPC-157's mechanisms, applications, and safety profile.
  - who_claims: grok/grok-4.3
  - slot: who_claims_what
  - sources: s12
- **c72** [mechanistic w=0.4] 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.
  - who_claims: gemini/gemini-2.5-flash (adversary)
- **c44** [system w=0.35] 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
  - who_claims: system/reflex
  - slot: what_is_known
- **c45** [system w=0.35] REFLEX OK [2026-06-29T11:29:08Z]: Kimi+Gemini live writeback evidenced — contributions=31 valid=true
  - who_claims: system/reflex
  - slot: what_is_known
- **c46** [system w=0.35] REFLEX OK [2026-06-29T11:29:08Z]: source forest not monoculture (bpc-157) — sources=55 types=review,clinical_trial,pubmed,reddit,youtube,x,medical
  - who_claims: system/reflex
  - slot: what_is_known
- **c47** [system w=0.35] REFLEX OK [2026-06-29T11:29:08Z]: adversary challenge layer exercised — challenges=2
  - who_claims: system/reflex
  - slot: what_is_known
- **c48** [system w=0.35] REFLEX OK [2026-06-29T11:29:08Z]: hash chain valid on flagship — chain head=d2bc16e73a7b
  - who_claims: system/reflex
  - slot: what_is_known
- **c50** [system w=0.35] REFLEX OK [2026-06-29T11:29:08Z]: unified graph API live — claims=110 edges=202
  - who_claims: system/reflex
  - slot: what_is_known
- **c51** [system w=0.35] REFLEX OK [2026-06-29T11:29:08Z]: graph canvas browser shipped — graph.html status=200
  - who_claims: system/reflex
  - slot: what_is_known
- **c66** [system w=0.35] Router live test — model output parses to ledger.
  - who_claims: system/conversation-router
- **c56** [anecdotal w=0.3] Positive anecdotal X report confirming good results from BPC-157 injury recovery protocol after 2+ months.
  - who_claims: grok/grok-4.3
  - slot: who_claims_what
  - sources: s8
- **c58** [preclinical w=0.22] 2025 systematic review of BPC-157 for musculoskeletal injuries, mostly preclinical with limited human data on knee pain relief.
  - who_claims: grok/grok-4.3
  - slot: who_claims_what
  - sources: s10
- **c61** [preclinical w=0.22] 2025 narrative review highlighting preclinical promise but very limited human evidence for BPC-157.
  - who_claims: grok/grok-4.3
  - slot: who_claims_what
  - sources: s13
- **c65** [preclinical w=0.22] 2024 review noting limited but positive clinical evidence for BPC-157 with no toxicity reported.
  - who_claims: grok/grok-4.3
  - slot: who_claims_what
  - sources: s17
- **c43** [anecdotal w=0.3] Deterministic ingest
  - who_claims: system/audit-response
  - slot: who_claims_what
  - sources: s4
- **c53** [anecdotal w=0.3] Positive user report on BPC-157 protocol for Achilles rupture recovery: fast healing, full weight bearing early, no side effects, doctor impressed.
  - who_claims: grok/grok-4.3
  - slot: who_claims_what
  - sources: s5
- **c54** [anecdotal w=0.3] Negative side effect report: persistent morning fatigue after starting oral BPC-157 protocol for neck/shoulder pain, didn't resolve after stopping.
  - who_claims: grok/grok-4.3
  - slot: who_claims_what
  - sources: s6
- **c55** [anecdotal w=0.3] Mixed/bad outcome: initial improvement then flare-up of old injuries and severe arm pain during BPC-157/TB500 protocol.
  - who_claims: grok/grok-4.3
  - slot: who_claims_what
  - sources: s7
- **c57** [anecdotal w=0.3] Positive user comment on YouTube: complete resolution of severe nerve pain after 2 weeks on BPC-157 protocol.
  - who_claims: grok/grok-4.3
  - slot: who_claims_what
  - sources: s9
- **c62** [anecdotal w=0.3] User anecdotes on BPC-157 for EDS/joint issues, including positive healing reports and some side effect mentions.
  - who_claims: grok/grok-4.3
  - slot: who_claims_what
  - sources: s14
- **c63** [anecdotal w=0.3] Negative anecdotal report of side effects like anxiety, nausea from BPC-157 in TBI patient.
  - who_claims: grok/grok-4.3
  - slot: who_claims_what
  - sources: s15
- **c64** [anecdotal w=0.3] YouTube video with user comments sharing personal experiences of BPC-157 healing tendinitis and other injuries.
  - who_claims: grok/grok-4.3
  - slot: who_claims_what
  - sources: s16
- **c68** [anecdotal w=0.3] 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.
  - who_claims: kimi/moonshot-v1-8k
  - slot: who_claims_what
  - sources: s5, s6, s7
- **c1** [speculative w=0.12] Articles are voxel graphs of tiered claims with hash-chained sources.
  - who_claims: system/axiom
  - slot: what_it_is
  - sources: s1
- **c3** [speculative w=0.12] Not medical advice — tier-honest evidence only.
  - who_claims: system/axiom
  - slot: disclaimer
  - sources: s1
- **c4** [speculative w=0.12] Problem 1 (hallucination): solved by tier weights + mandatory source_ids + hash-chained ledger — no source = unsourced + why_material; models cannot invent citations.
  - who_claims: system/design-axiom
  - slot: what_it_is
  - sources: s3
- **c5** [speculative w=0.12] 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.
  - who_claims: system/design-axiom
  - slot: what_it_is
  - sources: s3
- **c6** [speculative w=0.12] Problem 3 (knowledge rot): solved by append-only ledger — retractions stay visible as status:retracted + retraction events; corrections link to false claims permanently.
  - who_claims: system/design-axiom
  - slot: what_it_is
  - sources: s3
- **c7** [speculative w=0.12] Problem 4 (model monoculture): solved by mandatory posted_by provenance — each model contribution tagged and visible; cross-model challenge is a trust dimension.
  - who_claims: system/design-axiom
  - slot: what_it_is
  - sources: s3
- **c8** [speculative w=0.12] Problem 5 (knowledge sprawl): solved by ontology tree + misstep detection — peptide roots, condition branches, stack compositions; duplicate scope flagged for merge/reparent.
  - who_claims: system/design-axiom
  - slot: what_it_is
  - sources: s3
- **c9** [speculative w=0.12] Problem 6 (curation bottleneck): solved by populate→repair→fill-slots — constitution defines slots; machine extracts claims, assigns tiers, links voxel edges.
  - who_claims: system/design-axiom
  - slot: what_it_is
  - sources: s3
- **c10** [speculative w=0.12] Problem 7 (model communication friction): solved by self-explaining payloads (_self) + prompt-injection tags ([ARTICLE_CLAIM], [KIMI_COLLABORATE]) — bundle is operable without external docs.
  - who_claims: system/design-axiom
  - slot: what_it_is
  - sources: s3
- **c11** [speculative w=0.12] Novelty: cryptographic source chaining + mandatory source_ids replaces human-only fact-checking for citation integrity.
  - who_claims: system/design-axiom
  - slot: what_is_known
  - sources: s3
- **c12** [speculative w=0.12] Novelty: hardcoded tier weights in claim schema replace peer-review tone as evidence-strength signal.
  - who_claims: system/design-axiom
  - slot: what_is_known
  - sources: s3
- **c13** [speculative w=0.12] Novelty: append-only retraction events (blockchain-inspired) replace version-history silent edits for knowledge corrections.
  - who_claims: system/design-axiom
  - slot: what_is_known
  - sources: s3

## Voxel graph (72 atoms · 154 edges)
- full graph: https://miscsubjects.com/api/articles/protocol/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (17)
- chain valid: no · head: ``

### s1 · review · ok
- title: Article constitution (miscsubjects)
- url: https://miscsubjects.com/api/articles/constitution?format=markdown
- summary: Binding constitution: slots, claim rules, source rules, ontology rules, post_protocol.
- quote: **This widget:** `article_constitution` — **Article constitution**
- claim_ids: c1, c2, c3, c67, c70, c71
- hash: `b4a31ac6afd8c014`

### s2 · other · ok
- title: bpc-157 multi-model contributions ledger
- url: 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.
- quote: Cross-model collaboration evidence (bpc-157 contributions ledger):
models: grok/grok-4.3, grok-4.3, ingest:deterministic, fill-slots, kimi/moonshot-v1-8k, gemini/gemini-2.5-flash
count: 31
verification valid: true
URL: https://miscsubjects.com/api/articles/bpc-157/contributions
- claim_ids: c31, c38, c39, c40, c41
- hash: `66d7c9a0ed069e08`

### s3 · other · http_404
- title: miscsubjects-pages implementation repository
- url: https://github.com/[custodian]/miscsubjects-pages
- summary: Design rationale and implementation source for protocol architecture claims c4–c17.
- quote: Hash-chained epistemology stack — append-only tiered claims, provenance, adversarial challenge, self-explaining handoffs.
- claim_ids: c4, c5, c6, c7, c8, c9, c10, c11, c12, c13, c14, c15, c16, c17, c31, c37, c42, c69
- hash: `43fa1983dc917251`

### s4 · anecdotal · invalid
- title: Ingested evidence
- summary: Deterministic ingest
- 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
- claim_ids: c43
- hash: `debf0861fec00d53`

### s5 · reddit · ok
- title: BPC 157 doseage/frequencye
- url: https://www.reddit.com/r/AchillesRupture/comments/1m4u0ow/bpc_157_doseagefrequencye/
- summary: Positive user report on BPC-157 protocol for Achilles rupture recovery: fast healing, full weight bearing early, no side effects, doctor impressed.
- 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.
- claim_ids: c53, c68
- hash: `da8f9b41ef7fbc70`

### s6 · reddit · ok
- title: BPC-157 weird side effects
- url: https://www.reddit.com/r/Biohackers/comments/1rj388r/bpc157_weird_side_effects/
- summary: Negative side effect report: persistent morning fatigue after starting oral BPC-157 protocol for neck/shoulder pain, didn't resolve after stopping.
- 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.
- claim_ids: c54, c68
- hash: `d5836231e077ed4a`

### s7 · reddit · ok
- title: r/bpc_157
- url: https://www.reddit.com/r/bpc_157/
- summary: Mixed/bad outcome: initial improvement then flare-up of old injuries and severe arm pain during BPC-157/TB500 protocol.
- 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
- claim_ids: c55, c68
- hash: `7a5f358f79e1c577`

### s8 · x · ok
- title: BPC-157 Fanboy post on protocol
- url: https://x.com/bpc157fanboy/status/2062160809631863075
- summary: Positive anecdotal X report confirming good results from BPC-157 injury recovery protocol after 2+ months.
- quote: Yup! I Can attest to this protocol. Been using it for over two months now. Amazing results
- claim_ids: c56
- hash: `8202e92f7b4fadee`

### s9 · youtube · http_429
- title: What Science ACTUALLY Says About BPC 157 Benefits
- url: https://www.youtube.com/watch?v=gaQwrB8HW4o
- summary: Positive user comment on YouTube: complete resolution of severe nerve pain after 2 weeks on BPC-157 protocol.
- 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.
- claim_ids: c57
- hash: `7d956b11373488c5`

### s10 · review · ok
- title: Emerging Use of BPC-157 in Orthopaedic Sports Medicine: A Systematic Review
- url: https://pubmed.ncbi.nlm.nih.gov/40756949/
- summary: 2025 systematic review of BPC-157 for musculoskeletal injuries, mostly preclinical with limited human data on knee pain relief.
- 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.
- claim_ids: c58
- hash: `2328df2a1fc753e3`

### s11 · clinical_trial · ok
- title: Safety of Intravenous Infusion of BPC157 in Humans: A Pilot Study
- url: https://pubmed.ncbi.nlm.nih.gov/40131143/
- summary: 2025 pilot study confirming safety of IV BPC-157 in humans with no side effects observed.
- 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.
- claim_ids: c59
- hash: `75219f5a4e553df8`

### s12 · review · ok
- title: Multifunctionality and Possible Medical Application of the BPC 157 Peptide-Literature and Patent Review
- url: https://pubmed.ncbi.nlm.nih.gov/40005999/
- summary: 2025 literature and patent review on BPC-157's mechanisms, applications, and safety profile.
- 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.
- claim_ids: c60
- hash: `3ecd523a81dbc7eb`

### s13 · review · ok
- title: Regeneration or Risk? A Narrative Review of BPC-157 for Musculoskeletal Healing
- url: https://pubmed.ncbi.nlm.nih.gov/40789979/
- summary: 2025 narrative review highlighting preclinical promise but very limited human evidence for BPC-157.
- 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.
- claim_ids: c61
- hash: `4c14bdc0b92d971f`

### s14 · reddit · ok
- title: BPC-157 peptide? : r/eds
- url: https://www.reddit.com/r/eds/comments/1afrxql/bpc157_peptide/
- summary: User anecdotes on BPC-157 for EDS/joint issues, including positive healing reports and some side effect mentions.
- 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.
- claim_ids: c62
- hash: `cba9767b0198a408`

### s15 · reddit · ok
- title: Bpc 157 - bad experience : r/TBI
- url: https://www.reddit.com/r/TBI/comments/1ol0pzt/bpc_157_bad_experience/
- summary: Negative anecdotal report of side effects like anxiety, nausea from BPC-157 in TBI patient.
- quote: I started BPC and had increased anxiety, nausea, fatigue, and just did not feel good . Then got a cold (sneezing and stuffy).
- claim_ids: c63
- hash: `8525a135d4926852`

### s16 · youtube · http_429
- title: Peptide BPC-157 - Does It Work? Breaking Down the Research
- url: https://www.youtube.com/watch?v=HIrI8STJPJo
- summary: YouTube video with user comments sharing personal experiences of BPC-157 healing tendinitis and other injuries.
- 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 ...
- claim_ids: c64
- hash: `fe17716fcd7fa3ce`

### s17 · pubmed · ok
- title: The Stable Gastric Pentadecapeptide BPC 157 Pleiotropic Beneficial Activity
- url: https://pmc.ncbi.nlm.nih.gov/articles/PMC11053547/
- summary: 2024 review noting limited but positive clinical evidence for BPC-157 with no toxicity reported.
- quote: BPC 157 therapy has still limited but encouraging clinical evidence (no toxicity in clinical trials (i.e., effective in ulcerative colitis, phase II)
- claim_ids: c65
- hash: `e3241b74e28f1daf`

## Provenance (62 model passes)
- chain valid: yes · head: `f4a45da3ae155a67`

- collaborate · gemini/gemini-2.5-flash · 2026-06-29T12:27 · hash `cfdb497cfd1a`
- repair · system/audit-repair · 2026-06-29T12:45 · hash `34225764a71b`
- repair · system/audit-repair · 2026-06-29T12:45 · hash `db43cdefd3b4`
- repair · system/audit-repair · 2026-06-29T12:45 · hash `b49276034d9a`
- repair · system/audit-repair · 2026-06-29T12:45 · hash `afcd9d30d826`
- repair · system/audit-repair · 2026-06-29T13:26 · hash `e50ea62b71b7`
- repair · system/audit-repair · 2026-06-29T13:26 · hash `ba302d87a8fe`
- voxel_divide · owner · 2026-07-17T02:41 · hash `f4a45da3ae15`

## Question graph
- questions: 2 · evidence ingests: 4
- **qn_philosophy_protocol_how_does_the_philosophy_pros_4b5505e0** [gap] How does the philosophy prosecute the build, and how does the build prosecute the philosophy?
  - gaps: full task-adjusted logical density pricing; systematic philosophy-specific self-test questions; owner-style prosecution tied to corpus
- **qn_protocol_has_kimi_posted__3286246d** [enriched] Has Kimi posted?

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/protocol/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/protocol/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"protocol","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest protocol|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim protocol|tier|assertion`
- **iMessage ask:** `protocol|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `protocol`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/protocol/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/protocol/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*