Storytelling

Narrate how projects fit together — drawing the corpus boundary correctly and grounding every cross-project link in a real reference. (Encodes the 2026-06-07 ecosystem-boundary lesson.)

Translate a project's architecture and capabilities into faithful prose for the reader — accurate to the code and docs, never aspirational.

Tell a project's story by synthesizing a high-signal dossier and grounding every claim in it — invent nothing; improve quality by enriching the dossier, not by loosening the grounding rule.

Reconstruct the build journey over time from the actual record — timeline, pivots, and rough spots — grounded in git history and decisions, never a narrated guess.

Write story prose that is consistent in voice, signal-dense, and fitted to its audience and channel.

State who a project is for, what it is for, and its concrete value — grounded in the material, not hype.