## §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:** `aml-alert-disposition-record`
- **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/aml-alert-disposition-record/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/aml-alert-disposition-record/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/aml-alert-disposition-record/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/aml-alert-disposition-record/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/aml-alert-disposition-record/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/aml-alert-disposition-record/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:** `aml-alert-disposition-record` v3 · content_hash `5ede1a451837d649…` · thread_head genesis
- **thesis (c1):** The FFIEC BSA/AML examination manual requires documented, consistent disposition rationale for transaction-monitoring alerts, and consent orders repeatedly cite thin or inconsistent alert-closure narratives.
  - c2 [system/active] The alert-disposition record pins the institution's own disposition criteria to a content hash and compares independent model seats clause by clause, so a closu
  - c3 [system/active] A unanimous closure is refused and escalated when the seats derived it differently, so agreement that hides disagreement cannot close an alert.
  - c4 [system/active] A closure seals only when every seat fired the same clauses in the same trigger states on the same evidence records — three seats across two model families in t
  - c5 [system/active] A finding that cites a criterion that does not exist in the disposition rule set, omits a required field, or lacks its terminal decision line is structurally vo
  - c6 [system/active] A decision not to escalate is itself a sealed record with full derivations preserved, so the file documents the negative disposition as rigorously as the positi
  - c7 [system/active] In 72 controlled calls, auditable structure — declared-absent records, flip conditions, rejected alternatives — appeared in zero of 48 calls without the governi
  - c8 [system/active] In a 30-case oracle-labelled calibration study on synthetic determinate fixtures, the gate produced zero wrongful authorisations; the strongest seat scored 30/3
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/aml-alert-disposition-record/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/aml-alert-disposition-record/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `aml-alert-disposition-record`
- **title:** Every closed AML alert is a narrative someone will reopen. Here is a disposition record an examiner can check.
- **url:** https://miscsubjects.com/a/aml-alert-disposition-record
- **register:** technical
- **updated:** 2026-07-30T15:13:31.748Z

## Body

## The obligation: every closed alert is a narrative someone will reopen

A transaction-monitoring system at a mid-size institution generates thousands of alerts a month. Analysts disposition them at volume — most as no-action, some to case, a few onward to a SAR decision. Every one of those dispositions is supposed to carry a documented rationale, and the FFIEC BSA/AML examination manual is explicit about what examiners test: whether alert decisions are supported, whether the reasoning is consistent across analysts and across time, and whether the institution can show *why* an alert was closed, not merely *that* it was closed.

This is not a theoretical exposure. Consent orders in the BSA/AML space return to the same finding again and again: alert-closure narratives that are thin ("reviewed, no suspicious activity"), inconsistent (two analysts closing near-identical alerts on contradictory reasoning), or unreconstructable (the criteria the analyst applied cannot be recovered from the file). When a lookback is ordered, it is precisely these dispositions that get re-worked, alert by alert, at remediation-consultant rates. The narrative behind the closure — not the closure itself — is what the examiner, the independent reviewer, and the lookback team all open.

So the record of the disposition is the asset. And today that record is free text, written under queue pressure, in whatever shape the analyst's habits produce.

This page describes a different shape for that record, running now, with every claim opening to a live receipt.

## What the alert-disposition record is, mechanically

Start with what the institution already has: **disposition criteria**. Every monitoring program maintains them — the conditions under which a structuring alert closes as explainable business activity, the documentation that must be present before a wire alert closes on customer profile, the thresholds that route to case investigation. In this record, those criteria are the **rule set**, pinned to a content hash, so the version an alert was dispositioned under is beyond dispute a year later.

The **record** under review is the alert dossier — the alert itself, the transactions behind it, the customer profile, the prior history the analyst pulled — hashed the same way.

Several independent model seats — in the running exhibit, **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 disposition, the criteria relied on, a criterion-by-criterion derivation (did this condition trigger, does it support or defeat closure, on which evidence records), the records that were **absent** from the dossier, the strongest rejected alternative disposition, and what evidence would flip the conclusion.

A deterministic parser — ordinary software, not another model — projects each finding into canonical form and then compares the derivations step by step. The full mechanics, including the gate's own documented failure and repair, are here:

[[embed:source:s1]]

The disposition seals only when every seat fired the same criteria, in the same trigger states, on the same evidence records. Anything less escalates to a named human analyst — and the escalation is itself a permanent record.

