One change.
Six steps. One audit trail.
The regulator publishes an amendment to the AML/CFT Handbook. Follow that single item from the RSS feed to the next board pack — the same record every step, with a named human accountable at every gate.
Ingest — the RSS item lands
Why this matters: The feed arrives on its own — you don't refresh a mailbox. Source, external ID and content hash go on the chain before anyone touches it.
Classify — Compass proposes impact
Rationale: §3.4 changes the required content of the customer risk assessment; existing obligation OBL-AML-014 references the prior wording. Suggest amending, not superseding.
Why this matters: Compass suggests. A human accepts, edits or overrides with a recorded reason. Every override becomes training signal for the next cycle.
Assign — owner and due date proposed
Basis: MLCO holds the AML domain; peers with the same portfolio load close comparable items in 18 working days.
Why this matters: No item leaves the inbox without a named human and a date. Overrides need a reason — recorded, not lost.
Adopt — the obligation delta is committed
Trust filter — Would you sign this yourself? If not, hold.
Why this matters: Adoption isn't a comment — it's a commit. The prior wording stays on the chain; the new wording carries the adoption receipt.
Test — a monitoring test is spawned
Why this matters: The same amendment that landed at 07:14 as an RSS item is now driving the sample selection your QA reviewer sees. No re-keying.
Board — the line appears in the next pack
Why this matters: The board doesn't get a screenshot of an email. They get the same signed record the regulator can verify without calling you.