Foundation Pool: Tranche the Treasury, Don't Transfer It Whole

TL;DR The temp check moves the DAO's full treasury under Foundation control on day one — estimates in the thread range from ~$143M (Endowment plus liquid treasury, per 5pence.eth) to ~$250M once other DAO-held ENS is counted, per James. This amendment doesn't contest giving the Foundation operational control of the treasury — it scopes the initial transfer to a dedicated Foundation Pool sized to actual operational run-rate, released in quarterly tranches that renew automatically unless the DAO votes to pause them. Treasury not tied to Foundation-relative activity stays under existing DAO control until a separate vote says otherwise. PROBLEM / DIAGNOSIS The temp check's case for giving the Foundation operational control rests on real, undisputed problems: delegate fatigue and slow grant-cycle turnaround. What it doesn't establish is that the full treasury needs to move on day one to fix that — the proposal asks for the whole amount up front, sized to nothing in particular, rather than to what the Foundation will actually spend running grants and operations. A one-time full transfer also means the DAO's only lever, once it's done, is the temp check's own removal process — there's no ongoing point where continued funding gets re-examined against actual spend. PROPOSED MECHANISM A dedicated Foundation Pool, released in quarterly tranches. Instead of a single, full-treasury transfer, the DAO ratifies a Foundation Pool sized to actual Foundation-relative activity — grant and operations run-rate — released in quarterly tranches. Each tranche renews automatically unless the DAO votes to pause it, so the default is "renew on evidence" rather than "trust indefinitely." Treasury not tied to Foundation-relative activity (the Endowment, and DAO-held ENS not committed to Foundation operations) stays under existing DAO control until a separate vote assigns it elsewhere. WHY AMEND RATHER THAN LEAVE AS WRITTEN This doesn't slow the Foundation down — quarterly tranches sized to real run-rate is still faster than the token-vote-per-decision status quo the temp check is trying to fix, and the Foundation gets predictable, renewing funding rather than having to ask for more. What it removes is the single biggest irreversible step in the current proposal: handing over the full treasury before there's any operating history to size the transfer against. GUARDRAILS, RED-LINES, REVERSIBILITY Treasury access is tranche-gated, not lump-sum — the single biggest lever for reversibility in this amendment. Treasury not tied to Foundation-relative activity is unaffected and stays under existing DAO control. Pausing a future tranche only requires a DAO vote — no need to invoke the temp check's higher-friction removal process to slow or stop funding. OPEN QUESTIONS THIS AMENDMENT ANSWERS 1. Should the DAO hand the whole treasury and Endowment to the Foundation? Not on day one. Scope the initial transfer to a Foundation Pool sized to Foundation-relative activity; leave the Endowment and unrelated treasury under existing DAO control pending a separate vote. Remaining open for the DAO to size with its own data: exact tranche cadence and amount, which needs real grant/ops spend data the DAO doesn't have yet from a Foundation that hasn't operated. THE ASK This is submitted as an amendment to the temp check's treasury-transfer terms — not a change to the Foundation's board, mandate, or formation process. The ask is for the full-treasury transfer to be replaced with a tranched Foundation Pool before the temp check goes to a binding vote.