Home A - Z
Page Index

AeThex Docs

Blame

92ce00 Anonymous 2026-06-20 21:50:44
Add AeThex documentation page
1 
# Database Design
2
e48b9b Anonymous 2026-06-23 03:31:08
3
Database Design documents how AeThex data should be modeled, related, secured, and evolved across the platform.
92ce00 Anonymous 2026-06-20 21:50:44
Add AeThex documentation page
4
e48b9b Anonymous 2026-06-23 03:31:08
5
<div class="docs-section-heading">
6
<h2>Design goals</h2>
7
<p>Data models should support identity, organizations, projects, permissions, and auditability.</p>
8
</div>
92ce00 Anonymous 2026-06-20 21:50:44
Add AeThex documentation page
9
e48b9b Anonymous 2026-06-23 03:31:08
10
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.
11
12
## Core entities
13
14
- Users and [[Profiles]]
15
- [[Passport]] identities and [[Linked-Accounts]]
16
- [[Organizations]] and [[Teams]]
17
- [[Projects]] and project resources
18
- [[Permissions]] and roles
19
- Events, audit logs, and integration records
20
21
## Design rules
22
23
1. Prefer stable IDs over display names.
24
2. Track ownership and organization context explicitly.
25
3. Keep permission checks close to protected data.
26
4. Store audit fields for important state changes.
27
5. Version schemas and migrations with clear rollback notes.
28
29
<div class="docs-grid">
30
<a class="docs-card" href="/Architecture">Architecture</a>
31
<a class="docs-card" href="/Security-Model">Security Model</a>
32
<a class="docs-card" href="/Permissions">Permissions</a>
33
<a class="docs-card" href="/Projects">Projects</a>
34
</div>