aesthetic-fork-workflowlisted

# Aesthetic Fork Workflow ## The rule Fork every aesthetic decision into two or three variants — never one, never five. Make the variants diverge in direction, not in intensity. Render each one for real: the actual image, the actual name in place, the actual paragraph, the actual screen. State one advisory pick with one reason before the human looks, then stop advocating. Let the human's eye rule, and treat that ruling as the trunk the next fork grows from. Never substitute adjectives for a render, and never present a single option as a decision. Keep the fork loop inside the decision's time-box. ## Triggers - A response is about to describe a look in adjectives and ask whether it sounds right. - Only one option is on the table and the deciding question is whether it feels correct rather than whether it works. - The user asks for a name, a logo direction, a color system, a layout, a package, or a voice. - A draft is being revised toward "warmer" or "cleaner" with no reference render to compare against. - The user asks the same settled question a third time about how something looks, which usually means they have never actually seen the alternative they are imagining. - Copy is being rewritten for tone and the discussion is happening at the level of tone words instead of at the level of sentences. - An interface change is being approved from a description of behavior rather than from a visible or clickable state. - Two people in the conversation are using the same aestheti