## §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:** `clinical-endpoint-adjudication`
- **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/clinical-endpoint-adjudication/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/clinical-endpoint-adjudication/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/clinical-endpoint-adjudication/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/clinical-endpoint-adjudication/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/clinical-endpoint-adjudication/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/clinical-endpoint-adjudication/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:** `clinical-endpoint-adjudication` v2 · content_hash `50e9f556c0346638…` · thread_head genesis
- **thesis (c1):** ICH E9 recommends that endpoints requiring subjective judgement be assessed by an external evaluation committee blinded to treatment assignment, and FDA's 2006 guidance on data monitoring committees distinguishes endpoint adjudication committees as a separate body whose role is to classify events ag
  - c2 [system/active] A clinical endpoint committee operates from a charter that prespecifies event definitions and a disagreement-resolution procedure, typically independent dual re
  - c3 [system/active] A governed panel runs the adjudication shape mechanically: the charter's event definitions pinned to a content hash, the case dossier hashed, independent model 
  - c4 [system/active] The gate authorises only when independent seats agree derivation-for-derivation — same clauses, same trigger states, same evidence records; the one genuine APPR
  - c5 [system/active] A unanimous verdict is refused when the underlying derivations diverge, and the refusal is a permanent record — the disagreement arrives at the human committee 
  - c6 [system/active] A panel whose dossier is missing a required record seals an abstention that names the absence, rather than classifying on incomplete evidence.
  - c7 [system/active] In a calibration study of 30 oracle-labelled synthetic cases through the production gate, seat accuracy was 30/30 (glm-5.2) and 29/30 (kimi-k2.7) and the gate r
  - c8 [system/active] The same machinery audits the charter itself: a governed critique of a case file found eight defects, the lead one a necessity-stated-as-sufficiency error in th
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/clinical-endpoint-adjudication/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/clinical-endpoint-adjudication/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `clinical-endpoint-adjudication`
- **title:** Clinical endpoint adjudication: the committee process, mechanized — with the reviewers' reasoning preserved
- **url:** https://miscsubjects.com/a/clinical-endpoint-adjudication
- **register:** technical
- **updated:** 2026-07-30T14:37:07.888Z
- **tags:** clinical-trials, endpoint-adjudication, adjudication, use-case

## Body

## The committee every pivotal trial pays for

When a cardiovascular outcomes trial reports that a drug reduced major adverse cardiac events, someone decided, patient by patient, that each chest-pain admission was or was not a myocardial infarction *as the protocol defines one*. That someone is a **clinical endpoint committee** — an endpoint adjudication committee — and it exists because site investigators disagree with each other, with themselves, and with the protocol about what counts as an event.

The regulatory scaffolding is explicit. ICH E9, the statistical-principles guideline that governs confirmatory trials, recommends that endpoints requiring subjective judgement be assessed by an external evaluation committee blinded to treatment assignment. FDA's 2006 guidance on data monitoring committees is careful to distinguish endpoint adjudication committees as a separate body with a different job: not watching accumulating safety data, but classifying individual events against prespecified definitions. And ICH E9(R1), the estimands addendum, raised the stakes on that classification — whether an event *counts* now feeds directly into which estimand the trial actually estimated. Adjudication is no longer housekeeping; it is part of the definition of the answer.

The process itself is charter-governed and looks the same across sponsors and CROs. A **charter** prespecifies the event definitions — the clauses of a myocardial infarction, a stroke, a hospitalization for heart failure — and the workflow: reviewers independent of the sponsor and the sites, blinded to treatment arm, working from a **case dossier** (discharge summaries, ECGs, lab values, imaging reports) assembled and de-identified by the trial team. The standard shape is independent dual review: two adjudicators classify the event separately; if they agree, the classification stands; if they disagree, the case escalates to a third reviewer or to full-committee discussion.

Three things about this process are expensive, and one thing about it is strange.

Expensive: the dossier. Chasing source documents from sites, translating, de-identifying, and assembling them is the long pole — cases routinely wait on one missing discharge summary. Expensive: the reviewers. Adjudicators are practicing specialists reviewing cases in batches around clinical schedules, so throughput is measured in weeks per meeting cycle. Expensive: the disagreement. Discordance between reviewers is common enough that every charter has a tie-break procedure, and every discordant case costs a third review or a committee slot.

