Build the market data feeds screen for the system administrator
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
The system administrator has no screen for the market data feeds. The journey Keep the market data feeds running lists the feed bindings, says whether each source runs, and starts or stops a feed. The web client has no page and no BFF route for it. The system home shows it as an upcoming card.
2. Why
The subjects the screen needs mostly exist: marketdata.v1.feed_bindings.list,
.get and .put, synthetic.v1.feed_configs.list for the running set, and
synthetic.v1.ops.start_feed, .stop_feed, marketdata.v1.ops.start_feeds_under_folder
and .stop_feeds_under_folder. The journey records what is missing: no read for
the last tick, no stored source-to-series mapping, no list for the IR generation
configs, and no permission that gates start and stop. Start and stop are
reachable from the shell only.
The first slice is the read-only roster: the bindings joined to the running set.
It needs one BFF route in operations.ts and one page under the operations area.
Start, stop and the last tick wait on the server changes the journey names.
3. References
- User Journey: Keep the market data feeds running
projects/ores.web/packages/bff/src/operations.ts, where the sibling routes live.