Eurostat · EEA · JRC/GHSL · GISCO
Sources
Authoritative datasets and source artifacts enter with provenance, vintage, licence and identity evidence.
Build · living technical documentation
How Habitability is built.
A transparent view of the technical system, evidence pipeline and agent governance behind Habitability. This is a build map, not a claim that every research output is scientifically validated.
Architecture
From source to evidence product
The architecture is designed to keep data provenance, scientific method and product presentation connected without collapsing their different evidence states.
SourcesEurostat · EEA · JRC/GHSL · GISCO
Evidence enginePython · machine-checkable contracts
Data layerNeon · PostgreSQL
MethodologyVersioned registry · MVE gates
ProductNext.js · TypeScript
DeliveryGitHub · Actions · Vercel
Python · machine-checkable contracts
Evidence engine
Artifacts are inspected, checksummed and tested. Missing semantics fail closed rather than being silently inferred.
Neon · PostgreSQL
Data layer
Structured observations, territories and evidence metadata form the persistent data foundation.
Versioned registry · MVE gates
Methodology
Methods, transformations, limitations and evidence transitions are explicit and reviewable.
Next.js · TypeScript
Product
Evidence and methodology are translated into legible territory and research experiences.
GitHub · Actions · Vercel
Delivery
Branches, pull requests, deterministic CI and deployment previews create the controlled delivery path.
Evidence pipeline
Evidence before output
Habitability is built around a fail-closed evidence lifecycle. A technically usable artifact is not automatically a validated scientific result.
01Source
02Artifact
03Provenance
04Validation
05Transformation
06Indicator
07Research
08Validated
09Published
Research → Validated → Published are separate states. Transitions require their own evidence and governance gates.
Agent system
Bounded autonomy
Scientific evidence
Lane S
Source semantics, evidence contracts and scientific gates.
Data / product foundations
Lane D
Geographies, population artifacts, pipelines and product foundations.
Publication & methodology
Lane P
Method registry and publication discipline; not an additional autonomous Runner slot.
Human decisions
Founder gates
Publication, material commitments, legal/IP and other explicitly reserved decisions remain human-controlled.
The Runner follows a controlled loop: read canonical state → select an eligible mission → contract → branch → execute → test → PR → log → stop. It does not self-approve or self-merge.
Build Observatory
Measure the machine that builds the product
The Observatory consolidates project state from reviewed canonical evidence. When reconciliation is incomplete, it fails closed rather than publishing a stale completion percentage.
See the canonical Observatory for current reviewed state
Decisions & methodology
A durable institutional memory
Architecture choices, methodology versions, material HOLDs and governance decisions are recorded in GitHub so the website can explain not only what exists, but why it exists.