Governance

How decisions get made in the AI-Driven Dev Framework.

Four roles form a ladder, each rung keeps every right of the rungs below and adds its own.

👥 Roles

Tier	How you get there	Adds (on top of the rung below)	Team
Public	Free, any GitHub account	Open issues, comment, react / upvote ideas (signal only), open a pull request once its issue is validated	-
Core Team	Active AIDD programme member (training, community, coaching)	A counted roadmap vote + voice on direction	`core-team`
Certified Members	Pass the AIDD certification	Validate contribution issues (triage: move `Ideation` → `Todo` on the Roadmap board)	`certified-members`
Maintainer	Certified member promoted to give AIDD Trainings (Trusted Partner), or AIDD Staff	Approve & merge PRs, quality veto, appoint/promote, guard the standard	`trusted-partners`

Public reacts (👍 / upvote). This is a signal, not a counted vote; it promotes an item to a formal vote.
Core Team, Certified, Maintainer each cast one equal vote. The vote is a benefit of AIDD membership (the programme is a paid training / community / coaching offering), that is what turns a signal into a counted vote.
Maintainer holds the tiebreak and a quality veto as the top rung.
A poll runs ≥ 7 days. Accepted items land on the AIDD Roadmap board.
This vote decides roadmap priority, not whether a contribution issue can move to a PR, that validation is immediate, see CONTRIBUTING.md.

Merge authority is Maintainer only.
Lazy consensus (default): a Maintainer may merge if no other Maintainer objects within 72h, there is ≥1 Maintainer approval, and CI passes.
Quality veto: any Maintainer can block with a request-changes review until resolved.
Explicit consensus : for cross-plugin changes, contract changes, or licensing/governance changes: ≥2 Maintainer approve.