Database & Auth Roadmap

Trentarev exclusively uses local SQLite (via better-sqlite3) for persistence, eliminating external database overhead.

Write-Capable Tables

• Calls: Immutable events documenting structural positions.
• Activity: Append-only log defining changes or exits.
• Derivatives: Profile statistics are computationally aggregated from Calls + Activity.

Looking Forward (v2 Auth)

Currently, the app assumes a single local user. To permit cloud syncing, we plan to adopt:

1. Session Enforcement: Asymmetric JWT validation.
2. Row-Level Security: Migrating user_id into the indexing strategy.
3. Key-Exchange Integration: GitHub OAuth for minimal friction.