Skip to main content
STRIPED DONKEYWe do the heavy lifting.

Nairobi · People & society

Households.
Explore household structure and membership.

Explore household types, where households form and the dates that give those relationships context.

Public sample available

Read certification →Read evidence →Read audit findings →
← Back to Nairobi certification records

Published domain facts

Households
1,790,037
Current household members
4,739,703
Avg. household size
2.65
Lifecycle events
4,412,712

Overview

Known limits

Household size remains below the cited reference. Lifecycle fixes and remarriage are documented; exact assignment methods remain internal. The guide reports an ungenerated Patient household relationship. Households are synthetic, not civil records.

Review the source limits →
Full scope reference 2 documented sections
Published domain scope.

Published domain scope.

Track household formation, membership and family changes through time. Households share the Demographics data structure and persistent citizen identities.

  • Compare household types across wards
  • Inspect formation dates and dissolution status
  • Review the scope of membership histories
Households
1,790,037
Current household members
4,739,703
Avg. household size
2.65
Lifecycle events
4,412,712
Domain scope.

Domain scope.

Inspect the published scope and deployment boundaries.

Read the published detail

The household generated at the beginning of the city is not necessarily the household the citizen belongs to today. FCTE models formation, marriage, departure, childbirth, widowhood, divorce and remarriage as changing relationships between the same persistent synthetic citizens — not as static groupings assigned once and left alone.

Households live inside Demographics' own data structure (Household / HouseholdMember) — this page documents them on their own because the lifecycle is the story, not because they're a separate engine domain.

Nairobi City Twin™ · 1940–2026

Demographics'

Samples & fields

Published sample records.

Household membership sample · rows and field definitions

Household membership sample

Household codeHousehold typeWard nameFormation dateHead nameHead membership start dateCurrent member countHistorical departures
HH000503999SinglePersonGithurai1949-09-17Gichunge Gichunge1995-03-0410
HH001538568ExtendedPumwani1949-12-20Mwendwa Sagini2003-05-2930
HH000091822CompoundKawangware1950-10-13Furaha Gathura1992-11-1560

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

Published field definitions · 8 visible fields

Household code

The supplied household code.

Original field: HouseholdCode
Example: HH000503999

Household type

The recorded household structure.

Original field: HouseholdType
Example: SinglePerson

Ward name

The supplied ward name.

Original field: WardName
Example: Githurai

Formation date

The supplied household formation date.

Original field: FormationDate
Example: 1949-09-17

Head name

The supplied name of the current household head.

Original field: HeadName
Example: Gichunge Gichunge

Head membership start date

The membership start date supplied for the current household head.

Original field: HeadMembershipStartDate
Example: 1995-03-04

Current member count

The supplied count of current members.

Original field: CurrentMemberCount
Example: 1

Historical departures

The supplied total of historical departures; individual departure dates are not included.

Original field: HistoricalDepartures
Example: 0

