Source: frameworks/kit-master-plan/06-master-plan-full-document-qc.md

⚠️ NEEDS REVIEW — Imported from ~/advisory-os/ on Feb 19, 2026. Content is from Feb 10-12 and may not align with current vault framework files (Feb 15-18). Review and merge before using.

Client Delivery System — Quality Checklist

Scoring

Each item has a point value. Total: 100 points per document type. Passing threshold: 90%.

Run the relevant checklist before delivering any document to the advisor (Client Master Plan, Project Plan) or before the advisor shares with the client (Client Blueprint).

Client Master Plan

Header & GPS (20 points)

[ ] Client name, company name, team size, "since" date present — 4 pts
[ ] GPS trajectory summary is a synthesized narrative, not a data dump — 4 pts
[ ] GPS Position, Direction, Speed each have current value + change marker + date — 4 pts
[ ] Change markers correctly assigned (Changed/Consistent/Escalated) with rationale — 4 pts
[ ] GPS history section present and collapsible, older entries dimmed — 2 pts
[ ] Trajectory only updated when material shift occurred — 2 pts

Recurring Themes (15 points)

[ ] Themes sit between GPS and card grid — 2 pts
[ ] Each theme has: specific name (not generic), evidence summary, source tags — 4 pts
[ ] Themes cross-reference multiple sections (GPS + constraints + conversations + quotes) — 4 pts
[ ] New themes flagged as "New theme detected" — 2 pts
[ ] Updated themes flagged as "Updated evidence" — 2 pts
[ ] No theme generated without at least 2 data points across different sections — 1 pt

Constraints Section (20 points)

[ ] Constraints sourced from matrix, NOT from JSON constraint mentions — 4 pts
[ ] Each constraint shows: name, category, type (⬆️/⬇️), blocks, status, pattern flags — 4 pts
[ ] Upstream constraints list their downstream effects — 3 pts
[ ] Downstream constraints reference their upstream cause — 3 pts
[ ] Active Solve badge + initiative links present when Project Plan exists — 3 pts
[ ] Legend block explaining symbols present — 1 pt
[ ] Solved constraints retained with Solved status — 2 pts

Remaining Sections (20 points)

[ ] Seeds show: name, description, status badge, next steps. Initiative links when applicable — 3 pts
[ ] Recommendations linked to constraints where applicable — 3 pts
[ ] Quotes are verbatim with date and context. Never paraphrased — 3 pts
[ ] Actions have owner tags (mine/client/team) with color coding — 2 pts
[ ] Conversations are most-recent-first with expandable modal recaps — 3 pts
[ ] Team Roster is a structured section with names, roles, ownership tags — 3 pts
[ ] Active Initiatives subsection present in Current Engagement when Project Plans exist — 3 pts

Design & Format (15 points)

[ ] Standalone HTML, opens in browser, all CSS/JS inline — 3 pts
[ ] Design system colors match exactly (gold, charcoal, cream, etc.) — 3 pts
[ ] Cormorant Garamond headings, Inter body — 2 pts
[ ] Gold left-border on trajectory, key themes, and engagement items — 2 pts
[ ] Status badges use correct colors (success/warning/slate/danger) — 2 pts
[ ] Owner tags use correct colors (gold/teal/purple) — 1 pt
[ ] Brand mark "A" for Advisory OS present — 1 pt
[ ] max-width: 1400px — 1 pt

Data Integrity (10 points)

[ ] No data overwritten that should have been appended — 3 pts
[ ] GPS not auto-overwritten without advisor approval — 3 pts
[ ] Possible data issues flagged (name spellings, date mismatches, attribution) — 2 pts
[ ] Accumulation rule followed: history stacks, nothing deleted — 2 pts

Project Plan

Initiative Header & Matrix Banner (15 points)

[ ] Type label, initiative name, status, priority, category, build count, first identified date — 4 pts
[ ] "← Back to Master Plan" + "Generate Client Blueprint" navigation — 2 pts
[ ] Matrix validation banner with narrative insight and stat blocks — 4 pts
[ ] Stats show: upstream cause count, downstream resolved, capability cluster, pattern occurrence — 3 pts
[ ] Parent client reference correct — 2 pts

Deployment Plan (25 points)

