Token sheets that clients actually annotate

Tokens fail when they read like engineering-only shorthand. We split sheets into three bands: public names clients may repeat, internal aliases only your team uses, and deprecated labels marked with a strike tone.

We also print a one-page legend beside every review link. The legend explains how to suggest a change without inventing new vocabulary mid-project.

During critiques, we forbid live color picking in meetings. Instead, clients mark sections with numbered pins tied to the token sheet. The rule sounds stiff, but it prevents rainbow drift.

Builders who adopt the pin method report shorter threads because decisions reference a row, not a screenshot region alone.