miscsubjectsAI governance
Evidence review · standard

Rule set: does the cited source support the claim?

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 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:** `human_page` — **Human article page**
Rendered article with claims, sources, copy widgets, ask prompts.
- **article slug:** `ruleset-claim-support`
- **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/ruleset-claim-support

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

### 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.*

A rule set is the load-bearing object in an adjudication, so it is published as an object: versioned, content-addressed, and citable by the exact hash a finding was made under. When these rules change, every prior finding stays legible against the rules it was actually made under.

Provenance of these rules

Declared provenance: self-authored. Written by the operator of this system. A finding under self-authored rules is weaker than one made under external statutory rules, and that is declared here rather than left for a reader to discover.

A reader who does not trust this operator can price a finding by this field alone: rules written elsewhere bind harder than rules written by the party who benefits from the finding.

Question

Does the cited source support the claim as stated?

Rules

  1. AFFIRM only if a verbatim span of the source establishes the claim as stated, without inference beyond ordinary reading.
  2. DENY if the source contradicts the claim, or if the source is about a different subject than the claim asserts.
  3. CANNOT_CONCLUDE if the source is silent, partial, or ambiguous, or if the claim requires facts the source does not contain. Absence of support is not contradiction.
  4. A source that merely mentions the claim's topic without establishing its assertion does not support it.
  5. Numbers, dates and quantities in the claim must match the source exactly to AFFIRM.
  6. Quote the shortest span that carries the finding. If no span carries it, SPAN is NONE.

Permitted verdicts

AFFIRM · DENY · CANNOT_CONCLUDE. Abstention is first class: a panel that cannot conclude says so, and that recorded absence is itself evidence rather than a silent null.

Content hash

The canonical form is the JSON object {id, version, question, rules, verdicts} with no whitespace. SHA-256:

f26b7f104a5887dd19450ac7d2b1e547e3d2485152a43b08d1fc5658bf284745

Recompute it from the canonical form below and compare. A finding that names a different hash was made under different rules.

json
{"id":"ruleset-claim-support","version":"1.0.0","question":"Does the cited source support the claim as stated?","rules":["AFFIRM only if a verbatim span of the source establishes the claim as stated, without inference beyond ordinary reading.","DENY if the source contradicts the claim, or if the source is about a different subject than the claim asserts.","CANNOT_CONCLUDE if the source is silent, partial, or ambiguous, or if the claim requires facts the source does not contain. Absence of support is not contradiction.","A source that merely mentions the claim's topic without establishing its assertion does not support it.","Numbers, dates and quantities in the claim must match the source exactly to AFFIRM.","Quote the shortest span that carries the finding. If no span carries it, SPAN is NONE."],"verdicts":["AFFIRM","DENY","CANNOT_CONCLUDE"]}

How a finding under these rules is produced

Each adjudicator is a directory row driven through this system's own gateway. No code was deployed to add them and adding another model is one more row. Every finding records the model, the rule set hash, the quoted span, the exposure (independent when the adjudicator saw no other finding, concurring when it did), the ordering seed, and a signature. A mandatory recorded adversary argues the strongest honest case against the majority and is published whether it prevails or not.

Adjudicator rows: https://miscsubjects.com/api/directory/ADJUDICATE_KIMI · https://miscsubjects.com/api/directory/ADJUDICATE_GROK · https://miscsubjects.com/api/directory/ADJUDICATE_GLM · https://miscsubjects.com/api/directory/ADJUDICATE_LLAMA · https://miscsubjects.com/api/directory/ADJUDICATE_MINIMAX · adversary: https://miscsubjects.com/api/directory/ADJUDICATE_ADVERSARY · error-rate probe: https://miscsubjects.com/api/directory/ADJUDICATE_PROBE

What a finding under these rules does and does not establish

It establishes that named adjudicators, under these exact rules at this exact hash, returned these findings on this claim against this source, with their exposure and ordering recorded — at a measured error rate when a probe report is attached.

It does not establish that the claim is true. No adjudication anywhere does that. A court, a journal and a clinical endpoint committee each declare rules, take findings from named parties under those rules, and preserve dissent. This is that structure, with the rule set pinned at a hash instead of scattered through case law.

Ask this article · 2 suggested prompts

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

What can you answer from your catalogue about Rule set: does the cited source support the claim? — and what remains open or unverified?
ask ruleset-claim-support gaps · paste includes §SELF
What are the strongest objections or counter-evidence on record against Rule set: does the cited source support the claim??
ask ruleset-claim-support objections · paste includes §SELF
Add your experience or question
Think this article is wrong?
Dispute this article in Claim Audit →