What checks should we run on a set-up sample?

Run these checks on any sample before it is listed or passed to a customer, and record the result of each.

- **Key resolution:** every foreign key in accounts, services, tasks and events resolves to an existing parent record, and no table contains orphans or circular references. - **Condition carry-through:** each condition on an approval appears as a task, limit or flag on the resulting account, or is explicitly waived by an allowed role. - **Time order:** approvals precede accounts, accounts precede activation, and no event is stamped earlier than the record it changes. - **Exception variety:** duplicate, missing-evidence and amended-request cases differ in structure, not only in identifiers or wording. - **Scoring clarity:** each task has separate named checks, so a failed run identifies the behaviour that failed rather than returning one verdict. - **Split hygiene:** training and evaluation cases are marked, and no case appears in both. - **Disclosure review:** generated values are inspected for resemblance to real identifiers, rare combinations and source-specific details.