Governance-to-Execution Model
Purpose: Alignment, clarity, onboarding
Audience: Internal team, partners, funders, reviewers
I. Overview
Purpose of the architecture Relationship between DAO governance and L3C execution II. Executive Financial & Capital Execution Role(s)
(role-agnostic; instantiated by title as needed)
Canonical definition of the financial and capital execution function Executive scope, hierarchy, and delegation logic Operation across DAO, L3C, and affiliated entities Note: Specific titles (e.g., Director of Finance & Investments, Treasury Steward) are defined contextually and may vary by entity.
III. Treasury & Capital Management Scope
Liquidity and runway management Capital allocation and deployment Risk management, controls, and security Financial intelligence and reporting IV. Capital & Financial Strategy Scope
Investment and deployment logic Financial and investment policy design Ecosystem capital coordination V. Authority Boundaries
What governance bodies control (DAO, Board, Council) What legal entities control (L3C, foundation, operating entity) What execution roles are authorized to execute Explicit non-authorities and reserved powers VI. Execution Model
Governance → mandate → execution flow Reporting, feedback, and escalation loops VII. Accountability & Stewardship
Fiduciary posture and duty of care Mission and mandate alignment Long-horizon responsibility and non-extractive principles VIII. Use, Adaptation & Evolution
How this architecture is applied across entities and roles Role instantiation and succession Review, update, and amendment process Why this is the right abstraction
✅ Architecture is now person-independent ✅ Roles can change without rewriting governance ✅ Supports multiple execution roles, not just one ✅ Cleanly instantiates your role elsewhere (Role Specification) ✅ Reads as institutional, not personal
Your specific role now lives in:
Role Specification: Director of Finance & Investments Commons Steward role definition DAO Treasury Steward section
The architecture stays stable.
Optional (but recommended) addition
If you want to future-proof even more, add this sentence to Section II:
This architecture supports one or more delegated execution roles, which may be held by individuals or teams and instantiated under different titles across legal and governance contexts.