Source: frameworks/kit-blueprint/02-blueprint-terminology.md
Blueprint — Terminology
Client-facing vocabulary. These are the terms the client sees. No internal jargon.
Terms the Client Sees
| Internal Term | Client-Facing Term | Why |
|---|
| Constraint | (never used) | Replaced by observable situation descriptions |
| CPM | (never used) | Client sees "From Your Constraint Briefs" as a section label |
| Deploy chain | "How Each Build Gets Deployed" | The process visualization, not the internal term |
| Upstream/Downstream | (never used) | Internal classification only |
| GPS | (never used) | Internal tracking only |
| Mode 1/2/3 | (never used) | Internal operating modes |
| Prework | "What We Need From You" | Reframed as a request, not a requirement |
| Build | "Build" | This term IS used — clients understand it |
| Active/Queued | Shown visually, not labeled | Active builds have prominent styling; queued builds are dimmed |
Deploy Chain (Client View)
The client sees the 8-step process but with role names instead of internal owner codes:
| Step | What the Client Sees |
|---|
| Design | Advisor creates it |
| Review | Client reviews it |
| Implement | Advisor builds the final version |
| QC Round 1 | Quality check |
| Train | Team gets trained |
| QC Round 2 | Verification in practice |
| Team Runs It | Goes live |
| Optimize | Ongoing refinement |
The deploy chain legend shows three colors with names:
- Advisor color (e.g., steel blue) — steps the advisor handles
- Client color (e.g., copper/terra cotta) — steps requiring client action
- Team color (e.g., gold) — steps involving the client's team
Build Card States
| State | Visual Treatment | What the Client Understands |
|---|
| Active | Navy left border, full opacity | "This is being worked on now" |
| Queued | Dimmed opacity (0.8) | "This is coming up next" |
Prework / Needs States
| State | Visual Treatment | Client Experience |
|---|
| Still Needed | Navy accent, prominent card with explanation | "Here's what we need and why" |
| Received | Green accent, compressed grid | "Got it, thank you" |
Questions States
| State | Visual Treatment | Client Experience |
|---|
| Open | Navy accent, prominent card with context | "Here's what we need to figure out together" |
| Resolved | Green accent, compressed with inline answer | "Decided — here's what we landed on" |
Timeline Dot States
| State | Visual | Meaning |
|---|
| Complete | Green filled dot | "This week is done" |
| Current | Navy filled dot | "We're here now" |
| Future | Gray outline dot | "Coming up" |
Forbidden Terms
Never use these in a blueprint. They belong in internal documents only:
- Constraint, constraint ID (C1, C2, etc.)
- Upstream, downstream, co-primary, secondary
- CPM, matrix, constraint priority matrix
- GPS, position, direction, speed (as framework terms)
- Mode 1, Mode 2, Mode 3
- Tier 1, Tier 2 (constraint tiers)
- Pattern markers (recurring, escalating, same root cause)
- Product constraint
- Evidence base
- Stakeholder card