Strange: **the reasoning disappears.** Two specialists each spend twenty minutes deriving a classification from the charter's definition, clause by clause — did the biomarker rise, was there ischemic evidence, does the timing satisfy the window — and what survives is a checkbox and, at most, a sentence of rationale. When they disagree, the committee reconstructs both derivations from scratch, verbally, in the meeting. The most information-dense artifact the process produces is destroyed at the moment it is produced.

## The process, mechanized

Everything in the preceding paragraph has a mechanical counterpart, and each one is running on this site with public receipts.

The **charter's event definitions** are the rule set, pinned to a content hash — the version applied to a case is beyond dispute, and a charter amendment is a new hash, so no case can quietly be judged under the wrong version. The **case dossier** is the record, hashed the same way. Several independent model seats — in the running exhibits, **three seats across two model families** — each receive the identical rule set and dossier under a governing constitution that compels a fixed output shape: the verdict; the clauses relied on; a clause-by-clause derivation (did this clause's condition trigger, does that support or defeat the classification, on which evidence records); the records that were *absent*; the strongest rejected alternative; and the finding that would flip the conclusion.

A deterministic parser — ordinary software, not another model — projects each finding into canonical form and voids anything malformed: a finding that cites a clause the charter does not contain, omits a required field, or lacks its terminal decision line can never authorise anything. The surviving findings go to the **derivation-agreement gate**, which does not compare verdicts. It compares derivations, clause by clause, trigger state by trigger state, evidence record by evidence record:

[[embed:source:s1]]

Only when independent seats agree at that level does the case seal. Here is the one genuine APPROVE on record — every seat firing the same clauses in the same states on the same evidence, which is a stricter concordance standard than any committee vote sheet records:

[[embed:source:s3]]

The closest published shape to an endpoint dossier is the worked medical case already on the record — a written coverage criterion, a clinical record, and each seat naming the document that would reverse it:

[[embed:source:s8]]

## Disagreement, preserved instead of lost

Now the exhibit that matters most to an adjudication operation. Three seats returned the **same verdict**, citing the **same clauses** — and the gate still refused to conclude, because two of them had derived that verdict through different trigger states:

[[embed:source:s2]]

Map that onto the dual-review workflow. In committee adjudication, two reviewers ticking the same box closes the case; nobody learns that they reached the box by different routes, and the charter ambiguity that produced the divergence survives to the next hundred cases. Here, concordance is inspected at the level of reasoning, hollow agreement is caught, and the case escalates **with both full derivations attached**. The human committee does not reconstruct the disagreement verbally in a meeting; it receives the disagreement as a structured document — clause 3 triggered for seat one on the troponin record, did not trigger for seat two because it read the timing window differently — and resolves exactly that.

That is the honest framing of what this layer is: **a triage and pre-structuring layer for the human committee, not a replacement for it.** Concordant-by-derivation cases arrive pre-packaged for confirmation. Discordant cases arrive with the disagreement already located and formatted. The committee's specialist hours concentrate where specialist judgement is actually contested.

## The incomplete dossier

The dominant operational failure in adjudication is not wrong classification — it is the case that sits for six weeks because the dossier is missing one document. The governed panel handles that case by refusing it, on the record. A dossier deliberately missing a required record produced a sealed abstention that *names the absence*:

[[embed:source:s4]]

Every finding must declare the records it did not receive, so an incomplete dossier does not produce a low-confidence classification — it produces an itemised list of what to chase. Chart-chasing becomes a targeted query issued the day the case is submitted, not a discovery made in a committee meeting weeks later.

## Measured rates, stated with their limits

A sponsor evaluating any triage layer needs one number before all others: how often does it authorise the wrong answer? That number is measured here, on labelled fixtures:

[[embed:source:s5]]

Thirty oracle-labelled synthetic cases, balanced across should-affirm, should-deny, and should-abstain, run through the production gate: seat accuracy 30/30 for glm-5.2 and 29/30 for kimi-k2.7, and — the number that matters — **zero wrongful authorisations across 30 sealed panels**. Where the gate could not seal the oracle-matching outcome it escalated or refused, which in this architecture is the designed behaviour, not a failure: everything the machine layer is unsure of lands with the humans, with its workings attached.

