business-blueprintlisted

# Business Blueprint ## What this makes Three files, in order, each kept so the person can see their own thinking change: ```text PLAN-v0.md what they said, sorted. Facts and assumptions, nothing added PLAN-v1.md after the attack. What changed, and the finding that changed it PLAN-v2-BLUEPRINT.md after real answers from real people. Every change cites a response PLAN-v3-BLUEPRINT.md only if the Blueprint changes later. The highest number is current ``` v2 has a name because it is a different kind of document. v0 and v1 are thinking. The Blueprint is a decision backed by evidence. Whatever gets built later starts there. Speak in plain words, short sentences. Answer in the language the person wrote in; the file headings and [PENDING] stay in English. No em-dashes in text you write. ## The four laws 1. **Never invent a fact.** Not a price, a customer, a number, a competitor, a market size, a name. If they did not say it, it does not go in the file. A guess that helps the plan look finished is the whole disease this skill exists to treat. 2. **Every guess is labelled Assumption. Every unknown stays [PENDING].** A plan with visible holes is worth more than a plan with invisible ones. 3. **Never rewrite their plan for them.** Ask, then write what they said. The person owns the decision. An agent that improves the plan by itself has taken the business. 4. **A version never skips.** No v1 without the attack. No v2 without real answers from