Return on Governance: A Measurement Standard to Make the Empowered ENS Foundation Verifiable

This is an addition to "Empowering the ENS Foundation," not a rejection of it. The three amendment tracks already on the table converge on one machine — the SPP3 committee model — as their proof that delegated, empowered bodies can work. They are right that it works. But every one of them stops at the same gap: they specify who decides and how members are appointed, and none specifies how the community will *measure* whether an empowered Foundation or committee is actually performing in the long stretches between the rare, consequential votes everyone agrees the DAO should be reduced to. A body you vote on twice a year is a body you are flying blind on for the other 363 days. Governance you cannot see is governance you cannot steward. The missing layer is a Return-on-Governance (RoG) reporting standard: a small, fixed set of outcome metrics, published on-chain on a fixed cadence, that turns 'trust the board' into 'verify the board.' Concretely: (1) Treasury performance — opening balance, inflows, outflows by category, closing balance, and realized vs. budgeted spend, every quarter, in a machine-readable schema so anyone can diff it. (2) Mandate delivery — each committee publishes its charter's objectives as dated, checkable line items (shipped / slipped / dropped), the same discipline SPP3 already imposes on applicants, now turned back on the empowered bodies themselves. (3) Allocation outcomes — for every grant or envelope above a threshold, a one-line stated goal at funding time and a one-line observed result at the next reporting window, so the community can see what past funding actually produced before it renews. Why this specifically strengthens the Foundation proposal rather than fighting it: the temp check's own weak point is that once custody moves, the community's remaining power is a reactive removal petition — a nuclear button with no dashboard. RoG reporting is the dashboard. It makes the removal backstop usable (you can point to a missed, published metric instead of litigating vibes), it makes the tiered-authorization and ZK-quorum ideas from the accountability track legible (you can see which tier was used and what it produced), and it makes the envelope model from the leaner-DAO track enforceable (you can see whether unspent funds actually returned). It is cheap: it reuses the reporting rhythm SPP3 already runs, asks for a schema rather than a new institution, and can ship as a required attachment to the first Foundation budget rather than as a separate governance fight. Recommendation: adopt a Return-on-Governance reporting standard as a ratification condition on empowering the Foundation — a fixed metric set, a fixed quarterly cadence, an on-chain machine-readable schema, and a rule that any structural authority granted (custody, envelope, committee mandate) carries a corresponding published metric before it takes effect, not after. Fund fewer things, vote on fewer things, but measure every one of them. If the goal is a DAO that votes rarely and matters every time it does, then the votes it does cast have to be informed — and that requires making the Foundation the most measured foundation in open source, not merely the most carefully constituted one.