@1aboveio/skills 0.19.3 → 0.20.2

package/skills/payment/tld-detection/agents/openai.yaml

@@ -0,0 +1,9 @@
+interface:
+  display_name: "TLD Detection"
+  short_description: "Risk-tiered TLD clusters from exact currency-amount pairs"
+
+policy:
+  # Codex counterpart to SKILL.md disable-model-invocation: true
+  # (Claude Code / Pi). Keeps explicit invoke; blocks description-based
+  # auto-selection.
+  allow_implicit_invocation: false

package/skills/payment/tld-detection/evals/evals.json

@@ -0,0 +1,107 @@
+{
+  "skill_name": "tld-detection",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "We think some merchants are stuffing TLD volume through a normal MCC. Authorizations_2026-03.csv has descriptors, MCC, BIN country, amount, currency, timestamp, and response codes. Find potential TLD clusters.",
+      "expected_output": "Deduplicates auths without a US-BIN filter; partitions by normalized descriptor; detects exact currency-amount pairs with explicit absolute residual caps; freezes membership; compares each cluster with the same descriptor after removing that cluster; assigns High, Medium, or Low investigation priority; and quantifies exposure by risk tier and descriptor.",
+      "expectations": [
+        "Uses normalized descriptor as the partition key and does not use BIN country as a membership key.",
+        "Uses adjacent currency-specific absolute residual caps with sensitivity evidence and no percentage tolerance.",
+        "Requires at least three theoretical levels with a fixed 2x relationship between adjacent levels.",
+        "Reports only currency-amount pairs with at least 100 exact-member attempts and compares each with the same descriptor after removing that cluster.",
+        "Reports Top 3 issuing banks and BIN countries only after membership is frozen.",
+        "Assigns every identified cluster High, Medium, or Low risk without treating the tier as confirmation of TLD.",
+        "Sorts results High to Medium to Low and reports exact-member exposure separately by tier and descriptor.",
+        "Keeps run-specific methodology in a separate linked document.",
+        "Provides a Verdict of at most three sentences without confirmed-laundering language."
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Same descriptor seems to mix several ticket sizes that look like 9.99, 19.99, 39.99, 79.99. Another TLD name might be split across three billing descriptors. Cluster the book and tell me if those patterns hold.",
+      "expected_output": "Builds descriptor partitions and identifies qualifying currency-amount pairs independently inside them using at least three theoretical levels and a fixed 2x relationship; matching amounts across descriptors never merge membership.",
+      "expectations": [
+        "Builds descriptor partitions before currency-amount pairs.",
+        "Requires at least three theoretical levels and rejects non-2x relationships.",
+        "Requires at least 100 exact-member attempts before reporting a cluster.",
+        "Reports materially different currency-amount pairs under one descriptor.",
+        "Assesses MCC fit without calling a descriptor fabricated."
+      ]
+    },
+    {
+      "id": 3,
+      "prompt": "For each detected currency-amount pair, compare its behavior with the rest of the same descriptor.",
+      "expected_output": "Keeps BIN country out of the membership key, freezes exact membership, builds a same-descriptor baseline by removing only that cluster, compares the required rates and Top 3 dimensions, reports both BIN-country conditional shares, and charts transaction date and BIN-country local-hour distributions against that baseline.",
+      "expectations": [
+        "Does not partition detection by BIN country.",
+        "Uses the same descriptor after removing the current cluster as baseline.",
+        "Reports authorization success rate and suspected fraud as a share of attempts for Cluster and Baseline.",
+        "In each cluster definition, the anchor table reports attempts, authorization success rate, and suspected-fraud share for every theoretical level, including levels with fewer than 30 attempts.",
+        "For each Top 3 cluster BIN country, reports its share of the cluster and the cluster's share of all attempts in the same descriptor-country slice.",
+        "Treats exact 100% single-country concentration as a standout, Mixed as neutral, and country-slice coverage as descriptive without a risk threshold.",
+        "Charts transaction-date and BIN-country local-hour shares for Cluster and Baseline, normalizing each series independently."
+      ]
+    },
+    {
+      "id": 4,
+      "prompt": "Inside descriptor ACME, USD 10.00 is followed by 19.99 with 180 attempts, 20.00 with 40 attempts, and then 39.99. Build the potential TLD ladders.",
+      "expected_output": "Uses an explicit USD adjacent absolute residual cap; selects a primary exact anchor deterministically; may retain another exact anchor at the same theoretical level only if it clears the stated multi-anchor support floor; and applies exact descriptor, currency, and amount membership afterward.",
+      "expectations": [
+        "Runs ladder discovery only inside descriptor ACME.",
+        "Uses absolute adjacent residuals rather than percentage matching.",
+        "Selects the highest-count candidate as the primary anchor.",
+        "Retains an additional anchor only when it independently clears the declared support floor.",
+        "Never assigns every amount in a tolerance interval to the ladder."
+      ]
+    },
+    {
+      "id": 5,
+      "prompt": "Inside one descriptor I see an approximate EUR x2 amount pattern, but its selected exact amount keys total only 96 authorization attempts. Should it be reported?",
+      "expected_output": "Does not report the 96-attempt family; records it below threshold, keeps its transactions outside reported clusters, publishes its ranking, and does not invent a cluster from MCC or comparison features.",
+      "expectations": [
+        "Does not report the 96-attempt family.",
+        "Keeps its rows outside reported clusters.",
+        "Does not invent a cluster from comparison features.",
+        "Still provides a no-ladder Verdict of at most three sentences."
+      ]
+    },
+    {
+      "id": 6,
+      "prompt": "Descriptors ALPHA and BETA both have the exact USD 9.99, 19.99, 39.99 ladder with over 100 attempts, across several BIN countries. Should those transactions become one cluster?",
+      "expected_output": "Creates two descriptor-local currency-amount pairs, permits the same exact amounts in both descriptors, keeps their membership and same-descriptor baselines separate, and reports each independently.",
+      "expectations": [
+        "Creates two ladders because descriptor is the partition boundary.",
+        "Permits the same exact pairs in different descriptor ladders.",
+        "Does not merge matching fingerprints across descriptors.",
+        "Does not merge membership, metrics, or baselines.",
+        "Treats BIN country as post-membership reporting data."
+      ]
+    },
+    {
+      "id": 7,
+      "prompt": "USD 14.xx amounts are representative, but one percentage tolerance becomes too wide at larger amounts. Detect the ladders without sweeping a numeric interval into membership.",
+      "expected_output": "Runs a documented absolute-cap sensitivity grid, uses a currency-specific adjacent residual cap, searches every descriptor-local rung-pool seed, allows only sufficiently supported exact multi-anchors, rejects upper rungs outside the absolute cap, and freezes exact membership before BIN-country attribution.",
+      "expectations": [
+        "Does not use a percentage tolerance.",
+        "Reports the tested cap grid and selected cap.",
+        "Uses finite exact anchor sets with a stated multi-anchor support floor.",
+        "Rejects an upper rung whose adjacent residual exceeds the cap.",
+        "Computes BIN-country reporting values only after exact membership is frozen."
+      ]
+    },
+    {
+      "id": 8,
+      "prompt": "One cluster is 100% US BIN and covers 21.3% of its descriptor's US BIN attempts. Another is mixed and covers 33.8% of one descriptor-country slice. Grade and order the risk.",
+      "expected_output": "Treats the exact 100% single-country concentration as a standout and uses 21.3% only to explain its scale; treats Mixed as neutral and 33.8% as descriptive rather than a threshold; combines independent structural and behavioral evidence; assigns High, Medium, or Low risk; and sorts High to Medium to Low.",
+      "expectations": [
+        "Does not classify Mixed as Weak or automatically lower its risk tier.",
+        "Does not infer risk from a 20%, 33.8%, or other country-slice coverage threshold.",
+        "Requires exact 100% single-country composition for the BIN-country standout.",
+        "Reports cluster composition and descriptor-country slice coverage as separate conditional percentages.",
+        "Uses at least one independent corroborating characteristic before making a 100% single-country cluster High risk.",
+        "Preserves stable cluster IDs while sorting High to Medium to Low."
+      ]
+    }
+  ]
+}

