blueprint
Blueprint
A blueprint is the foundation a project is built on: the context that only the owner, the market and the money can supply, established carefully enough that anyone who builds, markets or runs the project can reason from it. It answers why this exists, for whom, what they need, how it wins, whether it makes money, what it is made of, what it may spend, how it should feel, and where it is going.
It is established with the owner, not written for them. The value is partly in the documents and partly in the understanding the two of you build while producing them. The owner sharpens an idea they may never have fully articulated. You learn the project well enough to make good calls later, and so does every model and person who reads it afterward.
What a blueprint holds, and what it leaves to the builder
| File | Establishes | Leaves to the builder |
|---|---|---|
vision.md |
Core idea · vision · philosophy · why us | Feature ideas, solutions |
market.md |
Market research (segments, size, alternatives, competitors, evidence of demand) · market strategy (wedge, positioning, channels, moat) | Campaign plans, content calendars |
business.md |
Business model and pricing · economics · targets | Payment-provider implementation |
product.md |
Users and their requirements · product requirements · quality bar · boundaries · success measures | Screens, flows, components, schemas, routes, APIs, copy |
brand.md |
Name · positioning · personality and voice · visual direction · assets | Design tokens, type scales, component styling, layouts |
stack.md |
Stack decisions and the criteria for open ones · infrastructure · resources · constraints · secrets policy | Architecture, data models, service boundaries, code structure |
plan.md |
Mission · phases and exit criteria · milestones · bets · risks · kill criteria · deferrals | Task lists, sprints, tickets, status |
The boundary follows from what models are now good at. Frontier models design interfaces, architect systems, model data, write copy and plan implementation well, often better than a specification written months earlier by someone who could not see the build. A blueprint that pre-decides those things caps the work at its author's level and goes stale the moment the build improves on it. What no model can work out is the owner's intent, the market's reality and the money's limits. The blueprint holds exactly that, thoroughly, and nothing else.