# Open Source

Open Source explains how public AeThex code, documentation, tools, and community contributions should be managed.

<div class="docs-section-heading">
  <h2>Contribution model</h2>
  <p>Open-source work should be useful, reviewable, and connected to the platform roadmap.</p>
</div>

Open-source contributions can include code, docs, examples, issue triage, templates, and community tooling. This page should link contributors to the right repos, standards, and decision processes as they become public.

## Contribution areas

- Documentation updates.
- SDK examples and integration samples.
- CLI improvements.
- Community tooling.
- Bug reports and reproduction cases.
- Governance or standards proposals.

## Maintainer expectations

- Keep contribution instructions current.
- Label beginner-friendly and high-priority work.
- Require review for security-sensitive changes.
- Archive decisions in docs or governance notes.

<div class="docs-grid">
<a class="docs-card" href="/Governance">Governance</a>
<a class="docs-card" href="/Policies">Policies</a>
<a class="docs-card" href="/SDKs">SDKs</a>
<a class="docs-card" href="/CLI">CLI</a>
</div>