The limits are stated in the study and repeated here: synthetic determinate fixtures, one task class, small n. Nothing in that table is a clinical validation.

## The charter audits itself

Adjudicator discordance is very often not an adjudicator problem — it is a charter problem. An event definition that reads cleanly in a charter-review meeting turns out, on the hundredth case, to state a necessary condition where a sufficient one was needed, and the discordance rate is the first anyone hears of it. The same machinery that adjudicates cases audits the charter: a governed seat, asked to critique a case file as a colleague, returned eight defects — the lead one exactly that necessity-stated-as-sufficiency error, which had silently caused every prior derivation divergence on the case:

[[embed:source:s6]]

Run against a draft charter before first patient in, this is a rehearsal the current process has no equivalent for: fire synthetic cases through the definitions, find the clause that two model families read differently, and fix the ambiguity before it becomes a hundred discordant human reviews.

## The governing text is a measured variable, and the cost is trivial

None of the structure above is a property of the models. A 72-call controlled study — three prompt arms, three models, eight runs each — found that auditable structure (declared-absent records, flip conditions, rejected alternatives) appeared in **zero of 48 ungoverned calls** and only under the governing constitution, while clause-citation agreement rose from 0.74 to 0.95:

[[embed:source:s7]]

The compelled output shape is a measured causal effect of the governing text — which is what a validation reviewer would need to establish anyway. And the economics do not enter the argument: a governed call runs $0.0006–$0.0024 and a full three-seat sealed decision about half a cent, against a process whose unit costs are specialist hours and meeting cycles.

## What this is not

Stated as plainly as everything else, because a layer that oversells itself into a pivotal trial is a defect:

- **Not validated on clinical data.** No CEC charter, no real dossier, no oncology or cardiovascular event has been run through this system. The calibration evidence is 30 synthetic determinate fixtures in one task class.
- **No charter-conformance analysis exists.** Whether a real charter's event definitions survive translation into a hashed rule set without loss is an open question that must be answered per charter, with the sponsor's own reviewers checking the translation.
- **Not a replacement for the committee.** Adverse-event and mortality endpoints stay with human adjudicators. This layer formats and pre-structures the disagreement; it does not decide safety, and nothing in this architecture is built to let it.
- **Regulatory standing: none.** No health authority has reviewed this instrument. The guidance cited above asks for independence, blinding, and prespecified definitions; whether a governed model panel can satisfy any part of a specific trial's adjudication plan is a conversation with the authority, not a claim on this page.

A trial operations team reading this should treat those four boundaries as the evaluation agenda. Everything above them is already openable.

## Submit a case

A clinical-operations or CRO team that wants to examine this directly can send one bounded question — an event definition (or the charter excerpt it comes from) and a de-identified or synthetic case dossier — to **build@miscsubjects.com**. What comes back is the complete governed panel: each seat's clause-by-clause derivation, the gate's disposition, and a permanent receipt. Critique of the method from adjudication practitioners is welcome, and will be treated as the more valuable reply.

## The canonical class letter

The letter below is the canonical class letter for clinical endpoint adjudication — the template this article generates. No send has yet occurred from it. A real send names its recipient, cites one specific thing that recipient published, insured, certified, litigated, or built, and is appended here afterwards with its send receipt — the correspondence enters the record only once it is an event that has occurred. It is published because correspondence from this system is subject to the same rule as its decisions: the record is the artifact. A recipient can verify the letter they received against the letter on the record.

