Add a simple prototype of the active positions overview to the Perps tab in Evelyn Mission Control. The purpose is to evaluate the layout and hierarchy before integrating Evelyn services.
The table has three columns:
Position — a tree hierarchy of wallet → venue → position.
Direction — Long or Short on position rows.
Position size, USD — the value on position rows.
A venue is either Jupiter or Phoenix.
Position rows have a faint red background for Short positions and a faint green background for Long positions. Keep the Long/Short text visible so that direction does not depend on color alone. Do not apply these background colors to wallet or venue rows.
Keep the implementation entirely within EMC and use hardcoded dummy data. Include Jupiter and Phoenix with multiple positions to demonstrate the hierarchy and columns. Expand the tree by default and allow groups to be collapsed. Leave direction and size empty on wallet and venue rows.
Clearly label the view as sample data. Phoenix rows are illustrative and do not imply an existing integration.
Do not add a Refresh button. Future service integration will update the view automatically. This task requires neither service communication nor simulated live updates.
Acceptance criteria
The Perps tab displays the tree table with the three specified column names.
Hardcoded sample data demonstrates wallet → venue → position for both Jupiter and Phoenix.
Both Long and Short positions appear with readable USD formatting.
Position rows have faint green backgrounds for Long and faint red backgrounds for Short, with readable text.
Wallet and venue rows do not use direction-based background colors.
Groups can be expanded and collapsed, and the tree is expanded by default.
The view is clearly marked as sample data.
No Refresh button is present.
Implementation remains local to EMC, without network calls or service changes.
Add a simple prototype of the active positions overview to the Perps tab in Evelyn Mission Control. The purpose is to evaluate the layout and hierarchy before integrating Evelyn services.
The table has three columns:
- **Position** — a tree hierarchy of wallet → venue → position.
- **Direction** — Long or Short on position rows.
- **Position size, USD** — the value on position rows.
A venue is either Jupiter or Phoenix.
Position rows have a faint red background for Short positions and a faint green background for Long positions. Keep the Long/Short text visible so that direction does not depend on color alone. Do not apply these background colors to wallet or venue rows.
Keep the implementation entirely within EMC and use hardcoded dummy data. Include Jupiter and Phoenix with multiple positions to demonstrate the hierarchy and columns. Expand the tree by default and allow groups to be collapsed. Leave direction and size empty on wallet and venue rows.
Clearly label the view as sample data. Phoenix rows are illustrative and do not imply an existing integration.
Do not add a Refresh button. Future service integration will update the view automatically. This task requires neither service communication nor simulated live updates.
**Acceptance criteria**
- The Perps tab displays the tree table with the three specified column names.
- Hardcoded sample data demonstrates wallet → venue → position for both Jupiter and Phoenix.
- Both Long and Short positions appear with readable USD formatting.
- Position rows have faint green backgrounds for Long and faint red backgrounds for Short, with readable text.
- Wallet and venue rows do not use direction-based background colors.
- Groups can be expanded and collapsed, and the tree is expanded by default.
- The view is clearly marked as sample data.
- No Refresh button is present.
- Implementation remains local to EMC, without network calls or service changes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Add a simple prototype of the active positions overview to the Perps tab in Evelyn Mission Control. The purpose is to evaluate the layout and hierarchy before integrating Evelyn services.
The table has three columns:
A venue is either Jupiter or Phoenix.
Position rows have a faint red background for Short positions and a faint green background for Long positions. Keep the Long/Short text visible so that direction does not depend on color alone. Do not apply these background colors to wallet or venue rows.
Keep the implementation entirely within EMC and use hardcoded dummy data. Include Jupiter and Phoenix with multiple positions to demonstrate the hierarchy and columns. Expand the tree by default and allow groups to be collapsed. Leave direction and size empty on wallet and venue rows.
Clearly label the view as sample data. Phoenix rows are illustrative and do not imply an existing integration.
Do not add a Refresh button. Future service integration will update the view automatically. This task requires neither service communication nor simulated live updates.
Acceptance criteria