
Converts stakeholder simulation findings into an actionable engagement strategy.
A comprehensive Strategic Alignment Report with 13 sections covering everything from executive summary through real-world action steps. The report converts simulation insights into specific conversations to have, questions to ask, and proposals to test with actual stakeholders. This is preparation, not prediction โ your first real conversation will update the strategy.
Discussion Synthesis & Strategic Alignment
TL;DR
How To Start
STEP 1Provide Discussion Transcript
-
discussion_transcript
· text · required
The Discussion Transcript from RCP-082, or a detailed record of multi-stakeholder deliberation with participant identities, positions taken, arguments made, and resolution status. -
real_world_constraints
· text · optional
Organizational politics, budget cycles, upcoming events, relationship dynamics not captured in personas. Example: “Board meeting is in 6 weeks; CFO and VP HR have a good working relationship; Engineering Director just started 3 months ago.” -
focus_areas
· text · optional
Specific areas for the synthesis to focus on. Example: “Focus on the engagement sequence and the Finance stakeholder’s conditions.”
STEP 2Review Analysis Summary
STEP 3Review Strategic Alignment Report
STEP 4Act on Real-World Action Steps
Usage Examples
How AI Reads This Recipe
- ANALYZE the discussion transcript systematically, extracting alignment points, blocking issues, negotiation opportunities, alliance patterns, opposition patterns, and position evolution.
- MAP alignment, opposition, and negotiation space. Distinguish strong alignment (shared position) from conditional alignment (support with conditions). Identify surprise findings where stakeholders behaved differently than their persona definitions predicted.
- IDENTIFY the most promising engagement paths using evidence-based sequencing logic: convert-blockers-first, build-coalition-first, or address-dependencies. State which strategy and why.
- RECOMMEND stakeholder-specific communication approaches grounded in both persona definitions and simulation behavior. Be specific: not “lead with data” but “open with the retention study cited in Round 2.”
- PRODUCE a structured 13-section Strategic Alignment Report with every recommendation traceable to simulation evidence.
- CONVERT all findings into testable real-world actions. Each action must be specific enough that the user could act on it tomorrow: who to talk to, what to propose, what question to ask, what to listen for.
When to Use This Recipe
- Have a Discussion Transcript from RCP-082 (or a detailed record of multi-stakeholder deliberation) and need to convert discussion findings into action steps.
- Want a structured engagement strategy with a recommended sequence for real stakeholder conversations.
- Need to identify blocking issues, negotiation opportunities, and alliance patterns from a multi-stakeholder discussion.
- Want testable hypotheses — specific questions, proposals, and conversation strategies — before engaging stakeholders in reality.
- Have completed the Stakeholder Analysis Workflow (RCP-080 → RCP-081 → RCP-082) and are ready for the final synthesis step.
Recipe FAQ
Q.Do I need to use RCP-082 first?
Q.How reliable are the engagement recommendations?
Q.What if the simulation didn’t reach consensus?
Q.Can I re-run this with updated information?
Q.Why doesn’t the report include probability scores?
Q.What’s the difference between a blocking issue and a concern?
Version History
THE ACTUAL RECIPE
RCP-000-000-083-DISCUSSION-SYNTHESIS-STRATEGIC-ALIGNMENT
The CRAFT Recipe
# RECIPE EXECUTION CODE (Parameters + Phases)
# Source: revised/WPRM-RCP-000-000-083-…-v3_00a.txt
# Added to permalink: P067-H131 (2026-05-06) โ closes
# “actual recipe code missing from permalink”
# finding raised by Richard at H131.
# =========================================================== # ===========================================================
# RECIPE PARAMETERS
# =========================================================== RECIPE_PARAMETERS = {
“discussion_transcript”: {
“type”: “string”,
“required”: True,
“description”: (
“The Discussion Transcript from RCP-082, “
“attached or pasted. Contains full discussion “
“record with position evolution and moderator “
“summaries.”
)
},
“real_world_constraints”: {
“type”: “string”,
“required”: False,
“default”: “”,
“description”: (
“Any real-world constraints the synthesis “
“should account for: organizational politics, “
“budget cycles, upcoming events, relationship “
“dynamics not captured in personas.”
),
“example”: (
“Board meeting is in 6 weeks; CFO and VP HR “
“have a good working relationship; Engineering “
“Director just started 3 months ago.”
)
},
“focus_areas”: {
“type”: “string”,
“required”: False,
“default”: “”,
“description”: (
“Specific areas the user wants the synthesis “
“to focus on. If not provided, the AI covers “
“all standard analysis dimensions.”
),
“example”: (
“Focus on the engagement sequence and the “
“Finance stakeholder’s conditions.”
)
}
} # ===========================================================
# PHASE 1: TRANSCRIPT ANALYSIS
# =========================================================== #AI->H::RecipeActive: (RCP-083 Discussion Synthesis & Strategic Alignment v3.00a)
#AI->H::Status: (Phase 1 โ Analyzing Discussion) # Load and parse Discussion Transcript
TRANSCRIPT = parse_discussion_transcript({discussion_transcript}) # Extract analysis dimensions
ANALYSIS = {
“alignment_points”: identify_alignment(TRANSCRIPT),
“blocking_issues”: identify_blocking_issues(TRANSCRIPT),
“negotiation_opportunities”: identify_flexibility(TRANSCRIPT),
“information_gaps”: identify_unresolved(TRANSCRIPT),
“surprise_findings”: identify_surprises(TRANSCRIPT),
“alliance_patterns”: map_alliances(TRANSCRIPT),
“opposition_patterns”: map_opposition(TRANSCRIPT),
“position_evolution”: track_position_changes(TRANSCRIPT)
} # Incorporate real-world constraints
IF {real_world_constraints} != “”:
ANALYSIS[“real_world_factors”] = parse_constraints(
{real_world_constraints}
) # Incorporate focus areas
IF {focus_areas} != “”:
ANALYSIS[“focus_priority”] = parse_focus({focus_areas}) # Present analysis summary for user review
PRESENT_ANALYSIS_SUMMARY(ANALYSIS) # โโ WAIT GATE 1 โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
# User reviews analysis summary. Opportunity to correct
# misinterpretations or add context before the full
# report is generated.
# โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ WAIT_FOR_ANALYSIS_CONFIRMATION # ===========================================================
# PHASE 2: STRATEGIC ALIGNMENT REPORT
# =========================================================== #AI->H::Status: (Phase 2 โ Building Strategic Alignment Report) REPORT = build_strategic_alignment_report(
analysis=ANALYSIS,
transcript=TRANSCRIPT,
constraints={real_world_constraints}
) # The Strategic Alignment Report includes:
#
# 1. EXECUTIVE SUMMARY
# – Topic and simulation scope
# – Number of stakeholders, rounds, format used
# – High-level finding (1-2 sentences)
#
# 2. STAKEHOLDER LANDSCAPE POST-DISCUSSION
# For each stakeholder:
# – Final position (from simulation end)
# – Shift from opening position (if any, with trigger)
# – Unresolved concerns
# – Communication approach that worked in simulation
#
# 3. ALIGNMENT MAP
# – Points of strong alignment (who agrees on what)
# – Points of conditional alignment (support with conditions)
# – Points of opposition (who disagrees on what)
# – Surprise alignments or oppositions
#
# 4. BLOCKING ISSUES (prioritized)
# For each:
# – What’s blocked and by whom
# – Influence level of the blocker
# – Resolution path suggested by simulation
# – What happens if unresolved
#
# 5. NEGOTIATION OPPORTUNITIES
# – Flexibility zones that emerged during simulation
# – Trade-offs that personas found acceptable
# – Conditional support patterns (“I’ll support if…”)
#
# 6. ALLIANCE MAP
# – Natural alliances (shared interests)
# – Tactical alliances (temporary alignment)
# – Which alliances to leverage in engagement
#
# 7. RECOMMENDED ENGAGEMENT SEQUENCE
# – Ordered list with rationale for each position
# – First-mover advantage (why start with this stakeholder)
# – Dependencies (what must happen before engaging X)
# – Estimated preparation needed per stakeholder
#
# 8. COMMUNICATION STRATEGY PER STAKEHOLDER
# – Lead with (data / narrative / proposal / question)
# – Frame the topic as (opportunity / risk / investment)
# – Address their primary concern first
# – Avoid (triggers, framings, or comparisons that
# caused resistance in simulation)
#
# 9. RISK MAP
# – Who could block, what triggers the block
# – Mitigation strategies from simulation evidence
# – Contingency if mitigation fails
#
# 10. UNRESOLVED QUESTIONS
# – What the simulation couldn’t resolve
# – Questions to ask real stakeholders
# – Areas where more research might help
#
# 11. SURPRISE FINDINGS (RULE 12)
# – Unexpected positions or flexibility
# – Mental model updates suggested
#
# 12. REAL-WORLD ACTION STEPS (RULE 9)
# For each stakeholder:
# – Specific conversation to have
# – Specific question to ask
# – Specific proposal to test
# – What to listen for in their response
# – How their response updates the strategy
#
# 13. SIMULATION LIMITATIONS (RULE 4)
# – What the simulation could not capture
# – Factors that may change outcomes in reality
# – “Be prepared to adjust after first conversations” PRESENT_REPORT(REPORT) # โโ WAIT GATE 2 โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
# User reviews full report. Opportunity to request
# adjustments, deeper analysis on specific sections,
# or additional action steps.
# โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ WAIT_FOR_REPORT_FEEDBACK # Apply any adjustments
IF USER_FEEDBACK.has_adjustments:
REPORT = apply_report_adjustments(REPORT, USER_FEEDBACK)
PRESENT_REVISED_SECTIONS(REPORT) # Closing frame (RULE 10)
REPORT_CLOSING = (
“This Strategic Alignment Report gives you a map and “
“a starting plan based on simulation findings. The “
“first real stakeholder conversation will update that “
“map. Be prepared to adjust your approach as you “
“learn what the simulation couldn’t capture.nn”
“Key principle: every recommendation in this report “
“is a HYPOTHESIS to test, not a conclusion to “
“implement. Real stakeholder engagement is where “
“strategy becomes real.”
) PRESENT_REPORT_CLOSING(REPORT_CLOSING) #AI->H::Status: (
Strategic Alignment Report complete. ANALYSIS COVERAGE:
Alignment points identified: {count_alignment}
Blocking issues identified: {count_blocking}
Negotiation opportunities: {count_negotiation}
Unresolved questions: {count_unresolved}
Surprise findings: {count_surprises}
Action steps generated: {count_actions} This completes the Stakeholder Analysis Workflow. WHAT YOU HAVE NOW:
– Stakeholder Map (from RCP-080)
– Stakeholder Persona File (from RCP-081)
– Discussion Transcript (from RCP-082)
– Strategic Alignment Report (this recipe) WHAT TO DO NEXT:
– Begin real stakeholder conversations using the
engagement sequence and action steps
– Update your strategy after each conversation
– Consider re-running RCP-082 with updated personas
if new information significantly changes the
landscape
) # ===========================================================
# HELPER FUNCTIONS
# =========================================================== def parse_discussion_transcript(transcript_content):
“””
Parse Discussion Transcript from RCP-082. Extracts: metadata, per-round data, position evolution,
moderator summaries, and key moments.
“””
pass def identify_alignment(transcript):
“””
Identify points where stakeholders aligned. Distinguishes strong alignment (shared position) from
conditional alignment (support with conditions).
“””
pass def identify_blocking_issues(transcript):
“””
Identify issues where influential stakeholders hold
unresolved objections that could halt progress. Prioritized by blocker influence level.
“””
pass def identify_flexibility(transcript):
“””
Map flexibility zones that emerged during discussion. Includes trade-offs accepted, conditional support
patterns, and compromise proposals.
“””
pass def identify_surprises(transcript):
“””
Find unexpected positions or shifts (RULE 12). Compares persona definitions with simulation behavior
to identify where assumptions may need updating.
“””
pass def map_alliances(transcript):
“””
Map alliance patterns between stakeholders. Distinguishes natural alliances (shared interests)
from tactical alliances (temporary alignment).
“””
pass def build_strategic_alignment_report(analysis, transcript,
constraints):
“””
Build the complete Strategic Alignment Report. 13 sections covering all analysis dimensions.
All recommendations grounded in simulation evidence.
All outcomes framed as hypotheses (RULE 2).
“””
pass # ===========================================================
# CROSS-REFERENCES
# ===========================================================
#
# WORKFLOW RECIPES:
# RCP-080 โ DR โ RCP-081 โ RCP-082 โ RCP-083 (THIS)
#
# INPUT:
# Discussion Transcript from RCP-082
# Real-world constraints from user
#
# OUTPUT:
# Strategic Alignment Report (final deliverable)
#
# RELATED RECIPES:
# RCP-004 (Socratic Competitor Analyzer) โ may complement
# stakeholder strategy with competitive framing
# RCP-054 (Balanced Perspective Analyzer) โ could validate
# whether the report fairly represents all positions
#
# =========================================================== # ===========================================================
# VERSION HISTORY
# =========================================================== VERSION_HISTORY = [
{
“version”: “v3.00a-R”,
“date”: “2026-04-27”,
“changes”: [
“Pipeline revision (P067-H094, run 53)”,
“Added WPRM_FIELD_CRAFT_FLAVORS (REC-19 auto-apply, ABSENTโADD)”,
“Version suffix -R denotes pipeline revision”
],
“created_by”: “P067-Cat (E) โ CWK-ADM-080”,
“project”: “CFT-PROJ-CP-067 (CRAFTFramework.ai Beta Refresh)”
},
{
“version”: “v3.00a”,
“date”: “2026-02-17”,
“changes”: [
“Initial recipe creation (new construction)”,
“Part of Stakeholder Analysis Workflow (4 of 4)”,
“Architecture designed H016, built H017”,
“12 behavioral rules”,
“2 WAIT gates (analysis confirmation, report feedback)”,
“13-section Strategic Alignment Report”,
“Hypothesis framing throughout (RULE 2)”,
“Simulation-grounded recommendations only (RULE 1)”,
“Surprise findings identification (RULE 12)”,
“Real-world action steps with testable specifics”,
“Explicit simulation limitation acknowledgment”
],
“created_by”: “Cat (B) – Operations Master”,
“project”: “CFT-PROJ-CP-051f (WPRM Recipe QA Testing)”
}
]
{
“recipe_id”: “RCP-000-000-083”,
“recipe_name”: “Discussion Synthesis & Strategic Alignment”,
“version”: “v3.00a-R”,
“schema_version”: “1.1”,
“schema_profile”: “Option-B typed-envelope (H041 LOCKED canonical)”,
“authored_by”: “Cat (P067) on H094 CRPW pipeline run 53”,
“source_of_truth”: “phase3/recipe-83/RCP-083-EXTENDED-AI-GUIDANCE.txt”,
“audience_scope”: “AI EXECUTION GUIDANCE (NOT FOR HUMAN USERS)”,
“ai_to_ai_communication”: {
“core_philosophy”: {
“type”: “prose”,
“body”: “RCP-083 is the BRIDGE between simulation and reality. It converts structured thought experiments into actionable engagement plans. Every recommendation is a hypothesis โ the user walks out with testable assumptions, not false certainty. Think of the AI as a post-game analyst who reviews the footage and prepares the next game plan, knowing the actual game will be different.”
},
“synthesis_methodology”: {
“type”: “keyed_list”,
“preamble”: “SYNTHESIS METHODOLOGY โ evidence handling, blocking issue identification, and engagement sequence logic.”,
“items”: [
{
“key”: “EVIDENCE HIERARCHY”,
“body”: “Prioritize evidence by strength: (1) Positions stated multiple times across rounds โ consistent, likely durable in reality. (2) Positions stated once with supporting reasoning โ credible but less tested. (3) Positions inferred from reactions or silence โ weakest, flag as inference. When a persona shifted position during the discussion, note BOTH the original and final positions. The shift itself is data.”
},
{
“key”: “BLOCKING ISSUE IDENTIFICATION”,
“body”: “A true blocking issue requires three elements: (1) A stakeholder with sufficient influence to halt progress, (2) An unresolved objection to a core element of the proposal, (3) No resolution path demonstrated in the simulation. If ANY of these is missing, it’s a concern, not a block. Overstating concerns as blocking issues creates false urgency. Understating true blocks creates blind spots.”
},
{
“key”: “ENGAGEMENT SEQUENCE LOGIC”,
“body”: “The sequence is the report’s highest-value output. Common strategies: Convert-blockers-first (engage potential blockers early, convert them to supporters or co-designers before they can organize opposition). Build-coalition-first (engage natural supporters to build momentum, then approach skeptics from a position of strength). Address-dependencies (some stakeholders need information from others; engage information providers first). State which strategy you’re using and why.”
}
]
},
“report_section_guidance”: {
“type”: “keyed_list”,
“preamble”: “REPORT SECTION GUIDANCE โ quality standards for key sections of the Strategic Alignment Report.”,
“items”: [
{
“key”: “EXECUTIVE SUMMARY”,
“body”: “2-3 sentences maximum. ‘We simulated [topic] with [N] stakeholders over [N] rounds. Key finding: [one-sentence takeaway]. Primary path forward: [one-sentence recommendation].'”
},
{
“key”: “STAKEHOLDER LANDSCAPE”,
“body”: “For each stakeholder: where they ended (not just where they started), what moved them (or didn’t), and what remains unresolved. This section answers ‘where do we stand with each person?'”
},
{
“key”: “ALIGNMENT MAP”,
“body”: “Visual-friendly format. Group stakeholders by position: supportive / conditional / opposed / undetermined. Note cross-group connections. This should be scannable.”
},
{
“key”: “BLOCKING ISSUES”,
“body”: “Prioritize ruthlessly. Most simulations reveal 1-3 true blocking issues. If you have more than 5, you’re either overstating concerns or the proposal needs fundamental rethinking (which is also a valid finding).”
},
{
“key”: “COMMUNICATION STRATEGY”,
“body”: “Be specific. ‘Lead with data’ is too vague. ‘Open with the SHRM retention study (cited in simulation Round 2), frame as investment with defined payback period, avoid everyone-is-doing-it framing (triggered skepticism in Round 3)’ is actionable.”
},
{
“key”: “REAL-WORLD ACTION STEPS”,
“body”: “This is the most important section. Each action should be a specific, testable hypothesis. Good: ‘Ask CFO: If we co-designed the evaluation metrics, would you support a 6-month pilot? Listen for whether they engage with the specifics or deflect to broader concerns.’ Bad: ‘Discuss pilot metrics with finance leadership.’ The distinction is specificity.”
}
]
},
“simulation_to_reality_transition”: {
“type”: “keyed_list”,
“preamble”: “SIMULATION-TO-REALITY TRANSITION โ calibrating user confidence in simulation outcomes.”,
“items”: [
{
“key”: “WHAT SIMULATION CAPTURES WELL”,
“body”: “Logical structure of stakeholder arguments. Which concerns are predictable given role and evidence. Where flexibility zones MIGHT exist. Which proposals address multiple concerns simultaneously.”
},
{
“key”: “WHAT SIMULATION MISSES”,
“body”: “Personal relationships and trust levels. Informal influence networks. Recent events that changed dynamics. Emotional responses to specific framings. Political calculations beyond the immediate decision. Information stakeholders have that wasn’t in the deep research.”
},
{
“key”: “CLOSING CALIBRATION”,
“body”: “The closing section should be clear: ‘Your first real conversation will teach you more than the entire simulation. Be prepared to update your strategy after every interaction.'”
}
]
},
“strategic_synthesis_engine”: {
“type”: “keyed_list”,
“preamble”: “STRATEGIC SYNTHESIS ENGINE โ the design pattern driving this recipe’s analytical approach.”,
“items”: [
{
“key”: “PATTERN DESCRIPTION”,
“body”: “Takes simulation transcript from RCP-082, systematically analyzes alignment, opposition, alliances, and negotiation space, then generates a 13-section Strategic Alignment Report with testable engagement sequence and action steps. Every recommendation grounded in simulation evidence (RULE 1), framed as hypothesis (RULE 2).”
},
{
“key”: “ANTI-PATTERNS”,
“body”: “Do NOT introduce new stakeholder intelligence beyond simulation data. Do NOT assign probability scores or percentages to outcomes (RULE 11). Do NOT claim strategic certainty โ all recommendations are hypotheses. Do NOT overstate concerns as blocking issues. Do NOT provide generic recommendations (‘build coalition support’) without specifics.”
},
{
“key”: “WORKFLOW CONTEXT”,
“body”: “RCP-083 is the 4th and final recipe in the Stakeholder Analysis Workflow (080โ081โ082โ083). Input is the Discussion Transcript from RCP-082. Output is the Strategic Alignment Report โ the workflow’s culminating deliverable that converts the entire simulation investment into actionable engagement strategy.”
}
]
},
“edge_cases”: {
“type”: “keyed_list”,
“preamble”: “EDGE CASES โ handling unusual simulation outcomes.”,
“items”: [
{
“key”: “SIMULATION ENDED WITHOUT RESOLUTION”,
“body”: “This is a VALID finding. Report should say: ‘The simulation did not produce consensus, which suggests this decision may require phased or conditional approaches rather than full-group agreement.'”
},
{
“key”: “ALL STAKEHOLDERS AGREED”,
“body”: “Be suspicious. Check whether artificial consensus crept in. If genuine, note: ‘Broad alignment suggests the proposal may succeed, but TEST this assumption โ simulation tends to underrepresent hidden objections.'”
},
{
“key”: “TRANSCRIPT IS THIN”,
“body”: “Work with what you have. Note in limitations that the simulation was brief and deeper exploration might reveal additional dynamics. Recommend specific areas where additional simulation rounds would help.”
},
{
“key”: “EXTENSIVE REAL-WORLD CONSTRAINTS”,
“body”: “Incorporate into engagement sequence and communication strategy. Real-world constraints often change the optimal engagement order.”
}
]
},
“quality_standards”: {
“type”: “keyed_list”,
“preamble”: “QUALITY STANDARDS โ report quality checklist for self-verification.”,
“items”: [
{
“key”: “EVIDENCE GROUNDING”,
“body”: “Every recommendation cites simulation evidence. No fabricated precision (percentages, probabilities). Hypothesis framing throughout.”
},
{
“key”: “BLOCKING ISSUE DISCIPLINE”,
“body”: “Blocking issues limited to genuine blocks (3-element test). Concerns and preferences clearly distinguished from blocks.”
},
{
“key”: “ACTIONABILITY”,
“body”: “Engagement sequence has rationale for each position. Communication strategies are specific and actionable. Action steps include what to say, ask, and listen for.”
},
{
“key”: “INTELLECTUAL HONESTY”,
“body”: “Simulation limitations explicitly acknowledged. Surprise findings highlighted. No new stakeholder intelligence introduced. Report is self-contained and readable independently. Closing transitions from simulation to real world.”
}
]
}
}
}
Show/Hide accordion โ “Extended Information for the AI” section (AI-to-AI execution guidance, failure modes, tone calibration, common mistakes)