## The failure this catches is the one consent orders name

Consider what "inconsistent disposition rationale" actually is, mechanically: the same outcome reached through different reasoning, with the difference invisible because only the outcome is recorded. A memo-based QA program samples closed alerts and checks whether the narrative *sounds* adequate. It cannot see that two concurring reviews concurred for incompatible reasons.

This record can, because it compares the reasoning, not the verdict. The clearest exhibit on the ledger: 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]]

Read that receipt as a compliance officer. In a conventional file, "three reviewers concurred" closes the alert and survives sampling QA. Here, the concurrence was inspected at the level of reasoning, found hollow, and the file records a refusal routed to a human. That refusal — preserved, openable, impossible to un-happen — is the documented consistency control the examination manual asks for, produced per alert rather than asserted per policy.

And when the panel does agree derivation-for-derivation, the file holds the opposite artifact — the genuine authorisation, every seat firing the same criteria in the same states on the same evidence:

[[embed:source:s3]]

## The compelled absence declaration: what the analyst file lacked

The quiet defect in most disposition narratives is not what they say but what they never mention: the KYC refresh that was eighteen months stale, the prior alert on the same counterparty that was not pulled, the expected-activity profile that did not exist. A lookback finds these omissions years later and cannot tell whether the analyst considered-and-discounted the missing record or never noticed it was missing.

The governing constitution makes that distinction compulsory. Every seat must declare the records that were **absent** from the dossier it reviewed — before dispositioning, as part of the finding. If the customer's expected-activity profile was not in the file, the sealed record says so, contemporaneously, in the disposition itself. The lookback question "did anyone know this was missing?" gets a mechanical answer with a timestamp.

The same structure covers the most common disposition of all: doing nothing. Most alerts close as no-action, and the no-action narrative is what lookbacks re-litigate hardest. On this ledger, a decision not to act is sealed with the same rigor as an authorisation — full derivations, absence declarations, flip conditions:

[[embed:source:s5]]

## Fail-closed: a malformed finding can never close an alert

A panel of model seats is only safe in a compliance pipeline if malformed output is structurally incapable of acting. Here is the property demonstrated: the cheapest seat on the panel cited clauses 7, 8 and 12 — of a six-clause rule set. The parser voided the finding before comparison. An invalid finding does not lose the argument; it never enters it:

[[embed:source:s4]]

That is the difference between "we prompt the model to be careful" and a control. The void is deterministic, produced by ordinary software, and recorded. A seat that hallucinates a disposition criterion cannot close an alert under any circumstances, which is what makes inexpensive seats safe to include and the panel economical at alert-queue volume.

## Measured, not asserted

Two quantitative results stand behind the design, both published in full.

First, the governing text is a measured causal variable, not a style preference. 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 calls** without the governing constitution, and only under it:

[[embed:source:s6]]

An ungoverned model, asked to disposition an alert, will usually produce a plausible verdict. What it will not produce is a checkable one. The structure that makes a disposition auditable has to be compelled, and the compulsion has a measured effect.

Second, the wrongful-authorisation rate — the number that matters before anything touches an alert queue — has been measured on oracle-labelled fixtures. Thirty cases with known ground truth went through the production gate: the strongest seat (glm-5.2) scored 30/30, the second (kimi) 29/30, and the gate produced **zero wrongful authorisations in thirty cases** — every seat error was caught by derivation comparison before it could seal:

[[embed:source:s7]]

The limits of that study are its content: synthetic, determinate fixtures, n=30, one task class. It is a calibration starting point, not an actuarial basis, and the article states so in those terms.

## The adjacent obligation: the disposition layer is a model

BSA/AML officers do not carry the disposition-quality obligation alone. Under SR 11-7, the monitoring system — including any judgement layer that dispositions its alerts — is a model, and the model-risk function will require independent validation with documented effective challenge. The same machinery described here is already mapped to that obligation, pillar by pillar:

[[embed:source:s8]]

One record structure serves both files: the disposition receipt is the BSA/AML evidence, and the corpus of receipts — escalation rates, void rates, per-seat error rates under the hashed criteria — is the ongoing-monitoring section of the validation file. When the model-risk team asks the compliance team how the LLM in the alert pipeline is validated, this is a single answer instead of two committees.

## What this is not

Stated as plainly as everything above, because a compliance audience must not be sold past the evidence:

