Blueprint (architecture and plan)
- Status
- Review
- Version
- 1.1.0
- Authority
- Not stated
- Applies to
- Core
Definition
A blueprint is a project’s architecture description: the document that says how a product is built to meet its requirements and why. It names the stakeholders and their concerns, then covers, in twelve sections, goals, constraints, context and interfaces, solution strategy, building blocks, runtime, deployment and operations, cross-cutting concepts, decisions, quality requirements, risks and technical debt, and a glossary, with an annex that maps each requirement to a section. Every significant choice in it is recorded as an ADR.
“Blueprint” is the Hub’s name for what ISO/IEC/IEEE 42010 calls an architecture description and many teams call a design document or design doc. Its section order follows arc42, cited by reference; the text is the Hub’s own.
Example
“The search runs inside the existing web container [ADR-0008]; an external search service was rejected for cost (see the record).” In a Hub project the blueprint is project/BLUEPRINT.md, written from templates/blueprint.md.
Related
- C4 model — how the context and container views are drawn.
- Architecture decision records — how choices are recorded.
- Architecture description — the sections, the tiers and the rules.
- Specification — the requirements the blueprint must cover.
- Project foundation — the playbook in which the blueprint is stage 5.
Sources
- Malte Ubl, “Design Docs at Google” — all rights reserved; summarised, not copied. Accessed 2026-11-20.
- The C4 model for visualising software architecture — CC BY 4.0; summarised, not copied. Accessed 2026-11-20.
- SWEBOK Guide v4.0 — all rights reserved; summarised, not copied. Accessed 2026-11-20.