pae/crimson_leaf
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: remove recursive task types from planning template

Browse Source 
Planning was spawning sub-planning and boardroom tasks which cascaded into dozens
of duplicate create_company attempts. Now only emits leaf tasks.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
David Baity
2026-03-10 12:19:15 -04:00
parent 37c8c1af49
commit 51dbf9f089
1 changed files with 13 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
templates/planning.yml
View File

@@ -46,12 +46,16 @@ steps:
hire_agent — recruit a new agent to the CL roster hire_agent — recruit a new agent to the CL roster
write_template — create or refine a PAE-Lang template write_template — create or refine a PAE-Lang template
create_company — incubate a new sovereign Tenant create_company — incubate a new sovereign Tenant
planning — sub-planning session for complex initiatives
boardroom — multi-agent deliberation on strategic decisions
research_plus — deep research with web search
analysis — data or situation analysis
quick — short single-step response quick — short single-step response
CRITICAL DISPATCH RULES:
- Do NOT create planning or boardroom sub-tasks. You ARE the planning step.
All deliberation happens HERE in this session, not as child tasks.
- Produce ONLY actionable leaf tasks (hire_agent, write_template, create_company, quick).
- For company creation: emit ONE create_company task with ALL details in the description.
Do NOT split charter design, CEO recruitment, and company creation into separate tasks.
The create_company template handles the full flow internally.
Be specific about agent assignments — use EXACT names from the TEAM ROSTER. Be specific about agent assignments — use EXACT names from the TEAM ROSTER.
When the group has genuinely agreed on a complete plan, include exactly: When the group has genuinely agreed on a complete plan, include exactly:
@@ -76,8 +80,11 @@ steps:
No ambiguous assignments. No placeholder names. No ambiguous assignments. No placeholder names.
VALID TASK TYPES (use ONLY these exact strings): VALID TASK TYPES (use ONLY these exact strings):
hire_agent, write_template, create_company, planning, boardroom, hire_agent, write_template, create_company, quick
research_plus, analysis, quick
RULES:
- Do NOT emit planning or boardroom tasks. Deliberation already happened above.
- For create_company: emit ONE task with the full opportunity in the description.
- type: package - type: package
packet_type: PlanningResponsePacket packet_type: PlanningResponsePacket