ADR-103 config-screen bootstrap read pattern
This walkthrough records the doctrine added for config/catalog screen bootstrap reads.
What changed
The PR adds docs/decisions/adrs/ADR-103-config-screen-bootstrap.md and the registry entries that make it discoverable in pramaan-docs.
Why it matters
Config screens currently fan out to five backend calls. In cold staging, that can race up to five Lambda cold boots and produce an 11 second page load.
The ADR turns that finding into a config-archetype rule: use one domain-scoped read-only aggregate for screen bootstrap.
Decision summary
- Use a read-only aggregate such as
GET /app/matter-config-bootstrap. - Collapse cold-instance fan-out from N calls to 1 call.
- Keep the aggregate firm-scoped through bearer token and RLS.
- Require the endpoint shape in the canonical OpenAPI contract.
- Require a new ADR only when a screen must break the read-only pattern.
Not in scope
No backend endpoint, frontend consumption, drawer navigation, or cache implementation ships in this PR. Those remain follow-up work in the owning repos.