Goal: engineering operations
Reader: Engineering managers running recurring rituals and release operations. Meta cluster: B — process & systems Scenarios: 8 · Examples: 11
Scenarios
| Scenario | Tier | Engines | Example files |
|---|---|---|---|
| deploy rhythm | T1 | vega | deploy-frequency-calendar.md<br>deploy-punchcard-weekday-hour.md |
| ops rhythm | T1 | infographic | quarterly-business-rhythm.md<br>operating-cycle-loop.md |
| shift handover | T1 | infographic | support-shift-handover.md<br>shift-handover-timeline.md |
| release pace | T1 | echarts | calendar-release-pace.md |
| launch readiness | T1 | infographic | launch-readiness-checklist.md |
| oncall coverage | T1 | infographic | oncall-coverage-wheel.md |
| ops checklist | T1 | infographic | daily-ops-checklist-columns.md |
| standup | T1 | infographic | sprint-standup-talking-points.md |
Reading order
Ritual boards (standup, rhythm, checklist) are read top-down; deploy/pace calendars are read as texture.
Engines in this goal
echarts— report-grade charts and dashboardsinfographic— template-driven boards, sequences and comparisonsvega/vega-lite— statistical views where the data needs transforms
Details, limits and anti-patterns: ../engines/echarts.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
- A twelve-step ritual board → split into recurring and one-off work
- Checklists with no owner in the description