docs

These files are working notes, not part of the app. They are excluded from the public GitHub Pages site by _config.yml.

File	What	Refresh
PROJECT_OVERVIEW.md	What the system is, how the bot works, safety, research state, quality, incidents	Weekly
ROADMAP.md	Now, next, later, each with its gate	Weekly
CAREER_PORTFOLIO.md	Résumé bullets, stories, quotable numbers with caveats	Weekly, or after a notable change
OPENING_STRATEGY.md	History only: the retired opening window paper test (OW1), synopsis and theory	Never; the recorder was removed on 2026-10-12
PROPOSALS.md	Plain-words proposals for money you oversee while L1 runs: core savings, idle cash, a drawdown rule, L1 itself, a paper-first Kalshi experiment, and what is not proposed	When a research result changes the evidence, and before any new money goes anywhere
SPREAD1_FORWARD_TEST.md	Spec only: forward test of a spread filter (skip spread of 2c or more) on live L1 orders, shadow rule, sample, verdict words, kill criteria	Never; read once at its trigger
SUPPORT_CHAT_DESIGN.md	Design only: landing page "Got questions?" bubble, admin Inbox with ticket statuses, email replies, abuse controls, phases	Never; read when the owner says to start it
mockups/	Fixture-rendered screenshots of the Kalshi page (wide, menu open, phone)	When the page changes

Weekly refresh checklist

1. Update the date line at the top of each file.
2. Overview: live record (settled trades, wins, net), balance, variant count, forward-check status, anything new in the incidents list.
3. Roadmap: move finished items to "Done recently", re-read the gates, add what the week opened.
4. Career notes: only numbers that are in the overview; keep the caveat column.
5. Re-render mock-ups if the page changed (the fixture script is described in the PR that added them).
6. Never put keys, account numbers, or the owner's email in these files.