Leigen — Q3 Alignment & Ratification Session
Rev 2 — July 19, evening. Async ratification is running: Bob's first eval-spec responses are in and folded into the tracker below. The meeting is now optional — this page is the working record. Orange chips = an answer is still owed.
The Goal (one paragraph)
Q3 = the AI Agent Prop Fund. Get at least one Intelligent Trading System (ITS) live by September 30 — starting with Marcus V2. Every Tradovate slot is a trader's seat that must be earned: each ITS gets a virtual capital pool and must grow it without blowing up, while passing a daily decision-quality review (DDQ). Mechanical strategies (ORB etc.) move to a simulation engine — they can power an ITS, but only agentic traders hold seats, because judgment is what makes live automation trustworthy.
Where Things Stand (as of Rev 2)
The Path — 5 Steps to "Marcus Is Deployed" (plain terms)
1. Safety plumbing (Vash — 2 of 3 built) — Three pieces: the name tag ✅ (every order records which trader placed it — built, in review), the receipt system ✅ (a restart or network hiccup can never cause a duplicate or orphaned order — built, in review), and the on-switch (trading authority is an explicit, expiring authorization that verifies it actually took effect — next).
2. One box (Bob — the current long pole) — Marcus's brain, broker connector, and commands currently live across different branches that can't import each other. Package them into one tested unit, so what we rehearse is exactly what runs.
3. Prove the books (Monday — automatic) — The bookkeeping bug (#147: real trades happened, zero fills recorded) is fixed and deployed. Monday's first ORB trade must land correctly in the books. No trusted books → no rehearsal.
4. The dress rehearsal (together, ~1 day) — Seven checks like a pre-flight: read-only checks → place & cancel a far-away order → one real supervised fill → move the stop & verify the broker moved it → restart mid-trade & recover → close out with records matching the broker exactly → switch off & prove no orders possible.
5. Deployed = evaluation begins (~Jul 28–Aug 1) — Marcus trades daily on his demo seat: virtual pool tracked, DDQ graded, Slack ping to Bob before each entry (logged, never controlling). Live money is a separate authorization after he passes — September.
Agenda (if the sit-down happens — otherwise the tracker above is the record)
Ratification Tracker (Rev 2 — Bob's responses folded in)
AGREED settled NEEDS ANSWER owner owes a call DEFAULT STANDS no objection raised — silence ratifies at merge
Clarifications (answering Bob's notes directly)
"What is B minus?" — what DDQ actually is. DDQ is Adam's daily grade of the trader's process, built from evidence (trade records, order lifecycles, decision logs) — never from P&L and never from the trader's self-report. Each day he checks five things: was the data healthy when the trader decided · did the trader stay inside its mandate · were risk rules respected · were the decisions defensible (including correctly doing nothing) · are the logs clean. "Avg ≥ B−" was shorthand for "consistently clean" — it confused its first reader, so the letter grades are dead. New proposal: each day is graded CLEAN / MINOR / MATERIAL / DISQUALIFYING; passing requires zero DISQUALIFYING days and no pattern of MATERIAL ones. A losing day can grade CLEAN; a winning day that broke rules cannot. The pool answers whether to trust a trader — DDQ answers why. Exact format is Adam's to ratify.
Where R goes (it doesn't fully die). Per Bob: the gates become plain dollars — pass +$1,500, fail −$1,000, daily lockout in dollars. But every trade still declares its planned risk at entry in its decision log: Adam needs it to check risk compliance anyway, and it quietly builds the dataset for comparing traders of different sizes when there's more than one seat filled. Logged, never gating.
Frozen mandate, in one breath (new since Bob's read) — The mandate is who the trader is: prompt, model, risk policy, input set. It freezes when the trader leaves the Foundry; changing any of it mid-eval voids the eval and sends the trader back for a fresh start. Everything around the trader — plumbing, data delivery routes, monitoring — stays freely changeable, logged. Rule of thumb: fix the desk, never the trader.
Still Owed — One Answer Each
The Two GEX Answers (#164) — Defined
GEX Answer #1 — Can our GEXstream login run in two places at once? Bob's Mac holds a logged-in GEXstream session that captures the rich options data (vGEX) Marcus decides on. For the VPS to capture that same feed on its own — the autonomy requirement — it needs its own logged-in session. The question: does GEXstream allow one account logged in from the Mac and the VPS simultaneously, or does the second login kick the first (or breach the terms), meaning we buy a second seat? A complete answer is one of: "simultaneous works, confirmed" · "second seat needed — it costs $X/mo" · "unclear from the ToS, here's what support said." Checking account settings, the ToS, or just testing a dual login for ten minutes settles it.
GEX Answer #2 — Where does the rich-capture code live? Bob built the Mac-local capture that logs the rich GEX snapshots Marcus uses. Vash has to port that exact capture to the VPS so both machines record the same thing — then prove they match with a two-session parity check. The question: where is the source — which repo, branch, and folder? If it only exists on the Mac, push it anywhere reachable. A complete answer: a repo/branch/path, plus one line on how it runs — dependencies, the login flow, and when/how often it captures.
Why these two, and how urgent — Neither blocks the evaluation: Marcus runs on Bob's Mac-local data through every supervised phase, per the ratified data ruling (#170). But both block Vash's #164 build starting next week — and #164/#165 (VPS captures its own rich GEX + delivers it verifiably) are the hard gates for autonomy and live capital. Every week these answers wait, the September live milestone gets tighter. Ten minutes of Bob's time now protects the quarter's endgame.
Timeline
NOW ————————— late July ————————— August ——————————— September ——→
Mon: books proof Rehearsal G1–G3 EVALUATION RUNS DAILY pass → LIVE ($1–1.5k)
(#147 acceptance) G4 supervised fill (Bob's Mac data, Bob |
~Jul 24–28 supervising, VPS executes) |
—— in parallel —— |
#164/#165: VPS rich GEX └─ then Mac Mini =
+ delivery (autonomy gate) autonomous host
Mini purchased + set up (brains only)
Who Owns What
Sources: PR #182 (Evaluation Spec v1 + frozen mandate), PR #177 (Q3 OKR), issue #170 (Marcus cutover master, incl. the data ruling), PR #183 (trader_id), savegame 2026-07-19, Bob's async eval-spec notes (7/19 evening). Rev 2 — updated July 19, 2026, evening.