Vireo Case Study | Samuel Gelosh

The brief

Vireo connects the gap between consuming trading education and reviewing an actual decision. The product links preparation, learning, practice, simulated execution, journaling, and review. The difficult work is making each step refer to the same person, lesson, and attempt, so that a completed screen represents saved work and can support the next session.

My contribution

Define the preparation-to-review journey and the evidence that allows a learner to continue from one stage to the next.
Develop server-issued attempts, owned evidence records, and shared completion state across the Academy, dashboard, and continuation controls.
Work through historical replay, order handling, protective brackets, position reversal accounting, and price precision in simulated execution.
Connect trade and no-trade journals, written reflections, and saved review relationships; include source identity and membership checks in mentor context.
Review the relationship between billing events, credits, and access so product state can be reconciled with durable records.

The experience, step by step

Prepare & learn
Establish the session context and the lesson the learner is working on.
Practice & execute
Work through an owned attempt and inspect a simulated decision in historical replay.
Journal & review
Save the trade or no-trade decision, reflect on it, and connect the review to the same evidence.

Decisions that shaped the product

Save before showing completion

Completion is a persistence problem as well as an interface problem. The repaired source waits for the server response, exposes failures and retry, and rejects evidence associated with another account, date, or attempt. Shared saved state keeps different screens from reporting contradictory progress.

Make a no-trade decision reviewable

Choosing not to trade is a valid session outcome. The workflow supports a written no-trade journal and review without inventing a trade to satisfy the interface or assigning a performance score that the evidence does not support.

Separate participation from demonstrated skill

An owned, saved attempt shows participation. It does not establish trading mastery or profitability. The product needs that distinction so its learning and review features can describe what happened without claiming more than the record supports.

One session, consistent evidence across screens

Earlier completion paths could display success before persistence finished. The repair work follows that failure across the lesson writer, evidence validation, dashboard projection, execution review, and journal relationships. This is why Vireo is more than a collection of screens: the same record has to remain coherent as the learner moves through the product.

Explore the work

Explore the public product preview

The public preview shows the product direction. The September 9 repair branch is separate from the published application and still needs database and deployed-flow validation.

Open Vireo’s preview

Inspect a shipped education workflow

The Academy on this portfolio is a separate, working example of how I connect learning content, practice, calculations, and reviewable methods.

Read the Academy case study

Where it stands

An implemented product and a coordinated repair revision with 406 recorded passing unit, component, and handler tests, plus a passing production build. These checks describe the September 9 source revision, not deployed customer outcomes. The release remains in development while the actual Vireo database, migrations, and payment/member flows await validation.

Connect the practice. Preserve the evidence.