Data Governance

How we manage content ownership, quality controls, and review cycles.

Content Domains & Ownership

DomainOwnerReview CycleSLA
Economic facts & indicatorsEditorial TeamQuarterly30 days after source update
Tourism & travelEditorial TeamMonthly14 days after change
Historical contentHeritage Expert PanelAnnually90 days after discovery
Diaspora directoryCommunity ManagerContinuousMember-driven updates
API & technical docsTech LeadPer releaseSame-day as deployment
Investment dataEconomic AnalystQuarterly30 days after source update
UNESCO & heritage sitesHeritage Expert PanelAnnually90 days

Quality Controls

  • Automated validation: Schema validation on all API responses
  • Freshness monitoring: Alerts when content exceeds its review interval
  • Link integrity: Automated checks for broken URLs in sitemap and llms.txt
  • Consistency checks: Cross-validation between API, HTML, and llms.txt surfaces
  • Test coverage: 284 automated tests (212 unit + 72 E2E)

Data Contracts

Each dataset exposed via the API follows a data contract:

FieldRequiredDescription
ownerYesTeam or person responsible
sourceYesPrimary data source
confidenceYesverified / estimate / editorial
valid_fromYesStart of validity period
valid_untilYesEnd of validity period
reviewed_atYesLast human review date
refresh_intervalYesExpected update frequency

Change Management

  • All content changes tracked via changelog (JSON + Atom feed)
  • Breaking API changes announced with Deprecation and Sunset headers
  • Versioned llms.txt with last-updated field
  • Discovery manifest updated on each release
Governance Principles
  1. One canonical source per fact
  2. Every claim has provenance
  3. Freshness is observable
  4. Confidence is explicit
  5. Changes are traceable

Rapports mensuels

Stats plateforme, bases historique/géo et contenu — mis à jour mensuellement.

Chargement du dernier rapport…

API : GET /api/v1/governance/monthly