package/skills/payment/tld-detection/references/clean.md

@@ -0,0 +1,51 @@
+# Data cleaning
+
+Run on the authorization extract before any clustering. Record every drop
+count in the report appendix.
+
+Do not filter to US-BIN here. Issuer country remains available for the
+cluster-versus-baseline Top 3 BIN-country comparison.
+
+## 1. Exact-row dedup
+
+Drop bitwise-duplicate rows (same values in every column used). Count
+them. They are extract artefacts, not extra attempts.
+
+## 2. Identity dedup
+
+If `Transaction ID` / `Auth ID` is unique when present, keep one row per
+id (first by time).
+
+Otherwise, if `Order ID` is present, keep one row per
+(`Order ID`, time, amount, currency, masked PAN / last4 if present).
+Retries of the same order at different times stay distinct.
+
+If none of those identities exist, **skip this step** — keep the
+exact-row-deduped table and say identity-dup was skipped. Do not stop
+the run. Do not invent a customer id from BIN + amount.
+
+## 3. Amount and currency
+
+- Clustering key uses the **original** amount and currency.
+- Normalize `10`, `10.0`, `10.00` to the same decimal key.
+- Drop rows with missing amount or currency; count them.
+- Do not FX-convert before clustering. A 9.99 EUR rung is not a 9.99 USD
+  rung. Amount sums later stay inside one currency; never add EUR to USD.
+
+## 4. Missing dimensions
+
+Rows with missing descriptor or BIN / issuer country stay in the
+clustering universe. Missing descriptors enter the `UNKNOWN_DESCRIPTOR`
+partition; missing countries enter the `UNKNOWN_BIN_COUNTRY` reporting
+bucket after membership is frozen.
+
+## Output of this step
+
+A cleaned table plus a one-line census:
+
+```
+raw N → exact-dup drop n1 → identity-dup drop n2 (or skipped)
+→ missing amount/currency n3 → cleaned universe U
+```
+
+All later attempt counts use `U`, not `raw N`.

