{"source":"helm_charlie_feature_proposals","mode":"local_review_first","updatedAt":"2026-06-08T21:22:52.076Z","proposals":[{"id":"feature-proposal-2026-06-08T21-22-52.076Z-8c2f1092","createdAt":"2026-06-08T21:22:52.076Z","updatedAt":"2026-06-08T21:22:52.076Z","status":"local_review","requestedBy":"charlie_chat","originalRequest":"Dad says the stop page is confusing and we should build a simpler trailing stop walkthrough.","title":"Charlie Feature Proposal: Simpler Stop Walkthrough","problem":"Dad/Mike surfaced a possible product need: Dad says the stop page is confusing and we should build a simpler trailing stop walkthrough.","dadReadableSummary":"Charlie Feature Proposal: Simpler Stop Walkthrough: Dad/Mike surfaced a possible product need: Dad says the stop page is confusing and we should build a simpler trailing stop walkthrough.","suggestedBuild":"Build a Dad-readable stop workflow that shows current holding, existing stop evidence, fixed-vs-trailing explanation, step-by-step action, approval warning, and after-action verification.","affectedAreas":["stops/orders","Codex Builder queue"],"priority":"high","safetyNotes":["Do not send email, launch Codex, deploy code, or change Schwab orders from this proposal alone.","Any trade/order/stop feature must keep draft -> approval -> preflight -> execution -> verification as separate steps.","Feature should be Dad-readable and avoid internal implementation language on the main UI."],"acceptanceChecks":["Dad-facing copy explains the next action without relying on developer terminology.","No live email, trade, or deploy action happens without explicit approval.","Charlie can cite what was captured and what is still missing.","Stop/order workflows show current evidence and after-action verification.","Focused tests, TypeScript, build, and localhost smoke pass before review."],"codexTaskPrompt":"Charlie Feature Proposal: Simpler Stop Walkthrough\n\nDad/Mike request: Dad says the stop page is confusing and we should build a simpler trailing stop walkthrough.\nProblem: Dad/Mike surfaced a possible product need: Dad says the stop page is confusing and we should build a simpler trailing stop walkthrough.\nSuggested build: Build a Dad-readable stop workflow that shows current holding, existing stop evidence, fixed-vs-trailing explanation, step-by-step action, approval warning, and after-action verification.\nAffected areas: stops/orders, Codex Builder queue\n\nSafety notes:\n- Do not send email, launch Codex, deploy code, or change Schwab orders from this proposal alone.\n- Any trade/order/stop feature must keep draft -> approval -> preflight -> execution -> verification as separate steps.\n- Feature should be Dad-readable and avoid internal implementation language on the main UI.\n\nAcceptance checks:\n- Dad-facing copy explains the next action without relying on developer terminology.\n- No live email, trade, or deploy action happens without explicit approval.\n- Charlie can cite what was captured and what is still missing.\n- Stop/order workflows show current evidence and after-action verification.\n- Focused tests, TypeScript, build, and localhost smoke pass before review.\n\nProposal fingerprint: cf496e5f","approvalBoundary":"Local proposal only. Charlie has not emailed Will, launched Codex, changed Helm, deployed code, sent email, or touched Schwab. Will must approve before this becomes a Codex build task."}],"note":"Feature proposals stay local until Will approves email, Codex build, or dismissal."}