**Design Narratives** turn collaborative storytelling into a practical design loop—very close to agile user stories, but written in scenes and beats. Where agile might say “As a ___, I want ___ so that ___,” we say: *In this scene, [role] makes [move] in [place], using [spell], expecting [outcome].*
The scene is mapped on a Story maps page; the moves are expressed as reusable Story Glyphs —icons for function and sketches for feel — each with its own Icon Page and inline SVG.
Because each glyph can carry a tiny behavior (“spell”), a narrative reads as both story *and* specification. The rhythm is iterative and non-linear: **map → draft → playtest → reflect → fork → guide → govern → remap**.
Authors keep their own sites and voices, yet weaving is easy: press **Fork**, reuse or adapt the glyphs and scenes you need, and provenance follows the page.
In practice, a narrative becomes an executable guide: icons power UI, spells run the steps, and the page anchors meaning.
This lets students, researchers, artists, and developers move smoothly from *reading a story*, to *using an icon*, to *running a guide*, to *governing a project*—without giving up authorship or autonomy.
# See - Icons & Scenes and the starter pattern in Beat Page Template.