package/skills/payment/tld-detection/references/clustering.md

@@ -0,0 +1,219 @@
+# Currency-amount-pair clustering
+
+Goal: partition the cleaned universe by descriptor, find stuffing (掺量)
+as **approximate geometric ladders** inside each descriptor, then decompose
+each qualifying ladder into BIN-country attribution components and contrast
+it against the remainder.
+
+## Descriptor partition
+
+Partition key = `normalized descriptor`.
+
+- Trim, case-fold, and collapse repeated whitespace. Preserve the most
+  frequent source spelling for display.
+- Do not fuzzy-match or strip dynamic suffixes unless the extract documents
+  their semantics.
+- Use `UNKNOWN_DESCRIPTOR` for missing values; do not drop them.
+
+Freeze descriptor assignment before ranking amounts. Report each descriptor's
+attempt count and share of `U`. A ladder belongs to exactly one descriptor;
+the same exact currency-amount-pair may legitimately belong to ladders in
+different descriptors.
+
+BIN country is **not** a partition or membership key. Normalize it after
+ladder formation and report its attempt counts, shares, auth rates, suspected-
+fraud rates, and local-hour shapes as attribution components.
+
+## Currency-amount-pair
+
+Key = (`currency`, `amount`) on the original (not FX-converted) amount.
+
+Count = authorization **attempts** in the current partition. Rank
+descending by count. Ties: smaller amount first, then currency code.
+
+## High-count set and rung pool
+
+Work **per partition, then per currency**. In the table below, `|P|` is
+the authorization-attempt count of the current partition.
+
+| Set | Membership |
+|---|---|
+| High-count (seeds) | union of (a) pairs with count ≥ `max(30, 0.5% of \|P\|)` (b) the partition top 25 pairs by count (c) per currency in the partition, the top 10 pairs with count ≥ 30 |
+| Rung pool | pairs with count ≥ `max(5, 0.1% of \|P\|)` |
+
+State the thresholds. Use the high-count set for ranking. Test every rung-pool
+pair as a possible seed for a three-level 2x relationship; otherwise a
+representative lower-volume path can be structurally impossible to discover.
+Extra levels may be quieter amounts in
+the rung pool, and (c) keeps a smaller currency visible inside the partition.
+
+If the rung pool has fewer than three pairs in every currency of a partition,
+that partition has no three-level ladder to test. Still publish its ranking
+table when it is among the largest partitions or has a below-threshold family.
+
+## Ladder detection
+
+Ladder detection has two separate phases. **Discovery** uses an adjacent,
+currency-specific absolute residual cap. **Membership and every downstream
+metric use the exact descriptor plus selected currency-amount-pairs only.**
+Never widen final membership to a numeric interval or another descriptor.
+
+### Adjacent absolute-residual rule
+
+For exact amounts `a < b` in one descriptor and currency, multiplier `m` has:
+
+```text
+residual = |b - a · m|
+```
+
+They are adjacent anchors only when `residual ≤ ε_currency`. Do not use one
+percentage tolerance across amounts: its absolute allowance grows with the
+amount and can merge materially different upper-rung prices.
+
+Configure and report one cap per currency represented in a partition's rung
+pool. For a two-decimal currency, test a sensitivity grid such as `0.02,
+0.05, 0.10, 0.15, 0.25` and retain the smallest operationally justified cap
+under which material paths are stable. Fail closed when a rung-pool currency
+has no cap; currencies below the rung-pool threshold need no cap.
+
+Use the bundled deterministic implementation after producing a cleaned
+authorization CSV:
+
+```bash
+python3 {baseDir}/scripts/detect_ladders.py cleaned-authorizations.csv \
+  --descriptor-column descriptor --bin-country-column bin_country \
+  --currency-column currency --amount-column amount \
+  --cap USD=0.15 --multi-anchor-min-attempts 24 \
+  --sensitivity-cap USD=0.02 --sensitivity-cap USD=0.05 \
+  --sensitivity-cap USD=0.10 --sensitivity-cap USD=0.15 \
+  --sensitivity-cap USD=0.25
+```
+
+The CLI does not clean or deduplicate the CSV; complete
+[clean.md](clean.md) first.
+
+### Family from a seed (up and down)
+
+Starting from every rung-pool seed, expand recursively upward and downward
+using only adjacent matches. A theoretical level may contain several exact
+anchors. Select the highest-count match as its primary anchor; retain an
+additional match only when that exact pair independently clears the stated
+portfolio support floor (default 24 attempts, corresponding to the Worldpay
+portfolio rung floor). Record that floor and test it separately for a new
+portfolio.
+
+Every retained key must be in the partition's rung pool and match an anchor
+in the adjacent level. The finite retained keys become the explicit anchor
+set. Tolerance never acts on transactions after selection: final membership
+is exact equality on (`descriptor`, `currency`, `amount`). BIN country is
+attached only after this membership is frozen.
+
+### Required 2x family
+
+A candidate family must use **`m = 2`** between every adjacent theoretical
+level and contain **at least three theoretical levels**. Example: 1x, 2x, 4x,
+8x around the seed, including downward (`19.99` can find `9.99` and `39.99`).
+There is no two-level exception, and relationships based on `m = 3`, `4`, `5`,
+`10`, or any other multiplier do not form clusters.
+
+For each seed, rank qualifying paths by: more theoretical levels; more exact-
+member attempts; then lower summed adjacent residual. The attempt threshold
+below independently determines whether the family becomes a reported cluster.
+
+### Minimum cluster size
+
+Sum attempts only over rows in the partition whose keys are the selected
+exact currency-amount-pairs. A family is a reported cluster only when that
+exact membership has **≥100 authorization attempts**. Keep smaller
+families in the run methodology document as `below threshold`; do not validate them or
+issue cluster verdicts for them. Their rows remain in canonical baseline
+`B` and descriptor remainder `B_D` unless selected exact keys are claimed
+by another reported ladder in the same descriptor.
+
+### Several groups
+
+Within each partition, process unused rung-pool seeds in descending attempt
+count. A currency-amount-pair joins **at most one** reported cluster in that
+partition — the first qualifying family that claims it. Below-threshold
+families do not reserve keys. Never let a claim in one partition reserve the
+same pair in another partition.
+
+Name clusters `C1`, `C2`, … by descending total attempts. For each, record
+the descriptor partition, seed, currency, multiplier, absolute cap, summed
+fit residual, theoretical levels, all exact anchors and counts, multi-anchor
+levels, total attempts, and post-formation BIN-country components.
+
+Ignore one-off round amounts (`100`, `1000`) unless they sit on a ladder.
+A popular SKU price is not a cluster by itself.
+
+### None found
+
+If no family qualifies in any partition, **do not invent clusters** from
+MCC or comparison features. Publish the partition and pair rankings, contrast
+the top pairs only as context if useful, and skip cluster verdicts.
+
+## Baseline
+
+For each cluster, **Baseline** means every authorization in the same descriptor
+after removing that cluster's exact member keys. Other identified
+currency-amount pairs remain in this baseline. This is the only comparison
+population used in cluster characteristics. If the cluster consumes the whole
+descriptor, report comparison values as `n/a`.
+
+For the overall impact table only, `Baseline` means rows in the cleaned universe
+that belong to no identified currency-amount pair. Keep this distinct from the
+per-cluster same-descriptor baseline.
+
+If two currencies each have a ladder, they are separate clusters. Do not
+merge across currencies.
+
+## Contrast vs baseline
+
+Same window and descriptor. Compare each cluster with its baseline on:
+
+| Metric | Formula |
+|---|---|
+| Authorization success rate | approvals / attempts |
+| Suspected fraud as share of attempts | suspected-fraud attempts / attempts |
+| Top 3 issuing banks | count and share of that series |
+| Top 3 BIN countries | count and share of that series |
+
+Separately report Descriptor, descriptor total attempts, cluster attempts,
+cluster share of descriptor, and MCC.
+
+Require a stated min-n before ranking a cluster-versus-baseline rate
+(default attempts ≥ 30). Below that, show the contrast rate as `n/a (n=…)`.
+The definition anchor table is not a ranking contrast: always compute
+authorization success rate and suspected-fraud share for every theoretical
+level from that level's exact member attempts, including n < min-n. Combined
+`*` levels use the combined attempts of the level. Do not write `n/a` on the
+anchor table because the rung is small.
+
+Use the contrast to assign investigation-priority risk under
+[decision.md](decision.md), not as a fraud label. Treat materially different
+authorization, suspected-fraud, issuing-bank, date, and local-hour behavior as
+independent characteristics under thresholds declared in the run methodology.
+
+For each Top 3 cluster BIN country, report both its share of the cluster and
+the cluster's share of all attempts in the same descriptor-country slice. An
+exact 100% single-country cluster is a standout. `Mixed` is neutral, and
+country-slice coverage is descriptive only: do not set a universal threshold
+or award risk points for values such as 20% or 33.8%.
+
+## What not to do
+
+- Do not treat MCC as a partition or clustering key.
+- Do not discover ladders across descriptor boundaries.
+- Do not use BIN country as a ladder partition or membership key.
+- Do not k-means the amounts.
+- Do not convert to USD and then look for ladders.
+- Do not search only upward from the busiest rung.
+- Do not use a percentage tolerance across amounts.
+- Do not assign every amount inside an interval; select finite exact anchors first.
+- Do not retain a low-support additional anchor merely because it is near a primary anchor.
+- Do not report a cluster with fewer than three theoretical levels.
+- Do not use any adjacent-level multiplier other than 2x.
+- Do not report a cluster with fewer than 100 attempts.
+- Do not put the same pair in two clusters within one partition.
+- Do not merge matching amount fingerprints across descriptors.
+- Do not call the output a customer segment or a marketing cohort.