CSV ↓JSON ↓PARQUET ↓Field guide CSV ↓Field guide JSON ↓Inspect the dataset →
Complete published field dictionary · 44 fields
HouseholdIdHousehold reference
The supplied identifier of this household.Example: 21797
HouseholdCodeHousehold code
The supplied household code.Example: HH000503999
HouseholdTypeHousehold type
The recorded household structure.Example: SinglePerson
SnapshotDateSnapshot date
The supplied reference date for the sample. Hidden from displayed sample columns; preserved in source downloads.Example: 2026-07-02
FormationDateFormation date
The supplied household formation date.Example: 1949-09-17
HouseholdAgeYearsHousehold age years
Household age in years at the supplied snapshot date.Example: 76
WardIdWard reference
The supplied ward identifier.Example: 26
WardNameWard name
The supplied ward name.Example: Githurai
WardIncomeMultiplierWard income multiplier
Ward income multiplier as supplied in the extract.Example: 0.85
WardInformalSectorRateWard informal sector rate
Ward informal-sector rate as supplied in the extract.Example: 0.45
HeadCitizenIdHead resident reference
The resident identifier supplied for the current household head.Example: 4639940
HeadNameHead name
The supplied name of the current household head.Example: Gichunge Gichunge
HeadAgeHead age
Head age at the supplied snapshot date.Example: 31
HeadGenderHead gender
The supplied gender value of the current household head.Example: M
HeadMembershipStartDateHead membership start date
The membership start date supplied for the current household head.Example: 1995-03-04
SpouseCitizenIdSpouse resident reference
The resident identifier supplied for the current spouse, when present.Example: 1377047
SpouseNameSpouse name
The supplied name of the current spouse.Example: Karani Gathura Mwangi
SpouseAgeSpouse age
Spouse age at the supplied snapshot date, when recorded.Example: 43
SpouseGenderSpouse gender
The supplied gender value of the current spouse.Example: M
SpouseMembershipStartDateSpouse membership start date
The membership start date supplied for the current spouse, when recorded.Example: 2006-08-14
CurrentMemberCountCurrent member count
The supplied count of current members.Example: 1
HeadCountHead count
Current members with the Head role.Example: 1
SpouseCountSpouse count
Current members with the Spouse role.Example: 0
ChildCountChild count
Current members with the Child role.Example: 0
OtherMemberCountOther member count
Current members in other household roles.Example: 0
MaleCountMale count
Current members recorded as male.Example: 1
FemaleCountFemale count
Current members recorded as female.Example: 0
Age0To4CountMembers aged 0–4
Current members aged 0 to 4.Example: 0
Age5To14CountMembers aged 5–14
Current members aged 5 to 14.Example: 0
Age15To24CountMembers aged 15–24
Current members aged 15 to 24.Example: 0
Age25To64CountMembers aged 25–64
Current members aged 25 to 64.Example: 1
Age65PlusCountMembers aged 65+
Current members aged 65 or older.Example: 0
DependencyAgeCountDependency age count
The source count of dependency-age members.Example: 0
WorkingAgeCountWorking age count
The source count of working-age members.Example: 1
DependencyRatioPctDependency ratio (%)
Dependency-age members per 100 working-age members, as supplied.Example: 0.00
YoungestMemberAgeYoungest member age
Age of the youngest current member, as supplied.Example: 31
OldestMemberAgeOldest member age
Age of the oldest current member, as supplied.Example: 31
AverageMemberAgeAverage member age
Mean age of current members, as supplied.Example: 31.00
LifetimeMembershipRowsLifetime membership rows
The supplied lifetime count of membership rows; these individual rows are not included.Example: 1
HistoricalDeparturesHistorical departures
The supplied total of historical departures; individual departure dates are not included.Example: 0
FirstRecordedMembershipDateFirst recorded membership date
Earliest recorded membership date, as an aggregate endpoint. It is not a separate identified member event.Example: 1995-03-04
MostRecentMembershipActivityDateMost recent membership activity date
Latest membership activity date, as an aggregate endpoint. The specific activity is not identified.Example: 1995-03-04
HouseholdLifecycleOriginHousehold lifecycle origin
The supplied classification of how the household originated.Example: Baseline
HasMembershipHistoryMembership history recorded
Whether the source flags membership history.Example: 0
Download complete field guide JSON ↓
Additional records and schema context 1 documented sections
From a household code to a real membership history.

From a household code to a real membership history.

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

Inspect the published definitions and release context.

Read the published detail

Every row above is real and published on Nairobi release — not illustrative. See Follow the Citizen above for the full traced timeline.

Direct synthetic records from the current City Twin™ release. No record represents a real family.

Explore Household Data →

Public entity familyRepresentsDisclosure boundary
Household identitySynthetic household formation and closure contextPhysical household fields are controlled
Membership journeyRelationship roles and residence spans through timeExact reassignment sequence and fields are controlled
Housing connectionTenure and housing contextPhysical join path is controlled
Lifecycle contextBirth, death, marriage and migration effects on household stateTransition mechanics are controlled
Household IDHouseholdCodeFormationDateStatus
Explore Household Data →

Connections

Known and possible relationships

Inspect the published definitions and release context.