[ ] Numbered build sequence with correct ordering (highest leverage first) — 4 pts
[ ] Each build shows: title, description, resolves line, timing badge, owner tags, deploy chain — 5 pts
[ ] Active build has gold left border. Queued builds at 0.7 opacity — 2 pts
[ ] Deploy chain follows 8-step methodology (Design → Review → Implement → QC1 → Train → QC2 → Live → Optimize) — 4 pts
[ ] Each build delivers standalone relief (doesn't depend on later builds) — 4 pts
[ ] Resolves lines correctly map builds to constraint numbers — 3 pts
[ ] Build sequence rationale documented in Notes — 3 pts

GPS, State Comparison, Themes (20 points)

[ ] GPS scoped to initiative (not copy of parent Client Master Plan GPS) — 4 pts
[ ] Current State vs. Target State comparison present — 4 pts
[ ] Target state items tagged to which build delivers them — 3 pts
[ ] Recurring themes scoped to initiative with evidence and source tags — 4 pts
[ ] Product constraints flagged with red styling + ⚠️, not included in builds — 3 pts
[ ] Product constraint includes coaching note about when/how to address — 2 pts

Supporting Sections (20 points)

[ ] Constraints are subset of parent Client Master Plan, correctly scoped — 4 pts
[ ] Stakeholders show name, role, ownership tag (Owner/Involved/Bottleneck) — 3 pts
[ ] Pre-work section with questions, rationale, and status — 4 pts
[ ] Evidence section with verbatim quotes, source, date, advisory notes — 3 pts
[ ] Notes include: methodology details, tool access, timing, coaching notes, commercial context — 3 pts
[ ] Actions split by owner with correct tagging — 3 pts

Design & Format (10 points)

[ ] Matches Project Plan golden reference layout — 3 pts
[ ] Design system colors exact — 2 pts
[ ] Brand mark "A" for Advisory OS — 2 pts
[ ] max-width: 1400px — 1 pt
[ ] Standalone HTML, functional in browser — 2 pts

Data Integrity (10 points)

[ ] Data pulled correctly from parent Client Master Plan — 3 pts
[ ] Constraint numbers match parent Client Master Plan — 3 pts
[ ] No internal language that should have stayed on parent document — 2 pts
[ ] Data issues flagged — 2 pts

Client Blueprint

Content Curation (30 points)

[ ] NO diagnostic language anywhere: no upstream/downstream, no tiers, no pattern flags, no matrix references — 6 pts
[ ] NO internal notes, coaching flags, product constraints, incongruence flags — 4 pts
[ ] NO technical constraint numbering — 2 pts
[ ] Constraint expressed in client's own words — 4 pts
[ ] "From Your Constraint Brief" block leads with client's verbatim quote — 4 pts
[ ] Advisor positioned as builder, not analyst — 4 pts
[ ] Tone: direct, confident, second-person throughout — 3 pts
[ ] Every section answers: What? Why? What do you need from me? When? — 3 pts

Structure (30 points)

[ ] Hero section with initiative name and reframing subtitle — 3 pts
[ ] Constraint source block with client quote + advisor reframe — 4 pts
[ ] Current State vs. Target State in plain language (no build numbers or constraint refs) — 4 pts
[ ] 8-step deployment visual with "your role is step 2 and step 7" framing — 4 pts
[ ] Build cards with: number, title, description, "What changes" outcome, deploy details — 4 pts
[ ] First build gets gold left border + "This Week" tag — 2 pts
[ ] Access Required section with what, why, when — 2 pts
[ ] Pre-work section with questions and rationale — 3 pts
[ ] Timeline with active dot, weekly entries, role tags, final milestones — 4 pts

Design & Format (20 points)

[ ] max-width: 1000px (narrower, reads like a proposal) — 3 pts
[ ] Design system colors exact — 3 pts
[ ] Brand mark "A" for Advisory OS — 2 pts
[ ] Footer with advisor name, brand, month/year — 2 pts
[ ] Print styles included (@media print) — 3 pts
[ ] Standalone HTML, functional in browser — 3 pts
[ ] Matches Client Blueprint golden reference layout and tone — 4 pts

Comparison Check (20 points)

[ ] Compare against Project Plan: everything diagnostic is gone — 5 pts
[ ] Compare against Project Plan: everything the client needs to know is present — 5 pts
[ ] Reframing is consistent (no slips back into internal language) — 5 pts
[ ] Build descriptions match between Project Plan and Client Blueprint (same scope, different language) — 5 pts

Update Validation (for document updates, not new documents)

When updating an existing document, additionally verify:

[ ] Changes clearly stated: what was added, updated, or flagged
[ ] No existing data overwritten that should have been preserved
[ ] Status sync correct if initiative builds completed
[ ] New themes flagged as drafts pending advisor approval
[ ] GPS changes presented as side-by-side, not auto-overwritten
[ ] Cross-references checked between updated section and rest of document