CA-UNITYP · Unit Types & Hierarchy
The unit-type taxonomy, node archetypes, and hierarchy rules for the organization.
Configuration artifact
CA-UNITYP defines the unit-type taxonomy and hierarchy rules for one organization. It is the configuration basis that lets Nodes inherit archetype meaning and sit in a valid organizational topology.
How It Works
CA-UNITYP configures the unit-type taxonomy, the node-archetype assignment for each unit type, and the hierarchy rules. It is an active foundational artifact, visible from the start of configuration alongside CA-CUSNED, with no prerequisite of its own.
Dependency role. CA-UNITYP is always relevant. It has no prerequisites and is visible at start. Once validated, it is a prerequisite for CA-OFFNAT (with CA-CUSNED), for CA-UNILIF, and for CA-GTMACC.
Statements
- CA-UNITYP means Unit Types & Hierarchy.
- CA-UNITYP configures unit-type taxonomy, node-archetype assignment, and hierarchy rules.
- CA-UNITYP is an active foundational artifact visible at configuration start.
- CA-UNITYP has no prerequisite.
- CA-UNITYP, once validated, is a prerequisite for CA-OFFNAT, CA-UNILIF, and CA-GTMACC.
Why It Matters
Almost everything structural in O2A hangs off unit types: a Node draws its archetype from its unit type, and the hierarchy rules decide what valid topology looks like. Because so many later concerns — lifecycles, offerings, go-to-market — read against unit types, CA-UNITYP is foundational and unlocks the widest part of the graph.
Related
- Node — the entity that inherits its archetype from a unit type.
- CA-CUSNED — the other start artifact and CA-OFFNAT co-prerequisite.
- CA-UNILIF — the lifecycle artifact CA-UNITYP unlocks.
- Dependencies — the full unlock graph.