Dsail Regulated Industry Rules

---
name: dsail-regulated-industry-rules
description: "Apply a firm's written rules the same way to every case: trade surveillance thresholds, order routing policy, FINRA rulebook reviews and disclosure rules, suitability standards, customer due diligence and risk rating rules, fee schedules, insurance policy wording for coverage and claims, catastrophe deductibles, medical necessity and clinical guidelines, treaty cession terms and referral rules. Each result cites the rule that decided, for an examiner or an auditor."
---

# Regulated-industry rules with DSAIL

The written rules a regulated firm applies one case at a time: a compliance
manual, a FINRA rulebook, a suitability standard, underwriting or claims
guidelines, insurance policy wording, clinical criteria, a fee schedule, treaty
terms. DSAIL turns them into a ruleset whose every result names the rule that
decided, so the same facts get the same answer whoever is on the desk, and the
basis for a decision can be shown to an examiner later.

The `dsail` skill has the authoring sequence, the grammar and the integrity
rule. Follow it. This skill is about how these policies map onto it.

## Before writing any DSAIL

- Restate the policy in plain English, rule by rule, and get the person's
  confirmation. Name the manual section for each rule; it goes into the rule's
  description comment, so the review and every result carry it.
- DSAIL applies rules that are already written. Where the manual leaves a case
  to judgement (a "reasonable" standard, an exception a supervisor may grant),
  say so and leave that decision with the person. Do not invent a threshold.

## How these rules usually look

- **Caps and thresholds in money**: gift limits, fee breakpoints, deductibles,
  surveillance thresholds. Declare the unit on the claim (`// @unit giftValue
  USD`) and write it on every literal (`giftValue <= 100 "USD"`).
- **Limits that depend on a category**: the recipient type, the account tier,
  the coverage line, the territory. Declare the category as an enum and branch
  with `CASE` or `IF`.
- **Ordered tiers** such as risk ratings: an ordered enum
  (`["low","medium","high"]`) compares with `<` and `>`.
- **"At least N of the following"** (medical necessity, referral triggers,
  enhanced due diligence): one boolean per criterion, counted with `If`.
- **Running totals and look-backs** (gifts to the same recipient this calendar
  year, trades in the last thirty days): DSAIL checks one case's claims and does
  not aggregate history. Make the total a claim your system computes from its
  records, and write the rule against the sum.
- **One assert per written rule**, so a FALSE names the rule that blocked it.

## Example

```
version 1.3;
// @ask recipientType Who would receive the gift: a public official, a client, or a prospect the firm is pitching?
declare recipientType as enum {"public_official","client","prospect"};
// @ask giftValue What is the value of the proposed gift, in USD?
// @unit giftValue USD
// @range giftValue 0..1000000
declare giftValue as numeric;
// @ask priorGiftsThisYear What is the total value of gifts already given to this recipient this calendar year, in USD?
// @unit priorGiftsThisYear USD
// @range priorGiftsThisYear 0..1000000
declare priorGiftsThisYear as numeric;
// @ask meetsCriterionA Does the record show the first clinical criterion is met?
declare meetsCriterionA as boolean;
// @ask meetsCriterionB Does the record show the second clinical criterion is met?
declare meetsCriterionB as boolean;
// @ask meetsCriterionC Does the record show the third clinical criterion is met?
declare meetsCriterionC as boolean;

// Manual 4.1: no gift of any value to a public official.
assert no_gifts_to_officials { recipientType != "public_official" };
// Manual 4.2: gifts to one recipient may not exceed 100 USD in a calendar year.
assert annual_gift_cap { priorGiftsThisYear + giftValue <= 100 "USD" };
// Guideline 7: at least two of the three clinical criteria are met.
assert two_of_three_criteria { If(meetsCriterionA, 1, 0) + If(meetsCriterionB, 1, 0) + If(meetsCriterionC, 1, 0) >= 2 };
```

The section numbers and amounts are illustrative; use the policy's own.

## Checking, and keeping the record

- Extract claim values with the prompt pack on the user's own model. A fact the
  file does not state is "unknown", never a guess.
- Save the ruleset under a name and record the accountable person's approval
  against its hash. A later edit is a new revision and needs its own approval.
  The hash, the claim dictionary and the results are the record of what was
  decided, under which rules, on which facts.

## Not this skill

Routing a request to an approver or deciding who may act, scoring or ranking
risk where no written rule says how, judgements the policy leaves to a person,
and drafting or interpreting the policy itself.

<!-- generated by dsail 1.0.6; wire contract 2.10.0; re-run `dsail plugin-bundle` to refresh -->