1.7 KiB
1.7 KiB
Proposal
Why
Issue #103 addresses a real Phoenix order with fills and remaining children that disappears from EMC because its market metadata is missing. Retaining and propagating a concise warning protects Evelyn's account oversight without introducing trading actions.
What Changes
- Preserve eligible unresolved TWAPs as immutable account-owned warning observations, including orders without open positions.
- Show a small amber triangle and short description on the owning position or Cross account, with distinct-order summaries on every ancestor through Perpetual Contracts regardless of expansion state.
- Preserve original times and failure/freshness qualifications; clear resolved warnings on successful reads. Continue hiding zero-fill and completed orders.
- Keep normal TWAP progress, valuations and margin risk independent. Update meaningful documentation and verify with temporary fixtures and JavaFX previews.
Capabilities
New Capabilities
None.
Modified Capabilities
phoenix-perps-service: discover TWAPs for empty existing accounts and retain unresolved filled orders without weakening identity validation.evelyn-perps-service: preserve warning ownership, including warning-only Cross accounts, through immutable snapshots and retained failures.evelyn-perps-overview: display and aggregate accessible TWAP warnings through the complete tree, including collapsed branches.
Impact
Phoenix account and Evelyn snapshot records gain warning lists with compatible constructors. The decoder, reader, mapping and Perps table change; no new dependencies or transaction operations. Repository docs and the shared Evelyn overview change under the owner's explicit documentation instruction. No commits, pushes, Hub restart or deployment.