Eve · decision memo · 2026-07-02, night
Everything below is built, verified, and waiting on a word. Each block is one ruling: the call · why now · options with real consequences · my recommendation · what happens on your word. Answer in one line (“1b · 2a · 3a · 4a”) or annotate anything.
All four slices are merged and verified. The rail is dark; nothing sends until the flags flip AND you tap a card. The own-inbox proof is also the only way to verify the Gmail token’s send permission — code can’t see it.
What “yes” actually turns on (verified against the code): the draft surface + approve endpoint; the live executor — every send still gated on your tap, per card, forever in v1; and the command channel (the executor’s own AND requires it): free-text Telegram DMs to Eve start getting real conversational replies from her brain. Deterministic commands unchanged; Salesforce writes stay locked behind their own separate flag; the API key it needs is already live. Rollback: flags off — byte-identical to today, one command.
Options: a — flip now, watch the own-inbox draft land · b — flip at your desk, same protocol · c — hold.
Recommendation: b — a sitting where you can watch the whole journey and reply to yourself to see the watch flip. On “flip it”: I set the flags, verify live, and Eve lays her first real draft in your thread. Counterparty replies join existing threads only after the join-resolution slice (chipped); your own-inbox proof doesn’t need it.
The audit’s needs-new-source pile — 47 of the 147 questions being handed to you — is one source asked forty ways: deal stage, activity history, amounts, owner. No other seat expansion comes close.
Options: a — yes in principle; I author the full two-layer spec next (read-only creds, source discipline, promote-layer shape), build sequenced after Phase B · b — later; the unchecked-lists keep naming it, nothing breaks · c — no.
Recommendation: a. On your word: the spec lands for your red-pen; nothing touches Salesforce until it survives review and you ratify it.
The plan’s direction and all three calls are ratified; the annotatable surface still awaits your optional fine-detail red-pen. Phase B is the organ — discriminating questions, the check library, findings with receipts, the decision-memo screen — plus the brief-producer and the weak-line sharpening folded in.
Options: a — build now; your later annotations fold as amendments (Layer 1 is locked) · b — wait for your pass.
Recommendation: a — the baseline is frozen and the build order is evidence-confirmed; waiting buys polish on decisions already made. On your word: the Phase B workflow launches, same discipline as everything tonight.
“Every claim is tried in its own court” (+ the [M]/[J] authoring rule and the pairing pattern) currently binds Eve’s canon only. Promotion makes it govern every gate in every repo. Why it’s earned: it caught two real defects in one session, in opposite directions — my code-gate ruling on a meaning question (your catch), and a judgment-agent asserting a mechanical negative without a receipt (the audit’s false “fabrication,” killed by re-running the grep).
Options: a — yes; I draft the constitution amendment as its own one-page ruling for your ratification · b — keep it Eve-local and let it prove out further.
Recommendation: a. Nothing enters the constitution until you ratify the exact text.
Canonical source: docs/ai/design/eve-open-calls-2026-07-02.md. Sibling surfaces: the ratified draft-flow spec (/specs/eve-draft-flow-send-rail-2026-07-02.html) and the investigation-bar plan (/design/eve-investigation-bar-plan-2026-07-02.html), both on this same server.