DEUS MACHINA

PROJECT: Complete Existing Python Trading Application — PyQt6, Flask, Schwab and Windows

I need an experienced trading-systems engineer to complete and validate HYPERION DEUS EX MACHINA.

This is an existing-repository integration project. The application already contains strategy/execution modules, a GUI, provider adapters, OAuth, persistence and automated tests.

EXISTING STACK
Python 3.13, PyQt6, Flask, Schwab OAuth/API, Finviz Elite, AlgoX Flow and durable local state.

REQUIRED EXPERIENCE
• Python/PyQt desktop trading applications.
• Qt threading, signals/slots and responsive tables.
• Flask integration and polling/SSE reconnect behavior.
• Broker OAuth and execution.
• Partial fills, protective exits, cancellation and reconciliation.
• Restart recovery and duplicate-order prevention.
• Windows deployment and testing.
• US equities/options and cash-account buying-power controls.

SCOPE
1. Review the repository and identify remaining gaps.
2. Wire existing GUI controls to backend commands and effective settings.
3. Verify every GUI page/action represents implemented behavior.
4. Preserve the approved GUI design.
5. Demonstrate authentic data → qualifying signal → simulated entry/fill → protection/exit → restart → final flat state.
6. Inject failures and prove entry blocking, recovery and no duplicate orders.
7. Verify Windows startup/shutdown and GUI/backend reconnect.
8. Compare Finviz/AlgoX displayed values with backend scanner/context values.
9. Deliver code, evidence, operating instructions and an updated completion report.

CASH ACCOUNT ONLY
No short equities or short options. No SELL_SHORT or SELL_TO_OPEN. Closing sells must not exceed reconciled owned quantities, accounting for pending exits. Enforce settled-cash limits and cash reservations.

SAFETY
PAPER only; LIVE disabled. No real orders or real-token revocation. Keep credentials private. Any future live test requires separate written authorization.

CUSTOM OFFER REQUIREMENTS
• Inspect the repository before promising completion.
• Identify the developer who will personally perform the work.
• Propose review, integration/recovery and acceptance/handoff milestones.
• Specify objective acceptance evidence.
• Identify optional streaming/history work separately.
• State availability and US market-hours overlap.

DELIVERY
A complete updated repository named Hyperion.zip; GUI sitemap and backend command mapping; regression results; Windows instructions; reproducible lifecycle/recovery evidence; accurate completion report.

Screenshots or passing unit tests alone are insufficient.

PLEASE ANSWER
• Which broker-connected Qt trading applications have you personally built?
• Have you integrated Schwab?
• How do you prevent duplicate orders after a timeout or restart?
• How do you reconcile partial fills and competing exits?
• How do you enforce settled-cash buying power?
• Can you demonstrate PAPER crash recovery on Windows? We prioritize demonstrated execution reliability and desktop integration experience.