Layer 1
Source records
Datasets, indicators, and records come from Data Civic. Public sector pages consume those records rather than maintaining a separate copy of the same evidence.
Methodology
The platform separates verified source data, derived analysis, and experimental product features so users can tell what is observed, what is calculated, and what is still a prototype.
A compelling interface never upgrades weak evidence into a stronger claim. Scope, source, and derivation stay visible even as the product becomes easier to use.
Layer 1
Datasets, indicators, and records come from Data Civic. Public sector pages consume those records rather than maintaining a separate copy of the same evidence.
Layer 2
Computed values are allowed only when the transformation is documented and the result is clearly distinguished from an official source statistic.
Layer 3
Features such as Power Business forecasts may use synthetic or modelled data for product validation, but they remain explicitly separated from the public evidence layer.
How pages are built
infrastructure.civic.ng reads infrastructure datasets, indicator definitions, and record series from data.civic.ng. The sector pages then present those records as readable summaries, trends, comparisons, and state views.
The site does not silently fill gaps. Missing state data remains missing. Missing years are not interpolated. A national indicator is not restated as an LGA or state outcome.
When a derived series is used, such as road length by state, the page labels it as derived and keeps the methodology boundary visible.
Evidence labels
National vs state
Power, telecom, and water currently use national series. Roads have one state-backed derived series. State pages only show a sector when verified state rows exist for it.
Experimental boundary
Synthetic forecasts, demo feeders, simulated outages, and sample business savings in Power Business are product-validation artifacts. They are not silently mixed into public infrastructure claims.