Governance & Leadership Structure
The Framework M Software Foundation operates under a collaborative, open-governance model inspired by leading open-source software foundations.
Our governance structure emphasizes Lazy Consensus, mandatory Consensus Seeking, and Committee Stewardship to build trust, foster co-design, and provide clear operational leadership.
1. Governance Committees & Leadership Division
Operational leadership is structured around two dedicated committees reporting to the Board of Directors:
A. Technical Steering Committee (TSC)
- Scope: Architectural decisions (ADRs/RFCs), release cycles, core monorepo packages, CI/CD pipelines, and maintainer onboarding.
- Role: The TSC provides technical leadership, driving software architecture innovation, maintaining code quality standards, and governing core repository releases.
B. Community Development Committee (CDC)
- Scope: Community development, member outreach, ecosystem growth, contributor programs, and membership verification.
- Role: The CDC leads community engagement, member advocacy, developer events, and public outreach across individual and institutional membership tiers.
2. Membership Tier Matrix
The Foundation maintains transparent membership classes based on equity ownership, annual contributions, and honorary community recognition:
| Membership Class | Description & Access | Fee / Structure | Voting & Rights |
|---|---|---|---|
| Permanent Members | Shareholders / Equity Owners who purchase Foundation shares | Permanent / Equity Purchase | Voting Rights & Board Representation |
| Corporate Annual Members | Enterprise & Institutional adopters | Annual Membership | Technical advisory, B2B engagement & ecosystem priority |
| Individual Annual Members | Professional developers, students & academics | Annual Membership | Contributor access, educational resources & community tools |
| Honorary Members | Outstanding open-source contributors & community leaders | Free / Non-paying (Nominated) | Recognized advisory status & merit-based nomination |
3. Decision-Making & Dispute Resolution
Framework M employs a progressive consensus model designed to encourage joint problem-solving:
Decision Lifecycle:
- Lazy Consensus (Default): Day-to-day RFCs, documentation updates, and routine committee operations pass automatically if no explicit objections are raised within a 72-hour window.
- Mandatory 7-Day Consensus-Seeking Window: If a committee member or director raises a reasoned objection, it triggers a mandatory 7-day joint refinement period for collaborative co-design and compromise.
- Board Escalation & Resolution: If a proposal remains unresolved after the 7-day consensus-seeking period, it is escalated directly to the Board of Directors for final review and binding resolution.
Decision-Making Frameworks
- Request for Comments (RFCs): Used for proposing technical features and protocol changes.
- Architecture Decision Records (ADRs): Logging architectural choices.
- Contributor License Agreement (CLA): Intellectual property rights management for code contributions.