Skip to main content
STRIPED DONKEYWe do the heavy lifting.

Lagos · Economy & commerce

Insurance.
Explore policies, coverage and claims context.

Start with the published policy sample, then review the documented relationships between coverage, residents and claims.

Public sample available

Published domain facts

Structural Certification Checks, Lagos (data population in progress)
1 PASS / 14 N/A
Policy, Coverage & Claims Context
Connected
Real Nigerian NAICOM-Licensed Insurers
6
Nigeria InsuranceType Catalog, 3 Compulsory Lines
10

Overview

Domain scope

Start with the published policy sample, then review the documented relationships between coverage, residents and claims.

Read the published guide →

Known limits

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 →
Full scope reference 3 documented sections
Published domain scope.

Published domain scope.

Trace policies, coverage, premiums and claims for synthetic residents. Concurrent protections retain their separate policy and coverage references.

  • Compare policy coverage types
  • Inspect start years and policy status
  • Check which claim relationships are documented
Structural Certification Checks, Lagos (data population in progress)
1 PASS / 14 N/A
Policy, Coverage & Claims Context
Connected
Real Nigerian NAICOM-Licensed Insurers
6
Nigeria InsuranceType Catalog, 3 Compulsory Lines
10
Domain scope.

Domain scope.

Inspect the published scope and deployment boundaries.

Read the published detail

One citizen. Multiple protections. One connected life.

Lagos City Twin™ · 1940–2026

What Insurance actually models — and where it stops.

What Insurance actually models — and where it stops.

Inspect the published definitions and release context.

Read the published detail

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.

DomainCore QuestionKey Objects
InsuranceWhat coverage protects this citizen, and against what?Payer, policy, coverage, claim and premium context
HealthcareWhat clinical care did the citizen receive?Care encounter and diagnosis context
EmploymentDoes this citizen have employer-provided cover at all?Contract and employer context
BusinessIs the insurer itself a registered enterprise?Registered-enterprise context

Samples & fields

Published sample records.

Public sample · rows and field definitions

Public sample

StatusResident referenceInsurance plan tierHow coverage was obtainedSubmitted dateAmount claimedApproved amountAmount paid
Approved22250288BasicEmployer2023-05-29922415.00737932.000.00
Approved12404726BasicEmployer2021-10-1546548.0037238.400.00
Partial21551430BasicPersonal2026-03-04299905.00239924.000.00

Showing 3 of 100 sample rows and 8 of 9 fields. “Not recorded” is a display label; downloads retain original values.

Published field definitions · 8 visible fields

Status

The state recorded for the in this extract.

Original field: Status
Example: Approved

Resident reference

The synthetic resident reference used to connect this record to other city data.

Original field: CitizenId
Example: 22250288

Insurance plan tier

The tier assigned to the recorded insurance plan.

Original field: PlanTier
Example: Basic

How coverage was obtained

The recorded route through which the insurance coverage was obtained.

Original field: AcquisitionType
Example: Employer

Submitted date

The date recorded for the submitted event.

Original field: SubmittedDate
Example: 2023-05-29

Amount claimed

The amount requested in the recorded insurance claim, in local currency.

Original field: ClaimAmount
Example: 922415.00

Approved amount

The amount approved in the source record, in local currency.

Original field: ApprovedAmount
Example: 737932.00

Amount paid

The amount recorded as paid, in local currency.

Original field: PaidAmount
Example: 0.00

Complete published field dictionary · 9 fields
CitizenIdResident reference
The synthetic resident reference used to connect this record to other city data.Example: 22250288
PlanTierInsurance plan tier
The tier assigned to the recorded insurance plan.Example: Basic
AcquisitionTypeHow coverage was obtained
The recorded route through which the insurance coverage was obtained.Example: Employer
SubmittedDateSubmitted date
The date recorded for the submitted event.Example: 2023-05-29
StatusStatus
The state recorded for the in this extract.Example: Approved
ClaimAmountAmount claimed
The amount requested in the recorded insurance claim, in local currency.Example: 922415.00
ApprovedAmountApproved amount
The amount approved in the source record, in local currency.Example: 737932.00
PaidAmountAmount paid
The amount recorded as paid, in local currency.Example: 0.00
FraudFlagClaim flagged for fraud
The synthetic indicator showing whether the claim was flagged for possible fraud.Example: NONE
Download complete field guide JSON ↓
Additional records and schema context 1 documented sections
From a company to a citizen's claim history.

