Scott.Idem/OSIT-AE-App-Svelte
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: seventh-pass archive unsafe legacy references

Browse Source
This commit is contained in:
Scott Idem
2026-06-12 17:07:03 -04:00
parent e6fb4b289f
commit 75e7ca541a
12 changed files with 61 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
documentation/AE__Architecture.md
View File

@@ -1,5 +1,7 @@
# Aether Project Architecture
**Last Updated:** 2026-06-12
This document outlines the overall architecture and key technologies used in the Aether SvelteKit frontend project.
## 1. Project Overview
@@ -20,7 +22,7 @@ The Aether project is a Svelte and SvelteKit based application, utilizing Tailwi
- TipTap (`element_editor_tiptap.svelte`) — WYSIWYG rich-text for content fields (IDAA, Journals, Leads notes)
- **Icons:** Lucide Icons (SVG Icons)
- **Markdown Parsing:** `marked` library
- **State Management:** Svelte stores, potentially with `liveQuery` from Dexie for reactive IndexedDB interactions.
- **State Management:** Svelte 5 runes plus Dexie `liveQuery`. Events persisted state uses `runed` `PersistedState`; core and IDAA still contain legacy coarse-grained persisted stores pending migration.
### 2.1. Journals as the Canonical Frontend Pattern
@@ -78,8 +80,8 @@ Used for client-side persistence of various application states and configuration
Used for more structured client-side data storage, often for caching and offline capabilities.
- `ae_core_db`: Core database instance.
- `<module>`: Module-specific database instances.
- `db_core`: Core database instance.
- `db_<module>`: Module-specific database instances (for example, `db_events` and `db_journals`).
- `<custom>`: Custom module-specific database instances (none currently defined).
## 5. Data Sorting
@@ -97,9 +99,9 @@ A set of standardized field names and types are used across Aether objects.
These fields are expected to be present in most Aether objects.
- `id`: Primary key for an object (internal use, often a UUID).
- `id_random`: Randomly generated ID for an object (often used for external exposure or URL parameters).
- `<object_type>_id_random`: Specific random ID for an object (e.g., `person_id_random`).
- `<object_type>_id`: Canonical randomized string ID returned by V3 (for example, `person_id`). Use this for URLs, relationships, and Dexie indexed lookups.
- `id`: Generic randomized string alias when returned by V3; do not assume it is a DB autonumber.
- `id_random` / `<object_type>_id_random`: Legacy aliases. Do not introduce new usage.
- `code`: Short, unique identifier.
- `name`: Display name.
- `enable`: Boolean for active/inactive status.