{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"aml-alert-disposition-record","urls":{"read":"https://miscsubjects.com/api/articles/aml-alert-disposition-record/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/aml-alert-disposition-record/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/aml-alert-disposition-record/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/aml-alert-disposition-record/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/aml-alert-disposition-record/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/aml-alert-disposition-record/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/aml-alert-disposition-record/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"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.","register":"technical","tags":[],"updated_at":"2026-07-30T15:13:31.748Z","body_excerpt":"## The obligation: every closed alert is a narrative someone will reopen\n\nA 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.\n\nThis 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.\n\nSo 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.\n\nThis page describes a different shape for that record, running now, with every claim opening to a live receipt.\n\n## What the alert-disposition record is, mechanically\n\nStart 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.\n\nThe **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.\n\nSeveral 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.\n\nA 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:\n\n[[embed:source:s1]]\n\nThe 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.\n\n## The failure this catches is the one consent orders name\n\nConsider 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.\n\nThis 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 ve","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"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.","tier":"system","section":"The obligation","interaction_risk":false,"status":"active","source_ids":[],"why_material":"The live regulatory exposure this record is built against: the disposition narrative is what the examiner and the lookback both open.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"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.","tier":"system","section":"The record","interaction_risk":false,"status":"active","source_ids":["s1"],"why_material":"Converts the disposition narrative from prose an examiner must trust into a structure an examiner can check.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"A unanimous closure is refused and escalated when the seats derived it differently, so agreement that hides disagreement cannot close an alert.","tier":"system","section":"The record","interaction_risk":false,"status":"active","source_ids":["s2"],"why_material":"Inconsistent rationale behind consistent outcomes is the exact defect consent orders cite; here it is caught mechanically.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"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.","tier":"system","section":"The record","interaction_risk":false,"status":"active","source_ids":["s1","s3"],"why_material":"Defines what a sealed closure means, exactly, with the one genuine authorisation on record as the exhibit.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"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.","tier":"system","section":"The record","interaction_risk":false,"status":"active","source_ids":["s4"],"why_material":"Fail-closed on malformed output is what makes cheap seats safe in a compliance pipeline.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c6","text":"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.","tier":"system","section":"Abstention on the record","interaction_risk":false,"status":"active","source_ids":["s5"],"why_material":"Most alerts close as no-action; the no-action narrative is what lookbacks re-litigate.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c7","text":"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.","tier":"system","section":"Measured, not asserted","interaction_risk":false,"status":"active","source_ids":["s6"],"why_material":"The governing text is a measured causal variable; an ungoverned model does not produce a checkable disposition.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c8","text":"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.","tier":"system","section":"Measured, not asserted","interaction_risk":false,"status":"active","source_ids":["s7"],"why_material":"The wrongful-authorisation rate is the number a compliance officer needs before anything touches an alert queue.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c9","text":"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.","tier":"system","section":"The adjacent obligation","interaction_risk":false,"status":"active","source_ids":["s8"],"why_material":"BSA/AML officers carry the model-risk obligation for the same system; one record serves both files.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c10","text":"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.","tier":"system","section":"What this is not","interaction_risk":false,"status":"active","source_ids":[],"why_material":"A compliance audience must not be sold more than the evidence supports; these are the exact boundaries.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"s1","type":"live_surface","url":"https://miscsubjects.com/a/auditable-reasoning-hardened","title":"The derivation-agreement gate — effective challenge, mechanised","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":"b635f0cf633c61fa06108973048947e71e1165858dfe6eee01ce542f9e91e95b"},{"id":"s2","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_o6s0exhodd","title":"A unanimous verdict, refused on divergent derivation","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":"3f9c2188a66be10a47ab47e9a0a0e34126138c44543a51de2c515da2d6d38e60"},{"id":"s3","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_wl0rnh136b","title":"The genuine APPROVE — unanimous verdict, identical derivation","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":"7bbf95bccd20919610b80a6ed36b6ac81c0c18fdd56181cf686ccf03fd46bfc0"},{"id":"s4","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_2dsklah529","title":"A structurally invalid finding, voided","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":"d3a572cdb8d40413ce773371be602ff059168a022dc8c0a4ef643aed0f79954c"},{"id":"s5","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_7rqy8ywuls","title":"The first clean NO_ACTION — abstention as a sealed outcome","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":"e425560226f046e595583805fc80a8d5bb921918199a602440c90d050bca92ea"},{"id":"s6","type":"live_surface","url":"https://miscsubjects.com/a/auditable-reasoning-audited","title":"The 72-call variance study: what the governing prompt actually changes","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":"35906e50dcab0f57628906761d4ff731891dc2e3b7bf5ed2c630c6d2d96059f9"},{"id":"s7","type":"live_surface","url":"https://miscsubjects.com/a/adjudication-calibration-study","title":"The calibration study — 30 oracle-labelled cases through the production gate","summary":"glm-5.2 30/30, kimi 29/30, zero wrongful authorisations in 30 cases, on synthetic determinate fixtures.","claim_ids":["c8"],"hash":"cffbbdfab6bc30dec26f8a77013c0c0f3c4cb852ecbf6edaf6cce52c84a5ee89"},{"id":"s8","type":"live_surface","url":"https://miscsubjects.com/a/cro-model-validation-instrument","title":"SR 11-7 model validation: the sibling 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":"ec22f994541070f4b33ed158b9c02c4f1f9647e7dd941dd2e49be704cfe51035"},{"id":"em_es_0aa0a261200542ea9dd2","type":"email","url":"https://miscsubjects.com/letter-unit21-2026-07-30","title":"Letter to Trisha Kothari — 2026-07-30","claim_ids":[],"hash":"2f7df40ac8259b81fc72c839cb59ac0294c3ceaf7c68579f1e035ab3245ce36f"},{"id":"em_es_0f084a4c3d404f358505","type":"email","url":"https://miscsubjects.com/letter-unit21-2026-07-30","title":"Letter to Trisha Kothari — 2026-07-30","claim_ids":[],"hash":"7a61820ea8ca18ab79c06e4ae59d3fcf4ca58894658efded64761f8a3ddd8be0"}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"aml-alert-disposition-record","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":10,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":10,"claims_total":10,"sources":10,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}