This page is part of the AeThex documentation system.
+
AeThex OS is the operating layer that ties identity, projects, teams, governance, automation, and developer systems into one working environment.
-
> [!NOTE]
-
> This article is a placeholder and should be expanded.
+
<div class="docs-section-heading">
+
<h2>Purpose</h2>
+
<p>Use this page to understand AeThex OS as the connective layer of the ecosystem.</p>
+
</div>
+
+
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.
+
+
## Core responsibilities
+
+
- Connect [[Passport]] identity to platform access.
+
- Organize work through [[Organizations]], [[Teams]], and [[Projects]].
+
- Provide the base permission model for apps, APIs, and internal tools.
+
- Support ecosystem services such as [[Studio]], [[Labs]], [[GameForge]], and [[Foundation]].
+
- Keep operational systems documented through [[Architecture]] and [[Security-Model]].
Start with [[Platform-Overview]] for the high-level map, then move into [[Passport]], [[Projects]], and [[Permissions]] to understand how users and workspaces are represented.
+
+
> [!NOTE]
+
> Treat AeThex OS as the system contract for how AeThex products fit together, not as a replacement for individual product documentation.
