refactor: establish standalone application boundary
This commit is contained in:
+2
-2
@@ -1,6 +1,6 @@
|
||||
# Governance Registries
|
||||
|
||||
These registries describe the approved product surface of the modular preservation candidate.
|
||||
These registries describe the approved product surface of the standalone application.
|
||||
|
||||
- `pages.config.json`: primary page identity, navigation group, access expectation, scrolling,
|
||||
and mobile composition policy.
|
||||
@@ -8,7 +8,7 @@ These registries describe the approved product surface of the modular preservati
|
||||
- `api.config.json`: current routes generated from the preserved `server.py` API surface, with
|
||||
one feature owner and backend access class per route. Its dispatcher implementation lives in
|
||||
`backend/application.py`.
|
||||
- `architecture-inventory.json`: generated inventory of candidate pages, routes, tables,
|
||||
- `architecture-inventory.json`: generated inventory of current pages, routes, tables,
|
||||
providers, model entry points, CSS layers, and remaining code hotspots.
|
||||
- `data-fields.config.json`: canonical data products, provider eligibility, intended use, and
|
||||
known blocked datasets.
|
||||
|
||||
Reference in New Issue
Block a user