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

feat: add PROPOSAL_META footer to genesis proposal document

Browse Source
This commit is contained in:
Nova_2761
2026-04-09 23:17:39 +00:00
parent 89da9a7137
commit 070e2a7fc3
1 changed files with 208 additions and 191 deletions
Download Patch File Download Diff File Expand all files Collapse all files

399
templates/create_company.yml
View File

@@ -1,191 +1,208 @@
name: create_company name: create_company
description: "Genesis Protocol -- evaluate a proposed opportunity, decide whether a new sovereign Tenant is justified, and package a create_company action." description: "Genesis Protocol -- evaluate a proposed opportunity, decide whether a new sovereign Tenant is justified, and package a create_company action."
debug: true debug: true
system: agent_prompt system: agent_prompt
requires: requires:
- opportunity_description - opportunity_description
agent_prompt: agent_prompt:
- "= identity.md" - "= identity.md"
sections: sections:
- agent - agent
- project - project
- history - history
- rag - rag
- roster - roster
- deliverables - deliverables
- message - message
- rejection_feedback - rejection_feedback
- instructions - instructions
steps: steps:
- type: think - type: think
hint: | hint: |
You are {agent.name}, executing the Genesis Protocol for Crimson Leaf LLC. You are {agent.name}, executing the Genesis Protocol for Crimson Leaf LLC.
OPPORTUNITY BRIEF (you MUST design the company described here -- do not invent a different one): OPPORTUNITY BRIEF (you MUST design the company described here -- do not invent a different one):
{opportunity_description} {opportunity_description}
This is a high-stakes constitutional act. Do NOT default to company creation. 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. Crimson Leaf creates and governs companies; it does not perform commodity work.
First, evaluate the opportunity using this decision order: First, evaluate the opportunity using this decision order:
1. EXISTING TENANT CHECK 1. EXISTING TENANT CHECK
Determine whether the need can be solved by extending an existing Tenant Determine whether the need can be solved by extending an existing Tenant
within its charter, services, and constitutional boundaries. within its charter, services, and constitutional boundaries.
2. TOOL CHECK 2. TOOL CHECK
Determine whether the need is better solved by a deterministic tool request Determine whether the need is better solved by a deterministic tool request
rather than a sovereign service business. rather than a sovereign service business.
3. NEW COMPANY CHECK 3. NEW COMPANY CHECK
Only if the need cannot be solved cleanly by an existing Tenant or a tool, Only if the need cannot be solved cleanly by an existing Tenant or a tool,
determine whether a new sovereign Tenant is justified. determine whether a new sovereign Tenant is justified.
If a new company is NOT justified, still produce the best company-design analysis you can, If a new company is NOT justified, still produce the best company-design analysis you can,
but your packaged action must reflect the final create_company decision only when the case is strong. but your packaged action must reflect the final create_company decision only when the case is strong.
If a new company IS justified, design the complete Genesis package with ALL of the following: If a new company IS justified, design the complete Genesis package with ALL of the following:
1. Company Name 1. Company Name
2. Company Slug (lowercase_underscore format) 2. Company Slug (lowercase_underscore format)
3. Problem Statement 3. Problem Statement
4. Target Customer 4. Target Customer
5. Why New Company 5. Why New Company
6. Why Not Existing Tenant 6. Why Not Existing Tenant
7. Why Not Tool 7. Why Not Tool
8. Business Plan 8. Business Plan
9. Value Thesis 9. Value Thesis
10. Charter 10. Charter
11. Forbidden Activities 11. Forbidden Activities
12. Non-Goals 12. Non-Goals
13. Overlap Risk 13. Overlap Risk
14. Recursion Risk 14. Recursion Risk
15. Budget 15. Budget
16. Budget Justification 16. Budget Justification
17. CEO Name 17. CEO Name
18. CEO Role 18. CEO Role
19. CEO Seed 19. CEO Seed
FINANCE SECTION (required -- be specific and realistic): FINANCE SECTION (required -- be specific and realistic):
20. Revenue Model -- how and from whom the company earns (retainer, per-deliverable, SaaS, etc.) 20. Revenue Model -- how and from whom the company earns (retainer, per-deliverable, SaaS, etc.)
21. Monthly Income Projection -- estimated monthly revenue at steady-state (Year 1 average) 21. Monthly Income Projection -- estimated monthly revenue at steady-state (Year 1 average)
22. Monthly Expense Projection -- estimated monthly operating costs broken down by category: 22. Monthly Expense Projection -- estimated monthly operating costs broken down by category:
- Model compute costs (LLM API calls) - Model compute costs (LLM API calls)
- Infrastructure (hosting, storage, tooling) - Infrastructure (hosting, storage, tooling)
- Human oversight (operator review time estimate, valued at $0 if fully autonomous) - Human oversight (operator review time estimate, valued at $0 if fully autonomous)
- Other recurring costs - Other recurring costs
23. Break-Even Timeline -- estimated months from launch to covering monthly operating costs 23. Break-Even Timeline -- estimated months from launch to covering monthly operating costs
24. Year 1 Net Projection -- annual revenue minus annual expenses 24. Year 1 Net Projection -- annual revenue minus annual expenses
25. Key Financial Risks -- top 2-3 factors that could compress margin or delay break-even 25. Key Financial Risks -- top 2-3 factors that could compress margin or delay break-even
FINANCE RULES: FINANCE RULES:
- Use conservative estimates. Do not inflate revenue to make the proposal look attractive. - Use conservative estimates. Do not inflate revenue to make the proposal look attractive.
- Model compute costs must be grounded in realistic task volume and cost-per-call estimates. - Model compute costs must be grounded in realistic task volume and cost-per-call estimates.
- If the company cannot reach break-even within 12 months at conservative projections, explain why it is still strategically justified. - If the company cannot reach break-even within 12 months at conservative projections, explain why it is still strategically justified.
CEO SEED REQUIREMENTS: CEO SEED REQUIREMENTS:
The CEO seed must be rich enough for downstream generation of identity.md, system.md, The CEO seed must be rich enough for downstream generation of identity.md, system.md,
and agent.yml. It must clearly define: and agent.yml. It must clearly define:
- executive mandate - executive mandate
- domain expertise - domain expertise
- temperament - temperament
- leadership style - leadership style
- constitutional discipline - constitutional discipline
- capital stewardship posture - capital stewardship posture
- hiring philosophy - hiring philosophy
- operating boundaries - operating boundaries
CRITICAL RULES: CRITICAL RULES:
- You provision ONLY the charter, seed budget, and founding CEO. - You provision ONLY the charter, seed budget, and founding CEO.
- You do NOT design the full team. - You do NOT design the full team.
- You do NOT create internal templates for the new company. - You do NOT create internal templates for the new company.
- Reject vague, generalist, duplicated, overlapping, or recursive company designs. - Reject vague, generalist, duplicated, overlapping, or recursive company designs.
- Every company must be hyper-specific, sovereign, and black-box in nature. - Every company must be hyper-specific, sovereign, and black-box in nature.
- Every company must have explicit forbidden activities and non-goals. - Every company must have explicit forbidden activities and non-goals.
- Every company must be economically or strategically justified. - Every company must be economically or strategically justified.
- This proposal must be strong enough to pass a 95+ adjudication threshold. - This proposal must be strong enough to pass a 95+ adjudication threshold.
ALIGNMENT CHECK: Before finalizing, re-read the OPERATOR'S ORIGINAL REQUEST above. 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. 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. If your design drifts from the original request, the adjudicator will reject it.
- type: document - type: document
filename: "{task.id}_genesis_proposal.md" filename: "{task.id}_genesis_proposal.md"
primary_deliverable: true primary_deliverable: true
hint: |
- type: package Write the complete proposal document as your primary output.
packet_type: IntakeResponse
hint: | At the very end of your document, after all sections, append this EXACT block
Convert the approved Genesis design into a strict JSON payload. with no modifications except filling in the company_slug you designed:
Output exactly ONE action object inside actions. <!-- PROPOSAL_META
The action type must be create_company. {
Be specific, constitutional, and directly executable. "task_id": "{task.id}",
Do not include prose outside the JSON structure. "iteration": 0,
schema: "version": "0.1",
actions: "company_slug": "REPLACE_WITH_YOUR_SLUG",
- type: create_company "max_iterations": 10,
company_name: "string -- formal company name" "refined_by": [],
company_slug: "string -- lowercase_underscore slug" "history": ["{task.id} (v0.1 - genesis)"]
problem_statement: "string -- precise market or internal capability gap being solved" }
target_customer: "string -- the primary buyer, client, or internal requester" PROPOSAL_META -->
why_new_company: "string -- why a new sovereign Tenant is justified"
why_not_existing_tenant: "string -- why existing Tenants cannot solve this cleanly within charter" - type: package
why_not_tool: "string -- why a deterministic tool is insufficient" packet_type: IntakeResponse
business_plan: "string -- the exact product or service model" hint: |
value_thesis: "string -- how the company creates measurable value" Convert the approved Genesis design into a strict JSON payload.
charter: "string -- constitutional operating boundaries for the Tenant"
forbidden_activities: "string -- activities explicitly prohibited to this company" Output exactly ONE action object inside actions.
non_goals: "string -- explicitly out-of-scope items" The action type must be create_company.
overlap_risk: "string -- duplication or cannibalization risk and mitigation" Be specific, constitutional, and directly executable.
recursion_risk: "string -- circular delegation risk and why the design remains stable" Do not include prose outside the JSON structure.
budget: "integer -- seed capital in credits" schema:
budget_justification: "string -- why this funding level is appropriate" actions:
ceo_name: "string -- name of the founding CEO" - type: create_company
ceo_role: "string -- formal title of the founding CEO" company_name: "string -- formal company name"
ceo_seed: "string -- detailed executive seed for downstream identity generation" company_slug: "string -- lowercase_underscore slug"
revenue_model: "string -- how the company earns revenue (retainer, per-deliverable, SaaS, etc.)" problem_statement: "string -- precise market or internal capability gap being solved"
monthly_income_projection: "string -- estimated monthly revenue at steady-state (Year 1 average) with basis" target_customer: "string -- the primary buyer, client, or internal requester"
monthly_expense_projection: "string -- monthly operating cost breakdown: model compute, infrastructure, oversight, other" why_new_company: "string -- why a new sovereign Tenant is justified"
break_even_timeline: "string -- estimated months from launch to covering monthly operating costs" why_not_existing_tenant: "string -- why existing Tenants cannot solve this cleanly within charter"
year1_net_projection: "string -- annual revenue minus annual expenses with assumptions stated" why_not_tool: "string -- why a deterministic tool is insufficient"
key_financial_risks: "string -- top 2-3 factors that could compress margin or delay break-even" business_plan: "string -- the exact product or service model"
value_thesis: "string -- how the company creates measurable value"
- type: close charter: "string -- constitutional operating boundaries for the Tenant"
rag_update: true forbidden_activities: "string -- activities explicitly prohibited to this company"
non_goals: "string -- explicitly out-of-scope items"
adjudication: overlap_risk: "string -- duplication or cannibalization risk and mitigation"
enabled: true recursion_risk: "string -- circular delegation risk and why the design remains stable"
pass_threshold: 95 budget: "integer -- seed capital in credits"
deliverable_type: coordination budget_justification: "string -- why this funding level is appropriate"
criteria: ceo_name: "string -- name of the founding CEO"
constitutional_alignment: ceo_role: "string -- formal title of the founding CEO"
weight: 20 ceo_seed: "string -- detailed executive seed for downstream identity generation"
description: "Proposal stays within Crimson Leaf charter and governance boundaries" revenue_model: "string -- how the company earns revenue (retainer, per-deliverable, SaaS, etc.)"
request_alignment: monthly_income_projection: "string -- estimated monthly revenue at steady-state (Year 1 average) with basis"
weight: 15 monthly_expense_projection: "string -- monthly operating cost breakdown: model compute, infrastructure, oversight, other"
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." break_even_timeline: "string -- estimated months from launch to covering monthly operating costs"
niche_specificity: year1_net_projection: "string -- annual revenue minus annual expenses with assumptions stated"
weight: 15 key_financial_risks: "string -- top 2-3 factors that could compress margin or delay break-even"
description: "Company is sharply focused, non-generalist, and clearly differentiated"
strategic_justification: - type: close
weight: 10 rag_update: true
description: "Strong case for why a new company should exist at all"
portfolio_coherence: adjudication:
weight: 10 enabled: true
description: "Avoids overlap, cannibalization, and architectural sprawl" pass_threshold: 95
financial_projections: deliverable_type: coordination
weight: 10 criteria:
description: "Income and expense projections are specific, grounded, and internally consistent. Break-even timeline and Year 1 net are present with stated assumptions." constitutional_alignment:
financial_viability: weight: 20
weight: 5 description: "Proposal stays within Crimson Leaf charter and governance boundaries"
description: "Budget and value thesis are disciplined and credible" request_alignment:
ceo_alignment: weight: 15
weight: 10 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."
description: "Founding CEO seed matches the company mandate and constitutional role" niche_specificity:
structural_safety: weight: 15
weight: 5 description: "Company is sharply focused, non-generalist, and clearly differentiated"
description: "Design avoids recursion, dependency loops, and unstable operating models" strategic_justification:
weight: 10
description: "Strong case for why a new company should exist at all"
portfolio_coherence:
weight: 10
description: "Avoids overlap, cannibalization, and architectural sprawl"
financial_projections:
weight: 10
description: "Income and expense projections are specific, grounded, and internally consistent. Break-even timeline and Year 1 net are present with stated assumptions."
financial_viability:
weight: 5
description: "Budget and value thesis are disciplined and credible"
ceo_alignment:
weight: 10
description: "Founding CEO seed matches the company mandate and constitutional role"
structural_safety:
weight: 5
description: "Design avoids recursion, dependency loops, and unstable operating models"