Domain scope
Start with the published policy sample, then review the documented relationships between coverage, residents and claims.
Read the published guide →Lagos · Economy & commerce
Start with the published policy sample, then review the documented relationships between coverage, residents and claims.
Public sample available
Published domain facts
Start with the published policy sample, then review the documented relationships between coverage, residents and claims.
Read the published guide →Public sample available
Preview samples & fields →Catalog initialization was repaired; full-scale policy, claim and premium generation remains in progress in the documented release. Concurrent employer policies and the unconfirmed Employment link remain gaps. Unsupported checks report N/A. Figures are unsuitable for actuarial pricing or real underwriting.
Review the source limits →Trace policies, coverage, premiums and claims for synthetic residents. Concurrent protections retain their separate policy and coverage references.
Inspect the published scope and deployment boundaries.
One citizen. Multiple protections. One connected life.
Lagos City Twin™ · 1940–2026
Inspect the published definitions and release context.
Every capability below is backed by release evidence or certification; the physical design is intentionally generalized.
Insurer and payer context represented as public semantic entities.
Policy products carry coverage, premium and acquisition context linked to the issuing insurer. Exact physical fields and constraints are controlled.
A citizen may hold distinct active policy relationships concurrently while duplicate enrollment in the same policy remains prevented.
Claims carry amount, outcome and cause context appropriate to the policy line. Internal field-level design is not public.
Selected insurance lines can be analyzed alongside accident and premium-payment context through controlled semantic relationships.
Coverage and claim timing is checked against the citizen lifecycle so analytically impossible post-lifecycle records are not treated as valid.
Synthetic by design: FCTE insurance records are analytically representative coverage and claims data. They are not real policyholder records, real claims history, or a substitute for any insurer's or regulator's own data. The public data model claims only the capabilities described here; physical internal methods remain controlled.
Healthcare models the clinical encounter. Employment determines whether employer-provided cover exists. Insurance models the coverage relationship itself — the policy, the enrollment, and what happens when a claim is filed.
| Domain | Core Question | Key Objects |
| Insurance | What coverage protects this citizen, and against what? | Payer, policy, coverage, claim and premium context |
| Healthcare | What clinical care did the citizen receive? | Care encounter and diagnosis context |
| Employment | Does this citizen have employer-provided cover at all? | Contract and employer context |
| Business | Is the insurer itself a registered enterprise? | Registered-enterprise context |
| Status | Resident reference | Insurance plan tier | How coverage was obtained | Submitted date | Amount claimed | Approved amount | Amount paid |
|---|---|---|---|---|---|---|---|
| Approved | 22250288 | Basic | Employer | 2023-05-29 | 922415.00 | 737932.00 | 0.00 |
| Approved | 12404726 | Basic | Employer | 2021-10-15 | 46548.00 | 37238.40 | 0.00 |
| Partial | 21551430 | Basic | Personal | 2026-03-04 | 299905.00 | 239924.00 | 0.00 |
Showing 3 of 100 sample rows and 8 of 9 fields. “Not recorded” is a display label; downloads retain original values.
The state recorded for the in this extract.
Original field: Status
Example: Approved
The synthetic resident reference used to connect this record to other city data.
Original field: CitizenId
Example: 22250288
The tier assigned to the recorded insurance plan.
Original field: PlanTier
Example: Basic
The recorded route through which the insurance coverage was obtained.
Original field: AcquisitionType
Example: Employer
The date recorded for the submitted event.
Original field: SubmittedDate
Example: 2023-05-29
The amount requested in the recorded insurance claim, in local currency.
Original field: ClaimAmount
Example: 922415.00
The amount approved in the source record, in local currency.
Original field: ApprovedAmount
Example: 737932.00
The amount recorded as paid, in local currency.
Original field: PaidAmount
Example: 0.00
CitizenIdResident referencePlanTierInsurance plan tierAcquisitionTypeHow coverage was obtainedSubmittedDateSubmitted dateStatusStatusClaimAmountAmount claimedApprovedAmountApproved amountPaidAmountAmount paidFraudFlagClaim flagged for fraudInspect the published definitions and release context.
Representative semantic rows for the Lagos insurance model. These are synthetic examples, not policyholder records or a disclosure of the internal data structures.
Explore Coverage Data →
| Public entity family | Represents | Disclosure boundary |
| Payer & product context | Insurer/payer and policy-product context | Physical company/policy fields are controlled |
| Coverage relationship | Resident protection and acquisition context | Physical uniqueness constraints and keys are controlled |
| Premium context | Premium-payment history and status context | Exact payment fields and duplicate rules are controlled |
| Claims context | Claim amount/outcome/cause and care context | Adjudication fields and design are controlled |
| Coverage Type | Product Context | Acquisition | Status |
| Motor Vehicle | Compulsory / personal protection | Personal | Active |
| Group Life | Employer-sponsored protection | Employer | Active |
| Individual Life | Personal life protection | Personal | Active |
Inspect the published definitions and release context.
| Domain or context | Relationship and published scope |
| Resident coverage relationship | release integrity checked |
| Business | insurer/payer enterprise context where available; physical linkage and reconciliation are controlled |
| Demographics | coverage and claim activity is bounded by the resident lifecycle |
| Transport | Nigeria's Motor line AccidentClaim links to Accident (deferred relationship, added post-domain) |
| Employment | Employment context (employer-sponsored coverage is represented conceptually; internal linkage is not asserted publicly) |
Inspect the published definitions and release context.
Connections follow the published domain scope. Optional, contextual and planned relationships retain their stated limits below.
| Domain or context | Relationship and published scope |
| Resident coverage relationship | release integrity checked |
| Business | insurer/payer enterprise context where available; physical linkage and reconciliation are controlled |
| Demographics | coverage and claim activity is bounded by the resident lifecycle |
| Transport | Nigeria's Motor line AccidentClaim links to Accident (deferred relationship, added post-domain) |
| Employment | Employment context (employer-sponsored coverage is represented conceptually; internal linkage is not asserted publicly) |
Striped Donkey V5.89 - 7 September 2026
Counts, prices and “live/today” certification statements reflect this dated edition. They are not a current rerun or offer. The current scope, known limits and accepted quote take priority.
Catalog initialization was repaired; full-scale policy, claim and premium generation remains in progress in the documented release. Concurrent employer policies and the unconfirmed Employment link remain gaps. Unsupported checks report N/A. Figures are unsuitable for actuarial pricing or real underwriting.
Read the source limits →Inspect the published definitions and release context.
The public model supports concurrent coverage across genuinely distinct policy relationships while preventing duplicate enrollment in the same policy context. The physical uniqueness rules, repair history and internal logic are intentionally withheld.
Inspect the published definitions and release context.
Nigeria's extension models a general-lines insurer market — companies, compulsory-lines products, P&C/life claims with no clinical link at all. This is a substantive difference in the city-specific data model, not a cosmetic naming change.
Real NAICOM-registered insurers: Leadway Assurance (1970, Composite), AXA Mansard (1989, Composite), AIICO Insurance (1963, Life), Custodian Investment (1995, Non-Life), Coronation Insurance (1969, Composite), FBN Insurance (2010, Life). Three of the 10 InsuranceType lines are compulsory under Nigerian regulation: Motor Vehicle, Group Life (Employers), and Workman Compensation (NSITF).
Leadway Assurance (1970), AXA Mansard (1989), AIICO Insurance (1963), Custodian Investment (1995), Coronation Insurance (1969), FBN Insurance (2010) — each populated with a real NAICOM registration number.
Motor Vehicle Insurance, Group Life (Employers) and Workman Compensation (NSITF) are flagged IsCompulsory=1 — matching NAICOM's real compulsory-insurance regulation.
Open Insurance Evidence Catalogue →
| Dimension | Nigeria (Lagos) |
| Core Model | General P&C / life insurer |
| Companies | 6 NAICOM-licensed insurers |
| Product Catalog | 10-type InsuranceType, 3 compulsory |
| Claim Linkage | ClaimCauseCatalog (no clinical link) |
| Motor/Accident Line | Motor Vehicle Insurance, Accident-linked |
| Beneficiary Modeling | Beneficiary-share consistency represented as a public analytical rule |
| Fraud Detection | FraudFlag only, no baseline amount |
Catalog initialization was repaired; full-scale policy, claim and premium generation remains in progress in the documented release. Concurrent employer policies and the unconfirmed Employment link remain gaps. Unsupported checks report N/A. Figures are unsuitable for actuarial pricing or real underwriting.
Catalog initialization was repaired; full-scale policy, claim and premium generation remains in progress in the documented release. Concurrent employer policies and the unconfirmed Employment link remain gaps. Unsupported checks report N/A. Figures are unsuitable for actuarial pricing or real underwriting.
Two concurrent employer-provided policies for the same citizen (e.g. from concurrent formal employment at two employers) is a real, disclosed gap — deliberately deferred rather than silently forbidden by an overly broad rule. This is a known and disclosed limitation, not a hidden one.
Employer-sponsored coverage is represented conceptually. This page does not claim a confirmed, verified direct read from Employment's Contract rows into Coverage — that specific cross-domain link has not been confirmed in the data model.
Synthetic citizens and coverage records are not real people and carry no real personally identifiable information. This page makes no claims about compliance frameworks for handling real policyholder data.
Beneficiary and accident-line checks are Nigeria-extension concepts; they report N/A rather than PASS when the extension or prerequisite context is not active — by design, not as a hidden gap.
Fraud-analysis depth differs by city. The certification framework reports unsupported city-specific checks as N/A rather than treating them as defects; exact fields and reconciliation logic are controlled.
Claim amounts, approval rates and premium figures are analytically representative, not sourced from any real insurer's or regulator's actual claims experience. They should not be used for actuarial pricing or real underwriting decisions.
On 2026-08-07 a catalog-starting configuration gap was found on both City Twins that left Coverage, Claim and Premium Payment records unpopulated despite the generation job reporting success — the eligibility checks were correctly refusing to run against an empty policy catalog. The root cause has been fixed and the catalog re-initialized; full-scale generation of Coverage, Claim and Premium Payment records is in progress as of this release and not yet reflected in every figure on this page.
View All Insurance Limitations →
Inspect the published definitions and release context.
Insurance certification evaluates release-level structural, temporal and lifecycle consistency across payer, policy, coverage and claims context. Public results show the outcome and current data-availability state; physical constraints, deployment history and recovery mechanics are intentionally withheld.
Open Insurance Realism Report →
N/A is used deliberately when prerequisite data doesn't exist — never to hide a failure. As of 2026-08-06, that's true for nearly this entire battery: insurance data is currently empty in Lagos (0 FAIL either way, but only 1 of 15 checks is applicable to the current release state). The domain has previously been validated against populated release data. This page reports the current release state rather than substituting a last-known-good result.
Explore Every Insurance Check →
Choose the records, dates and connected domains you need. Final availability, delivery scope and licensing are agreed with your quote.
Read the terms for public previews and commercial orders before requesting your extract.
Published release reference · These recorded checks are not a current rerun.
Explore the supplied synthetic example and its source references.
120 real Policy rows exist today, naming a real Nigerian insurer — Leadway Assurance Company Ltd — across Life, Motor and Health (NHIS) product lines.
confirmed in the published source: Coverage, Claim and PremiumPayment all have 0 rows. The product catalog is real; no citizen-level enrollment, coverage or claim activity has been generated yet.
Employment or scheme enrollment → Policy selection → active Coverage → filed Claim is the designed model — shown as scope, not as a live result.
Risk becomes coverage. One citizen. Multiple protections. One connected life.
Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™