Civil Registration.
Trace identity and registered life events.

FCTE ties the registration of vital and civil-status events — births, deaths and national identity — to the same synthetic citizen used across the City Twin™. This isn't a separate registry of imaginary documents. It's the administrative trail that already lives inside Demographics and Households: who was registered, when, and how completely.

Nairobi City Twin™ · 1940–2026

Civil Registration is presented as an administrative lifecycle layer connected to Demographics birth and death context and inside the Citizen identity record — surfaced here as its own domain because it answers a different question than either of those tables was built to answer on its own.

Every birth carries an IsRegistered flag and, when registered, a certificate-style number in the shape BR/000012345/NAI — generated alongside the birth, not bolted on afterward.

The same pattern applies to deaths — an IsRegistered flag and a DR/000012345/NAI-style number, so a death can be a real demographic event without necessarily being a registered civic one.

A NationalId and RegistrationDate represent when an eligible synthetic citizen enters the civic-identity record. Issuance is age-gated, and uniqueness is checked at release level.

Registration is not all-or-nothing. Coverage is ward-scaled, inversely tied to how informal a ward's economy is — matching the real pattern that informal, high-density areas register vital events less completely, not more.

The gap between an event happening and it being registered shrinks across seven historical eras — from a decade-scale lag before 1940 to a 60-day lag from 2010 onward, tracking the real shift from paper-based to digital administration.

Marriage and divorce change a citizen's household role and are dated events, but they carry no dedicated registration flag, certificate number, or completeness/lag model. This page does not claim otherwise.

Synthetic by design: FCTE civil-registration fields are analytically representative administrative data. They are not real birth certificates, death certificates, national ID numbers or marriage/divorce records, and no generated record should be read as evidence that a corresponding real event occurred.

Demographics models the underlying population event. Civil Registration models its administrative representation — whether that event left a formal civic record, and how long that took.

Representative synthetic Nairobi release rows shown at the public semantic level. Physical source identifiers and extraction paths are controlled.

Explore Civil Registration Data →

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

One synthetic citizen, one identity, several life events — each one leaving its own administrative trace.

The registration timestamp itself carries a real, progressive lag from BirthDate — long for citizens born before 1940, short for those born after 2010 — rather than always landing on the same day.

Certification requires DeathDate to fall strictly after the citizen's own date of birth and never in the future — a real, checked invariant, not an assumption.

Two distinct behaviors are genuinely modeled here — completeness (was it ever registered?) and timing (how long after the event?). Both vary; neither is a flat assumption.

The same seven-era lag ceiling applies to both Birth and Death registration timing — a real, symmetric design choice, not two independently tuned numbers.

Registration completeness: a 70% base rate, scaled by each ward's informal-sector share and clamped between 40% and 95% — so a ward with a larger informal economy shows measurably lower registration completeness, not higher. A 2026-07-15 fix corrected an inverted version of this formula that had briefly shown the opposite (informal wards appearing better-registered than formal ones).

Registration completeness for Marriage/Divorce: PLANNED, not implemented. No completeness or lag model exists for these events today — this page will not show one until it's real.

Kenya's citizen-generation history weights the 1963–1970 window as a registration-volume surge, explicitly citing independence and the real Kenya ID Act of 1967 as the modeled driver — not an unlabeled bump in the data.

Nairobi's registration history is modeled from its own historical event sequence rather than a generic shared timeline.

Registration completeness is ward-scaled today, not yet re-derived by decade on top of the historical citizen-generation eras above — a real distinction this page keeps separate rather than blurring together.

Open Civil Registration Evidence Catalogue →

Civil Registration has no dedicated certification battery of its own — its claims are certified by the same demographics checks that already validate Citizen, Birth, Death and household-lifecycle chronology, because those are the tables every registration field actually lives on.

Open Civil Registration Realism Report →

Civil Registration shares the Demographics review: 21 structural checks and 8 realism checks. Published Nairobi results from 2026-08-06 report all 21 structural checks as PASS or N/A (0 FAIL), and 8/8 realism checks passed (0 WARN).

Explore Every Demographics Check →

• certification check resident date of birth not in the future
• certification check civil-registration date not before DOB
• certification check No duplicate NationalId values — 0 duplicates Nairobi, re-verified 2026-08-06
• certification check birth date matches the citizen's own DOB
• certification check death date falls after the citizen's own DOB
• certification check death date not in the future

• certification check Every living citizen has exactly one current household role
• certification check At most one current Spouse per household; role dates are internally consistent
• certification check A dissolved household has no current members, and vice versa
• certification check A citizen's household transitions never overlap — a real live-caught defect (Remarriage computed before its own Divorce) that this check now guards against
• certification check A household join date never precedes the member's own birth

Marriage, Divorce, Widowhood and Remarriage change a citizen's household role with a real date, but no independent MarriageRegistration/DivorceRegistration table, certificate number, or completeness/lag model exists. This page will not claim one exists until it does.

NationalId is intentionally age-gated, so citizens without an ID are concentrated among younger ages. A NULL NationalId should therefore be read as an expected lifecycle state for many children, not as a registration failure.

Completeness is scaled by each ward's current informal-sector rate, not independently re-derived for each historical era on top of the citizen-generation history's own timeline. A citizen born in 1950 and one born in 2020 in the same ward share the same completeness formula today.

Synthetic registration records are data fields — a flag, a number, a date — not simulated birth certificates, death certificates, ID cards or any other legal document or credential.

No generated registration record should be interpreted as evidence that a corresponding real birth, death, marriage or divorce occurred to any real person.

Birth and death registration are represented at event level, but the model does not retain a persistent field identifying the exact registration office or channel that handled each event. Office-level administrative routing is therefore outside the current release boundary.

View All Civil Registration Limitations →

A real, registered Birth row — registration number BR/000000005/NAI.

A real NationalId on the same citizen, issued after their registered birth.

A real, registered Death row — registration number DR/000000005/NAI, closing this citizen's civic history at age 28.

Both registration numbers are real and published — the full civic-identity lifecycle this domain exists to track.

A life event becomes a civic record. One Resident ID. Multiple life events. Multiple civic records — where the model actually supports them.

Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™