Blame
|
1 | # Governance |
||||||
| 2 | ||||||||
|
3 | Governance describes how decisions, proposals, policies, and stewardship work across AeThex. |
||||||
|
4 | |||||||
|
5 | <div class="docs-section-heading"> |
||||||
| 6 | <h2>Purpose</h2> |
|||||||
| 7 | <p>Governance keeps ecosystem decisions visible, reviewable, and connected to the people affected by them.</p> |
|||||||
| 8 | </div> |
|||||||
|
9 | |||||||
|
10 | Governance is the decision-making layer. It should explain how proposals are created, reviewed, accepted, rejected, implemented, and archived. It connects closely with [[Foundation]], [[Policies]], [[Open-Source]], and [[Community]]. |
||||||
| 11 | ||||||||
| 12 | ## Governance areas |
|||||||
| 13 | ||||||||
| 14 | - Proposal intake and review. |
|||||||
| 15 | - Policy changes. |
|||||||
| 16 | - Open-source contribution direction. |
|||||||
| 17 | - Ecosystem standards. |
|||||||
| 18 | - Public roadmap and stewardship decisions. |
|||||||
| 19 | ||||||||
| 20 | ## Proposal lifecycle |
|||||||
| 21 | ||||||||
| 22 | 1. Draft the proposal with context and motivation. |
|||||||
| 23 | 2. Identify affected systems, teams, and communities. |
|||||||
| 24 | 3. Invite review from maintainers or stakeholders. |
|||||||
| 25 | 4. Record the decision and rationale. |
|||||||
| 26 | 5. Track implementation and follow-up work. |
|||||||
| 27 | ||||||||
| 28 | <div class="docs-grid"> |
|||||||
| 29 | <a class="docs-card" href="/Foundation">Foundation</a> |
|||||||
| 30 | <a class="docs-card" href="/Policies">Policies</a> |
|||||||
| 31 | <a class="docs-card" href="/Open-Source">Open Source</a> |
|||||||
| 32 | <a class="docs-card" href="/Community">Community</a> |
|||||||
| 33 | </div> |
|||||||