Charlie sees the stop evidence and will verify after changes.
Future Charlie app
Dad opens this, asks Charlie, and sees the next safe action.
This preview shows the product shape after Helm moves from a laptop prototype into a hosted, mobile-friendly app. The core stays the same: Charlie researches, explains, drafts, verifies, and asks before anything sensitive happens.
9:32 ETCharlie
Good morning, Mike.No new buy today. Two things to review.
Ask Charlie by voice
Watch, do not buy yet. Charlie needs source and sizing checks.
Alert near Dad's reassessment zone before any trim decision.
Needs approval
Build a simpler stop walkthrough from Dad's feedback?
Research Brain
Charlie combines Dad's account, IBD discovery, finance emails, public headlines, Schwab Research, and memory into a plain-English answer.
Execution Workbench
Stops, trailing stops, buys, and sells move through draft, approval, preflight, submit, verify, and journal. No silent trading.
Self-Repair
Charlie detects broken auth, stale sources, missing quotes, browser issues, and files repair requests before Dad has to diagnose them.
Codex Build Queue
Dad's feature requests become proposals for Will. Approved proposals become Codex build tasks with tests and review.
How it becomes a real app
- Dad talks to Charlie on phone or desktop.
- Charlie reads account context, source evidence, alerts, and memory.
- Charlie gives a Dad-readable recommendation or creates a proposal.
- Will approves research, feature builds, emails, or execution steps.
- Codex builds approved changes in a branch, verifies, and returns a review.