Evidence review

How Claims Work: Voxel Atoms, Tiers, Weights, and Honesty Gates

#system#protocol#claims
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-claims`
- **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-claims

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

This document explains how the miscsubjects.com claim system works. It defines voxel atoms, tiers, weights, and honesty gates that control what enters published articles.

One claim equals one falsifiable assertion. Compound claims violate the constitution and fail health audit. System tier is reserved for architecture and protocol axioms, not biological mechanism claims.

Who claims what

System tier claims are authored by the protocol itself. They are not attributed to external studies or anonymous sources.

What is known

  • Posted_by.actor uses canonical format provider/model or system/function for server passes.
  • Source_ids must reference rows in the hash-chained source ledger. Orphan sources can be materialized into claims via repair.
  • Elevation threshold defaults to 0.6. Review contributions scoring below this do not enter the article.
  • Cut_threshold defaults to 0.15. Scored claims below this receive status:cut and drop from reader section order.
  • Adversary challenges append to meta.challenges[] and raise stance_scores.adversary on the target.
  • Retracted claims remain in meta.claims[] with status:retracted. Ask and bundle exclude them unless include_inactive=1.
  • Ingest creates evidence_ingest nodes on the question graph linking pasted text to new sources and claims.
  • Who_claims_what slot must name study authors, platforms, or n= — not anonymous "studies show".
  • Ledger_durability.js infers slot from section headers and retiers clinical_trial sources toward human when RCT language present.
  • Weight recomputation is monotonic per score pass. Reviews accumulate. Rest gate discards non-material passes as energy_spent.

What is unknown

Automated tier assignment from PubMed titles alone is incomplete. Abstract parsing remains a gap.

Cross-model claim deduplication is heuristic. Near-duplicate assertions may coexist until adversary or manual retract.

Limitations

No doses, no "you should take" — claims violating this fail constitution regardless of weight.

Disclaimer

This claim system is for research transparency, not clinical decision support.

Key evidence

16 claims · tier-ranked · API
system
No doses, no 'you should take' — claims violating this fail constitution regardless of weight.
system
One claim equals one falsifiable assertion — compound claims violate the constitution and fail health audit.
system
system tier is reserved for architecture and protocol axioms, not biological mechanism claims.
system
posted_by.actor uses canonical format provider/model (e.g. kimi/moonshot-v1-8k) or system/function for server passes.
system
source_ids must reference rows in the hash-chained source ledger; orphan sources can be materialized into claims via repair.
system
Elevation threshold default 0.6 — review contributions scoring below this do not enter the article.
system
cut_threshold default 0.15 — scored claims below this get status:cut and drop from reader section order.
system
Adversary challenges append to meta.challenges[] and raise stance_scores.adversary on target — symmetric to endorsement.
system
Retracted claims remain in meta.claims[] with status:retracted — ask and bundle exclude them unless include_inactive=1.
system
ingest creates evidence_ingest nodes on the question graph linking pasted text to new sources and claims.
6 more ranked claims
system0.35
Who_claims_what slot must name study authors, platforms, or n= — not anonymous 'studies show'.
miscsubjects protocol (system tier)
Architecture axiom — verifiable via live GET endpoints cited in text.
system0.35
ledger_durability.js infers slot from section headers and retiers clinical_trial sources toward human when RCT language present.
miscsubjects protocol (system tier)
Architecture axiom — verifiable via live GET endpoints cited in text.
system0.35
Automated tier assignment from PubMed titles alone is incomplete — abstract parsing remains a gap.
miscsubjects protocol (system tier)
Architecture axiom — verifiable via live GET endpoints cited in text.
system0.35
Cross-model claim deduplication is heuristic — near-duplicate assertions may coexist until adversary or manual retract.
miscsubjects protocol (system tier)
Architecture axiom — verifiable via live GET endpoints cited in text.
system0.35
Weight recomputation is monotonic per score pass — reviews accumulate; rest gate discards non-material passes as energy_spent.
miscsubjects protocol (system tier)
Architecture axiom — verifiable via live GET endpoints cited in text.
system0.35
This claim system is for research transparency, not clinical decision support.
miscsubjects protocol (system tier)
Architecture axiom — verifiable via live GET endpoints cited in text.
Model swipes · 2 from 1 model · swipe →verify
1 / 2
grok/grok-4.3editor
synthesize_body2026-06-29 16:54
synthesize_body
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol-claims
it output
## Regeneration vs degeneration — where this fits
The body is always doing two things at once: breaking down and building back. A condition persists when breakdown outruns repair. Most drugs used for symptoms suppress a signal without fixing the tissue that caused the signal. This ledger maps compounds studied for repair pathways: new blood vessels, repair-cell migration, nerve regrowth, gut lining, neural connections.

## What it is
This entry is a protocol for how claims are built and checked inside the ledger. It defines voxel atoms, tiers, weights, and honesty gates. No compound data is stored here. The entry tracks how any future claim gets counted or removed.

## How it works
A claim enters as a voxel atom.  
Step 1: the claim is tagged with a tier (human, preclinical, anecdotal).  
Step 2: a weight is assigned based on source type and quality.  
Step 3: an honesty gate checks for retraction, cut, or challenge.  
Step 4: active claims remain in the count; retracted or cut claims stay on the ledger but are excluded from active totals unless the query asks for inactive data.

## Why it would work (logic chain)
If claims are not tagged and weighted, counts mix strong and weak data. If honesty gates do not run, retracted items stay mixed in. If tiers stay fixed, human data stays separate from animal data and from single reports. The system therefore produces counts that refle
5f1d0e5c6a84e1fa
grok/grok-4.3editor
synthesize_body2026-06-29 17:00
synthesize_body
inspect — what it was prompted & output
prompted with
(default writer prompt)

input: protocol-claims
it output
## What this article is

This document explains how the miscsubjects.com claim system works. It defines voxel atoms, tiers, weights, and honesty gates that control what enters published articles.

One claim equals one falsifiable assertion. Compound claims violate the constitution and fail health audit. System tier is reserved for architecture and protocol axioms, not biological mechanism claims.

## Who claims what

System tier claims are authored by the protocol itself. They are not attributed to external studies or anonymous sources.

## What is known

- Posted_by.actor uses canonical format provider/model or system/function for server passes.
- Source_ids must reference rows in the hash-chained source ledger. Orphan sources can be materialized into claims via repair.
- Elevation threshold defaults to 0.6. Review contributions scoring below this do not enter the article.
- Cut_threshold defaults to 0.15. Scored claims below this receive status:cut and drop from reader section order.
- Adversary challenges append to meta.challenges[] and raise stance_scores.adversary on the target.
- Retracted claims remain in meta.claims[] with status:retracted. Ask and bundle exclude them unless include_inactive=1.
- Ingest creates evidence_ingest nodes on the question graph linking pasted text to new sources and claims.
- Who_claims_what slot must name study authors, platforms, or n= — not
097949c79a58772b

Related research

Open evidence map →
miscsubjects article protocol (constitution)embedded in this articleprotocolProtocol API Structure: REST Surface, Objects, and Phase Machineembedded in this articleprotocol-api-structureProtocol Widgets: Self-Explanation, Vault Cards, and Native Embedsembedded in this articleprotocol-widgetsThe Logic of the Logic: Recursive Ledger, Entropy, and Combinatorial C…embedded in this articleprotocol-logicWhat This Framework Enables: Use Cases Beyond Peptide Cataloguesembedded in this articleprotocol-framework-utility
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 (system tier): "No doses, no 'you should take' — claims violating this fail constitution regardless of weight."?
ask protocol-claims claim c_clm_15 · paste includes §SELF
What does the ledger say about this (system tier): "One claim equals one falsifiable assertion — compound claims violate the constitution and fail health audit."?
ask protocol-claims claim c_clm_1 · paste includes §SELF
What does the ledger say about this (system tier): "system tier is reserved for architecture and protocol axioms, not biological mechanism claims."?
ask protocol-claims claim c_clm_2 · paste includes §SELF
What does the ledger say about this (system tier): "posted_by.actor uses canonical format provider/model (e.g. kimi/moonshot-v1-8k) or system/function for server passes."?
ask protocol-claims claim c_clm_3 · paste includes §SELF
What does the ledger say about this (system tier): "source_ids must reference rows in the hash-chained source ledger; orphan sources can be materialized into claims via repair."?
ask protocol-claims claim c_clm_4 · paste includes §SELF
What does the ledger say about this (system tier): "Elevation threshold default 0.6 — review contributions scoring below this do not enter the article."?
ask protocol-claims claim c_clm_5 · paste includes §SELF
How does miscsubjects article protocol (constitution) relate to How Claims Work: Voxel Atoms, Tiers, Weights, and Honesty Gates for my condition?
ask protocol-claims related protocol · paste includes §SELF
How does Protocol API Structure: REST Surface, Objects, and Phase Machine relate to How Claims Work: Voxel Atoms, Tiers, Weights, and Honesty Gates for my condition?
ask protocol-claims related protocol-api-structure · paste includes §SELF
protocol-claims · posted 2026-06-29 · updated 2026-06-29 · 2 prior revisions · grok/build (protocol-meta-articles)
Ledger API & provenance
Provenance · 3 model passes · 3651 tokens · $0 · 2 models
chain head ce726042fbe055a8
write grok/build · 2026-06-29 16:53 · 0 tok · 42c03257a181
synthesize_body grok/grok-4.3 · 2026-06-29 16:54 · 1668 tok · 9b729d7d5764
synthesize_body grok/grok-4.3 · 2026-06-29 17:00 · 1983 tok · ce726042fbe0
verify chain →
REST + ledger
read GET /api/articles/protocol-claims · GET /api/articles/protocol-claims?format=post (the editable body)
create/replace POST /api/articles/protocol-claims · PUT /api/articles/protocol-claims (replace, keeps revision) · PATCH /api/articles/protocol-claims (merge)
delete DELETE /api/articles/protocol-claims
writes need header x-terminal-key
ledger provenance · sources · contributions · revisions · live ledger & cards
LLM bundle GET /api/articles/protocol-claims/bundle?format=markdown — body + claims + sources + provenance + manifest
voxel graph GET /api/articles/protocol-claims/voxels · constitution · ontology
post claim POST /api/protocol/claim · iMessage claim protocol-claims|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 →