Project status · September 2026

Build the measure before the machine.

Habitability is being developed as a territorial intelligence platform: measure how habitable a place is, understand how it changes through time, and eventually anticipate future trajectories.

Current priority

Select the historical CORE.

The Grenoble historical audit has passed. The existing Eurostat layer is sufficiently rich to support a serious 10-year backtest attempt. The current task is now methodological: select a compact, defensible set of indicators before defining dimensions, normalization or any headline score.

First validation milestone

194

Indicators with Grenoble data over 2014–2024

101

Indicators with at least 70% historical coverage

13

Indicators with at least 90% historical coverage

183

Continuous series within their observed historical window

Decision: do not launch a new source-hunting campaign. Existing Eurostat history is sufficient to proceed to CORE indicator selection and test whether a defensible trajectory can be constructed.

What has already been built

Public beta and product architectureBuilt
PostgreSQL observation layer with Eurostat city / FUA dataBuilt
Indicator dictionary and metadata layerBuilt · review needed
Grenoble 2014–2024 historical coverage auditValidated
Habitability semantic frameworkIn progress
Derived metric recipesPrototype
Data provenance, gaps and source-candidate modelBuilt
Scout, validator and orchestration prototypesPrototype · frozen

What is not yet validated

Historical CORE

Coverage is sufficient, but the relevant non-redundant indicator set has not yet been selected.

Core methodology

Dimensions, directionality, normalization and aggregation rules are not yet frozen.

Headline index

No public Habitability score should be treated as validated until the historical backtest succeeds.

Cross-city robustness

The methodology has not yet been tested unchanged across several territories.

Forecasting

2030–2050 scenarios remain downstream of a trusted historical measurement model.

Automation at scale

Agents can maintain and explain the system later; they are not the current bottleneck.

Project guardrail

No new agent development until the Grenoble backtest works.

New automation should only be added when it removes a demonstrated bottleneck in the validated methodology or data-maintenance workflow. Individual missing data points should not pull the project away from the core validation path.

Validation trajectory

Step 01 · Validated

Historical coverage audit

Validated for Grenoble over 2014–2024: 194 indicators with data, 101 with at least 70% coverage, 13 with at least 90% coverage, and 183 continuous series.

Step 02 · Current

Core indicators

Reduce the broad indicator universe to a defensible core based on relevance, historical coverage, stability and geographic comparability.

Step 03 · Next

Dimensions

Lock the conceptual structure and assign core indicators to a small set of stable Habitability dimensions.

Step 04 · Next

Normalization

Define transparent normalization, directionality, missing-data and aggregation rules before producing any headline score.

Step 05 · Next

Grenoble 10-year backtest

Reconstruct Grenoble through time using the same methodology each year and test whether the trajectory is interpretable and robust.

Step 06 · Next

Methodology validation

Test face validity, sensitivity to weights, missing-data robustness and geographic consistency.

Step 07 · Next

Cross-city validation

Apply the exact same framework to several additional territories before claiming general validity.

Step 08 · Next

Website integration

Turn validated trajectories, drivers and provenance into the core public experience on habitability.eu.

Step 09 · Later

Agents & automation

Use scouts, validators and explainers to maintain the system once the methodology is stable—not to define it.

Step 10 · Later

Forecasting

Only after the historical model is trusted, extend Habitability from observed trajectories toward future scenarios.

The product thesis

Habitability should not merely rank places. Its distinctive value is to show whether a territory is becoming more or less habitable, which forces drive that change, how trustworthy the evidence is, and—later—how the trajectory could evolve.

Sequence: Data → 10-year backtest → Methodology → Cross-city validation → Public product → Agents → Forecasting.