Fix: design_roundtable.yml uses invalid step type 'boardroom'

Changed type: boardroom to type: think with route: boardroom.
Also added synthesis think step before package so Victor summarizes
the boardroom debate into structured fields before Scribe serializes.

pipeline.py only recognizes: think, package, reply, close, document, pdf, tool, spawn
'boardroom' as a step type would silently fail (pipeline_unknown_step log).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
David Baity
2026-03-02 23:56:09 -05:00
parent 2562737944
commit 30ba600e77

View File

@@ -3,15 +3,6 @@ description: >
The Crimson Leaf board debates their independent design reviews in 23 The Crimson Leaf board debates their independent design reviews in 23
structured rounds, reaching consensus on required changes before polish. structured rounds, reaching consensus on required changes before polish.
participants:
- Victor
- Nolan
- Sarah
- Elena
iteration_limit: 3
convergence_signal: "CONSENSUS REACHED"
participant_prompt: participant_prompt:
- "= identity.md" - "= identity.md"
@@ -27,7 +18,9 @@ sections:
- instructions - instructions
steps: steps:
- type: boardroom - type: think
route: boardroom
rotate_participants: true
loop: loop:
max_iterations: 3 max_iterations: 3
condition: until_consensus condition: until_consensus
@@ -39,15 +32,6 @@ steps:
COMPANY DESIGN UNDER REVIEW: {task.message} COMPANY DESIGN UNDER REVIEW: {task.message}
YOUR REVIEW:
{this_agent_review}
OTHER REVIEWS:
[Victor] {victor_review}
[Nolan] {nolan_review}
[Sarah] {sarah_review}
[Elena] {elena_review}
Round {task.iteration} of the design review debate. Round {task.iteration} of the design review debate.
Respond to the other board members' most critical points: Respond to the other board members' most critical points:
@@ -64,7 +48,23 @@ steps:
3. Any unresolved risks that must be accepted or mitigated 3. Any unresolved risks that must be accepted or mitigated
When the group has reached sufficient consensus for the polish step, When the group has reached sufficient consensus for the polish step,
end your response with: CONSENSUS REACHED end your response with: consensus_reached: true
- type: think
agent: "Victor"
hint: |
You are Victor, CEO of Crimson Leaf LLC.
The design roundtable is complete. Synthesize the board's debate into a
structured consensus summary:
1. DESIGN VERDICT — GO or KILL, with Victor's final reasoning
2. KEY CHANGES — exact list of changes to apply during design_polish
3. CONSENSUS CRITIQUE — one paragraph summary of the board's unified position
4. VICTOR FINAL — Victor's closing statement
5. NOLAN FINAL — Nolan's final position summary
6. SARAH FINAL — Sarah's final position summary
7. ELENA FINAL — Elena's final position summary
- type: package - type: package
schema: schema:
@@ -88,3 +88,6 @@ steps:
nolan_final: "{nolan_final}" nolan_final: "{nolan_final}"
sarah_final: "{sarah_final}" sarah_final: "{sarah_final}"
elena_final: "{elena_final}" elena_final: "{elena_final}"
- type: close
rag_update: true