38 lines
2.4 KiB
Markdown
38 lines
2.4 KiB
Markdown
# evelyn-perps-overview Specification
|
|
|
|
## Purpose
|
|
|
|
Let the owner inspect Evelyn perpetual positions grouped by wallet and venue in Mission Control, beginning with a clearly labeled sample-data prototype.
|
|
|
|
## Requirements
|
|
|
|
### Requirement: Perps overview displays a collapsible position hierarchy
|
|
The Perps tab SHALL display a tree table with columns `Position`, `Direction`, and `Position size, USD`. The hierarchy SHALL be wallet → venue → position, expanded by default, with collapsible wallet and venue groups. Wallet and venue rows SHALL leave direction and size empty.
|
|
|
|
#### Scenario: Open either environment's Perps tab
|
|
- **WHEN** the owner opens Perps in Production or Test
|
|
- **THEN** the three named columns and the fully expanded hierarchy are visible
|
|
- **AND** direction and size appear only on position rows
|
|
|
|
#### Scenario: Collapse and expand groups
|
|
- **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 remain entirely within EMC, using no network calls, service changes, service communication, Refresh button, or simulated live updates for the prototype.
|
|
|
|
#### 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 automated update of sample positions
|
|
- **AND** displaying and interacting with the prototype uses only local EMC data
|