Blueprints

Build · blueprint

▶Start here

You are here: Build → Blueprints This type is for you if: you need system structure, ownership, and phased rollout before you run a playbook or open the repo. Not this? Playbooks = execute · Laravel/CodeCanyon guides = theory without build intent.

The map

graph TD
  BP["Blueprint"] --> Arch["Architecture"]
  BP --> Own["Ownership"]
  BP --> Plan["Phased plan"]
  Plan --> PB["Playbook<br/>when executable"]

---

Start here

No blueprints published yet. When you add one, place it at build/blueprints/<category>/<subcategory>/<slug>.mdx with matching frontmatter — see Path layout.

CodeCanyon playbook Execution path after design is agreed.

Laravel architecture guide System shape that often becomes a blueprint input.

Laravel concepts handbook ZajModules, admin tiers, schema — design anchors.

Understand everything — blueprint vs playbook

Keep the blueprint as the design anchor when a playbook grows out of it — don’t delete the architecture when you add phases. Blueprints are diagram-heavy: boundaries, ownership, and before/after phases.