## §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:** `ruleset-claim-support`
- **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/ruleset-claim-support/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/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)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/ruleset-claim-support/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/ruleset-claim-support/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/ruleset-claim-support/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/ruleset-claim-support/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:** `ruleset-claim-support` v1 · content_hash `4c6b86c7d4846d64…` · thread_head genesis
- **thesis:** FLAGGED — this article's thesis does not reduce to one falsifiable root claim — audit finding, not fudged
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/ruleset-claim-support/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/ruleset-claim-support/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `ruleset-claim-support`
- **title:** Rule set: does the cited source support the claim?
- **url:** https://miscsubjects.com/a/ruleset-claim-support
- **register:** standard
- **updated:** 2026-07-30T00:29:39.571Z
- **tags:** ruleset, adjudication, evidence, self-authored

## Body

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.

## Claims (0)


## Voxel graph (0 atoms · 0 edges)
- full graph: https://miscsubjects.com/api/articles/ruleset-claim-support/voxels

## Article constitution

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

## Source ledger (0)
- chain valid: yes · head: `genesis`

## Provenance (1 model passes)
- chain valid: yes · head: `77ad1733ecba240e`

- publish ruleset · Fable 5 (Claude Code) · 2026-07-30T00:29 · hash `77ad1733ecba`

## Question graph
- questions: 0 · evidence ingests: 0

## 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/ruleset-claim-support/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/ruleset-claim-support/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"ruleset-claim-support","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest ruleset-claim-support|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim ruleset-claim-support|tier|assertion`
- **iMessage ask:** `ruleset-claim-support|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:** `ruleset-claim-support`
- **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/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)
- **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/ruleset-claim-support/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.*