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
| Field | Required | Type | Description |
|---|---|---|---|
kind | yes | "tier" | Must be exactly "tier" |
view | no | string | Rendering intent. Default: pyramid |
title | no | string | Title rendered above the diagram |
items | yes | array of Item | At least one item required |
Item fields
| Field | Required | Type | Description |
|---|---|---|---|
label | yes | string | Text displayed in the tier level |
emphasis | no | string | "primary" or "secondary". See schema. |
status | no | string | "success", "normal", "warning", or "critical". See schema. |
View values
| value | Meaning | Min items | Max items |
|---|---|---|---|
pyramid | Stacked layers from apex (first) to base (last) | 1 | — |
concentric | Nested 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
Example — concentric (onion)
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
| Slot | Measured in | Hangul (unchanged / whole) | Latin (unchanged / whole) |
|---|---|---|---|
items[].label | 3 items | — / — | — / — |
concentric
| Slot | Measured in | Hangul (unchanged / whole) | Latin (unchanged / whole) |
|---|---|---|---|
items[].label | 3 items | 11 / 11 | 19 / 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
| Field | Type | Required | Values / meaning |
|---|---|---|---|
kind | enum | yes | tier |
view | enum | no | pyramid, concentric |
title | string | no |
items — 1 or more elements
| Field | Type | Required | Values / meaning |
|---|---|---|---|
label | string | yes | |
emphasis | enum | no | primary, secondary |
status | enum | no | success, normal, warning, critical |
concentric
Fields
| Field | Type | Required | Values / meaning |
|---|---|---|---|
kind | enum | yes | tier |
view | enum | no | pyramid, concentric |
title | string | no |
items — 1 or more elements
| Field | Type | Required | Values / meaning |
|---|---|---|---|
label | string | yes | |
emphasis | enum | no | primary, secondary |
status | enum | no | success, normal, warning, critical |