22 lines
1.4 KiB
Markdown
22 lines
1.4 KiB
Markdown
# Proposal
|
|
|
|
## Why
|
|
Issue #98 replaces sample portfolios with the owner's actual Jupiter positions so Mission Control can provide a useful read-only overview. Existing Jupiter position reads and the separate TEST/PROD services can be reused.
|
|
|
|
## What Changes
|
|
- Supply six PROD wallet addresses and one TEST address from Hub construction, with the corresponding existing Jupiter integrations.
|
|
- Refresh asynchronously at startup and every 60 seconds; keep immutable snapshot reads independent of integration calls.
|
|
- Preserve failed wallets' last successful data, clear successful empty results, and order positions deterministically.
|
|
- Remove sample/Phoenix positions and sample notices while retaining the existing table and polling.
|
|
- Update project documentation and the canonical system documentation in the sibling `r35157_docs` repository as explicitly requested.
|
|
|
|
## Capabilities
|
|
### New Capabilities
|
|
None.
|
|
### Modified Capabilities
|
|
- `evelyn-perps-service`: Live Jupiter refresh, real environment-specific wallet configuration and per-wallet failure behavior.
|
|
- `evelyn-perps-overview`: Real Jupiter data without prototype labels, preserving the existing presentation and row reconciliation.
|
|
|
|
## Impact
|
|
Perps configuration and implementation, Hub construction, EMC labels, and documentation in both repositories. No changes to trading operations, Phoenix integration, cache TTLs, or the parameterless public read API.
|