# Database Design

Database Design documents how AeThex data should be modeled, related, secured, and evolved across the platform.

<div class="docs-section-heading">
  <h2>Design goals</h2>
  <p>Data models should support identity, organizations, projects, permissions, and auditability.</p>
</div>

AeThex data should be designed around durable platform concepts instead of temporary UI screens. The core model starts with users and identities, then expands into organizations, teams, projects, permissions, integrations, and operational records.

## Core entities

- Users and [[Profiles]]
- [[Passport]] identities and [[Linked-Accounts]]
- [[Organizations]] and [[Teams]]
- [[Projects]] and project resources
- [[Permissions]] and roles
- Events, audit logs, and integration records

## Design rules

1. Prefer stable IDs over display names.
2. Track ownership and organization context explicitly.
3. Keep permission checks close to protected data.
4. Store audit fields for important state changes.
5. Version schemas and migrations with clear rollback notes.

<div class="docs-grid">
<a class="docs-card" href="/Architecture">Architecture</a>
<a class="docs-card" href="/Security-Model">Security Model</a>
<a class="docs-card" href="/Permissions">Permissions</a>
<a class="docs-card" href="/Projects">Projects</a>
</div>