planning-data-architecture

To design database schemas for user stories, read the story scope and supporting architecture docs to identify entities and relationships, ensuring schema design aligns with consumed shared contracts. This prevents data model drift by validating architecture against story requirements.

Story-scoped data architecture is a data model validated against a specific user story's requirements and consumed contracts. You need it during Phase 3 planning when dispatching data architecture work for a single user story that includes data candidate domains.

Map database indexes to query access patterns by discovering implied read and write patterns from story planning documents, then explicitly defining index mappings that support those operations alongside integrity and migration considerations in the final data document.

Yes, you can use existing shared contracts when planning data architecture by treating them as authoritative sources for shared entities. This ensures the story-scoped schema design supports all required contract terms and prevents model drift.

The best way to document database migration and integrity considerations is to write them into a dedicated data architecture file. Define lifecycle-aware rules by mapping read/write patterns to indexes and outputting the final architecture to the story's data document.

No, planning data architecture is scoped for a single user story. It produces a story-specific data document by discovering entities and access patterns from that individual story's requirements and related planning documents.