package/skills/payment/tld-detection/references/decision.md

@@ -0,0 +1,85 @@
+# Risk decision
+
+After currency-amount-pair detection and same-descriptor baseline comparison,
+assign investigation-priority risk tiers. This is prioritization, not a finding
+that transaction laundering occurred.
+
+## Eligibility versus risk
+
+The cluster gate (at least three theoretical levels, fixed 2x adjacency, at
+least 100 exact-member attempts) determines which currency-amount pairs enter
+the result. Passing that gate does not by itself determine High, Medium, or Low
+risk.
+
+Risk uses independent post-membership evidence:
+
+- structural strength beyond the minimum, such as a fourth or later level
+- cluster share of its descriptor
+- authorization-success and suspected-fraud differences versus the same-
+  descriptor baseline
+- issuing-bank differences versus that baseline
+- transaction-date and BIN-country-local-hour differences versus that baseline
+- externally evidenced MCC or merchant-business mismatch; never infer this
+  from a suggestive descriptor name alone
+
+Declare portfolio-specific thresholds for a materially different rate,
+distribution, or descriptor share in the run methodology before assigning
+risk. Do not invent universal cutoffs after seeing the results.
+
+## BIN-country evidence
+
+BIN country is post-membership evidence, not a partition, membership key, or
+veto. `Mixed` is neutral and must never reduce a risk tier by itself.
+
+For every Top 3 cluster BIN country, report both conditional views:
+
+```text
+cluster composition = cluster attempts in country / all cluster attempts
+country-slice coverage = cluster attempts in country /
+                         all attempts in the same descriptor and country
+```
+
+An exact **100% single-BIN-country cluster** is a standout characteristic.
+Country-slice coverage explains how large that concentration is inside the
+descriptor-country population, but it has no fixed threshold and contributes
+no independent risk points. Values such as 20% or 33.8% are descriptive, not
+self-interpreting risk signals. Any value below 100% is not promoted merely
+because it is numerically high.
+
+## Risk tiers
+
+Assign exactly one tier to every identified currency-amount pair:
+
+| Tier | Use when |
+|---|---|
+| High | An exact 100% single-country standout has at least one independent corroborating risk characteristic, or several independently strong non-country characteristics converge |
+| Medium | At least two independent characteristics materially differ from the same-descriptor baseline, but High is not justified |
+| Low | The structural cluster gate is met, but observed corroborating evidence is limited or not material |
+
+Do not use a generic 0–100 score unless the business has approved and calibrated
+its weights and cutoffs. Missing fields reduce confidence and must be disclosed;
+they are not evidence that risk is Low.
+
+Sort report results `High → Medium → Low`. Within a tier, sort by the number and
+magnitude of independently supported characteristics, then by exact-member
+attempts. Preserve stable cluster IDs when sorting an existing result.
+
+## Length and required content
+
+The Verdict is at most three sentences for the whole book:
+
+1. State the highest risk tier found and that it is an investigative priority,
+   not confirmation that TLD occurred.
+2. For High-risk clusters, give descriptor, representative anchors, attempts,
+   descriptor share, standout evidence, and the clearest independent
+   corroborating characteristic.
+3. Give exact-member exposure by risk tier and as a share of all authorization
+   attempts.
+
+If no currency-amount pair qualifies, state that none qualified, name the top
+descriptor and candidate amounts, and report zero identified-cluster exposure.
+Do not invent a cluster. Do not recommend filing a SAR, terminating a merchant,
+or correcting an MCC.
+
+First use of TLD is “transaction laundering (TLD)”. Proofread with
+[terminology.md](terminology.md).

