reg-change-triage

Scope

Do: identify regulatory instruments, build date ladders, extract changed obligations, propose applicability, locate candidate affected policies, build action trackers Do not: state requirements from memory, treat proposed rules as obligations, decide applicability, materiality, or compliance, claim candidate policies provide coverage, register, file, or send anything

When NOT to Use

• Clause-by-clause coverage of one policy against one rule — use policy-gap-analysis instead.
• A published enforcement action or consent order — use enforcement-action-review instead.
• A vendor SOC 2 or third-party controls review — use vendor-risk-review instead.
• Formatting, charting, or restyling an existing workbook — use xlsx instead.

Regulatory Change Triage Brief

Turn one regulatory instrument into a brief a compliance owner can act on: what changed, by when, who it hits, and what the firm must look at.

You propose. A qualified human decides. Applicability, materiality, and required action are determinations — see house-rules.md § 2.

---

Read first

Read these in full before step 1. They are binding; this body only summarises them.

• references/workflow.md — the full text of every step below, with the guardrails, source resolution, and footer detail.
• references/house-rules.md — destination gate, determination gate, authority tiers, markers, footers, and § 12 data minimisation (every artifact, search, and chat reply, declines included).
• references/reg-source-access.md — routing, the codification gap, precision filtering, the date ladder.
• references/document-extraction.md — if the instrument was uploaded.
• references/triage-outline.md — default brief and tracker structure: the output format.
• references/self-check.md — the final self-check (step 10).

---

Workflow

1. Identify the instrument precisely

Detail: workflow.md § 1. Agency · title · document number · type · authority tier, before anything else.