Docs menu

Method guide / Blueprint

Design before generation.

A Blueprint gives business and technical owners a shared design to review before consequential implementation begins.

Make the important design choices reviewable

The Blueprint explains the intended solution, the major boundaries, and the tradeoffs that matter to the outcome. Its exact form and depth depend on the system and the risk of the change.

  • System boundaries and important interfaces
  • Security and operational considerations
  • Migration and continuity risks
  • Open decisions and the planned evidence

Architecture remains accountable to the Goal

A design is valuable when the customer can understand why it supports the Goal, which Context shaped it, and what evidence will be used to evaluate the result. Private design artifacts and internal implementation methods remain engagement-specific.