Domain Compression

Consolidate overlapping domain concepts by extracting the minimal set of entities, actions, and states from technical requirements, then renaming duplicate entities to unify terminology while keeping behavior intact. This ensures scenario architecture stays aligned with its PRD and implementation.

Domain modeling terminology drift occurs when duplicate data shapes, names, or flows diverge across requirements and code. It causes scenario architecture incoherence, requiring duplication collapse to unify redundant paths under a single expressive concept without regressing functionality.

Unify duplicate data shapes and flows by spotting repeated structures across layers and renaming duplicate entities under a single expressive concept. Document the collapsed domain model in docs/concepts/ARCHITECTURE.md to maintain consistent names and shapes without regressing functionality.

Compress domain concepts from a PRD when analyzing architecture documentation reveals overlapping terminology and redundant paths. Apply domain core reconstruction to extract minimal entities, actions, and states, ensuring actors and flows share consistent names across layers.

Domain compression normalizes terminology across architectural layers by reading scenario docs and collapsing redundant domain concepts into one consistent vocabulary. It simplifies redundant paths and updates data shapes so actors, flows, and states remain coherent.

The limitation of compressing domain concepts is that behavior must remain intact during duplication collapse. You must document the collapsed model and update data shapes and flows carefully to avoid regressing functionality when renaming duplicate entities across layers.