nats-broker Conformance Pack
User Storiesβ
- backend services can communicate over a shared broker for trades and market prices.
- frontend can receive live account updates and pricing updates over websocket via ingress.
Functional Requirementsβ
FR-1001FR-1002FR-1004FR-1005FR-1006FR-1009FR-1011FR-1012FR-1016
Non-Functional Requirementsβ
NFR-1002NFR-1003NFR-1004NFR-1005NFR-1006NFR-1007
Acceptance Criteriaβ
- NATS service is reachable and healthy in state runtime.
- Pricing topics (
pricing.<TICKER>) are observable from websocket clients. - Publisher cadence/ratio config is exposed and valid via
/health. - Trade events include non-null execution price.
- Position events and REST payloads include non-null average cost basis.
- Realtime position updates preserve aggregate blotter semantics (existing security rows update in place).
- UI semantics for market-vs-open and value-vs-cost use deterministic marker/highlight rules.
Verification Referencesβ
scripts/start-state-007-pricing-awareness-market-data-generated.sh(planned)scripts/test-state-007-pricing-awareness-market-data.sh(planned)