Sprint 54: add depends_on sequencing — adjudicate_tenant waits for research, create_company waits for adjudication

This commit is contained in:
2026-03-12 03:54:44 +00:00
parent a0aafc1d72
commit 9a6c34f2b4

View File

@@ -2,13 +2,10 @@ name: planning
description: "Crimson Leaf executive planning — boardroom deliberation, structured task breakdown, child task dispatch." description: "Crimson Leaf executive planning — boardroom deliberation, structured task breakdown, child task dispatch."
debug: true debug: true
system: agent_prompt system: agent_prompt
participant_prompt: participant_prompt:
- "= identity.md" - "= identity.md"
agent_prompt: agent_prompt:
- "= identity.md" - "= identity.md"
sections: sections:
- agent - agent
- project - project
@@ -20,7 +17,6 @@ sections:
- templates - templates
- message - message
- instructions - instructions
steps: steps:
- type: think - type: think
rotate_participants: true rotate_participants: true
@@ -65,6 +61,11 @@ steps:
Do NOT split charter design, CEO recruitment, and company creation into separate tasks. Do NOT split charter design, CEO recruitment, and company creation into separate tasks.
The create_company template handles the full flow internally. The create_company template handles the full flow internally.
SEQUENCING RULE:
- adjudicate_tenant and create_company tasks MUST wait for all prior research tasks.
They cannot run until market_intelligence, portfolio_architectural_review, and
write_charter are all complete. This MUST be expressed using depends_on in the task list.
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:
@@ -87,6 +88,9 @@ steps:
- agents: EXACT name(s) from TEAM ROSTER - agents: EXACT name(s) from TEAM ROSTER
- task_type: MUST be one of the valid template names listed below - task_type: MUST be one of the valid template names listed below
- priority: 1 (critical) to 5 (nice-to-have) - priority: 1 (critical) to 5 (nice-to-have)
- depends_on: list of task_name values this task must wait for before it can start.
Use the EXACT task_name strings of the blocking tasks.
Omit this field entirely if this task has no blockers.
Order tasks correctly — blockers before dependents. Order tasks correctly — blockers before dependents.
No ambiguous assignments. No placeholder names. No ambiguous assignments. No placeholder names.
@@ -97,9 +101,14 @@ steps:
audit_tenant, charter_audit, financial_audit, capital_allocation_audit, audit_tenant, charter_audit, financial_audit, capital_allocation_audit,
retire_tenant, adjudicate_tenant, quick retire_tenant, adjudicate_tenant, quick
RULES: MANDATORY SEQUENCING RULES:
- adjudicate_tenant MUST have depends_on listing ALL research/charter tasks.
Valerius cannot adjudicate without completed research and a charter.
Example: depends_on: ["Market Intelligence", "Portfolio Architectural Review", "Write Charter"]
- create_company MUST have depends_on that includes the adjudicate_tenant task.
A company must NOT be created until adjudication passes.
Example: depends_on: ["Adjudicate Tenant"]
- Do NOT emit planning or boardroom tasks. Deliberation already happened above. - 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
@@ -111,6 +120,8 @@ steps:
- "string — EXACT agent name from TEAM ROSTER" - "string — EXACT agent name from TEAM ROSTER"
task_type: "string — MUST be a template name from the valid list" task_type: "string — MUST be a template name from the valid list"
priority: "integer 1 (critical) to 5 (nice-to-have)" priority: "integer 1 (critical) to 5 (nice-to-have)"
depends_on:
- "string — exact task_name of a blocking task (omit this field if no dependencies)"
insert_children: true insert_children: true
- type: close - type: close