Turfi Platform Documentation

Standard Status Values

• active: current and available for normal platform operations.
• inactive: retained for history or temporary suppression, but not treated as current.
• archived: historical and intentionally out of the active operating set.

Transition Rules

• Status transitions should preserve referential integrity and historical records.
• Registries with governed delete or historical invariants should favor lifecycle transitions over destructive delete.
• Where a table uses is_active rather than a dedicated status, the admin UI may synthesize lifecycle display state from that boolean.

Entity-Specific Notes

• Players, organizations, clubs, and teams have higher lifecycle sensitivity because downstream history, participation, and duplicate-resolution systems depend on them.
• Shared-data entities such as addresses and contacts should normally be inactivated or relinked, not deleted, when dependencies exist.