Scope
Do: retrieve enforcement orders, quote admission posture, extract alleged conduct, cited rules, remedies, derive read-across themes, map candidate firm controls
Do not: restate allegations as fact, rely on an order's rule characterization, state the firm has a violation, deficiency, or compliance gap, infer root cause, file, send, or commit anything
When NOT to Use
- Researching a customer or counterparty — use
kyc-research-pack instead.
- Triaging a newly published rule — use
reg-change-triage instead.
- Formatting or restyling an existing document — use
docx instead.
Enforcement-Action Read-Across
What the regulator actually penalised, what it required, and where the firm should look.
Two directions of care. Allegations against the respondent are not facts about the
respondent. Exposure observations about the firm are not admissions by the firm. Both rules hold
at once — house-rules.md § 2 and § 6.
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 — retrieving the order and the rules it cites.
references/document-extraction.md — consent-order extraction, allegation vs finding.
references/readacross-outline.md — default memo and control-gap table: the output format.
references/self-check.md — the final self-check (step 8).
Workflow
1. Retrieve the order
Detail: workflow.md § 1. Connector → direct route → browser → ask for an upload →
NOT RETRIEVED. Establish agency · respondent · docket · date · type. A litigated decision holds
findings; a consent order usually holds allegations. Never treat them alike.
2. Establish the admission posture — before anything else
Detail: workflow.md § 2. Find and quote the admission language. It governs every sentence
about the respondent: no admission → "the order alleges"; partial → only admitted facts stated as
admitted; litigated → "the tribunal found". Posture unknown →
GAP — admission posture not established, and the alleged register throughout. The chat reply
uses the alleged register too; a conduct list starts "The order alleges:". Never "the firm did
X" where the order alleges it.
3. Extract the conduct, the rules, and the remedies
Detail: workflow.md § 3.
- Alleged conduct: quoted, with paragraph citations, in the posture's register.
- Rules cited: list them as cited, then retrieve each one; never rely on the order's
characterisation. Run the codification check. With the definitions section not retrieved,
every entity term in a rule quote or paraphrase reads
[covered entity].
- Remedies: each with deadline, scope, one-time or ongoing, quoted as
The order requires the respondent to "<text>" (¶ n). Never a plain-English paraphrase such as
"stop charging these fees": it presupposes the conduct. An undated Effective Date makes every
relative deadline lead with NOT FOUND - order states no calendar date (Gn); "<wording>".
- What the order does not say: root cause, control design, detection interval, population.
Each absence is its own bullet leading with
NOT FOUND - the order states no <what> (Gn).
4. Derive read-across themes
Detail: workflow.md § 4. Turn the alleged conduct into control-failure patterns the firm can
test itself against, each phrased as a question and anchored to the order's paragraphs and the
cited rule. Never a conclusion about the firm.
5. Map to the firm's controls
Detail: workflow.md § 5. Locate controls in M365 or a GRC connector: control ID or policy ·
version · approval status · owner · what it addresses (topical link only) · what it does not. A
theme with no control is NOT FOUND - <repository> has no record of a control for <theme> (Gn):
a genuine finding, never a blank.
6. Frame exposure as hypotheses
Detail: workflow.md § 6. Every observation is a question for a named function, marked
NOT DETERMINED — <function> assesses, with what was and was not located. Coverage of the firm's
entities or products is proposed applicability, with the retrieved defining provision cited, or
none - defining provision not retrieved. Never write that the firm has a deficiency, gap, or
violation. A read-across memo can become discoverable.
7. Emit the memo and table
Detail: workflow.md § 7. docx builds the memo and xlsx the workbook, per
readacross-outline.md. Counts state their denominators.
8. Final self-check, then count
- Save the artifact text, the chat reply (
reply.md), and the search log (searches.md: one
REQ | <source> | ok / failed / not attempted line per request and one
HIT | <query> | <document> | used / rejected (Gn) / duplicate (Gn) / set aside line per document returned).
- Run
python scripts/lint_deliverable.py <artifact> --reply reply.md --searches searches.md.
Fix every ERROR, resolve every CHECK, and re-run until it prints ERROR: 0
(house-rules.md § 13).
- Work through every item in
references/self-check.md, including the alleged-register grep
the script cannot fully judge.
- Build the footer counts from the G-list and D-list last, then recount.
Guardrails
Full list: workflow.md, Guardrails.
- Never restate an allegation as fact, in the memo or the chat reply; never omit "without
admitting or denying" where the order has it.
- Never rely on the order's characterisation of a rule; retrieve it, and run the codification
check before calling it current.
- Never state that the firm has a violation, deficiency, or compliance gap; never infer a root
cause the order does not state.
- Never paraphrase a remedy; quote it. Never treat a supervisory expectation as a rule.
- Never fabricate. Never claim a save succeeded when it failed. Nothing is filed, sent, or
committed on the firm's behalf.
Output footer
Per house-rules.md § 9 and workflow.md, Output footer: destination · order with agency,
docket, date, and type · admission posture, quoted · route and retrieval date · rules cited
and retrieved · codification checks · control repository searched · connectors · themes and
themes with no control · open items by marker type · determinations outstanding · files and save
result · template used.
Example
Input: Agency consent order, Respondent neither admits nor denies findings.
Output: Admission posture quoted; conduct described as "the order alleges" throughout.
Theme 1: Are fee disclosures reviewed against product terms before release?
Control mapping: NOT FOUND - no control located for Theme 1 (G1).
Observation: NOT DETERMINED - Compliance assesses (D1); no firm violation stated.
Reference files
references/workflow.md — full step text, guardrails, source resolution, footer detail.
references/self-check.md — the final self-check.
references/house-rules.md — gates, tiers, markers, footers, data minimisation, the lint step.
references/reg-source-access.md — retrieving the order and the cited rules.
references/document-extraction.md — consent-order extraction, allegation vs finding.
references/readacross-outline.md — default memo and control-gap table.
1---2name: enforcement-action-review3description: Reads a public enforcement action, complaint, settlement, or consent order and produces a read-across against the firm's controls covering alleged conduct, cited rules, and corrective actions. Exposure is framed as hypotheses for human review, never admissions. Use when the user says "could this happen here", "what does this consent order mean for us", "lessons learned from this enforcement action", "read this across to our controls", or "which controls does this implicate". Do NOT use for customer or counterparty research (use kyc-research-pack), new rules, bulletins, SR letters, or proposed or final regulations (use reg-change-triage), request trackers (use exam-request-response), document formatting (use built-in docx), or sending email (use built-in outlook-email).4metadata:5 source: https://skillmd.com/skills/microsoft/enforcement-action-review6 icon: Gavel7---89## Scope1011**Do:** retrieve enforcement orders, quote admission posture, extract alleged conduct, cited rules, remedies, derive read-across themes, map candidate firm controls12**Do not:** restate allegations as fact, rely on an order's rule characterization, state the firm has a violation, deficiency, or compliance gap, infer root cause, file, send, or commit anything1314## When NOT to Use1516- **Researching a customer or counterparty** — use `kyc-research-pack` instead.17- **Triaging a newly published rule** — use `reg-change-triage` instead.18- **Formatting or restyling an existing document** — use `docx` instead.1920# Enforcement-Action Read-Across2122What the regulator actually penalised, what it required, and where the firm should look.2324**Two directions of care.** Allegations against the respondent are not facts about the25respondent. Exposure observations about the firm are not admissions by the firm. Both rules hold26at once — `house-rules.md` § 2 and § 6.2728---2930## Read first3132Read these in full before step 1. They are binding; this body only summarises them.3334- `references/workflow.md` — the full text of every step below, with the guardrails, source35 resolution, and footer detail.36- `references/house-rules.md` — destination gate, determination gate, authority tiers, markers,37 footers, and § 12 data minimisation (every artifact, search, and chat reply, declines included).38- `references/reg-source-access.md` — retrieving the order and the rules it cites.39- `references/document-extraction.md` — consent-order extraction, allegation vs finding.40- `references/readacross-outline.md` — default memo and control-gap table: the output format.41- `references/self-check.md` — the final self-check (step 8).4243---4445## Workflow4647### 1. Retrieve the order4849Detail: `workflow.md` § 1. Connector → direct route → browser → ask for an upload →50`NOT RETRIEVED`. Establish agency · respondent · docket · date · type. A litigated decision holds51findings; a consent order usually holds allegations. Never treat them alike.5253### 2. Establish the admission posture — before anything else5455Detail: `workflow.md` § 2. Find and **quote** the admission language. It governs every sentence56about the respondent: no admission → "the order alleges"; partial → only admitted facts stated as57admitted; litigated → "the tribunal found". Posture unknown →58`GAP — admission posture not established`, and the alleged register throughout. **The chat reply59uses the alleged register too**; a conduct list starts "The order alleges:". Never "the firm did60X" where the order alleges it.6162### 3. Extract the conduct, the rules, and the remedies6364Detail: `workflow.md` § 3.6566- **Alleged conduct:** quoted, with paragraph citations, in the posture's register.67- **Rules cited:** list them as cited, then **retrieve each one**; never rely on the order's68 characterisation. Run the codification check. With the definitions section not retrieved,69 every entity term in a rule quote or paraphrase reads `[covered entity]`.70- **Remedies:** each with deadline, scope, one-time or ongoing, quoted as71 `The order requires the respondent to "<text>" (¶ n)`. Never a plain-English paraphrase such as72 "stop charging these fees": it presupposes the conduct. An undated Effective Date makes every73 relative deadline lead with `NOT FOUND - order states no calendar date (Gn); "<wording>"`.74- **What the order does not say:** root cause, control design, detection interval, population.75 Each absence is its own bullet leading with `NOT FOUND - the order states no <what> (Gn)`.7677### 4. Derive read-across themes7879Detail: `workflow.md` § 4. Turn the alleged conduct into control-failure patterns the firm can80test itself against, each phrased as a question and anchored to the order's paragraphs and the81cited rule. Never a conclusion about the firm.8283### 5. Map to the firm's controls8485Detail: `workflow.md` § 5. Locate controls in M365 or a GRC connector: control ID or policy ·86version · approval status · owner · what it addresses (topical link only) · what it does not. A87theme with no control is `NOT FOUND - <repository> has no record of a control for <theme> (Gn)`:88a genuine finding, never a blank.8990### 6. Frame exposure as hypotheses9192Detail: `workflow.md` § 6. Every observation is a question for a named function, marked93`NOT DETERMINED — <function> assesses`, with what was and was not located. Coverage of the firm's94entities or products is proposed applicability, with the retrieved defining provision cited, or95`none - defining provision not retrieved`. **Never write that the firm has a deficiency, gap, or96violation.** A read-across memo can become discoverable.9798### 7. Emit the memo and table99100Detail: `workflow.md` § 7. `docx` builds the memo and `xlsx` the workbook, per101`readacross-outline.md`. Counts state their denominators.102103### 8. Final self-check, then count1041051. Save the artifact text, the chat reply (`reply.md`), and the search log (`searches.md`: one106 `REQ | <source> | ok / failed / not attempted` line per request and one107 `HIT | <query> | <document> | used / rejected (Gn) / duplicate (Gn) / set aside` line per document returned).1082. Run `python scripts/lint_deliverable.py <artifact> --reply reply.md --searches searches.md`.109 Fix every `ERROR`, resolve every `CHECK`, and re-run until it prints `ERROR: 0`110 (`house-rules.md` § 13).1113. Work through every item in `references/self-check.md`, including the alleged-register grep112 the script cannot fully judge.1134. Build the footer counts from the G-list and D-list last, then recount.114115---116117## Guardrails118119Full list: `workflow.md`, Guardrails.120121- Never restate an allegation as fact, in the memo or the chat reply; never omit "without122 admitting or denying" where the order has it.123- Never rely on the order's characterisation of a rule; retrieve it, and run the codification124 check before calling it current.125- Never state that the firm has a violation, deficiency, or compliance gap; never infer a root126 cause the order does not state.127- Never paraphrase a remedy; quote it. Never treat a supervisory expectation as a rule.128- Never fabricate. Never claim a save succeeded when it failed. Nothing is filed, sent, or129 committed on the firm's behalf.130131## Output footer132133Per `house-rules.md` § 9 and `workflow.md`, Output footer: destination · order with agency,134docket, date, and type · **admission posture, quoted** · route and retrieval date · rules cited135and retrieved · codification checks · control repository searched · connectors · themes and136themes with no control · open items by marker type · determinations outstanding · files and save137result · template used.138139### Example140141```142Input: Agency consent order, Respondent neither admits nor denies findings.143Output: Admission posture quoted; conduct described as "the order alleges" throughout.144Theme 1: Are fee disclosures reviewed against product terms before release?145Control mapping: NOT FOUND - no control located for Theme 1 (G1).146Observation: NOT DETERMINED - Compliance assesses (D1); no firm violation stated.147```148149## Reference files150151- `references/workflow.md` — full step text, guardrails, source resolution, footer detail.152- `references/self-check.md` — the final self-check.153- `references/house-rules.md` — gates, tiers, markers, footers, data minimisation, the lint step.154- `references/reg-source-access.md` — retrieving the order and the cited rules.155- `references/document-extraction.md` — consent-order extraction, allegation vs finding.156- `references/readacross-outline.md` — default memo and control-gap table.