Source: frameworks/kit-project-plan/02-project-plan-terminology.md

Project Plan — Terminology

Locked vocabulary for the project plan system. These terms have specific meanings. Use them exactly.

Deploy Chain (8 Stages)

Every build moves through exactly 8 stages, always in this order:

Stage	Meaning	Who
Design	Advisor creates the deliverable structure and content	Advisor
Review	Client or stakeholder reviews the design	Client/Stakeholder
Implement	Advisor builds the actual deliverable	Advisor
QC1	First quality check against the QC checklist	Advisor
Train	Stakeholders are trained on the deliverable	Advisor + Team
QC2	Second quality check — does it work in practice?	Advisor
Live	Deliverable goes into production use	Team
Optimize	Refinement based on real-world usage	Advisor + Team

Deploy Chain Statuses

Visual State	CSS Class	Meaning
Green fill	`.complete-step`	Stage is done
Navy fill	`.active-step`	Currently in this stage
Gray outline	(default)	Not yet started

Build States

State	CSS Class	Meaning
Active	`.build-card.active`	Currently being worked — navy left border
Queued	`.build-card.queued`	Designed but not yet in production — dimmed opacity
Complete	`.build-card.complete`	All 8 deploy stages done — green left border

Build Tags

Tag	CSS Class	When Used
This Week	`.this-week-tag`	Build has active work this week — navy background
Week N	`.week-tag`	Shows scheduled week — gray background
Synergy	`.synergy-tag`	Two builds share constraints and should be solved together

Constraint Hierarchy

Tier	CSS Class	Meaning
Upstream / Co-Primary	`.constraint-item.primary`	Root cause or equal-weight driver. Red left border.
Secondary	`.constraint-item.secondary`	Caused by or amplified by upstream constraints. Copper left border.
Downstream	`.constraint-item.downstream`	Symptoms or effects. Gray left border.

Pattern Markers

Marker	Meaning
Recurring	Same constraint appears across multiple sessions
Escalating	Constraint is getting worse over time
Same Root Cause	Multiple constraints trace to one upstream issue
Solve Together	Builds addressing these constraints should be bundled

Theme Classification

Type	CSS Class	Meaning
Critical	`.theme-item.critical`	Needs action now. Red left border.
Emerging	`.theme-item.emerging`	Watching — not yet actionable. Orange left border.

Owner Roles

Used in build card owner tags and deploy chain legend:

Role	CSS Class	Color	Meaning
Owns	`.owner-tag.owns`	Gold	Responsible post-deployment
Designs	`.owner-tag.designs`	Steel blue	Creates the deliverable structure
Approves	`.owner-tag.approves`	Copper	Reviews and signs off
Executes / Support	`.owner-tag.involved`	Stone	Runs it day-to-day or provides support

Color assignments are locked per client. Once a person is assigned a color, that color stays throughout the engagement. Document the mapping in the client-specific skill.

GPS

Scoped to the initiative (not the overall engagement):

Field	Meaning
Position	Where the initiative stands right now — factual, observable
Direction	Where it's heading based on current trajectory
Speed	Pace of progress — momentum indicators

Prework States

State	Visual Treatment	Meaning
Still Needed	Navy accent, prominent card	Blocking a build — needs client action
Future	Stone accent, faded	Will be needed for a later build
Received	Green accent, compressed grid	Client provided it — acknowledged

Stakeholder Badge Types

Badge	CSS Class	Color	Meaning
Owner	`.stakeholder-badge.owner`	Gold	Owns builds post-deployment
Approver	`.stakeholder-badge.approver`	Copper	Reviews and signs off
Designer	`.stakeholder-badge.designer`	Steel blue	Creates/implements
Executor	`.stakeholder-badge.executor`	Stone	Runs it day-to-day
Support	`.stakeholder-badge.support`	Light gray	Provides input but not primary

Action Statuses

Status	Display
Completed	Checkbox checked + "Completed: [date]"
Outstanding	Checkbox unchecked + "Outstanding since [date]"
Due	Checkbox unchecked + "Due: [date]"

Action Owner Types

Type	CSS Class	Color
Advisor	`.action-owner.mine`	Steel blue
Client	`.action-owner.client`	Copper
Team	`.action-owner.team`	Gold