r35157/com_r35157_nenjim-hubd-impl_ref
0
0
Fork 0
Code Issues 18 Pull Requests Actions Packages Projects Releases Wiki Activity

98: Populate EvelynPerpsService with real Jupiter positions

Browse Source
This commit is contained in:
minimons
2026-10-22 13:37:29 +02:00
parent 0ec22d5215
commit df5cc0eda7
15 changed files with 334 additions and 113 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/specs/evelyn-perps-overview/spec.md
+16 -19
View File
@@ -2,7 +2,7 @@
## Purpose
Let the owner inspect Evelyn perpetual positions grouped by wallet and venue in Mission Control, beginning with a clearly labeled sample-data prototype.
Let the owner inspect Evelyn perpetual positions grouped by wallet and venue in Mission Control, with stable row identities across service snapshot updates.
## Requirements
@@ -18,24 +18,6 @@ The Perps tab SHALL display a tree table with columns `Position`, `Direction`, a
- **WHEN** the owner collapses and then expands a wallet or venue
- **THEN** its descendants are hidden and then shown again
### Requirement: Sample positions communicate direction and USD size
The overview SHALL include hardcoded Jupiter and Phoenix venues with multiple sample positions, including both Long and Short directions. Position rows SHALL show `Long` or `Short` text and USD sizes with grouping separators and two decimal places. Long rows SHALL have faint green backgrounds and Short rows faint red backgrounds with readable text; wallet and venue rows SHALL have no direction-based color.
#### Scenario: Inspect sample positions
- **WHEN** the owner inspects Jupiter and Phoenix examples
- **THEN** both venues have multiple positions and both directions are demonstrated
- **AND** position sizes use readable USD formatting
- **AND** only position rows use direction-based backgrounds, with direction also conveyed by text
### Requirement: Prototype is clearly labeled and entirely local
The Perps view SHALL explicitly label its data as sample data and explain that Phoenix rows are illustrative without an existing integration. It SHALL obtain positions only from the Perps service's current in-memory snapshot, with no external network calls, Refresh button, or simulated position changes. EMC SHALL own all UI components, row colors and formatting.
#### Scenario: Inspect the prototype boundary
- **WHEN** the Perps tab is displayed
- **THEN** sample-data and illustrative-Phoenix labels are visible
- **AND** there is no Refresh button or simulated update of sample positions
- **AND** displaying and interacting with the prototype uses only the service's local sample snapshot
### Requirement: Asynchronous polling follows window visibility
EMC SHALL request the current Perps snapshot from each environment's own service immediately on opening and every three seconds while visible, without blocking the UI thread. UI updates SHALL occur only on the JavaFX thread. Hiding the window SHALL stop polling; reopening SHALL create only one active polling loop and ignore results belonging to an earlier window session. Poll failures SHALL preserve the current view and allow subsequent attempts.
@@ -59,3 +41,18 @@ The Perps table SHALL retain matching wallet, venue and position identities acro
#### Scenario: Poll unchanged positions
- **WHEN** a user collapses a group or selects a position and repeated snapshots are unchanged
- **THEN** the same rows remain, with the same expansion and selection and no rebuild or refresh
### Requirement: Jupiter positions communicate direction and USD size
Position rows SHALL show Long or Short and USD sizes with grouping separators and two decimal places. Long rows SHALL have faint green backgrounds and Short rows faint red backgrounds; wallet and venue rows SHALL have no direction-based color. Existing columns and hierarchy SHALL be preserved.
#### Scenario: Inspect real positions
- **WHEN** real Jupiter positions are displayed
- **THEN** direction appears as readable text and background color, with formatted USD size
### Requirement: EMC presents service data without sample notices
EMC SHALL obtain positions only from its environment's in-memory service snapshot and SHALL contain no sample positions, sample notices, illustrative-Phoenix notices, or Refresh button. EMC SHALL own UI components, colors and formatting; integration reads SHALL belong to the service.
#### Scenario: Snapshot changes
- **WHEN** positions are added or removed after refresh
- **THEN** EMC reconciles rows by identity while preserving retained selections and expansion state
- **AND** no sample labels or Phoenix examples appear