ktayl IS — Architecture at a Glance
If you read one page to understand ktayl, read this. It is the whole business-application architecture on a single screen: who uses it, the insurance value chain, the legacy core it wraps, the shared platforms (Data · AI · Documents), and the foundations everything runs on — plus a reading path into the detailed docs. Depth lives elsewhere; this is the mental model.
:::note One insurer, one IS — and a separate product ktayl-solution is a fictional commercial-lines (IARD / large-risk) insurer; everything here is its information system. Retrieva is a separate product (RNCP cert / DORA) that only runs on this platform — it is not a ktayl business app and appears nowhere below. :::
:::info Status legend (what's live vs not) — verified against the running cluster 2026-09-30 🟢 live in prod · 🔵 live on dev only · 🟡 partial (some pieces live) · ⚪ planned (not built yet). Only the tagged domains/platforms actually run; untagged arrows are the value-chain pipeline, not a status claim. The authoritative box-by-box status is the table under the picture. :::
The one picture
Read it top-down: people → the apps they touch → the insurance value chain (the business) → the legacy core that one domain wraps → the shared Data/AI/Document platforms → the foundations.
┌─────────────────────────────────────────┐
PEOPLE │ Underwriters · Claims handlers · Brokers │
│ Finance · Compliance · Ops │
└─────────────────────┬─────────────────────┘
│ browser-first, SSO (Authentik + MFA)
CHANNELS / APPS ┌─────────────────────▼─────────────────────┐
(how work gets done) │ Web apps · Underwriter/Claims workbench │
│ Broker portal · Digital workplace (M365-alt)│
└─────────────────────┬─────────────────────┘
│ every call: OIDC · RBAC · audit
══════════════ BUSINESS VALUE CHAIN (the insurer itself — Track A) ══════════════
DISTRIBUTION ─► UNDERWRITING ─► POLICY ADMIN ─► CLAIMS ─► BILLING ─► REINSURANCE
⚪ #13 🔵 #12 🟢 #6 🟢 #11 ⚪ #14 ⚪ #22
broker/CRM workbench contracts FNOL→ premium treaty/
submissions rating/quote endorsements settle finance cessions
feeds UW ▲ ⚪ RISK ENGINEERING #21 (risk survey → prevention) spans the chain ◆ ⚪ INTERNATIONAL PROGRAMMES #23 (master/local · DIC/DIL)
│ │
│ │ (Claims is delivered by wrapping a legacy)
══════════════ LEGACY SPINE — one deliberate initiative (Track C) — LIVE on dev+prod ══════════════
┌──────────────▼───────────────┐
│ GlobalCore (System of Record) │ MySQL* · Java · SOAP · batch
│ FROZEN · OUTSIDE k8s │ holds the CLAIMS domain
└──────────────┬───────────────┘ *simulated Oracle-era legacy (ADR-002)
ACL wraps it: │ SOAP→JSON (writes) · Debezium binlog→NATS JetStream (CDC)
┌──────────────▼───────────────┐
│ ktayl-claims (#11) = the ACL │ modern Claims, built AS the wrap — LIVE
│ + CQRS read-model (CNPG) │ reads = projection; writes = SOAP (ADR-008)
│ + Angular adjuster workbench │ nginx BFF → internal ACL (ADR-009)
└──────────────┬───────────────┘
│ clean domain events on NATS (never raw legacy access)
══════════════ SHARED PLATFORMS (serve every domain — transversal) ══════════════
┌───────────────────┬────────────────────────┬───────────────────────────┐
│ DATA / ACTUARIAL │ AI / AUTOMATION │ ENTERPRISE DOCUMENT PLATFORM│
│ #5 │ #4 · #18 · #19 │ #24 │
│ warehouse · BI │ RAG (docs) + SQL-tools │ parse→chunk→metadata→embed │
│ semantic/metrics │ (data) · Copilot (last) │ →vector DB · GED · e-sign │
└───────────────────┴────────────────────────┴───────────────────────────┘
also transversal: 🟡 INTEGRATION (#25 · API-GW/events/ETL) · ⚪ MDM (#20 · golden records) · 🟡 COMPLIANCE (#15 · AML/sanctions/obligations) · ⚪ ITSM (#16 · GLPI/CMDB)
══════════════ FOUNDATIONS (live) + GOVERNANCE (continuous — Track B) ══════════════
k3s · GitOps (ArgoCD/Kargo) · IaC (OpenTofu) · Observability (OTel/Prom/Grafana/Tempo)
Identity (Authentik) · Secrets (Vault/ESO) · Supply-chain (cosign/SBOM/Trivy)
GOVERNANCE gate every domain clears: regulatory impact · AI-Act tier · NFR + security + resilience
What's live vs planned
The single source of truth for the picture above — every box, with its verified status (checked against the running cluster on 2026-09-30, not the roadmap). 🟢 prod · 🔵 dev only · 🟡 partial · ⚪ planned.
| Box | Status | Note |
|---|---|---|
| Policy Admin #6 | 🟢 prod | the first live core system (dev+prod) |
| Claims #11 — ACL + Debezium CDC + CQRS read-model + adjuster workbench | 🟢 prod | the legacy-spine wrap, live end-to-end (dev+prod) |
| Underwriting #12 | 🔵 dev | intake→rating→quote→bind + workbench UI live on dev; prod promotion pending |
| Distribution / CRM #13 · Billing #14 · Reinsurance #22 | ⚪ planned | scaffold / no app yet |
| Data / Actuarial #5 | 🟡 partial | Metabase BI + CNPG live (Slice 1); warehouse / semantic layer / actuarial planned |
| AI / Automation #4 · #18 · #19 | 🟢 prod | LiteLLM · Langfuse · Qdrant · RAG · LangGraph/CrewAI agents — mature |
| Enterprise Document #24 | 🟡 partial | e-sign + storage + RAG ingest live (Docuseal/Nextcloud); records-mgmt DMS planned |
| Integration #25 | 🟡 partial | NATS / Temporal / n8n engines live; API + event catalogue + BPM/approvals planned |
| MDM #20 | ⚪ planned | golden records parked — the keystone gap for cross-domain (customer) analytics |
| Risk Engineering #21 | ⚪ planned | scaffold; risk survey → prevention recommendations → feeds underwriting (the P1 insurability pivot) |
| International Programmes #23 | ⚪ planned | scaffold (ktayl-ip-portal backlog); master/local policies · DIC/DIL · PO↔SO premium/claims flows |
| Compliance & Enterprise Risk #15 | 🟡 partial | obligations register (doc) + DORA pattern proven via Retrieva; AML/sanctions screening planned |
| ITSM #16 | ⚪ planned | scaffold; GLPI (ITIL v4) + CMDB — not yet live |
| Foundations — k3s · GitOps (ArgoCD/Kargo) · Observability · Identity · Secrets · Supply-chain | 🟢 prod | mature |
Reading the value chain honestly: it is live at both ends (Policy + Claims in prod) with the operational middle (Underwriting on dev; Pricing/Billing planned) still in progress — not a fully running end-to-end insurer yet.
The three tracks (why nothing is scattered)
Every item on the roadmap is in exactly one of three parallel tracks — this is the organising idea:
| Track | What it is | Contains |
|---|---|---|
| A — Business build | the insurance value chain, built domain by domain | Distribution #13 → Underwriting #12 → Policy Admin #6 (live) → Claims #11 (live) → Billing #14 → Reinsurance #22 · + Risk Engineering #21 · International Programmes #23 (value-chain) · Compliance #15 (governance-adjacent) · ITSM #16 (enterprise-IT) |
| B — Governance | the gate every Track-A build clears (not a phase) | regulatory impact · AI-Act tier · NFR/security/resilience by design |
| C — Modernization lab | the legacy-wrap muscle, feeding real integration skill into A | GlobalCore (legacy core) + the ktayl-claims ACL + GenApp M1–M4 |
Foundations (platform #3, AI #4, digital workplace #10) are live and underpin all three.
How every domain is built (one repeatable recipe)
1. FDE playbook → understand the domain (process, users, pain, data, KPIs)
2. BMAD spec+stories → the implementation contract
3. Thin end-to-end slice → (uses Track-C wrap patterns when it touches the legacy)
4. Governance gate → Track-B: regulatory impact + AI-Act tier + NFR/security/resilience
5. Deploy (GAP wrapper chart) → iterate
So the docs aren't a pile of apps — they're one architecture, three tracks, one recipe per domain.
Reading path (where to go next)
| You want to understand… | Read |
|---|---|
| What to build next / the tracks | 🧭 IS Build Roadmap |
| The functional target (12 domains + 4 layers) + the legacy spine | 🏛 EA Blueprint |
| Every app, its stack + status | Business Applications Catalog |
| The legacy-core wrap (GlobalCore + MySQL + Claims — LIVE)* | Legacy-Core Modernization |
| How AI is applied (RAG vs SQL-tools, the copilot) | AI-First Operating Model |
| Regulation & compliance-by-design | Regulatory Operating Model |
| A worked domain (deep-dive) | Underwriting FDE Playbook · Policy Service · Legacy-Core Modernization / Claims |
One-line takeaway: ktayl is a greenfield-modern insurer whose value chain is live at both ends — Policy #6 and Claims #11 in prod — with the operational middle (Underwriting on dev; Pricing/Billing planned) still in progress, all built domain-by-domain on a mature k8s platform, with one deliberate legacy spine (Claims via GlobalCore/MySQL, simulated) — live end-to-end to prove real enterprise modernization — all clearing a continuous governance gate.