00 — START HERE: Constraint Priority Matrix

This is the setup and orientation document for the Constraint Priority Matrix. Read this to understand what it is, what it does, what files it needs, and how to use it.

What This Is

The Constraint Priority Matrix is the diagnostic engine for Advisory OS. It takes a client's self-reported constraints and session data, and produces a prioritized analysis that tells you what to solve, in what order, and why. Everything downstream — the Client Master Plan, Project Plan, Blueprint, and SOPs — depends on the matrix output.

This is a Tier 1 framework (meaning: it works for any client, is not branded to a specific client, and uses Advisory OS defaults). You do not duplicate this per client. Every client's data runs through the same matrix.

What It Produces

A markdown artifact containing:

1. Prioritized Constraint List — Each constraint numbered, tiered (1–4), typed (Upstream/Downstream, with 🧠 Behavioral modifier when applicable), with pattern flags (Recurring, Escalating, Same Root Cause, Solve Together, Conditional Solve Together)
2. Visual Matrix — Capability category × speed grid showing where constraints concentrate
3. Session Prep Brief — Recommended focus, questions to ask, status checks for Unknown constraints, pattern watch items for the next session
4. QC Score — Every output is scored against the Quality Checklist before delivery. 90+ to pass. Dedicated validation passes for Direction anchoring, data gap detection, and behavioral constraint identification.

A separate HTML presentation skill exists for client-facing use (proposals, screen shares, engagement upgrades, milestone presentations). See 06-constraint-priority-matrix-output-skill.md. The weekly working output is always markdown.

Three Operating Modes

The mode is determined by what documents exist — not by how many sessions you've had.

Where the Output Goes

The full matrix output moves to the next framework in the assembly line:

• Client Master Plan (client-specific) — Matrix output updates the constraints section, checks for initiative triggers, updates themes

File Inventory

Instructions File

Knowledge Files

Total: 1 instructions file + 8 knowledge files + this orientation document = 10 files.

Per-Session Uploads (What You Feed It Each Week)

Mode 1 — First matrix run

Feed ALL available files, oldest first:

1. Client Reference Data — correct spellings for names, tools, company
2. Client's stated goal or vision — if the client has done vision work, a "year of ___" statement, or declared an annual goal in any setting, this is the primary Direction anchor (see Direction Gate in workflow instructions)
3. All constraint briefs (chronological)
4. All session transcripts (chronological)
5. All JSON session files (if available)
6. All group session data where this client participates (TPC, coaching groups, etc.) — these surface stated goals, behavioral patterns, and peer-facing signals that don't appear in 1:1 sessions

Mode 2 — Returning client, no project plan

1. Client Reference Data
2. Client Master Plan — carries all prior constraint history
3. Client's stated goal or vision — confirm still current
4. New constraint brief — latest week only
5. New session transcript — latest session only
6. New JSON session file — if available
7. New group session data since last matrix run — if available

Mode 3 — Returning client with active project plan

1. Client Reference Data
2. Client Master Plan — carries all prior constraint history
3. Project Plan — carries build sequence, timelines, deployment chain
4. Client's stated goal or vision — confirm still current
5. New constraint brief — latest week only
6. New session transcript — latest session only
7. New JSON session file — if available
8. New group session data since last matrix run — if available

What This Does NOT Do

• Does not produce client-facing documents (that's the Blueprint, generated from the project-plan-system)
• Does not update the Client Master Plan (that's the master-plan-system — you take the matrix output there)
• Does not design deployment packages (that's the Build Design Agent in the project-plan-system)
• Does not produce SOPs or deliverables (that's the build process within each client project)
• Does not apply client branding (this is Tier 1 — Advisory OS defaults only)
• Does not produce HTML output (that's 06 — the HTML presentation skill, used for client-facing deliverables)

Maintenance

• When terminology changes: Update 02-constraint-priority-matrix-terminology.md, then push to this framework AND every downstream framework that references constraints.
• When processing rules change: Update constraint-priority-matrix-instructions.md.
• When a new quality check is needed: Update 04-constraint-priority-matrix-quality.md.
• When you complete a particularly clean matrix run: Consider replacing the relevant golden example (03a/03b/03c) with an anonymized version of the new output.

File Location

~/advisory-os/frameworks/constraint-priority-matrix/
    00-constraint-priority-matrix-start-here.md          (this file)
    constraint-priority-matrix-instructions.md
    01-constraint-priority-matrix-context.md
    02-constraint-priority-matrix-terminology.md
    03a-constraint-priority-matrix-golden-example-mode1.md
    03b-constraint-priority-matrix-golden-example-mode2.md
    03c-constraint-priority-matrix-golden-example-mode3.md
    04-constraint-priority-matrix-quality.md
    06-constraint-priority-matrix-output-skill.md