Remove the unused HTTP gateway base URL
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
1. What
Two declarations name the ores.http gateway from the browser side, and
nothing uses either:
projects/ores.web/packages/contracts/src/site.ts:56declareshttpBaseUrlon the site description.projects/ores.web/packages/wire-protocol/src/client.ts:430declaresdiscoverHttpBaseUrl(), and no file calls it.
2. Why
The BFF is the browser's only HTTP surface. ores.http serves callers
outside the browser, so a browser-side discovery path is a decision nobody
made. A declared-but-unused path is worse than an absent one: it reads as
the supported way to reach the gateway, and the next person adds a call
through it.
The signed-off architecture decision is to remove both rather than document them. It is a code change, so it belongs with the implementation work that follows the architecture task, not in a documentation change.
3. References
projects/ores.web/packages/contracts/src/site.ts:56— the declaration.projects/ores.web/packages/wire-protocol/src/client.ts:430— the unused method.- The component specification — states that the BFF is the browser's only HTTP surface.
- Audit the journey, provisioning and web-client architecture before the first implementation story — finding 5 and decision 2.
- Correct and add the architecture the journeys depend on — records this as a follow-up it does not do.