Tier

A tier diagram represents an ordered set of labeled levels. The view field determines how the levels are rendered and what relationship they express: pyramid shows them as ranked layers (importance, abstraction, or priority), while concentric shows them as nested rings (containment and dependency — the "onion" model).

Fields

FieldRequiredTypeDescription
kindyes"tier"Must be exactly "tier"
viewnostringRendering intent. Default: pyramid
titlenostringTitle rendered above the diagram
itemsyesarray of ItemAt least one item required

Item fields

FieldRequiredTypeDescription
labelyesstringText displayed in the tier level
emphasisnostring"primary" or "secondary". See schema.
statusnostring"success", "normal", "warning", or "critical". See schema.

View values

valueMeaningMin itemsMax items
pyramidStacked layers from apex (first) to base (last)1—
concentricNested rings from core (first, innermost) to periphery (last)1—

When view is omitted, the engine uses pyramid.

In concentric, item order reads inner → outer: the first item is the innermost core (the contained center), each subsequent item a ring enclosing it. This expresses containment and outer-depends-on-inner relationships (architecture layers, stakeholder rings, product layers). The data structure is identical to pyramid — only the rendering and the relationship it conveys differ.

Example

Maslow's Hierarchy of Needs Pyramid, top to base: Self-Actualization, Esteem, Love & Belonging, Safety, Physiological. Maslow's Hierarchy of Needs Self-Actualization Esteem Love & Belonging Safety Physiological

Example — concentric (onion)

Clean Architecture Layers Concentric rings, core outward: Entities, Use Cases, Interface Adapters, Frameworks & Drivers. Clean Architecture Layers Entities Use Cases Interface Adapters Frameworks & Drivers

Label capacity

How long a label can be before the engine sets it smaller, wraps it, or cuts it short with "…". Each number is measured by rendering a small reference declaration with a growing label and reading the diagnostics render_detailed returns, so the table always agrees with them. Lengths are in characters written without spaces: Hangul syllables are one em wide, Latin lowercase letters about half that. unchanged is the longest label shown at the usual size on one line; whole is the longest shown without "…". A slot's width depends on its siblings, so read a number as a guide for the reference declaration named in the second column and use declart validate --strict for the declaration itself.

A dash means the engine reports nothing for the slot up to 120 characters. That is not a promise that any length fits: a slot the engine does not fit at all draws a long label past the picture without a warning.

pyramid

SlotMeasured inHangul (unchanged / whole)Latin (unchanged / whole)
items[].label3 items— / —— / —

concentric

SlotMeasured inHangul (unchanged / whole)Latin (unchanged / whole)
items[].label3 items11 / 1119 / 19

Schema

What a declaration of this kind may contain, as declart schema and schema() report it. The value lists and counts are the ones the parser checks, and a test holds every field, count and rule to the parser in both directions, so a declaration written to this page parses. The prose above is the explanation; this is the reference.

pyramid

Fields

FieldTypeRequiredValues / meaning
kindenumyestier
viewenumnopyramid, concentric
titlestringno

items — 1 or more elements

FieldTypeRequiredValues / meaning
labelstringyes
emphasisenumnoprimary, secondary
statusenumnosuccess, normal, warning, critical

concentric

Fields

FieldTypeRequiredValues / meaning
kindenumyestier
viewenumnopyramid, concentric
titlestringno

items — 1 or more elements

FieldTypeRequiredValues / meaning
labelstringyes
emphasisenumnoprimary, secondary
statusenumnosuccess, normal, warning, critical