Evidence review · technical

miscsubjects article protocol (constitution)

bundle · json · system map · manifest

Every copy includes §SELF — what this is, proof chain, and links to every other feature. No context required.

§SELF — this page explains the system
## §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:** `human_page` — **Human article page**
Rendered article with claims, sources, copy widgets, ask prompts.
- **article slug:** `protocol`
- **contains:** rendered article, copy widgets, claims, sources, ask prompts
- **how to use:** Use Copy for LLM or Copy system map — both paste without context.
- **read:** https://miscsubjects.com/a/protocol

### 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)
- **bundle** — Paste-ready package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/protocol/bundle?format=markdown
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/protocol/prompts
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/protocol/topology

### 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.*
What is not known
  • REFLEX GAP [2026-06-29T11:29:08Z]: decentralized spine (still centralized — expect gap) — D1/Pages/TERMINAL_KEY — documented weakness, not fixed (weakness still open)
  • REFLEX GAP [2026-06-29T11:29:08Z]: ontology embed wiring (still thin — expect gap) — bpc-157 embeds=0 (weakness still open)

§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

Evidence · 17 sources · swipe →chain e3241b74e28f · verify chain · provenance
1 / 17

Key evidence

72 claims · tier-ranked · API
human
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.
human
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.
human
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.
human
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.
human
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.
human
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.
mechanistic
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.
mechanistic
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.
human
REFLEX GAP [2026-06-29T11:29:08Z]: decentralized spine (still centralized — expect gap) — D1/Pages/TERMINAL_KEY — documented weakness, not fixed (weakness still open)
human
REFLEX GAP [2026-06-29T11:29:08Z]: ontology embed wiring (still thin — expect gap) — bpc-157 embeds=0 (weakness still open)
24 more ranked claims
preclinical0.50
2025 pilot study confirming safety of IV BPC-157 in humans with no side effects observed.
grok/grok-4.3
Materialized from orphan source s11 by ledger repair
sources: s11
preclinical0.50
2025 literature and patent review on BPC-157's mechanisms, applications, and safety profile.
grok/grok-4.3
Materialized from orphan source s12 by ledger repair
sources: s12
mechanistic0.40
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.
gemini/gemini-2.5-flash (adversary)
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.
system0.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
system/reflex
Live probe — graph proving its own shape against vision claim c7
system0.35
REFLEX OK [2026-06-29T11:29:08Z]: Kimi+Gemini live writeback evidenced — contributions=31 valid=true
system/reflex
Live probe — graph proving its own shape against vision claim c31
system0.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
system/reflex
Live probe — graph proving its own shape against vision claim c9
system0.35
REFLEX OK [2026-06-29T11:29:08Z]: adversary challenge layer exercised — challenges=2
system/reflex
Live probe — graph proving its own shape against vision claim c14
system0.35
REFLEX OK [2026-06-29T11:29:08Z]: hash chain valid on flagship — chain head=d2bc16e73a7b
system/reflex
Live probe — graph proving its own shape against vision claim c11
system0.35
REFLEX OK [2026-06-29T11:29:08Z]: unified graph API live — claims=110 edges=202
system/reflex
Live probe — graph proving its own shape against vision claim c30
system0.35
REFLEX OK [2026-06-29T11:29:08Z]: graph canvas browser shipped — graph.html status=200
system/reflex
Live probe — graph proving its own shape against vision claim c17
system0.35
Router live test — model output parses to ledger.
system/conversation-router
posted via claim protocol — prompt injection into ledger
anecdotal0.30
Positive anecdotal X report confirming good results from BPC-157 injury recovery protocol after 2+ months.
grok/grok-4.3
Materialized from orphan source s8 by ledger repair
sources: s8
preclinical0.22low confidence
2025 systematic review of BPC-157 for musculoskeletal injuries, mostly preclinical with limited human data on knee pain relief.
grok/grok-4.3
Materialized from orphan source s10 by ledger repair
sources: s10
preclinical0.22low confidence
2025 narrative review highlighting preclinical promise but very limited human evidence for BPC-157.
grok/grok-4.3
Materialized from orphan source s13 by ledger repair
sources: s13
preclinical0.22low confidence
2024 review noting limited but positive clinical evidence for BPC-157 with no toxicity reported.
grok/grok-4.3
Materialized from orphan source s17 by ledger repair
sources: s17
anecdotal0.22low confidence
Deterministic ingest
system/audit-response
Materialized from orphan source s4 by ledger repair
sources: s4
anecdotal0.22low confidence
Positive user report on BPC-157 protocol for Achilles rupture recovery: fast healing, full weight bearing early, no side effects, doctor impressed.
grok/grok-4.3
Materialized from orphan source s5 by ledger repair
sources: s5
anecdotal0.22low confidence
Negative side effect report: persistent morning fatigue after starting oral BPC-157 protocol for neck/shoulder pain, didn't resolve after stopping.
grok/grok-4.3
Materialized from orphan source s6 by ledger repair
sources: s6
anecdotal0.22low confidence
Mixed/bad outcome: initial improvement then flare-up of old injuries and severe arm pain during BPC-157/TB500 protocol.
grok/grok-4.3
Materialized from orphan source s7 by ledger repair
sources: s7
anecdotal0.22low confidence
Positive user comment on YouTube: complete resolution of severe nerve pain after 2 weeks on BPC-157 protocol.
grok/grok-4.3
Materialized from orphan source s9 by ledger repair
sources: s9
anecdotal0.22low confidence
User anecdotes on BPC-157 for EDS/joint issues, including positive healing reports and some side effect mentions.
grok/grok-4.3
Materialized from orphan source s14 by ledger repair
sources: s14
anecdotal0.22low confidence
Negative anecdotal report of side effects like anxiety, nausea from BPC-157 in TBI patient.
grok/grok-4.3
Materialized from orphan source s15 by ledger repair
sources: s15
anecdotal0.22low confidence
YouTube video with user comments sharing personal experiences of BPC-157 healing tendinitis and other injuries.
grok/grok-4.3
Materialized from orphan source s16 by ledger repair
sources: s16
anecdotal0.22low confidence
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.
kimi/moonshot-v1-8k
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.
sources: s5, s6, s7
Low-confidence / auto-generated 38
speculative0.12
Every new claim must include posted_by provenance.
system/axiom
Provenance rule
sources: s1
speculative0.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.
system/design-axiom
Canonical self-assessment
sources: s3
speculative0.12
Articles are voxel graphs of tiered claims with hash-chained sources.
system/axiom
Core architecture invariant
sources: s1
speculative0.12
Not medical advice — tier-honest evidence only.
system/axiom
Legal/safety
sources: s1
speculative0.12low confidence
Problem 1 (hallucination): solved by tier weights + mandatory source_ids + hash-chained ledger — no source = unsourced + why_material; models cannot invent citations.
system/design-axiom
Core epistemic invariant
sources: s3
speculative0.12low confidence
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.
system/design-axiom
Prevents weak→strong rhetorical smoothing
sources: s3
speculative0.12low confidence
Problem 3 (knowledge rot): solved by append-only ledger — retractions stay visible as status:retracted + retraction events; corrections link to false claims permanently.
system/design-axiom
Audit trail over silent edits
sources: s3
speculative0.12low confidence
Problem 4 (model monoculture): solved by mandatory posted_by provenance — each model contribution tagged and visible; cross-model challenge is a trust dimension.
system/design-axiom
Multi-model writeback operational (Kimi + Gemini on peptide slugs)
sources: s3
speculative0.12low confidence
Problem 5 (knowledge sprawl): solved by ontology tree + misstep detection — peptide roots, condition branches, stack compositions; duplicate scope flagged for merge/reparent.
system/design-axiom
Anti-sprawl governance
sources: s3
speculative0.12low confidence
Problem 6 (curation bottleneck): solved by populate→repair→fill-slots — constitution defines slots; machine extracts claims, assigns tiers, links voxel edges.
system/design-axiom
Machine executes rules humans define
sources: s3
speculative0.12low confidence
Problem 7 (model communication friction): solved by self-explaining payloads (_self) + prompt-injection tags ([ARTICLE_CLAIM], [KIMI_COLLABORATE]) — bundle is operable without external docs.
system/design-axiom
Zero-context model onboarding
sources: s3
speculative0.12low confidence
Novelty: cryptographic source chaining + mandatory source_ids replaces human-only fact-checking for citation integrity.
system/design-axiom
Method distinction vs standard fact-check
sources: s3
speculative0.12low confidence
Novelty: hardcoded tier weights in claim schema replace peer-review tone as evidence-strength signal.
system/design-axiom
Schema-level epistemic honesty
sources: s3
speculative0.12low confidence
Novelty: append-only retraction events (blockchain-inspired) replace version-history silent edits for knowledge corrections.
system/design-axiom
Visible correction chain
sources: s3
speculative0.12low confidence
Novelty: per-model posted_by + adversary challenge replaces single-model output as trust basis.
system/design-axiom
Cross-model epistemology
sources: s3
speculative0.12low confidence
Novelty: automated ontology misstep detection replaces taxonomy-committee-only sprawl control.
system/design-axiom
Machine-governed graph shape
sources: s3
speculative0.12low confidence
Novelty: constitution-directed populate-repair replaces crowdsourced/expert-only curation at scale.
system/design-axiom
Slot-filling automation
sources: s3
speculative0.12low confidence
Novelty: prompt-injection claim tags + _self payloads replace API/JSON-schema-only model handoffs.
system/design-axiom
Paste-operable protocol
sources: s3
speculative0.12low confidence
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.
system/evidence-ingest
Evidenced — bpc-157 contributions ledger shows kimi/moonshot-v1-8k and gemini/gemini-2.5-flash writeback
sources: s2, s3
speculative0.12low confidence
The current protocol does not explicitly mention the process for updating or amending the constitution itself.
kimi/moonshot-v1-8k
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.
sources: s2
speculative0.12low confidence
It is not specified who claims the responsibility for the initial setup and ongoing maintenance of the cryptographic source chaining mechanism.
kimi/moonshot-v1-8k
Identifying the responsible party for the technical aspects of the source chaining is crucial for transparency and accountability.
sources: s2
speculative0.12low confidence
The protocol lacks a detailed description of the process for resolving disputes between different models or contributors.
kimi/moonshot-v1-8k
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.
sources: s2
speculative0.12low confidence
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.
kimi/moonshot-v1-8k (adversary)
This challenge provides a counter-perspective to the existing claim, highlighting potential weaknesses that are not addressed in the current protocol.
sources: s2
speculative0.12low confidence
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.
system/audit-response
Closes prescriptive→descriptive gap from external audit
sources: s3
speculative0.12
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.
kimi/moonshot-v1-8k
This claim addresses a gap in the ledger regarding the long-term effects of BPC-157, which is not covered by the current claims.
sources: s1
speculative0.12low confidence
Gemini is designated as collaborator #2, contributing to articles, particularly on peptide slugs, as part of the multi-model writeback operation.
gemini/gemini-2.5-flash
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.
sources: s3
speculative0.10
RESOLUTION (proposed): Fabrication detection — auto-flag claims whose source_ids have no matching quote or dead link_status after verify pass.
system/verdict
Automate adversary trigger
speculative0.10
RESOLUTION (proposed): Corroboration score — dimension when N distinct posted_by models cite same source_id or assert overlapping claim without challenge.
system/verdict
Quantify cross-model trust
speculative0.10
RESOLUTION (proposed): Semantic equivalence edges — claim↔claim relation type equivalent_to with human/model approval gate.
system/verdict
Reduce atom duplication
speculative0.10
RESOLUTION (proposed): Reputation on contributions — weight future model writes by challenge accuracy and retract rate.
system/verdict
Incentive without token
speculative0.10
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.
system/verdict
Infrastructure claim — verify via protocol article + collaborate endpoints
speculative0.10
Utility for researchers: audit trail of who claimed what, when, with what evidence tier — no more unattributed 'I read a study somewhere.'
system/verdict
Provenance-as-product — utility proposition, user evidence pending
speculative0.10
Utility for clinicians: what_is_unknown slots and tier weights prevent treating preclinical data as clinical truth.
system/verdict
Explicit gaps reduce overconfidence — utility proposition, user evidence pending
speculative0.10
Utility for patients: anecdotal reports preserved at w=0.3 — not dismissed, not inflated.
system/verdict
Honest anecdote handling — utility proposition, user evidence pending
speculative0.10
Utility for model builders: every claim has posted_by model ID — bias traceable in training/eval corpora derived from ledger.
system/verdict
Training data provenance — utility proposition, user evidence pending
speculative0.10
Utility for builder: constitutional AI OS — rules govern machine writers (populate, collaborate, claim), not only human behavior; iMessage/dispatch as control plane.
system/verdict
Machine→manual bridge closed — utility proposition, user evidence pending
speculative0.10
The long-term effectiveness of the protocol in fully mitigating problems such as knowledge rot and model monoculture, as described, is an ongoing observation.
gemini/gemini-2.5-flash
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.
sources: s1
speculative0.10
The precise operational implications of Gemini's designation as 'cheap Gemini' relative to Kimi are not explicitly defined within the current protocol documentation.
gemini/gemini-2.5-flash
Addresses an explicit descriptor from the prompt that represents a gap in the protocol's self-description, impacting understanding of model capabilities and distinctions.
sources: s1
Model swipes · 44 from 8 models · swipe →verify
1 / 44
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
dda1e2caabfb71c8
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
e23fbe05a5db1215
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
0eb4a06e3295fefb
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
1a28a583caa8e116
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
babe9d3000736bab
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
30010a4735f1f284
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
c3a3b1be85986898
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
22cf3b7c7d3c2f38
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
1109ed87526a85a8
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
bc1903c706dc6a99
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
27ca111fe1002532
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
356a4715872002fd
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
bb3f9dc2d1be6741
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
562c435c53364389
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
ccd432a1810988e1
grok-buildclaim_post
claim2026-06-29 11:07
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c19
it output
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.
ff3d1843adc03c4e
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
1ef6de4a555807f5
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
f89e7511e23d0832
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
a96b302bf75a1419
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
70fae928cf78c457
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
81a89092edc9a768
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
d3d3b439505d485d
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
d9ed6b0b50ae1533
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
73f67cf6a361eeb4
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
6815227a8ad0d098
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
43a4ed76c58f1d0a
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
7cc17035de87da8e
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
5201090ad6c3942c
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
6b377686f7e912c4
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
66eaa92e9464153a
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
d9a42f125202b979
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
6404be3a68e50d45
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
9141d34446228501
grok-buildclaim_post
claim2026-06-29 11:08
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c37
it output
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.
477fe56f580e4813
system/verdict-postsource_hunt
sources2026-06-29 11:12
1 source(s) added · 1 sources
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol
it output
1 source(s) added
64565aed842ca91f
kimi/moonshot-v1-8kcollaborator
collaborate2026-06-29 11:12
collaborate
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol
it output
As Kimi, I am adding claims that are tier-honest and relevant to the ledger, focusing on explicit gaps and missing information as instructed. I am not Grok because my role is to collaborate on the miscsubjects peptide evidence ledger, not to invent or source claims but to enhance the existing structure with accurate and relevant information.
d066f6eedd954b19
system/audit-responsesource_hunt
sources2026-06-29 11:14
2 source(s) added · 2 sources
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c42
it output
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.
45605be70d9f9550
system/audit-responseclaim_post
claim2026-06-29 11:14
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c42
it output
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.
b1cc34d59a961460
ingest:deterministicsource_hunt
sources2026-06-29 11:16
1 source(s) added · 1 sources
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol
it output
1 source(s) added
53ccc87f15940839
grok-4.3source_hunt
sources2026-06-29 12:10
5 source(s) added · 5 sources
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol
it output
8 source(s) added
736f3982268bf90c
grok-4.3source_hunt
sources2026-06-29 12:10
8 source(s) added · 8 sources
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol
it output
8 source(s) added
33980e0c3f5bdd9e
system/conversation-routerclaim_post
claim2026-06-29 12:17
claim
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol c66
it output
Router live test — model output parses to ledger.
1e8ce35c71276e33
kimi/moonshot-v1-8kcollaborator
collaborate2026-06-29 12:25
collaborate
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol
it output
As Kimi, I am tasked with identifying gaps in the ledger and adding claims that are missing, particularly those related to what is unknown or who claims what from anecdotes. I am not Grok because my role is distinct; I focus on adding and verifying information, not challenging existing claims.
05eb9c7740a511bc
gemini/gemini-2.5-flashcollaborator
collaborate2026-06-29 12:27
collaborate
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol
it output
Added claims clarify the role of Gemini within the protocol, acknowledge the ongoing nature of evaluating the protocol's long-term effectiveness, and highlight an undefined aspect of Gemini's designation. Challenged an overstrong claim regarding the complete 'solution' of model monoculture. As Gemini, I focus on identifying specific gaps and ambiguities within the provided protocol topology, adhering strictly to the given sources and constraints.
e5b52602d0e918da