From a company to a citizen's claim history.

Inspect the published definitions and release context.

Read the published detail

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 familyRepresentsDisclosure boundary
Payer & product contextInsurer/payer and policy-product contextPhysical company/policy fields are controlled
Coverage relationshipResident protection and acquisition contextPhysical uniqueness constraints and keys are controlled
Premium contextPremium-payment history and status contextExact payment fields and duplicate rules are controlled
Claims contextClaim amount/outcome/cause and care contextAdjudication fields and design are controlled
Coverage TypeProduct ContextAcquisitionStatus
Motor VehicleCompulsory / personal protectionPersonalActive
Group LifeEmployer-sponsored protectionEmployerActive
Individual LifePersonal life protectionPersonalActive

Connections

Known and possible relationships

Inspect the published definitions and release context.

Domain or contextRelationship and published scope
Resident coverage relationshiprelease integrity checked
Businessinsurer/payer enterprise context where available; physical linkage and reconciliation are controlled
Demographicscoverage and claim activity is bounded by the resident lifecycle
TransportNigeria's Motor line AccidentClaim links to Accident (deferred relationship, added post-domain)
EmploymentEmployment context (employer-sponsored coverage is represented conceptually; internal linkage is not asserted publicly)
Full relationship reference 1 documented sections
Known and possible relationships.

Known and possible relationships.

Inspect the published definitions and release context.

Read the published detail

Connections follow the published domain scope. Optional, contextual and planned relationships retain their stated limits below.

Domain or contextRelationship and published scope
Resident coverage relationshiprelease integrity checked
Businessinsurer/payer enterprise context where available; physical linkage and reconciliation are controlled
Demographicscoverage and claim activity is bounded by the resident lifecycle
TransportNigeria's Motor line AccidentClaim links to Accident (deferred relationship, added post-domain)
EmploymentEmployment context (employer-sponsored coverage is represented conceptually; internal linkage is not asserted publicly)

Domain guide

Insurance · archived guide edition

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.

Published scope and limits

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 →
Accessible HTML reference 2 documented sections
One citizen. Multiple protections. One connected life.

One citizen. Multiple protections. One connected life.

Inspect the published definitions and release context.

Read the published detail

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.

Lagos reflects Nigeria’s general insurance market structure.

Lagos reflects Nigeria’s general insurance market structure.

Inspect the published definitions and release context.

Read the published detail

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 →

DimensionNigeria (Lagos)
Core ModelGeneral P&C / life insurer
Companies6 NAICOM-licensed insurers
Product Catalog10-type InsuranceType, 3 compulsory
Claim LinkageClaimCauseCatalog (no clinical link)
Motor/Accident LineMotor Vehicle Insurance, Accident-linked
Beneficiary ModelingBeneficiary-share consistency represented as a public analytical rule
Fraud DetectionFraudFlag only, no baseline amount

Evidence & limits

Scope and known limits

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.

Evidence, findings and release history 2 documented sections
Known limits.

Known limits.

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 published detail

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 →

Does synthetic coverage resemble real insurance relationships?

Does synthetic coverage resemble real insurance relationships?

Inspect the published definitions and release context.

Read the published detail

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 →

  • Payer context — N/A, current release data not populated
  • Policy catalogue — N/A, current release data not populated
  • Coverage relationship integrity — N/A, current release data not populated
  • Claim value integrity — N/A, current release data not populated
  • Premium value & uniqueness — N/A, current release data not populated
  • Coverage chronology — N/A, policy and claim lifecycle data not currently populated
  • Beneficiary consistency — N/A where the Nigeria beneficiary extension is not active
  • Accident-line relationship — N/A until the prerequisite accident context is available
  • Resident-lifecycle boundary — PASS in the documented release state

Access & datasets

Scope your data request

Choose the records, dates and connected domains you need. Final availability, delivery scope and licensing are agreed with your quote.

Published access and recorded examples 1 documented sections
Recorded example.

Recorded example.

Published release reference · These recorded checks are not a current rerun.

Explore the supplied synthetic example and its source references.

Read the published detail

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™