Source: frameworks/kit-master-plan/02-master-plan-terminology.md
Client Master Plan — Terminology
GPS
| Term | Meaning |
|---|
| Position | Where the client is right now — factual, specific, current state |
| Direction | Where they want to go — their goals in their language |
| Speed | How fast they're moving — readiness, urgency, bandwidth |
| Trajectory | Narrative synthesis of all three dimensions — momentum read |
GPS Change Markers
| Marker | When to Use |
|---|
| Changed | Something moved since last update |
| Consistent | No change from last update |
| Escalated | Urgency increased — situation intensified |
Constraint Types
| Emoji | Term | Meaning |
|---|
| ⬆️ | Upstream | Root cause level — solving this resolves downstream symptoms |
| ⬇️ | Downstream | Symptom level — resolves when its upstream cause is solved |
Constraint Tiers
| Tier | Label | Meaning | Border Color |
|---|
| Tier 1 | Solve This Week | Upstream + high opportunity cost + actionable now | Gold |
| Tier 2 | Find Upstream | Important but needs investigation before solving | Slate |
| Tier 3 | Queue | Solve after Tier 1/2 are deployed | Slate |
| Tier 4 | May Self-Resolve | Will likely resolve when upstream constraints are solved | Muted (reduced opacity) |
Constraint Pattern Tags
| Emoji | Term | Never Use | Meaning |
|---|
| 🔁 | Recurring | — | Happens repeatedly on a cycle |
| 📈 | Escalating | ~~Compounding~~ | Gets worse each cycle you don't solve it |
| 📦 | Same Root Cause | ~~Cluster~~ | Multiple constraints are expressions of one missing system |
| ↔️ | Solve Together | ~~Synergy~~ | Two constraints amplify each other — solve in one project |
Constraint Statuses
| Status | Meaning |
|---|
| Open | Identified, not yet being worked |
| In Progress | Work has started |
| Active Solve | Actively being built this week |
| Designed | Solution designed, not yet deployed |
| Deployed | Live in the client's environment |
| Solved | Confirmed working, moved to solved section |
Recommendation Statuses
| Status | Meaning |
|---|
| Suggested | Advisor has proposed it |
| Accepted | Client agreed to proceed |
| In Progress | Being built |
| Designed | Solution designed, ready for review |
| Implemented | Live and working |
Seed Statuses
| Status | Meaning |
|---|
| Seed | Idea planted in conversation |
| Presented | Formally presented to client |
| Interested | Client expressed interest |
| Active | Agreement signed, work underway |
Action Item Owners
| Badge | Meaning | Color |
|---|
| Mine | Advisor's responsibility | Gold (#b79d64) |
| Client | Client's responsibility | Blue (#5a8a9a) |
Theme Severity (Border Colors)
| Color | Meaning |
|---|
| Red (#8b4049) | Critical, active, needs attention now |
| Gold (#b79d64) | Strategic or structural, important but not urgent |
| Amber (default) | Informational, worth tracking |
Engagement Statuses
| Status | Meaning |
|---|
| Active | Currently paying, work underway |
| Transitioned | Previous engagement that led to current one |
Capability Categories
These are the standard categories for classifying constraints and recommendations:
- Advisory Website
- Operational Systems
- Visibility Engine
- Pipeline Infrastructure
- Service Line Launch
- Product Suite
Most early-stage clients will cluster heavily in one category. That's expected — it confirms the engagement is a focused solve, not scattered.