Environment & Climate.
Explore environmental and climate context.

Historical events can be analyzed across connected city systems, but the public site intentionally stops at the semantic relationship: exact sensitivity coefficients, modifier weights, propagation sequence and generation model design are controlled.

This page shows what the Environment domain represents, how it connects analytically to the wider City Twin™, and where the evidence boundary sits.

Lagos City Twin™ · 1940–2026

FCTE's environment concept spans a deployed reference layer plus a designed-but-not-yet-generated entity model, including a Lagos-specific regulatory extension. internal build ordering and dependencies are intentionally not published.

A shared, platform-wide historical-event reference — 38 documented Lagos-relevant events with a domain-sensitivity mapping (111 rows) shared across the platform.

A static per-city reference table of min/average/max temperature by calendar month — a lookup, not a generated, growing dataset.

The designed core entity model — area-level flood assessments, sector emissions, ward canopy tracking, granular climate indicators and green-space inventory. None has a deployed table today.

AirQualityStation, AirQualityReading, WaterBody, WaterQualityReading, FloodEvent, plus a regulatory-governance layer (Organization, Permit, Inspection, Violation, EnforcementAction, ProtectedArea) referencing real Nigerian authorities (NESREA, LASEPA, NIMET, LASPARK, LASDRI, LASWA) — this is the intended Lagos-specific extension scope, not currently generated data.

Disclosed gap: only the historical-event and monthly-climate reference layers are real today. The entity-level tables described above, including the Lagos-specific regulatory layer, are the intended next build, not currently generated data — naming them here is scope-setting, not an design announcement.

Historical climate context is modeled separately from environment entities and connected at the analytical level.

━━ semantic relationship · ┄┄ separate platform context . Climate connects these concepts analytically without publishing the design layers underneath.

• Risk, emissions, canopy, climate and green-space context
• Physical dependency graph: controlled

• Documented historical events are city-scoped and time-aware
• Internal storage, consumer graph and propagation mechanics are controlled

The public Environment domain exposes environmental entity families, historical context and representative analytics. Exact target volumes, randomization, trend coefficients, modifier formulas, starting configurations and orchestration are intentionally withheld.

FCTE represents dated environmental shocks and climate context without publishing the modifier coefficients, propagation weights or execution sequence.

Geography, urbanisation and local evidence shape the release. Exact probability bands, trend coefficients and row-scale parameters remain controlled.

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

Historical event context is represented through documented categories, timing and qualitative impact direction. Exact modifier formulas, propagation weights, execution paths and domain-consumption logic are intentionally withheld.

The release exposes dated drought context for historical comparison while exact sensitivity coefficients, modifier weights, propagation paths and generation orchestration remain controlled.

The release exposes dated flooding context for cross-domain analysis without asserting that every environmental record was mechanically generated by the event.

The Environment domain publishes qualitative sensitivity categories for how climate shocks may relate to other city systems. Exact coefficients, propagation weights and modifier method are controlled.

Each row summarizes release-backed climate evidence at a qualitative public level. Exact configured coefficients and internal rationale metadata are controlled.

Historical event context is represented through documented categories, timing and qualitative impact direction. Exact modifier formulas, propagation weights, execution paths and domain-consumption logic are intentionally withheld.

Historical event context is represented through documented categories, timing and qualitative impact direction. Exact modifier formulas, propagation weights, execution paths and domain-consumption logic are intentionally withheld.

FCTE can represent a documented environmental shock and examine how related city systems change through time. The public site shows the conceptual pathway and evidence category, not the internal propagation recipe.

Environmental risk can be analyzed alongside disease burden, healthcare utilization and insurance context. This demonstrates cross-domain analytical value without exposing the modifier chain or internal intermediates.

Lagos uses the common FCTE public environmental vocabulary while retaining city-specific geography and evidence. Exact generation mechanisms and internal data structures differences are controlled.

Lagos's real, deployed environment layer today is the historical-event and monthly-climate reference data above — coastal flood, canopy and regulatory context is designed scope, not generated data.

Lagos environmental context is city-calibrated by geography and historical period. Exact probability bands, rates and target volumes are controlled.

A certification check requires a deployed dataset to check against; naming a domain in a catalog isn't that.

Exact modifier formulas, dampening and orchestration are controlled.

The public site distinguishes historical context from confirmed analytical relationships.

Flood risk uses area-level evidence and calibrated risk bands rather than a full hydraulic model of elevation, drainage and rainfall dynamics. Exact probability distributions, weights and assignment logic are controlled.

Environmental rows and historical events can share time and geography, but the public release does not claim that every environment record is directly generated from a historical event.

Multiple domains carry historical or climate context, but the public site does not publish the internal dependency graph or claim internal consumption everywhere.

Selected scenario and analytical workflows can propagate historical shock context. Automatic invocation, schedule, weights and execution paths are intentionally not published.

The public catalog documents model scope, evidence and certification maturity. Internal generation sequencing, target volumes, modifier parameters and orchestration are not published.

An area-level assessment would capture flood-risk category and assessment period so exposure could be compared consistently across Lagos — no FloodRisk table exists yet.

Once built, environmental risk could be analyzed alongside city investment intended to reduce that exposure — no such link exists today.

ClimateIndicator, TreeCanopy, CarbonEmission and GreenSpace are proposed, not deployed. What's real today is the 38-event historical reference and the monthly climate lookup used elsewhere on this page.

This is the intended shape of the workflow once Environment's entity model is built — not a description of what the domain does today.

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