The consolidation actions that follow directly from the reasoning — erasing concept-less families, absorbing duplicate families into a canonical survivor, and renaming families whose names fail to carry their stored concept. Empty only when the component truly has nothing to resolve.
Exact existing component namespace being consolidated.
Set-level reasoning for this component: which of its tables duplicate a concept modeled by another table (here or in another component) versus which are genuinely distinct — naming the stored concept, row grain, and lifecycle that decides each.
Per-component consolidation decided by the Database component-finalize pass.
Each survey reasons about one component's tables as a SET and carries the actions that follow directly from that reasoning, so a duplicate identified in the reasoning is consolidated in the same entry rather than noted in prose and forgotten.
Author
Samchon