Goal: organization and roles
Reader: HR and managers showing who reports where and what each team covers. Meta cluster: C — infrastructure & governance Scenarios: 6 · Examples: 8
Scenarios
| Scenario | Tier | Engines | Example files |
|---|---|---|---|
| org structure | T0 | infographic, vega | platform-org-structure.md<br>team-reporting-tree.md<br>org-chart-radial-tree.md |
| team handoffs | T2 | echarts | chord-team-handoffs.md |
| workforce profile | T2 | vega | workforce-seniority-pyramid.md |
| capability coverage | T2 | infographic | team-capability-icon-grid.md |
| capability maturity | T2 | infographic | capability-pyramid-framework.md |
| org update | T2 | html-css | org-update-card.md |
Reading order
Reporting structure first, then what each team can cover, then the workforce shape.
Engines in this goal
echarts— report-grade charts and dashboards- HTML/CSS — system architecture diagrams, cards and page-level layouts (no fence)
infographic— template-driven boards, sequences and comparisonsvega/vega-lite— statistical views where the data needs transforms
Details, limits and anti-patterns: ../engines/echarts.md · ../engines/html-css.md · ../engines/infographic.md · ../engines/vega.md.
Palette
Every figure takes its colours from a theme. Pick one in
../styles/palette.md — the token contract, the theme index and the
per-engine blocks all start there.
Most figures in this set want Default. Depart from it for the medium, not the topic: Print when it may be photocopied, Contrast for low vision or large-print handouts, Vivid when it will be projected, Accessible when colour must not be the only cue, Editorial for long-form reading, Slate for technical reference, Pastel when the figure sits inside gentle prose, Nord for a cool Nordic register. Every theme is designed for a light ground — the set has no dark page.
Don't
- An org chart with no indication of team size or scope
- Capability self-assessments with no evidence trail