package/skills/payment/tld-detection/references/report-template.md

@@ -0,0 +1,169 @@
+# Report template
+
+Save:
+
+```text
+reports/tld-detection/<scope>_clusters.md
+reports/tld-detection/<scope>_clusters.zh.md
+reports/tld-detection/<scope>_clusters.zh.html
+reports/tld-detection/<scope>_methodology.md
+reports/tld-detection/<scope>_methodology.zh.md
+reports/tld-detection/<scope>_methodology.zh.html
+```
+
+HTML is preferred when there are charts (Chart.js bars). No Markdown bold in report body.
+The cluster report and methodology document must link to each other. After
+writing, grep banned strings in [terminology.md](terminology.md).
+
+English Markdown headings on the left; Chinese HTML / `.zh.md` on the right.
+
+```markdown
+# Potential TLD currency-amount pairs — <window>
+# 潜在 TLD 币种金额对 — <window>
+
+## TLD Risk Assessment                  # TLD 风险评估
+[Separate methodology link]             # [独立方法文档链接]
+## High-Risk Clusters                   # 高风险 Cluster
+## TLD Risk Exposure                    # TLD 风险敞口
+### By risk tier and descriptor          # 按风险等级及 Descriptor
+### Overall exposure                     # 整体风险敞口
+## All Identified Currency-Amount Pairs # 全部识别出的币种金额对
+### Currency-Amount Pair C1             # 币种金额对 C1
+#### Definition                         # 定义
+#### Characteristics                    # 特征
+## Verdict                              # 结论
+```
+
+The separate methodology document uses this structure:
+
+```markdown
+# TLD currency-amount-pair detection methodology — <scope/window>
+# TLD 币种金额对识别方法 — <范围/时段>
+
+## Universe and cleaning                # 分析总体与清洗
+## Descriptor partition logic           # Descriptor 分区逻辑
+## Currency-amount-pair logic           # 币种金额对逻辑
+## Baseline and audit details           # 基线与审计明细
+```
+
+## Chapter requirements
+
+### TLD Risk Assessment / TLD 风险评估
+
+Answer these three questions directly and in this order:
+
+1. What is the highest investigation-priority risk tier found?
+2. Which clusters are High, Medium, and Low risk; what characteristics support
+   each tier; and what share do they represent inside their descriptors?
+3. What is the exact-member exposure by risk tier, descriptor, and across all
+   authorization attempts?
+
+Risk tiers prioritize investigation and do not confirm TLD. List results in
+`High → Medium → Low` order, then by evidence strength and attempts inside each
+tier. The ≤3-sentence conclusion lives in Verdict, not here.
+
+### Separate methodology / 独立方法文档
+
+Document the logic and values actually used for this run, not generic skill
+instructions. State the authorization grain and window; give the census from
+[clean.md](clean.md), BIN-country and currency mix, and portfolio
+constants.
+
+Partition logic defines the normalized descriptor key, normalization rules,
+the unknown bucket, descriptor counts, and shares. Currency-amount-pair
+logic explains within-descriptor ranking, adjacent currency-specific
+absolute residual caps, sensitivity evidence, the multi-anchor support floor,
+exact final membership, and the ≥100-attempt threshold. BIN country is
+post-formation attribution, not a partition or membership key.
+
+The ranking table contains partition, currency, exact amount, attempts,
+share of the descriptor, share of all authorization attempts, and selected
+cluster id or `baseline`. Chart attempt bars within the most relevant
+descriptors, sorted by count descending.
+
+Audit details contain drop counts, currency caps, sensitivity results,
+multi-anchor support floor, ≥100 cluster attempts, min-n for
+cluster-versus-baseline rate ranking (not the definition anchor table),
+descriptor-local high-count rule, baseline definitions, below-threshold
+families, risk-tier rules, all run-specific materiality thresholds, and files
+used. No skill name in the HTML footer; filenames only.
+
+### High-risk clusters / 高风险 Cluster
+
+Include High-risk clusters only. For each, show descriptor, representative
+anchors, attempts, share of its descriptor, share of all authorization attempts,
+risk basis, standout evidence, and the clearest independent corroborating
+characteristic. Do not describe the tier as confirmation that TLD occurred.
+
+### Risk exposure / 风险敞口
+
+Exposure is the disjoint exact-member attempt count of all identified clusters,
+separated into High, Medium, and Low risk. The by-tier-and-descriptor table
+reports descriptor attempts, cluster attempts, share of descriptor, share of
+all authorization attempts, risk tier, and cluster IDs. The overall view has
+one row per risk tier plus `Baseline` / `基线`, and the rows conserve all
+authorization attempts. Never combine the three tiers into a single “confirmed”
+or “supported TLD” impact figure.
+
+### Currency-amount-pair analysis / 全部识别出的币种金额对
+
+One subsection per identified currency-amount pair. Definition contains only
+Descriptor, seed, representative anchors, and cluster attempts. Express
+anchors as `USD 11.7 → USD 23.39* → USD 46.78`. Follow that with an anchor
+table whose columns are anchor, attempts, authorization success rate, and
+suspected fraud as share of attempts. Always compute both rates for every
+theoretical level from that level's exact member attempts, including levels
+with fewer than the contrast min-n (default 30). Do not write `n/a` on this
+table because the rung is small. For a level containing multiple nearby exact
+values, display its highest-count amount with `*`; the table totals attempts
+and rates across that level and explains `*`.
+
+Show the risk tier and concise basis immediately below the cluster heading.
+Characteristics contain Descriptor, descriptor total attempts, cluster
+attempts, cluster share of descriptor, and MCC. Then compare Cluster with the
+baseline formed by removing that cluster from the same descriptor. The
+comparison contains authorization success rate, suspected fraud as a share of
+attempts, Top 3 issuing banks, and Top 3 BIN countries.
+
+For every Top 3 cluster BIN country, add a table with country, cluster attempts,
+share of cluster, total attempts in the same descriptor-country slice, and
+cluster coverage of that slice. Mark exact 100% single-country composition as a
+standout. Treat `Mixed` as neutral. Do not assign a threshold or risk points to
+country-slice coverage, and do not promote any composition below 100% merely
+because it is high.
+
+Follow the tables with transaction-date and transaction-time charts comparing
+the cluster with the same-descriptor baseline. These are characteristics, not
+cluster membership conditions.
+
+When clustering finds no qualifying family, omit currency-amount-pair subsections,
+publish the ranking and below-threshold candidates in the methodology
+document, show zero identified-cluster exposure, and still write Verdict.
+
+### Verdict / 结论
+
+[decision.md](decision.md). **≤3 sentences** for the whole book, then an
+optional one-row-per-cluster table (risk tier + short basis). No extra
+bullets under this heading.
+
+## Charts
+
+Place each currency-amount pair's charts inside its analysis after the
+characteristics tables.
+
+| View | Mark |
+|---|---|
+| Representative-anchor attempts | Horizontal bar |
+| Cluster vs same-descriptor baseline rates | Grouped bar |
+| Transaction date trend, cluster vs same-descriptor baseline | Two-series line, each series normalized to its own attempt total |
+| Transaction time by BIN-country local hour, cluster vs same-descriptor baseline | Two-series line, each series normalized to its own attempt total |
+
+Label axes with the full metric (`授权笔数`, `比率 %`, `每日授权占比 %`,
+`每小时授权占比 %`). State that transaction time uses the BIN country's local
+hour and UTC when the BIN country has no configured timezone.
+
+## What the report is not
+
+Not a payment overview (`payment-analysis`). Not a holdout rule pack
+(`fraud-analysis`). Not a recommendation to file a SAR or to terminate a
+merchant.