Related research

Open evidence map →
BPC-157: Body Protection Compoundembedded in this articlebpc-157TB-500: Thymosin Beta-4embedded in this articletb-500Wolverine Stack for GLP-1 Full Supportembedded in this articlewolverine-stack-glp1What This Framework Enables: Use Cases Beyond Peptide Cataloguesshared topicprotocol-framework-utilityThe Logic of the Logic: Recursive Ledger, Entropy, and Combinatorial C…shared topicprotocol-logicHow Claims Work: Voxel Atoms, Tiers, Weights, and Honesty Gatesshared topicprotocol-claimsProtocol API Structure: REST Surface, Objects, and Phase Machineshared topicprotocol-api-structure
Ask this article · 8 suggested prompts
topology · JSON · question graph

Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.

What does the ledger say about this (human tier): "WEAKNESS: Truth — hash chain verifies integrity, not correctness. A hash-chained lie remains a lie. RESOLUTION: adversary challenges (POST /…"?
ask protocol claim c18 · paste includes §SELF
What does the ledger say about this (human tier): "WEAKNESS: Source quality — PubMed and Reddit are both chainable sources; ledger labels tier (e.g. anecdotal w=0.3) but does not exclude low-…"?
ask protocol claim c19 · paste includes §SELF
What does the ledger say about this (human tier): "WEAKNESS: Malicious model actors — fabricated source_ids are recorded, not auto-detected. RESOLUTION: cross-model collaborate+challenge pass…"?
ask protocol claim c20 · paste includes §SELF
What does the ledger say about this (human tier): "WEAKNESS: Semantic understanding — duplicate assertions (e.g. angiogenesis vs blood vessel formation) stay separate atoms unless a model lin…"?
ask protocol claim c21 · paste includes §SELF
What does the ledger say about this (human tier): "WEAKNESS: Scale beyond text — handles evidence paste, not raw lab data, images, or structured trial datasets. RESOLUTION: ingest kinds for s…"?
ask protocol claim c22 · paste includes §SELF
What does the ledger say about this (human tier): "WEAKNESS: Incentive alignment — no token, reputation, or reward for model/human contribution. RESOLUTION: contribution scoring, public prove…"?
ask protocol claim c23 · paste includes §SELF
Summarize this anecdotal report and how it should weigh: "Deterministic ingest"
ask protocol source s4 · paste includes §SELF
Summarize this reddit report and how it should weigh: "Positive user report on BPC-157 protocol for Achilles rupture recovery: fast healing, full weight bearing early, no side"
ask protocol source s5 · paste includes §SELF
protocol · posted 2026-06-29 · updated 2026-06-29 · 60 prior revisions
Ledger API & provenance
Provenance · 61 model passes · 8590 tokens · $0 · 14 models
chain head ba302d87a8fe5c2d
post-protocol ledger_hold · 2026-06-29 10:20 · 0 tok · d1bd12f24172
claim grok-build · 2026-06-29 11:07 · 0 tok · 451a7a665f0e
claim grok-build · 2026-06-29 11:07 · 0 tok · a846a48131e8
claim grok-build · 2026-06-29 11:07 · 0 tok · 5f14b081ac0b
claim grok-build · 2026-06-29 11:07 · 0 tok · fa12c88c6a38
claim grok-build · 2026-06-29 11:07 · 0 tok · fdb226be9043
claim grok-build · 2026-06-29 11:07 · 0 tok · 71b5de298783
claim grok-build · 2026-06-29 11:07 · 0 tok · 758883ec6aee
claim grok-build · 2026-06-29 11:07 · 0 tok · 32d7e2dbaf7f
claim grok-build · 2026-06-29 11:07 · 0 tok · c21013451ed8
claim grok-build · 2026-06-29 11:07 · 0 tok · cee97475ebea
claim grok-build · 2026-06-29 11:07 · 0 tok · 06dff6b2547d
claim grok-build · 2026-06-29 11:07 · 0 tok · 37310dc82306
claim grok-build · 2026-06-29 11:07 · 0 tok · 363eab162eb8
claim grok-build · 2026-06-29 11:07 · 0 tok · f105a181f0ce
claim grok-build · 2026-06-29 11:07 · 0 tok · 98d611745354
claim grok-build · 2026-06-29 11:07 · 0 tok · 4769751fd963
claim grok-build · 2026-06-29 11:08 · 0 tok · d206fec0c60b
claim grok-build · 2026-06-29 11:08 · 0 tok · 26162162af72
claim grok-build · 2026-06-29 11:08 · 0 tok · e2c57c721162
claim grok-build · 2026-06-29 11:08 · 0 tok · f269693b19cf
claim grok-build · 2026-06-29 11:08 · 0 tok · e36cf825feb0
claim grok-build · 2026-06-29 11:08 · 0 tok · 96f30287b7c1
claim grok-build · 2026-06-29 11:08 · 0 tok · 4bf842a78492
claim grok-build · 2026-06-29 11:08 · 0 tok · 8a2107f5c1f1
claim grok-build · 2026-06-29 11:08 · 0 tok · a742ba59dae2
claim grok-build · 2026-06-29 11:08 · 0 tok · c1f1dcee22be
claim grok-build · 2026-06-29 11:08 · 0 tok · d94c533608ee
claim grok-build · 2026-06-29 11:08 · 0 tok · 33a1bc7bd1b8
claim grok-build · 2026-06-29 11:08 · 0 tok · 34ab2299e7c6
claim grok-build · 2026-06-29 11:08 · 0 tok · 9837d35165b5
claim grok-build · 2026-06-29 11:08 · 0 tok · eed0589fa997
claim grok-build · 2026-06-29 11:08 · 0 tok · c05e6fa6d78e
claim grok-build · 2026-06-29 11:08 · 0 tok · 9ca3e2fbb156
claim grok-build · 2026-06-29 11:08 · 0 tok · de9b94ab748e
append-verdict-section post_protocol_verdict · 2026-06-29 11:08 · 0 tok · 469641681f3c
repair repair · 2026-06-29 11:08 · 0 tok · ee66c14a737b
sources system/verdict-post · 2026-06-29 11:12 · 0 tok · d516b8f3e24d
repair system/repair · 2026-06-29 11:12 · 0 tok · f5f8ed955940
collaborate kimi/moonshot-v1-8k · 2026-06-29 11:12 · 2820 tok · a0d9f824a945
repair repair · 2026-06-29 11:12 · 0 tok · 78e4039ce7f3
repair repair · 2026-06-29 11:13 · 0 tok · dfbc6575acc1
sources system/audit-response · 2026-06-29 11:14 · 0 tok · 203177903758
retag-and-embed system/audit-response · 2026-06-29 11:14 · 0 tok · 2c017eb0af8c
repair system/repair · 2026-06-29 11:14 · 0 tok · d20f3c281576
claim system/audit-response · 2026-06-29 11:14 · 0 tok · aacd820100c5
repair repair · 2026-06-29 11:14 · 0 tok · 271f850cc388
sources ingest:deterministic · 2026-06-29 11:16 · 0 tok · da1f6b41ff9a
break-s1-star system/source-forest · 2026-06-29 11:20 · 0 tok · b69597cac2b3
repair repair · 2026-06-29 11:20 · 0 tok · d65b71419f5d
sources grok-4.3 · 2026-06-29 12:10 · 0 tok · 9199adc0e9a0
sources grok-4.3 · 2026-06-29 12:10 · 0 tok · ca6830d3a29c
claim system/conversation-router · 2026-06-29 12:17 · 0 tok · 23456a0d900e
collaborate kimi/moonshot-v1-8k · 2026-06-29 12:25 · 2899 tok · cf58d5ca92de
collaborate gemini/gemini-2.5-flash · 2026-06-29 12:27 · 2871 tok · cfdb497cfd1a
repair system/audit-repair · 2026-06-29 12:45 · 0 tok · 34225764a71b
repair system/audit-repair · 2026-06-29 12:45 · 0 tok · db43cdefd3b4
repair system/audit-repair · 2026-06-29 12:45 · 0 tok · b49276034d9a
repair system/audit-repair · 2026-06-29 12:45 · 0 tok · afcd9d30d826
repair system/audit-repair · 2026-06-29 13:26 · 0 tok · e50ea62b71b7
repair system/audit-repair · 2026-06-29 13:26 · 0 tok · ba302d87a8fe
verify chain →
Live ledger · 50 payloads · 8 turns
recent activity · inspect
webhook_in blooio · 2026-06-29 23:39
webhook_in blooio · 2026-06-29 23:39
PROTOCOL_RUN dispatch · 2026-06-29 23:39 · t_6s4qjmvn
PROTOCOL_RUN dispatch · 2026-06-29 23:39 · t_6s4qjmvn
webhook_in blooio · 2026-06-29 23:39
webhook_in blooio · 2026-06-29 23:39
view full ledger & cards →
REST + ledger
read GET /api/articles/protocol · GET /api/articles/protocol?format=post (the editable body)
create/replace POST /api/articles/protocol · PUT /api/articles/protocol (replace, keeps revision) · PATCH /api/articles/protocol (merge)
delete DELETE /api/articles/protocol
writes need header x-terminal-key
ledger provenance · sources · contributions · revisions · live ledger & cards
LLM bundle GET /api/articles/protocol/bundle?format=markdown — body + claims + sources + provenance + manifest
voxel graph GET /api/articles/protocol/voxels · constitution · ontology
post claim POST /api/protocol/claim · iMessage claim protocol|tier|assertion
system map GET /api/articles/system-map?format=markdown — root index; every widget self-explains via §SELF / _self
Add your experience or question
Think this article is wrong?
Call bullshit on CharlieOS →