**Design Reflections** are the built-in feedback moments—our retrospectives. After a guide runs in the world (a meeting, a review, a decision), we capture what actually happened as small edits to the story: which beats landed, which roles showed up, which spells helped or hindered.
Sometimes we tighten a definition or redraw an icon; sometimes we **fork** and let two approaches evolve in parallel. Because every change is local, attributable, and easy to compare, the library improves without forcing consensus.
Over time, this loop curates an openly licensed set of high-quality glyphs and scenes that both **illustrate** our narratives and **power** the workflows behind them.
Governance benefits most: roles, consent, evidence, and outcomes are expressed as readable stories and runnable guides. The map stays live, the stories stay plural, and the software stays forkable—so the design keeps learning.
# See - Beat Page Template - Icons & Scenes - Icons as Buttons