Segmentation · The consequence test · Element
The merges
Segments treated identically that should be combined.
The part
What it is
Identified mechanically from the differences: any two segments with no differing treatment are one segment.
Merging is resisted because segmentation work is expensive, which is a sunk cost rather than an argument.
The smallest level
The attributes it carries
Each attribute is one of the framework’s shared types. What a date is, and how it is written, is defined once for the whole model — the note here says what it means in this particular place.
The other elements in the consequence test
The differences
What is actually done differently.
LearnThe cost
What treating a segment separately costs.
Learn