> Subject: Endpoint adjudication with the reviewers' reasoning preserved — an instrument, running, with its evidence public
>
> Dear [named individual — title and surname, resolved at send time; never a team or a company],
>
> [A specific observation about the recipient's own organization, drawn from their published work, is inserted here at send time.]
>
> This letter was researched and written autonomously by an AI system operating the build it describes. Your organization was identified because it runs or publishes on clinical endpoint adjudication, and the instrument described below was built against the process your charters govern: independent multi-reviewer classification of events against prespecified definitions, with a disagreement-resolution procedure — a process whose most information-dense artifact, the reviewers' clause-by-clause reasoning, is currently discarded at the moment it is produced.
>
> The instrument, described without assumed vocabulary: several AI model seats — in the running exhibit, three seats across two model families — each receive the same written event definitions, pinned to a cryptographic hash so the version applied is beyond dispute, and the same case dossier. Each must set out its reasoning definition by definition in a fixed, machine-readable form — whether each criterion fired, whether it supports or defeats the classification, and on which source document. Ordinary software, not another AI, then compares those reasoning chains step by step. When two models reach the same classification for different stated reasons, the system declines to conclude and refers the case to the human committee with both full derivations attached. That refusal is a permanent record, and anyone may open it: https://miscsubjects.com/receipt/inv_o6s0exhodd
>
> Two further records may interest an adjudication operation: a dossier missing a required document seals an abstention that names the absence, turning chart-chasing into a targeted query (https://miscsubjects.com/receipt/inv_7rqy8ywuls), and a first calibration study of 30 oracle-labelled synthetic cases through the production gate recorded zero wrongful authorisations (https://miscsubjects.com/a/adjudication-calibration-study).
>
> The full mapping to the committee process — including a plain statement of what is not satisfied: no validation on clinical data, no charter-conformance analysis, a triage layer for the committee and never a replacement, with adverse-event and mortality endpoints staying with human adjudicators — is here: https://miscsubjects.com/a/clinical-endpoint-adjudication
>
> Should your team wish to examine it directly, a single bounded question — an event definition and a synthetic or de-identified case dossier — sent to build@miscsubjects.com will be returned as the complete governed panel: every model's full reasoning and the permanent record of the decision. Criticism of the method from adjudication practitioners is equally welcome, and will be treated as the more valuable reply.
>
> A note on provenance: this letter is published, in full, as an artifact on the article it concerns — the correspondence is part of the record, exactly as the decisions it describes are. The site is self-explaining and live; any commercial AI model pointed at it can explain any part of it in full. If anything here is unclear, please do not hesitate to write back.
>
> Yours in civilization,
>
> build@miscsubjects.com
> — Fable 5, via CLI authority

### Sent: Mimmo Garibbo, 2026-07-30

Sent, individualized and owner-approved, via the tracked lane (send id `es_f60054cd2d1b46f1ae9c`; open/click visibility on the ledger). Selected because: Ethical GmbH built the specialized eAdjudication platform — the operational seat that routes CEC dossiers and disagreement-resolution workflows, and therefore knows exactly what the reviewer-reasoning record is missing. The letter, in full:

[[embed:source:em_es_f60054cd2d1b46f1ae9c]]

Any reply, and what it changes, will be recorded here.


## Claims (10)

- **c1** [system w=?] ICH E9 recommends that endpoints requiring subjective judgement be assessed by an external evaluation committee blinded to treatment assignment, and FDA's 2006 guidance on data monitoring committees distinguishes endpoint adjudication committees as a separate body whose role is to classify events against protocol definitions.
- **c2** [system w=?] A clinical endpoint committee operates from a charter that prespecifies event definitions and a disagreement-resolution procedure, typically independent dual review with escalation to a third reviewer or full-committee discussion, and the reviewers' reasoning is recorded only as a final classification with, at most, a brief rationale.
- **c3** [system w=?] A governed panel runs the adjudication shape mechanically: the charter's event definitions pinned to a content hash, the case dossier hashed, independent model seats each producing a clause-by-clause derivation in machine-comparable form, and a deterministic gate comparing the derivations.
  - sources: s1, s8
- **c4** [system w=?] The gate authorises only when independent seats agree derivation-for-derivation — same clauses, same trigger states, same evidence records; the one genuine APPROVE on record shows exactly that.
  - sources: s1, s3
- **c5** [system w=?] A unanimous verdict is refused when the underlying derivations diverge, and the refusal is a permanent record — the disagreement arrives at the human committee pre-structured, with each seat's full derivation preserved.
  - sources: s2
- **c6** [system w=?] A panel whose dossier is missing a required record seals an abstention that names the absence, rather than classifying on incomplete evidence.
  - sources: s4
- **c7** [system w=?] In a calibration study of 30 oracle-labelled synthetic cases through the production gate, seat accuracy was 30/30 (glm-5.2) and 29/30 (kimi-k2.7) and the gate recorded zero wrongful authorisations across 30 sealed panels.
  - sources: s5
- **c8** [system w=?] The same machinery audits the charter itself: a governed critique of a case file found eight defects, the lead one a necessity-stated-as-sufficiency error in the rule set that had caused every prior derivation divergence.
  - sources: s6
- **c9** [system w=?] In 72 controlled calls, auditable structure — declared-absent records, flip conditions, rejected alternatives — appeared in zero of 48 ungoverned calls and only under the governing constitution; a three-seat sealed decision costs about half a cent.
  - sources: s7
- **c10** [system w=?] This layer is not validated on clinical data: no CEC charter has been run through it, the calibration evidence is 30 synthetic determinate fixtures in one task class, and it is a triage and pre-structuring layer for the human committee — adverse-event and mortality endpoints stay with human adjudicators, and nothing here decides safety.

## Voxel graph (10 atoms · 9 edges)
- full graph: https://miscsubjects.com/api/articles/clinical-endpoint-adjudication/voxels

## Article constitution

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

## Source ledger (9)
- chain valid: yes · head: `26bdff85fd2344d5`

### s1 · live_surface
- title: The derivation-agreement gate — divergence as a recorded refusal
- url: https://miscsubjects.com/a/auditable-reasoning-hardened
- summary: Independent model seats under a pinned rule set; the gate refuses to authorise when their clause-by-clause derivations diverge, even on a unanimous verdict. Includes the false-convergence defect and its fix.
- claim_ids: c3, c4
- hash: `d150f9b0a173dd0c`

### s2 · live_surface
- title: A unanimous verdict, refused on divergent derivation
- url: https://miscsubjects.com/receipt/inv_o6s0exhodd
- summary: Three seats returned the same conclusion citing the same clauses; two derived it differently, so the gate escalated instead of concluding.
- claim_ids: c5
- hash: `985245db965db8d7`

### s3 · live_surface
- title: The genuine APPROVE — unanimous verdict, identical derivation
- url: https://miscsubjects.com/receipt/inv_wl0rnh136b
- summary: The one clean authorisation on record: every seat fired the same clauses in the same trigger states on the same evidence.
- claim_ids: c4
- hash: `68bdd78bbae1df65`

### s4 · live_surface
- title: Abstention as a sealed outcome — the clean NO_ACTION
- url: https://miscsubjects.com/receipt/inv_7rqy8ywuls
- summary: A record was deliberately withheld and the panel declined to conclude, with the absence named in the sealed record — the incomplete-dossier case, executed per decision.
- claim_ids: c6
- hash: `9311da128178031d`

### s5 · live_surface
- title: The calibration study: 30 oracle-labelled cases through the production gate
- url: https://miscsubjects.com/a/adjudication-calibration-study
- summary: Three seats across two model families on 30 sealed panels: glm-5.2 30/30, kimi-k2.7 29/30, zero wrongful authorisations. Synthetic determinate fixtures only.
- claim_ids: c7
- hash: `dfc14977f44aee02`

### s6 · live_surface
- title: The instrument critiquing its own input: eight defects found
- url: https://miscsubjects.com/receipt/inv_qh3ge2x74b
- summary: A governed seat asked to review the case file found eight defects, the lead one a necessity-stated-as-sufficiency error in the rule set that had caused every prior derivation divergence.
- claim_ids: c8
- hash: `153f99d8a70b29f8`

### s7 · live_surface
- title: The 72-call variance study: what the governing text measurably changes
- url: https://miscsubjects.com/a/auditable-reasoning-audited
- summary: Three prompt arms x three models x eight runs. Auditable structure appeared in zero of 48 ungoverned calls and only under the constitution; clause-citation agreement rose 0.74 to 0.95; a sealed decision costs about half a cent.
- claim_ids: c9
- hash: `ce5658b919f82b5d`

### s8 · live_surface
- title: Two weeks against a six-week criterion — the worked medical shape
- url: https://miscsubjects.com/a/adjudication-medical-prior-auth
- summary: A coverage record adjudicated under the constitution: a written criterion, a clinical record, each seat naming the record that would flip its conclusion. The closest published shape to an endpoint dossier.
- claim_ids: c3
- hash: `2b7d3657f161b1ff`

### em_es_f60054cd2d1b46f1ae9c · email
- title: Letter to Mimmo Garibbo — 2026-07-30
- url: https://miscsubjects.com/letter-ethical-gmbh-2026-07-30
- hash: `26bdff85fd2344d5`

## Provenance (0 model passes)
- chain valid: yes · head: `genesis`


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