Domain scope
Read sewer connection types, dates and active status alongside the household context in the published sample.
Read the published guide →Nairobi · Utilities & digital city
Read sewer connection types, dates and active status alongside the household context in the published sample.
Public sample available
Published domain facts
Read sewer connection types, dates and active status alongside the household context in the published sample.
Read the published guide →Public sample available
Preview samples & fields →Full active certification is not asserted. Sewer coverage is calibrated, not universal. Commercial categories do not establish Business identity links. Wastewater and Water are separate domains without a required data dependency.
Review the source limits →Inspect sewer connections, treatment context and levy billing. Wastewater is distinct from Water and has no hard Water dependency in this release.
Inspect the published scope and deployment boundaries.
FCTE represents wastewater through a household sewer-connection and levy layer : connection records, treatment-plant and sewer-line context, and recurring levy billing history. The public site shows the analytical chain without publishing physical table layouts, field mappings, generation targets or orchestration.
Household connection context is represented directly. This is a separate domain from Water — related in real-world infrastructure, but not treated as a hard dependency in this release.
Every public claim is backed by release evidence, regulatory context or certification. internal construction methods remain controlled.
Nairobi City Twin™
| Connection type | Connected date | Record active | Household type | Ward reference | Household reference |
|---|---|---|---|---|---|
| Residential sewer connection | 1971-07-17 | Yes | Compound | 85 | 30482 |
| Residential sewer connection | 1976-01-18 | Yes | Nuclear | 8 | 752096 |
| Shared facility sewer connection | 1999-12-26 | Yes | Nuclear | 10 | 1255852 |
Showing 3 of 100 sample rows and 6 of 6 fields. “Not recorded” is a display label; downloads retain original values.
The category or type assigned to the connection in the source record.
Original field: ConnectionType
Example: Residential sewer connection
The date recorded for the connected event.
Original field: ConnectedDate
Example: 1971-07-17
Whether the record is marked as active in the source record.
Original field: IsActive
Example: Yes
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: 85
The reference used to identify the household associated with this record.
Original field: HouseholdId
Example: 30482
HouseholdIdHousehold referenceWardIdWard referenceHouseholdTypeHousehold typeConnectionTypeConnection typeConnectedDateConnected dateIsActiveRecord activeInspect the published definitions and release context.
No live result is shown here. The proc chain is real and job-wired in the release; this catalog has not captured a completed run's actual row counts.
Inspect the published definitions and release context.
| Domain or context | Relationship and published scope |
| Treatment context | sewer line |
| Sewer line | household connection |
| Household connection | levy billing |
| Business identity linkage | not uniformly asserted |
| Hard dependency on Water | not asserted in this release |
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 |
| Treatment context | sewer line |
| Sewer line | household connection |
| Household connection | levy billing |
| Business identity linkage | not uniformly asserted |
| Hard dependency on Water | not asserted in this release |
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.
Full active certification is not asserted. Sewer coverage is calibrated, not universal. Commercial categories do not establish Business identity links. Wastewater and Water are separate domains without a required data dependency.
Read the source limits →Explore the entities and states represented by this domain.
The public Wastewater domain presents a common semantic service chain rather than the underlying internal data design. Nairobi's real sewer network reaches a minority of households, and this release's connection coverage is calibrated to reflect that rather than assuming near-universal reach.
Treatment-plant context anchors the city sewer-service model.
Sewer-line and zone context connect treatment capacity to neighborhoods.
Household-linked sewer connection and levy-billing context can be studied longitudinally.
Overflow and service-request context separates connection from actual service experience.
Connection coverage is calibrated against real infrastructure evidence rather than assumed to be near-universal.
Household and housing context can be compared where the release supports a valid relationship.
Synthetic by design: this is a calibrated analytical representation of sewer connection and billing, not real customer or asset 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 Nairobi release represents wastewater 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 zone-level sewer-connection context, while exact row targets, connection probabilities, temporal thinning strategies and generation sequencing remain private.
Certification maturity is incomplete in this release and is reported at outcome level without exposing deferred rule code or internal files.
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 Wastewater 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 |
| Treatment & network | Treatment-plant and sewer-line context | Internal asset-design assumptions are controlled |
| Connection & levy billing | Household-linked connection and billing context through time | Exact target volumes, fields and formulas are controlled |
| Reliability context | Overflow and service-request history | Operational simulation mechanics are controlled |
Full active certification is not asserted. Sewer coverage is calibrated, not universal. Commercial categories do not establish Business identity links. Wastewater and Water are separate domains without a required data dependency.
Full active certification is not asserted. Sewer coverage is calibrated, not universal. Commercial categories do not establish Business identity links. Wastewater and Water are separate domains without a required data dependency.
The release deliberately calibrates sewer-connection coverage against real infrastructure evidence rather than assuming a near-universal network, consistent with how sewer networks in the region actually operate.
Commercial and industrial service categories may exist without a direct relationship to a specific business identity. The marketplace does not infer one.
Full active certification is not yet asserted for this release; the gap is disclosed at capability level rather than through internal file or code excerpts.
Wastewater and Water are conceptually related infrastructure but are represented as separate domains in this release, without a required data dependency between them.
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.
A real Connection row, RESIDENTIAL, Ward 26 — 237,500 published on Nairobi.
confirmed in the published source: SewerLine, SewageLevy, OverflowEvent and ServiceRequest all have 0 rows. The connection population is real; levy billing and reliability history are designed but not yet generated.
Wastewater is presented as a semantic city-service relationship; the internal dependency design remains private.
Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™