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

2
templates/bootstrap_company.yml
View File

@@ -25,7 +25,7 @@ steps:
- Agent roster (4–8 agents with roles)
- Template procurement list
- Pipeline SOP
- Peter's GO decision
- Victor's GO decision
If any section is missing or the GO/NO-GO decision is not "GO", stop and explain why
this company cannot be bootstrapped. Do NOT proceed with a NO-GO design.

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}"

10
templates/design_polish.yml
View File

@@ -29,8 +29,8 @@ steps:
DESIGN VERDICT: {design_verdict}
Peter (CEO): {peter_final}
David (CTO): {david_final}
Victor (CEO): {peter_final}
Nolan (CTO): {david_final}
Sarah (Market Intelligence): {sarah_final}
ORIGINAL DESIGN SPECIFICATION:
@@ -40,7 +40,7 @@ steps:
1. Address every item in KEY CHANGES REQUIRED. Do not skip any.
2. Preserve everything the board marked as STRENGTHS.
3. Do not add new agents, templates, or pipeline steps that weren't discussed.
4. If a change conflicts with another, follow Peter's direction (CEO authority).
4. If a change conflicts with another, follow Victor's direction (CEO authority).
5. The output must be a COMPLETE, self-contained design specification with
all sections present — not a diff or changelog.
@@ -77,14 +77,14 @@ steps:
spawn:
- task_type: human_action
task_name: "Operator Approval: Green Light Bootstrap — {task.message}"
agent_name: Peter
agent_name: Victor
priority: 9
context:
gate_purpose: "Final approval before company creation — this spawns real infrastructure"
- task_type: bootstrap_company
task_name: "Bootstrap: {task.message}"
agent_name: David
agent_name: Nolan
priority: 8
depends_on:
- "Operator Approval: Green Light Bootstrap — {task.message}"

8
templates/design_roundtable.yml
View File

@@ -4,8 +4,8 @@ description: >
structured rounds, reaching consensus on required changes before polish.
participants:
- Peter
- David
- Victor
- Nolan
- Sarah
- Elena
@@ -37,8 +37,8 @@ steps:
{this_agent_review}
OTHER REVIEWS:
[Peter] {peter_review}
[David] {david_review}
[Victor] {peter_review}
[Nolan] {david_review}
[Sarah] {sarah_review}
[Elena] {elena_review}

4
templates/market_research.yml
View File

@@ -88,7 +88,7 @@ steps:
spawn:
- task_type: human_action
task_name: "Operator Review: Select Business Concept — {task.message}"
agent_name: Peter
agent_name: Victor
priority: 8
context:
market_pitch: "{market_pitch}"
@@ -96,7 +96,7 @@ steps:
- task_type: company_design
task_name: "Company Design Boardroom: {task.message}"
agent_name: Peter
agent_name: Victor
priority: 7
context:
market_pitch: "{market_pitch}"