Story: Subscribe tenants to provider feeds and prove the browser at scale
Table of Contents
This page documents a story in Sprint 30, carried unfinished from Sprint 28 at close. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
A tenant or party subscribes to a provider's feeds through a subscription and a route, the feed screen standard states the browser, the two scopes and the subscription, and the feed browser is proved with tens of thousands of feeds.
2. Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent sprint | Sprint 30 |
| Now | Not yet started. |
| Waiting on | Nothing. |
| Next | Break the story into tasks. |
| Last touched | 2026-11-08 |
3. Acceptance
- A screen shows what each provider offers, what a tenant or party consumes and since when, and writes the subscription and the route.
- The feed screen standard states the browser, the two scopes and the subscription, and the FX price feed screen conforms.
- Tens of thousands of feeds are generated, the tree, lists, running read, folder cascade and tick buffers are measured, and what does not hold is fixed.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Subscribe a tenant to provider feeds | BACKLOG | A screen that shows what each provider offers, what a tenant or party consumes and since when, and writes the subscription and the route that subscribe and unsubscribe. | ||
| Prove the feeds at scale | BACKLOG | Generate tens of thousands of feeds, measure the tree, the lists, the running read, the folder cascade and the tick buffers, fix what does not hold, and record the numbers. | ||
| State providers and scope in the feed screen standard | BACKLOG | The feed screen standard gains the browser, the two scopes and the subscription, and the FX price feed screen is brought to it. |