Skip to content
All selected work

Finance · Workflow tools

Local simulation · Prototype

Schwab Trading Console

A personal console prototype for reviewing positions by strategy, rehearsing closes, and making risk controls visible in a local simulation.

Role
Project initiator · Product direction
Approach
AI-assisted development with explicit attribution
Evidence reviewed

The starting point

Problem & product concept

Yi Zhou found his existing Schwab workflow cumbersome when he wanted to understand positions and prepare an action. He began building a personal workspace that puts positions, strategy context, and order review together.

Applicant account

Yi Zhou’s contribution

Yi Zhou identified the friction in his brokerage workflow, initiated the project, and set the direction for a personal trading console. He chose position review and strategy organization as the starting point and used AI assistance to develop the prototype.

Working with AI

Yi Zhou set the product goal from his own workflow. The project handoff records AI-assisted implementation and browser verification of the grid interface.

A specific challenge

Make a paused strategy’s restrictions understandable

Historical record

What surfaced

In the recorded simulation, the strategy remained paused after a liquidation restriction was applied. The interface needed to explain why start, resume, and order replenishment were unavailable.

Historical record

The response

The updated view displays the selected mock account, strategy state, and ledger context together. It explains the active liquidation restriction next to the disabled controls.

What this illustrates

Showing the state and the reason for a blocked action lets a person check the restriction before taking the next step.

Technical lesson drawn from the evidence. Yi Zhou’s personal reflection is being documented in his own words.

How the system is organized

A React and TypeScript interface reads positions, strategies, and orders from a local API. The mock backend maintains synthetic order and ledger records in SQLite. The browser places account context, strategy state, and the applicable controls together for review.

Simulated order review

  1. Review positions
  2. Check strategy context
  3. Rehearse a close
  4. Inspect order state and restrictions
Workflow in the local prototype using synthetic account and order records.
Positions and strategies
Review positions alongside their strategy context.
Simulated orders
Rehearse a close and review order, fill, and cancellation states in the mock environment.
Grid controls
Show the simulated ledger, reservations, and controls that govern start, resume, and order replenishment.

Decisions that shape the work

  • Use synthetic records to rehearse order workflows.
  • Keep the grid ledger distinct from the account overview.
  • Explain disabled controls alongside the strategy state and the active restriction.

Evidence & verification

Source inspection, local interface observations, historical reports, and applicant-supplied accounts establish different things. The labels below keep those boundaries visible.

Historical record

Recorded browser and API verification

The October 23 handoff records 59 browser checks and 67 API checks before and after the browser session. The overlapping API checks cover the same scope. The report records preserved simulation tables and the expected audit entries from opening a session.

Historical record

Paused strategy and visible restrictions

The archived screen shows the mock strategy still paused, with start and resume disabled and the reason visible. The recorded session inspected the existing state.

Read the public source-review note

An honest boundary

Current maturity & limitations

  • The verified scope is a local MOCK prototype using synthetic positions, orders, fills, and balances.
  • Live Schwab account connectivity, real order routing, and investment performance are outside the verified scope.
Planned

Next steps

  • Extend scenario coverage for close and cancellation states in the simulator.