The Tactic Playbook turns verified findings into grounded action.
The playbook is not a second source of truth about the customer. It is a controlled remediation layer: each tactic is mapped to the A-F Knowledge Base taxonomy, tied to maturity and anti-pattern themes, and used only when the assessment evidence supports the recommendation.
Evidence chooses the tactic. The tactic gives the roadmap depth.
The Engine first verifies source evidence, scores maturity and anti-pattern semantics, and locks the diagnosis. Only after that can the roadmap use the tactic playbook. This keeps the report useful without letting generic best practice material masquerade as customer evidence.
Stable tactic IDs
Each tactic keeps a stable `TAC-*` identifier. The ID anchors the recommendation and prevents broad advisory language from drifting away from the approved playbook.
KB-aligned coverage
Every tactic maps explicitly to maturity criteria and anti-pattern criteria across the A-F taxonomy. The mapping explains why the tactic belongs in the FinOps assessment model.
Activity depth
The playbook adds when-to-use rules, implementation activities, owner roles, expected artifacts, acceptance criteria, and risks. It enriches HOW without inventing facts.
The playbook covers all A-F domains and all 60 maturity / anti-pattern themes.
Coverage is direct and explicit: each tactic card declares which maturity criteria and anti-pattern criteria it can support when the locked findings justify its use.
The approved remediation patterns.
Each card below describes the tactic rationale, the linked Knowledge Base themes, and the activity layer that helps the roadmap explain WHY, WHAT, and HOW. It shows how approved actions translate verified evidence into practical delivery steps, artifacts, ownership, and controls.
What the playbook is allowed to do.
Allowed: guide roadmap mechanisms, implementation sequence, artifacts, owner roles, acceptance criteria, and risk controls after findings have been locked.
Forbidden: prove customer current state, appear as a source evidence quote, change Phase 1 or Phase 2 scoring, or add summary/diagnosis facts that the uploaded material did not support.
Practical rule: no tactic ID is better than a wrong tactic ID. When no exact tactic fits, the roadmap can still provide grounded actions without pretending a KB match exists.