FreeSCIM Database Control | Living ERD, Migration and Pruning

FreeSCIM living ERD showing identity, federation, infrastructure, evidence, and maintenance data domains — The living ERD keeps relationships visible as the platform evolves.

Governed maintenance sequence

InspectPreviewBack upApproveMigrate or pruneVacuum/analyzeVerify

Control surfaces

Living ERD

Current tables, relationships, domains, and schema evolution instead of a stale architecture drawing.

Runtime audit

Connectivity, required tables, indexes, migration ledger, storage, and schema gaps.

Migration console

Dry-run preview, checksums, statement counts, destructive-SQL detection, advisory locking, approval, and results.

Retention and pruning

Policy-based age retention, dry-run counts, bounded batches, optional size caps, and oldest-first deletion.

Backup and recovery

Pre-maintenance backups, restore posture, survivability, and rollback context.

Maintenance

Vacuum/analyze and post-operation verification with secret-safe output.

Safety guarantees

The safe migration path detects and blocks destructive SQL.
An advisory lock prevents concurrent migration execution.
Migration files are hashed and reconciled with the migration ledger.
Pruning is previewable and runs in bounded batches.
Database URLs and credentials are never printed in maintenance output.
Backup comes first unless a separately justified break-glass path is chosen.

The database is part of the control plane

Sessions, snapshots, mappings, topology, security events, operational memory, classroom state, and reconciliation all depend on a healthy schema. FreeSCIM therefore treats database lifecycle, retention, and recovery as first-class operational responsibilities.