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

rename: Peter→Victor (CEO), David→Nolan (CTO) — reserve human names for HITL operators

Browse Source 
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
David Baity
2026-03-01 01:15:39 -05:00
parent fc0260bba3
commit 24246f9cc3
14 changed files with 58 additions and 58 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
templates/company_design.yml
View File

@@ -35,9 +35,9 @@ steps:
Push back if the board drifts from what the data supports.
- Elena: Propose the agent roster (4–8 roles), chain of command, and pipeline SOP.
Specify exact task dependencies and execution order.
- David: Map Elena's pipeline to concrete PAE templates and tools. Flag any step
- Nolan: Map Elena's pipeline to concrete PAE templates and tools. Flag any step
that can't be executed with existing infrastructure. Propose procurement list.
- Peter: Challenge profitability. Ask hard questions about revenue model, cost
- Victor: Challenge profitability. Ask hard questions about revenue model, cost
structure, and time to first deliverable. You have Go/No-Go authority.
Write YOUR perspective on this round's discussion. React to what others said.
@@ -57,9 +57,9 @@ steps:
- type: think
route: llm
agent: "Peter"
agent: "Victor"
hint: |
You are Peter, CEO of Crimson Leaf LLC.
You are Victor, CEO of Crimson Leaf LLC.
The boardroom debate is complete. Synthesize the full transcript into a
COMPANY DESIGN SPECIFICATION document with these exact sections:
@@ -68,7 +68,7 @@ steps:
2. MARKET JUSTIFICATION — Why this company, why now (from Sarah's research)
3. AGENT ROSTER — Table: Name | Role | Title | Department | Responsibility
4. CHAIN OF COMMAND — Who manages whom, department structure
5. TEMPLATE STACK — Exact list of templates to procure (from David's analysis)
5. TEMPLATE STACK — Exact list of templates to procure (from Nolan's analysis)
6. PIPELINE SOP — Numbered steps with task_type, agent, dependencies (from Elena)
7. REVENUE MODEL — How the company makes money
8. SUCCESS METRICS — Measurable targets for the first 30/60/90 days
@@ -97,15 +97,15 @@ steps:
spawn:
- task_type: human_action
task_name: "Operator Review: Approve Design Direction — {task.message}"
agent_name: Peter
agent_name: Victor
priority: 8
context:
design_spec: "{design_spec}"
gate_purpose: "Review company design spec, approve before review cycle begins"
- task_type: design_review
task_name: "Design Review (Peter): {task.message}"
agent_name: Peter
task_name: "Design Review (Victor): {task.message}"
agent_name: Victor
priority: 6
context:
design_spec: "{design_spec}"
@@ -114,8 +114,8 @@ steps:
- "Operator Review: Approve Design Direction — {task.message}"
- task_type: design_review
task_name: "Design Review (David): {task.message}"
agent_name: David
task_name: "Design Review (Nolan): {task.message}"
agent_name: Nolan
priority: 6
context:
design_spec: "{design_spec}"
@@ -145,13 +145,13 @@ steps:
- task_type: design_roundtable
task_name: "Design Roundtable: {task.message}"
agents: [Peter, David, Sarah, Elena]
agents: [Victor, Nolan, Sarah, Elena]
priority: 7
context:
design_spec: "{design_spec}"
depends_on:
- "Design Review (Peter): {task.message}"
- "Design Review (David): {task.message}"
- "Design Review (Victor): {task.message}"
- "Design Review (Nolan): {task.message}"
- "Design Review (Sarah): {task.message}"
- "Design Review (Elena): {task.message}"