data-model-entities

Canonical data model entities enforce tenant scoping, soft deletes, immutable audit trails, and data retention policies across all platform schemas to prevent technical debt from diverging definitions. This Skill provides the authoritative reference for 19 core domain entities.

A data model entities reference serves as the single source of truth for platform data models and API shapes, defining core domain entities, their key fields, and relationships. It prevents schema divergence by acting as the canonical contract for database schemas and ORM models.

You need canonical entity definitions before writing any new database schema, migration, or ORM model to ensure adherence to the established data contract. This prevents technical debt by enforcing consistent data governance rules, including immutability and data retention policies.

Yes, the data model enforces data governance rules for immutable audit trails across all 19 core domain entities. It actively enforces tenant scoping, soft deletes, immutability, and data retention policies to maintain strict platform data integrity.

The best way to map relationships between core domain entities is to consult the canonical data model definitions. This Skill provides relationship mapping for all platform entities, ensuring you understand how different data models connect and interact within the platform.

Yes, you can use these canonical data model entities to generate database migrations. The definitions serve as the authoritative reference for database schemas, ensuring that your migrations maintain strict adherence to tenant scoping, soft deletes, and data retention policies.