Domain Discovery Process
Step 1: Understand Context
Ask user:
- •What business problem are we solving?
- •What industry/domain are you in? (Banking, Insurance, Telecom, Healthcare, etc.)
- •What regulatory jurisdictions apply? (Australia, NZ, EU, US, etc.)
- •Are there specific industry standards to align with?
Step 2: Load Relevant Standards
Based on user's industry, load ONLY the applicable standards guidance:
| Industry | Load Standards |
|---|---|
| Banking/Financial Services | BIAN, ISO 20022 |
| Insurance | ACORD |
| Telecommunications | TM Forum |
| Healthcare | FHIR |
Example:
code
User: "We're building a financial crime model for a bank in New Zealand" AI: Loading BIAN and ISO 20022 standards...
Step 3: Load Relevant Regulators
Based on user's jurisdiction, load ONLY the applicable regulatory guidance:
| Jurisdiction | Load Regulators |
|---|---|
| Australia/NZ Banking | APRA, RBNZ, Basel, FATF |
| EU | GDPR, Basel |
| US Banking | FDIC, OCC, Basel |
| Global AML | FATF |
Example:
code
User: "We need to comply with APRA and RBNZ requirements" AI: Loading APRA, RBNZ, Basel, and FATF regulatory guidance...
Step 4: Identify Core Concepts
Ask user about key business concepts to model.
Use loaded standards to find mappings:
- •If BIAN loaded → Search for BIAN Business Objects
- •If ACORD loaded → Search for ACORD data models
- •If TM Forum loaded → Search for SID entities
Step 5: Propose Domain Structure
Create domain.md with:
- •Metadata block (include regulatory scope from loaded regulators)
- •Entity summaries with standard references
- •Governance metadata aligned with regulatory requirements
Step 6: Validate with User
Present domain summary and ask: "Does this capture the right concepts and scope for your {industry} domain in {jurisdiction}?"
Wait for approval before creating detail files.