Domain or contextRelationship and published scope
DemographicsCitizen / Death (age-eligibility and mortality-triggered widowhood) CitizenOrigin (Pregnancy childbirths tagged NaturalizationPath = 'Pregnancy')
Wardhousehold placement, ward-aware since the v3.4/v1.1 generation model fix
WaterMeter / Billing (~70% of Nairobi's meters, Nairobi release-integrated)
HealthPatient (field exists; Patient has 0 rows, Nairobi)
Social ProtectionWIDOW beneficiary type exists, but is not created or triggered by Widowhood's real death-cascade mechanism above
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
DemographicsCitizen / Death (age-eligibility and mortality-triggered widowhood) CitizenOrigin (Pregnancy childbirths tagged NaturalizationPath = 'Pregnancy')
Wardhousehold placement, ward-aware since the v3.4/v1.1 generation model fix
WaterMeter / Billing (~70% of Nairobi's meters, Nairobi release-integrated)
HealthPatient (field exists; Patient has 0 rows, Nairobi)
Social ProtectionWIDOW beneficiary type exists, but is not created or triggered by Widowhood's real death-cascade mechanism above
DemographicsHousingSocial ProtectionHealthWater

Domain guide

Households · 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

Household size remains below the cited reference. Lifecycle fixes and remarriage are documented; exact assignment methods remain internal. The guide reports an ungenerated Patient household relationship. Households are synthetic, not civil records.

Read the source limits →
Open PDF ↗Download recorded guide ↓
Accessible HTML reference 4 documented sections
Modelled entities.

Modelled entities.

Explore the entities and states represented by this domain.

Read the published detail

FCTE Households represent household composition, headship and membership as it exists for real synthetic citizens today — and as it existed for them before today, one row per membership span, not one row per citizen.

A longitudinal household identity with formation and closure context — every household is either active or historically closed.

Membership spans capture relationship role and residence period so a citizen can be followed through changing household composition.

Exactly one current Head per active household (certification check/C18), reassigned automatically when a household's circumstances change.

TwoParent, SingleMother, SingleFather, ChildHeaded, Extended, SinglePerson and Other — a measured classification, not a generated label (certification check).

Formation, departure, marriage, childbirth, widowhood, divorce and remarriage — represented as distinct longitudinal lifecycle mechanisms and independently auditable.

The same Household ID is read by Housing (Tenancy, RentPayment, Eviction) and registered for Health (Patient) — one identity, several real roles.

Household identity and membership belong to the shared Demographics lifecycle. This page documents household change separately because it is central to the longitudinal resident story, while internal architecture remains controlled.

HousingHealthDemographics
Households don't stay the way they were generated.

Households don't stay the way they were generated.

Inspect the published definitions and release context.

Read the published detail

The records below are representative synthetic release examples. Pick a resident to trace the public household journey without exposing the underlying physical membership rows.

Female, DOB 1999-11-25, Nairobi. Four household rows, four different roles, under six years — a marriage, a divorce, and a remarriage eleven days after the divorce closed her single-person household.

Living as a Child in a bulk-generated household before marrying out.

Marriage-formed household — closed after 5½ years by divorce.

Divorce-formed single-person household — lasted 11 days before remarriage.

Remarriage-formed household — her current, live residence today.

Female, DOB 2001-10-18, Nairobi. Married into household HHLM001887863 in 2020, had a son in 2021, and departed alone after a 2026 divorce — custody of their son stayed with the father, who kept the household.

Born into this household; left at 18 to marry.

Marriage-formed household with Citizen 1887863 (Head). Son Citizen 5022698 born here 2021-02-16 (naturalization-path context = 'Pregnancy') — a real childbirth into an existing household, not a new household code.

Divorce-formed single-person household. Her ex-husband (1887863) kept HHLM001887863 and full-time custody of their son — an independent per-child custody roll, not automatic.

Male, DOB 1998-02-15, Nairobi. No marriage, no divorce — just an adult child leaving the household he was born into, as represented by the household departure mechanism.

Born into this household; departed independently at age 19 — no marriage, no death, just an adult child moving out.

Departure-formed single-person household — his current, live residence today.

Trace a Citizen Yourself →

Trace a Citizen Yourself →
Lifecycle transitions are represented as longitudinal events, not static flags.

Lifecycle transitions are represented as longitudinal events, not static flags.

Inspect the published definitions and release context.

Read the published detail

Six of these run as an incremental pass over the existing population; the seventh (Formation) only runs once, at city origin. Dissolution is not an eighth mechanism — it is the shared consequence, the Dissolve Household If Empty step, triggered automatically by Widowhood or Remarriage when a household's last current member leaves.

Households are initialized with city- and area-aware demographic context. Exact starting volumes, assignment sequence and generation methods are controlled.

A Child-role citizen 18+ leaves to head a brand-new single-person household.

Two Child-role citizens marry via age-banded propensity, rank-aligned by DOB within their ward.

Household roles are updated consistently after a death so longitudinal household state remains coherent. Exact reassignment sequence and transition logic are controlled.

Departing spouse forms a new single household; each child independently rolls custody — siblings can split between parents.

Closes and dissolves both partners' prior single households before forming one new joint household.

A known v1 boundary, disclosed: Remarriage currently excludes widowed parents who kept custody of a still-populated household.

A population, then a lifecycle laid on top of it.

A population, then a lifecycle laid on top of it.

Review the documented generation rules and assumptions.

Read the published detail

Household formation begins from city- and area-aware demographic context, then lifecycle changes are applied through controlled incremental passes. Release integrity checks protect chronology and relationship consistency. Exact staging, transaction, pairing and row-level repair logic are intentionally not published.

Mean household size (2.77, Nairobi), family structure mix and every lifecycle-event count on this page, verified live via analysis-ready.

Widowhood's child-headed household outcome (13.4% of all Nairobi households) — a direct, measured consequence of the Death + cascade mechanism, not separately generated.

Household size, composition, relationship structure and lifecycle-event distributions are calibrated to published demographic evidence and city-level certification targets. Exact matching weights and transition rules remain controlled.

Individual synthetic assignments are generated under controlled domain rules. Exact sampling, assignment order and parameterization are not published.

View Household Generation Methodology →

Realism reference band for certification check.

Fertility grounding for the Pregnancy mechanism, per city.

certification check — a measurement, not a target; no cited external benchmark yet.

Structural (certification check–C21) and realism (certification check–R08) batteries run live in Nairobi.

Open Household Source Catalogue →

Review Nairobi release history →Open Household Source Catalogue →

Evidence & limits

Scope and known limits

Household size remains below the cited reference. Lifecycle fixes and remarriage are documented; exact assignment methods remain internal. The guide reports an ungenerated Patient household relationship. Households are synthetic, not civil records.

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

Known limits.

Household size remains below the cited reference. Lifecycle fixes and remarriage are documented; exact assignment methods remain internal. The guide reports an ungenerated Patient household relationship. Households are synthetic, not civil records.

Read the published detail

Nairobi's 2.77 sits close to, but still under, its own KNBS 2019 Nairobi reference of ~2.9. Disclosed here, not glossed over.

Several integration defects affecting lifecycle consistency were identified and repaired during release hardening. Public history records the affected behavior and resolution; exact staging, transaction, ordering and row-repair mechanics remain internal.

The lifecycle model was expanded so remarriage can be represented without forcing an artificial household recreation. The behavioral fix is public; exact pairing and household-assignment logic is not.

Earlier city releases differed in a few household-history capabilities. The public model is now normalized at the semantic level; physical migration steps and field-level changes are intentionally withheld.

patient-to-household relationship exists in the data structure but Patient itself has 0 rows on Nairobi today — registered, not yet generated.

No synthetic household corresponds to a real family. Every citizen, relationship and lifecycle transition on this page is statistically generated, not drawn from real civil records.

View All Household Limitations →

View All Household Limitations →
Does the synthetic lifecycle resemble a real household?

Does the synthetic lifecycle resemble a real household?

Inspect the published definitions and release context.

Read the published detail

Both structural and realism certification pass with 0 FAIL in Nairobi today — a stronger position than most domains at this stage, achieved after several real bugs were found live and fixed. Two disclosed gaps remain, not hidden.

Open Household Realism Report →

The full certification check–C21 structural battery plus the 8-check certification check–R08 realism battery run live against Nairobi release.

A separate 8-check realism suite (certification check–R08) passes 8/8 on this City Twin™ today, with 0 FAIL and 0 WARN.

Explore Every Household Check →

  • certification check — one current membership per citizen: 0 violations, Nairobi
  • certification check — at most one current Spouse per household: 0 violations, Nairobi
  • certification check — JoinDate never precedes member's own DOB: 0 violations, Nairobi
  • certification check — every Head has a matching HouseholdMember row: 0 violations
  • certification check — dissolved households carry zero current members: 0 violations
  • certification check — chronological ordering across multi-hop chains: 0 violations, Nairobi
  • certification check — 80+ mortality-cohort consistency check: PASS, Nairobi (floor 15%)
  • certification check — mean household size within 1.5–7.0: PASS, Nairobi
  • certification check / R03 — birth/death rates within UN WPP 2022 bands: PASS, Nairobi
  • certification check — family structure measurement (7 categories): informational, no FAIL condition
Open Household Realism Report →Explore Every Household Check →
The lifecycle got more honest with every real bug found.

The lifecycle got more honest with every real bug found.

Inspect the published definitions and release context.

Read the published detail

View Full Demographics Change Log →

View Full Demographics Change Log →

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.

Request this domain Browse datasets
Published access and recorded examples 1 documented sections
Recorded example.

Recorded example.

Explore the supplied synthetic example and its source references.

Read the published detail

Formed by one of the seven Household Lifecycle mechanisms — Housing waits for it, doesn't create it.

A housing occupancy relationship opens in the same area, carrying tenure and rent context through time.

The household's own composition changes; Housing reacts only when the household itself dissolves.

Multiple Tenancy rows per unit stay queryable, ordering enforced by repair workflows and H14.

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

Explore Nairobi city overview →Browse Nairobi certification records →See the Evidence →Review licensing & delivery details →Configure full-domain access →Browse Households Data →HousingExplore Multi-Domain Access →
Contact SD for supporting artifacts →