Skip to content

Domain And Data Model

Purpose: model the durable truth of the system so data integrity, auditability, lifecycle, and configuration are visible.

Use this section by itself when entities, ownership, migrations, retention, or audit requirements need review.

Inputs

  • Core entities.
  • Entity ownership.
  • Lifecycle states.
  • Required, calculated, derived, or configured fields.
  • Audit and immutability needs.
  • Migration and seed-data posture.

Outputs

  • Conceptual data model.
  • Entity lifecycle map.
  • Audit requirements.
  • Configuration model.
  • Data integrity risks.

Agent Task Contract

Help the reader identify entities, lifecycle, audit events, retention decisions, migrations, and test-data needs. Do not invent data ownership or compliance requirements without evidence.