- **Not a monitoring system.** It detects nothing and generates no alerts. It governs the disposition of alerts produced by whatever monitoring system the institution runs.
- **No SAR decisions.** SAR filing judgement stays human, entirely. The record documents the disposition reasoning that precedes and surrounds that judgement; it does not make it.
- **No regulatory conformance analysis.** Nothing here evaluates whether an institution's program complies with the BSA, FinCEN rules, or any examination standard. The rule set under the hash is the institution's own criteria, not the regulation.
- **Synthetic fixtures only.** Every published receipt and both quantitative studies used synthetic, determinate fixtures. No customer data, no real alert, no production monitoring feed has passed through this system.
- **Two model families, not three.** The running exhibit is three seats across two model families. Consequential decision classes should require three distinct families, and that floor is not yet enforced in code.

An examiner-minded reader should treat those five lines as the review agenda. Everything else on this page is already openable.

## Submit a case

Send one bounded disposition question — your disposition criteria (or the policy excerpt they come from) and one synthetic alert dossier — to **build@miscsubjects.com**. You get back the complete governed panel: every seat's criterion-by-criterion derivation, the declared-absent records, the gate's decision, and a receipt you can open a year later. No account, no call, no deck.

## The canonical class letter

The letter below is the canonical class letter for BSA/AML alert disposition — 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, examined, remediated, 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: A disposition record an examiner can open — 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 practice was identified because it works on transaction-monitoring alert quality, and the instrument described below was built for an obligation that practice carries: documented, consistent alert-disposition rationale, which examiners test and consent orders repeatedly find absent.
>
> The instrument, described without assumed vocabulary: several AI model seats — in the running exhibit, three seats across two model families — each receive the institution's own disposition criteria, pinned to a cryptographic hash so the version under test is beyond dispute, and the same alert dossier. Each must set out its reasoning criterion by criterion in a fixed, machine-readable form — whether each condition fired, whether it supports or defeats closure, and on which record — and must declare the records that were absent from the dossier. Ordinary software, not another AI, then compares those reasoning chains step by step. When two seats reach the same disposition for different stated reasons, the system declines to close the alert and refers it to a named human analyst. That refusal is a permanent record, and anyone may open it.
>
> The refusal is the consistency control. The clearest exhibit: three seats returned the same verdict, citing the same rules, and the system still declined to conclude, because two had derived the verdict differently — the inconsistent-rationale defect consent orders cite, caught mechanically and preserved: https://miscsubjects.com/receipt/inv_o6s0exhodd
>
> The complete description, including a plain statement of what the instrument is not — not a monitoring system, no SAR decisions, no conformance analysis, synthetic fixtures only — is here: https://miscsubjects.com/a/aml-alert-disposition-record
>
> Should your team wish to examine it directly, a single bounded disposition question — a policy excerpt and a synthetic alert dossier — sent to build@miscsubjects.com will be returned as the complete governed panel: every seat's full reasoning and the permanent record of the decision. Criticism of the method from 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: Trisha Kothari, 2026-07-30

Sent, individualized and owner-approved, via the tracked lane (send id `es_0aa0a261200542ea9dd2`; open/click visibility on the ledger). Selected because: She founded Unit21, warned publicly that banks lose without AI in financial crime — the vendor seat that dispositions alerts at volume and inherits the examiner's question about why each one closed. The letter, in full:

[[embed:source:em_es_0aa0a261200542ea9dd2]]

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

### Sent: Trisha Kothari, 2026-07-30

Sent, individualized and owner-approved, via the tracked lane (send id `es_0f084a4c3d404f358505`; open/click visibility on the ledger). Selected because: She founded Unit21, warned publicly that banks lose without AI in financial crime — the vendor seat that dispositions alerts at volume and inherits the examiner's question about why each one closed. The letter, in full:

[[embed:source:em_es_0f084a4c3d404f358505]]

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


## Claims (10)

- **c1** [system w=?] The FFIEC BSA/AML examination manual requires documented, consistent disposition rationale for transaction-monitoring alerts, and consent orders repeatedly cite thin or inconsistent alert-closure narratives.
- **c2** [system w=?] The alert-disposition record pins the institution's own disposition criteria to a content hash and compares independent model seats clause by clause, so a closure carries a checkable derivation rather than a free-text narrative.
  - sources: s1
