migration: establish exact preserved app baseline

2026-07-30 23:51:48 +08:00
commit e4a9b2e647
389 changed files with 126625 additions and 0 deletions
@@ -0,0 +1,26 @@
+# Governance Registries
+
+These registries describe the approved product surface during architecture migration.
+
+- `pages.config.json`: primary page identity, navigation group, access expectation, scrolling,
+  and mobile composition policy.
+- `features.config.json`: feature ownership, backend access class, data scope, and availability.
+- `api.config.json`: transitional inventory of current routes, generated from `server.py` and
+  assigned to a feature owner.
+- `data-fields.config.json`: canonical data products, provider eligibility, intended use, and
+  known blocked datasets.
+- `data-quality.config.json`: freshness, coverage, units, adjustment, point-in-time, and
+  fail-closed rules for every canonical data product.
+- `jobs.config.json`: background schedules, dependencies, lock keys, retry policy, timeouts,
+  and output versions.
+
+During Stage 04 these files are contract inputs, not runtime replacements. Backend access in
+`api_access.py` remains authoritative until the HTTP governance phase switches it atomically.
+Frontend visibility remains a presentation concern and never grants backend access.
+
+Regenerate the transitional API inventory after a route change:
+
+```shell
+python tools/build_api_registry.py
+python tools/build_api_registry.py --check
+```