Repository Docs & Knowledge Base

Consolidated Spensara documentation repository (722 Markdown & architecture documents in ../repository)

Detailed engineering and feature implementation specifications.

implementation-specs/specs/BackendDatabaseConsolidation/TASK2.2.md 1,449 bytes · Updated Oct 23, 2026 10:44 AM EDT

Raw File

TASK 2.2: Add backend customer API key and audit log persistence

Move Laravel-owned customer API keys and activity logs into backend persistence.

Likely files:

The backend must own:

API key persistence should remain customer-scoped and support secure create, update, read, and delete flows.

Audit logging, if retained, should be written by backend application operations rather than Laravel local model writes.

[ ] Backend has persistence for customer API keys
[ ] Backend has persistence for audit logs if retained
[ ] EF migration exists for the new tables
[ ] DI wiring exists for the new repositories/services
[ ] Laravel CustomerApiKey and ActivityLog are no longer required as sources of truth after cutover

Treat secrets carefully. Avoid exposing raw values beyond necessary admin workflows.
If activity log retention is not required, explicitly document that before skipping the entity.