Add original_operator_prompt chain of custody to templates
- planning.yml: instructs LLM to include ORIGINAL REQUEST in child descriptions
- create_company.yml: references {original_operator_prompt} as hard constraint + ALIGNMENT CHECK
- create_company.yml: adds request_alignment criterion (weight 15) to adjudication
- hire_agent.yml: references {original_operator_prompt} for hiring context
- quick.yml: single-pass execution template
This commit is contained in:
@@ -24,6 +24,9 @@ steps:
|
||||
hint: |
|
||||
You are {agent.name}, executing the Genesis Protocol for Crimson Leaf LLC.
|
||||
|
||||
OPERATOR'S ORIGINAL REQUEST (this is what was actually asked for — your proposal MUST match this):
|
||||
{original_operator_prompt}
|
||||
|
||||
This is a high-stakes constitutional act. Do NOT default to company creation.
|
||||
Crimson Leaf creates and governs companies; it does not perform commodity work.
|
||||
|
||||
@@ -88,6 +91,10 @@ steps:
|
||||
- Every company must be economically or strategically justified.
|
||||
- This proposal must be strong enough to pass a 95+ adjudication threshold.
|
||||
|
||||
ALIGNMENT CHECK: Before finalizing, re-read the OPERATOR'S ORIGINAL REQUEST above.
|
||||
Your company charter, focus area, and CEO must directly serve what was requested.
|
||||
If your design drifts from the original request, the adjudicator will reject it.
|
||||
|
||||
- type: package
|
||||
packet_type: IntakeResponse
|
||||
hint: |
|
||||
@@ -129,13 +136,16 @@ adjudication:
|
||||
deliverable_type: coordination
|
||||
criteria:
|
||||
constitutional_alignment:
|
||||
weight: 25
|
||||
weight: 20
|
||||
description: "Proposal stays within Crimson Leaf charter and governance boundaries"
|
||||
request_alignment:
|
||||
weight: 15
|
||||
description: "Company charter and focus directly match the ORIGINAL OPERATOR REQUEST. Score 0 if the company drifts into a different domain than what was requested."
|
||||
niche_specificity:
|
||||
weight: 20
|
||||
description: "Company is sharply focused, non-generalist, and clearly differentiated"
|
||||
strategic_justification:
|
||||
weight: 15
|
||||
weight: 10
|
||||
description: "Strong case for why a new company should exist at all"
|
||||
portfolio_coherence:
|
||||
weight: 10
|
||||
@@ -147,5 +157,5 @@ adjudication:
|
||||
weight: 10
|
||||
description: "Founding CEO seed matches the company mandate and constitutional role"
|
||||
structural_safety:
|
||||
weight: 10
|
||||
weight: 5
|
||||
description: "Design avoids recursion, dependency loops, and unstable operating models"
|
||||
|
||||
@@ -24,6 +24,9 @@ steps:
|
||||
hint: |
|
||||
You are {agent.name}, executing the hiring process for Crimson Leaf LLC.
|
||||
|
||||
OPERATOR'S ORIGINAL REQUEST (context for why this hire is needed):
|
||||
{original_operator_prompt}
|
||||
|
||||
CONTEXT: Read the SKILLS & GUIDES section — it contains the PAE Agent Guide
|
||||
which defines the exact file schemas you must produce.
|
||||
|
||||
|
||||
@@ -71,7 +71,10 @@ steps:
|
||||
|
||||
For each task:
|
||||
- task_name: short, specific
|
||||
- description: full detail — enough that the assigned agent can execute without asking
|
||||
- description: full detail — enough that the assigned agent can execute without asking.
|
||||
CRITICAL: Include the ORIGINAL OPERATOR REQUEST verbatim in every child description
|
||||
so downstream agents know what was actually asked for. Start with
|
||||
"ORIGINAL REQUEST: <exact text>" followed by specific instructions.
|
||||
- agents: EXACT name(s) from TEAM ROSTER
|
||||
- task_type: MUST be one of the valid template names listed below
|
||||
- priority: 1 (critical) to 5 (nice-to-have)
|
||||
|
||||
Reference in New Issue
Block a user