Please read carefully for full consideration DO NOT POST QUESTIONS TO BOARD THEY WILL BE IGNORED There is a technical document if you would like consideration please fill out document alon with your bid this is not a crypto bot and i am not seeking a feature builder Senior Broker Execution Engineer – Full Automation Hardening & System Cohesion – Cash-Only Options Engine I am completing a nearly finished Python-based automated options trading system. Strategy logic is complete. This engagement is not about alpha or indicator development. This is systems engineering, execution safety, wiring integrity, and production reliability. System Context Per current architecture: Schwab Trader API OAuth implemented Token server active Cash account only Single-leg equity options only One position per ticker One directional bias only (CALL or PUT, never both) Three execution modes (Manual / Semi-Automatic / Full-Automatic) GUI cockpit completed RiskEngine built Idempotent submission implemented (requires hardening) Reconciliation loop exists (requires strengthening) Simulation layer partially implemented Objective Deliver a fully hardened, synchronized, production-ready automated execution system that: Cannot double-submit orders Cannot violate the one-position-per-symbol rule Cannot violate directional bias rule Cannot violate cash-only enforcement Cannot execute if GUI and backend disagree Fails closed under ambiguity Survives 9:30 AM open volatility Is safe for controlled live use This is not tied to strategy performance. Expanded Scope (Hybrid Model) Phase 1 – Execution Core Hardening Deterministic state machine Idempotent intent model Parent and child lifecycle separation Partial fill handling under volatility Cancel/replace ambiguity handling Broker-authoritative reconciliation Ambiguity freeze model Phase 2 – Full Wiring and Cohesion Complete GUI-to-backend mapping Mode enforcement server-side Button gating correctness Server-side double-click prevention Contract quantity integrity enforcement Kill-switch propagation across sessions One-option-per-symbol enforcement Directional bias persistence Lock acquisition and release rules GUI design must not change. Only functional corrections are permitted. Phase 3 – Risk and Cash Enforcement Settled cash validation Unsettled proceeds exclusion Buying power reconciliation Lock on cash-state drift Phase 4 – Simulation Structural Completion Live and SIM adapter parity Shared RiskEngine logic Deterministic partial fill simulation Absolute separation preventing SIM from routing to LIVE Phase 5 – Unusual Whales Integration (Read-Only) Non-blocking adapter Circuit breaker isolation No execution dependency on this API Phase 6 – Controlled Live Readiness Open-market stress protocol Reconciliation stress testing Failure injection testing Final validation checklist Known limitations documentation Ownership Expectation Developer must: Take responsibility for automation state machine integrity Ensure backend is authoritative over GUI Ensure wiring and plumbing operate cohesively Deliver documented state transitions Deliver inspectable logs Provide a clear fail-closed policy Be available during US market hours for validation testing Required Experience Do not apply if: You have only built backtesting systems You have not routed live broker API orders You have not handled OAuth lifecycle management You have not handled partial fills You have not debugged race conditions Must demonstrate: Broker API production experience Idempotent order routing Distributed locking models Execution reconciliation systems Cash-account enforcement logic Asynchronous concurrency handling Engagement Structure Milestone-based Milestones funded in stages and held in escrow Acceptance tied to deterministic criteria Payment gated by documented state validation Timeline: 2 weeks