Association Hierarchy
What It Models
The hierarchy describes how the association arranges national bodies, regions, chapters and other units. Staff define the permitted kinds of placement and can inspect both today's arrangement and earlier parentage.
Identity and Attributes
Unit kinds supply placement permissions, affiliation choices and availability. Units hold current parent references; derived ancestry and depth support navigation and validation. Dated parent periods retain the explanation and actor, while versions preserve what an earlier reader could have known.
Relationships
Units supply the nodes being arranged. Programs and packages reference kinds when defining which units a membership requires. Those references belong to configuration and do not transfer ownership of the kind catalogue.
Invariants
The structured invariants identify placement checks and their enforcement points. Their scope distinguishes ordinary placement transactions from imports, which deliberately defer rebuilding until the producer finishes.
How It Is Stored and Shared
The structure service stores kinds, current ancestry and dated parentage. Configuration reads kinds for validation, and other applications can read ancestry through published database functions. Unit and kind query registrations describe the datasets Platform can expose.
Open Design Questions
Product must settle the current-tree treatment of a merged source and whether scheduled restructuring is needed. Historical answers use current unit names and codes, and a same-day placement correction retains its predecessor only in versions.