Task: Build the market data sources board and the subscriptions screen
Table of Contents
This page documents a task in the Rework the market data feeds into a market data service with adapters — the remaining work story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
Operations shows the market data sources board, and Market data shows subscriptions and routes, both reading the service.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Rework the market data feeds into a market data service with adapters — the remaining work |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-26 |
3. Acceptance
- Operations, Market data sources: the tiles, the sources table, the alert and the detail panel.
- Market data, Subscriptions: the party's rights and its routes, with create and remove.
4. Plan
(Implementation strategy. Written when work starts; key decisions
are distilled into the parent story's * Decisions at close, but the
plan itself stays — it is the historical record of what we did.)
5. Measurements
Every number this task claims about a tree, with the command that produced it
and the commit it was measured at. A number without both is not a measurement,
because a clean-up record describes a tree and trunk moves under a branch: a
consumer count, a gate's component count and a suite's size all change with no
code changing, and the reader of a bare number cannot tell which tree it came
from. Where the raw output matters, put it in an evidence/ file beside the
task and name that file in the Command column.
| What | Value | Command | Commit |
|---|---|---|---|
6. Notes
7. Test Scenarios
Manual QA scenarios (scaffolded via compass add test_scenario)
that verify this task. Link
new ones here as they're created; the scenario doc itself links back
via its "Verifies task" field.
| Scenario | State | Notes |
|---|---|---|
8. PRs
| PR | Title |
|---|---|
| #3868 | [web] Draw the market data sources board and the subscriptions screen |
9. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
10. Measurements
| What | Value | Command |
|---|---|---|
| JS suite | 3340 tests, 269 files | npm test in projects/ores.web |
| New BFF tests | 14 | src/subscriptions.test.ts |
| New board tests | 12 | operations/marketDataSources.test.tsx |
| New screen tests | 11 | marketdata/subscriptionsScreen.test.tsx |
| Typecheck | clean, six workspaces | npm run typecheck |
| Live subscriptions | 2 | GET /api/marketdata/subscriptions |
| Live routes | 2 | GET /api/marketdata/routes |
| Adapters | 23 statuses, matched the shell | GET /api/marketdata/adapters |
11. Result
Operations now has the market data sources board, and Market data has the subscriptions and routes screen.
- The board reads the adapter status once and draws the tiles, the alert, the table and the detail panel. Four prototype fields are stated as gaps because the status does not carry them: the source kind, the quality drops, the routed parties and the state history.
- The subscriptions screen reads the party's rights and its routes through the BFF, and creates and removes them through the service's put and delete. Creating needs the session's party; deleting states the version and asks for the reason.
- Two BFF reads were added: subscriptions and routes, plus a catalogue read for the providers and sources a route names. No service operation was added.
Open. The party administrator role has no marketdata subscriptions or routes read in the seed, so a human party account sees nothing until the role is granted. The running web service serves the new bundle after a build and a restart. The usage and cost screen has no price read.
Deferred: the usage and cost screen, and the versions history, which has no BFF read.