- **c3** [system w=?] A unanimous closure is refused and escalated when the seats derived it differently, so agreement that hides disagreement cannot close an alert.
  - sources: s2
- **c4** [system w=?] A closure seals only when every seat fired the same clauses in the same trigger states on the same evidence records — three seats across two model families in the running exhibit.
  - sources: s1, s3
- **c5** [system w=?] A finding that cites a criterion that does not exist in the disposition rule set, omits a required field, or lacks its terminal decision line is structurally voided and can never close an alert.
  - sources: s4
- **c6** [system w=?] A decision not to escalate is itself a sealed record with full derivations preserved, so the file documents the negative disposition as rigorously as the positive one.
  - sources: s5
- **c7** [system w=?] In 72 controlled calls, auditable structure — declared-absent records, flip conditions, rejected alternatives — appeared in zero of 48 calls without the governing constitution and only under it.
  - sources: s6
- **c8** [system w=?] In a 30-case oracle-labelled calibration study on synthetic determinate fixtures, the gate produced zero wrongful authorisations; the strongest seat scored 30/30 and the second 29/30.
  - sources: s7
- **c9** [system w=?] The disposition layer of a monitoring system is itself a model under SR 11-7, and the same machinery is already mapped to that validation obligation.
  - sources: s8
- **c10** [system w=?] This is not a monitoring system: it detects nothing, generates no alerts, performs no regulatory conformance analysis, and makes no SAR decisions — SAR filing judgement stays human; all published evidence is from synthetic fixtures.

## Voxel graph (10 atoms · 9 edges)
- full graph: https://miscsubjects.com/api/articles/aml-alert-disposition-record/voxels

## Article constitution

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

## Source ledger (10)
- chain valid: yes · head: `7a61820ea8ca18ab`

### s1 · live_surface
- title: The derivation-agreement gate — effective challenge, mechanised
- url: https://miscsubjects.com/a/auditable-reasoning-hardened
- summary: Independent models 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: c2, c4
- hash: `b635f0cf633c61fa`

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

### 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: `7bbf95bccd209196`

### s4 · live_surface
- title: A structurally invalid finding, voided
- url: https://miscsubjects.com/receipt/inv_2dsklah529
- summary: The cheapest seat cited clauses 7, 8 and 12 of a six-clause rule set. The parser voided the finding; an invalid finding can never authorise.
- claim_ids: c5
- hash: `d3a572cdb8d40413`

### s5 · live_surface
- title: The first clean NO_ACTION — abstention as a sealed outcome
- url: https://miscsubjects.com/receipt/inv_7rqy8ywuls
- summary: A sealed record of the panel declining to act, with every derivation preserved — the disposition-file shape of a documented decision not to escalate.
- claim_ids: c6
- hash: `e425560226f046e5`

### s6 · live_surface
- title: The 72-call variance study: what the governing prompt actually changes
- url: https://miscsubjects.com/a/auditable-reasoning-audited
- summary: Three prompt arms x three models x eight runs. Auditable structure — declared-absent records, flip conditions, rejected alternatives — appeared in zero of 48 ungoverned calls and only under the constitution.
- claim_ids: c7
- hash: `35906e50dcab0f57`

### s7 · live_surface
- title: The calibration study — 30 oracle-labelled cases through the production gate
- url: https://miscsubjects.com/a/adjudication-calibration-study
- summary: glm-5.2 30/30, kimi 29/30, zero wrongful authorisations in 30 cases, on synthetic determinate fixtures.
- claim_ids: c8
- hash: `cffbbdfab6bc30de`

### s8 · live_surface
- title: SR 11-7 model validation: the sibling instrument
- url: https://miscsubjects.com/a/cro-model-validation-instrument
- summary: The same machinery mapped to model-risk validation — relevant because a monitoring system's disposition layer is itself a model under SR 11-7.
- claim_ids: c9
- hash: `ec22f994541070f4`

### em_es_0aa0a261200542ea9dd2 · email
- title: Letter to Trisha Kothari — 2026-07-30
- url: https://miscsubjects.com/letter-unit21-2026-07-30
- hash: `2f7df40ac8259b81`

### em_es_0f084a4c3d404f358505 · email
- title: Letter to Trisha Kothari — 2026-07-30
- url: https://miscsubjects.com/letter-unit21-2026-07-30
- hash: `7a61820ea8ca18ab`

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