Blame
|
1 | # AeThex OS |
||||||
| 2 | ||||||||
|
3 | AeThex OS is the operating layer that ties identity, projects, teams, governance, automation, and developer systems into one working environment. |
||||||
|
4 | |||||||
|
5 | <div class="docs-section-heading"> |
||||||
| 6 | <h2>Purpose</h2> |
|||||||
| 7 | <p>Use this page to understand AeThex OS as the connective layer of the ecosystem.</p> |
|||||||
| 8 | </div> |
|||||||
| 9 | ||||||||
| 10 | AeThex OS is not a single app screen. It is the shared system model behind the AeThex network: accounts, permissions, organizations, projects, workflows, and platform services working together under one identity layer. |
|||||||
| 11 | ||||||||
| 12 | ## Core responsibilities |
|||||||
| 13 | ||||||||
| 14 | - Connect [[Passport]] identity to platform access. |
|||||||
| 15 | - Organize work through [[Organizations]], [[Teams]], and [[Projects]]. |
|||||||
| 16 | - Provide the base permission model for apps, APIs, and internal tools. |
|||||||
| 17 | - Support ecosystem services such as [[Studio]], [[Labs]], [[GameForge]], and [[Foundation]]. |
|||||||
| 18 | - Keep operational systems documented through [[Architecture]] and [[Security-Model]]. |
|||||||
|
19 | |||||||
|
20 | <div class="docs-grid"> |
||||||
| 21 | <a class="docs-card" href="/Passport">Passport</a> |
|||||||
| 22 | <a class="docs-card" href="/Organizations">Organizations</a> |
|||||||
| 23 | <a class="docs-card" href="/Projects">Projects</a> |
|||||||
| 24 | <a class="docs-card" href="/Architecture">Architecture</a> |
|||||||
| 25 | </div> |
|||||||
| 26 | ||||||||
| 27 | ## Where to go next |
|||||||
| 28 | ||||||||
| 29 | Start with [[Platform-Overview]] for the high-level map, then move into [[Passport]], [[Projects]], and [[Permissions]] to understand how users and workspaces are represented. |
|||||||
| 30 | ||||||||
| 31 | > [!NOTE] |
|||||||
| 32 | > Treat AeThex OS as the system contract for how AeThex products fit together, not as a replacement for individual product documentation. |
|||||||