Domain scope
Explore meters, service zones and installation context before reviewing the documented reliability and billing coverage.
Read the published guide →Lagos · Utilities & digital city
Explore meters, service zones and installation context before reviewing the documented reliability and billing coverage.
Public sample available
Published domain facts
Explore meters, service zones and installation context before reviewing the documented reliability and billing coverage.
Read the published guide →Public sample available
Preview samples & fields →Water access does not establish a causal disease mechanism or direct Business identity links. Certification results are shown only when captured; defined checks alone do not establish a PASS.
Review the source limits →Inspect water supply, meters, service zones, billing and outages. Cross-domain relationships apply only where the release supports them.
Inspect the published scope and deployment boundaries.
FCTE exposes a semantic water-service model spanning supply, storage, distribution, customer service and outages. The public site shows the analytical chain without publishing physical table layouts, field mappings, generation targets or orchestration.
Household water-service context is represented directly. Business and health relationships are only presented where the release supports them; contextual overlap is not described as a causal mechanism.
Every public claim is backed by release evidence, regulatory context or certification. internal construction methods remain controlled.
Lagos City Twin™
| Meter type | Service zone | Smart meter | Prepaid meter | Install date | Household type | Ward reference | Household reference |
|---|---|---|---|---|---|---|---|
| Household connection | IKORODU | No | No | 1957-06-30 | Compound | 76 | 45880 |
| Commercial premises | INFORMAL | No | No | 2006-06-19 | Compound | 144 | 105077 |
| Household connection | LEKKI | No | No | 1981-10-16 | Nuclear | 108 | 124961 |
Showing 3 of 100 sample rows and 8 of 8 fields. “Not recorded” is a display label; downloads retain original values.
The category or type assigned to the meter in the source record.
Original field: MeterType
Example: Household connection
The service area assigned to the connection or subscriber.
Original field: ServiceZone
Example: IKORODU
Whether the meter is recorded as a smart meter.
Original field: IsSmart
Example: No
Whether the meter is recorded as using prepaid billing.
Original field: IsPrepaid
Example: No
The date recorded for the install event.
Original field: InstallDate
Example: 1957-06-30
The recorded household structure, such as a single-person or extended household.
Original field: HouseholdType
Example: Compound
The reference used to identify the ward associated with this record.
Original field: WardId
Example: 76
The reference used to identify the household associated with this record.
Original field: HouseholdId
Example: 45880
HouseholdIdHousehold referenceWardIdWard referenceHouseholdTypeHousehold typeMeterTypeMeter typeServiceZoneService zoneIsSmartSmart meterIsPrepaidPrepaid meterInstallDateInstall dateInspect the published definitions and release context.
Inspect the published definitions and release context.
| Domain or context | Relationship and published scope |
| Supply context | service area |
| Service area | household service |
| Household service | consumption / billing |
| Reliability events | service area |
| Business identity linkage | not uniformly asserted |
| Health relationship | contextual unless explicitly modeled |
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 |
| Supply context | service area |
| Service area | household service |
| Household service | consumption / billing |
| Reliability events | service area |
| Business identity linkage | not uniformly asserted |
| Health relationship | contextual unless explicitly modeled |
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.
Water access does not establish a causal disease mechanism or direct Business identity links. Certification results are shown only when captured; defined checks alone do not establish a PASS.
Read the source limits →Explore the entities and states represented by this domain.
The public Water domain presents a common semantic service chain rather than the underlying internal data design. Lagos includes regulator-aligned service and tariff context.
Treatment and source context anchor the city water system.
Reservoir and storage context supports service-area analysis.
Network and service-area context connect infrastructure to neighborhoods.
Household-linked access, consumption and billing can be studied longitudinally.
Outage and restoration context separates access from actual service quality.
Household, housing and health can be compared where the release supports a valid relationship.
Synthetic by design: this is a calibrated analytical representation of water service, not real customer or meter records.
━━ Public semantic relationship · ┄┄ Disclosed boundary.
Inspect the published definitions and release context.
The public traversal shows the service lifecycle semantically. Exact connection probabilities, target volumes, starting configurations and orchestration are withheld.
The Lagos release represents water as a connected longitudinal service context. Internal generation order and scale parameters remain controlled.
Inspect the published definitions and release context.
The public site exposes area-level water access and service context, while exact row targets, connection probabilities, temporal thinning strategies and generation sequencing remain private.
Defined certification checks cover completeness, billing plausibility, service timing and geographic coverage; exact thresholds are controlled.
Actual PASS/FAIL outcomes are only claimed when captured by the catalog. Defined rules and deployed behavior are not treated as the same thing.
Review the documented generation rules and assumptions.
The public Water domain shows the queryable service model while keeping generation workflows, target volumes, starting configurations, internal relationships and reconciliation methods private.
| Public entity family | Represents | Disclosure boundary |
| Supply & storage | Source, treatment and storage context | Internal asset-design assumptions are controlled |
| Distribution | Network/service-area context | Physical topology is not published |
| Metering & billing | Consumption and billing context through time | Exact target volumes, fields and formulas are controlled |
| Reliability & telemetry | Outage, quality and service-performance context | Operational simulation mechanics are controlled |
Water access does not establish a causal disease mechanism or direct Business identity links. Certification results are shown only when captured; defined checks alone do not establish a PASS.
Water access does not establish a causal disease mechanism or direct Business identity links. Certification results are shown only when captured; defined checks alone do not establish a PASS.
Water access and health outcomes can be compared geographically, but the current release does not claim a direct causal mechanism from water service into disease or outbreak generation.
Commercial and industrial service categories may exist without a direct relationship to a specific business identity. The marketplace does not infer one.
Certification results are only shown when captured; defined checks alone do not imply a PASS.
Commercial service categories do not imply a direct business identity relationship; public analyses should treat that as a model boundary.
Back to Domain Directory →
Inspect the published definitions and release context.
Certification categories and release maturity are visible. Exact thresholds, source queries, generation model logic and orchestration remain controlled.
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.
confirmed in the published source: water. Meter has 698,000 rows on Lagos today, versus 190,000 on Nairobi. The data structure is deployed; generation has not run here yet.
The same service model already live on Nairobi — source, distribution, metering and reliability context — is designed for Lagos but not yet populated.
Water is presented as a semantic city-service relationship; the internal dependency design remains private.
Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™