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

fix: company_proposal YAML corruption -- remove duplicated old template content, enable adjudication

Browse Source
This commit is contained in:
David Baity
2026-04-29 10:13:55 -04:00
parent ee13878667
commit 514aef210b
1 changed files with 16 additions and 258 deletions
Download Patch File Download Diff File Expand all files Collapse all files

274
templates/company_proposal.yml
View File

@@ -332,261 +332,19 @@ steps:
Keep it to 4-6 lines. Professional tone. No fluff. Keep it to 4-6 lines. Professional tone. No fluff.
adjudication: adjudication:
enabled: false enabled: true
- type: tool pass_threshold: 80
action: git_read_file deliverable_type: proposal
params: criteria:
path: "deliverables/proposals/index.md" market_research:
output_key: prior_proposals weight: 30
optional: true description: "Real web-sourced market data with [Title](URL) citations -- no invented statistics"
completeness:
- type: think weight: 25
max_tokens: 2000 description: "All required sections present: exec summary, cost model, risk analysis, company spec"
output_key: exec_summary specificity:
hint: | weight: 25
You are writing a professional business plan for a proposed subsidiary. description: "Specific company name/slug, concrete 90-day metrics, no vague filler"
The brief from the strategic review is in the task message above. no_duplicates:
weight: 20
IMPORTANT: Use the company name, slug, and purpose EXACTLY as stated in description: "Proposed company does not duplicate an existing subsidiary or prior proposal"
the brief. Do NOT rename, rebrand, or creatively reinterpret the company.
The brief was written from the mission charter -- it is authoritative.
=== PRIOR PROPOSALS (read this before writing) ===
{prior_proposals}
=== END PRIOR PROPOSALS ===
The prior proposals above are your institutional memory. Study them.
Do NOT repeat a company that was already proposed. Do NOT reuse names,
slugs, or concepts that were rejected. Build something new and better.
Write the EXECUTIVE SUMMARY section. Include:
1. PROPOSED COMPANY
- Full name and slug (EXACTLY as given in the brief -- do not invent a new name)
- One-sentence purpose statement
- Which existing gap it closes (reference the mission charter)
2. PROBLEM STATEMENT
What is Crimson Leaf Holdings unable to do today without this company?
Be specific. Give examples of decisions we cannot make, costs we cannot measure,
or opportunities we cannot capture because this gap exists.
3. PROPOSED SOLUTION
How does this company close the gap?
What would it do in the first 30 days? First 90 days?
4. STRATEGIC FIT
How does this company advance the primary mission (profitable AI publishing)?
How does it interact with existing subsidiaries?
Write in professional business plan style. No fluff. No filler.
- type: think
max_tokens: 1500
output_key: cost_model
hint: |
Write the COST MODEL AND FINANCIAL PROJECTIONS section.
Include:
1. SETUP COSTS
- Gitea repo creation (one-time, zero API cost, ~5 minutes of Copilot time)
- Initial template development (estimate tasks * cost per task)
- Initial agent configuration
2. RECURRING OPERATIONAL COSTS
- Estimated tasks per week at steady state
- Average cost per task (power model: ~$0.05-0.15 per task typical range)
- Weekly and monthly API cost projection
3. COST-BENEFIT ANALYSIS
- What is the cost of NOT having this company? (lost revenue, blind decisions, etc.)
- What is the break-even point? When do the benefits outweigh the costs?
4. BUDGET CONSTRAINT CHECK
- Current Genesis Fund status: UNKNOWN (this is itself evidence for CLO need)
- Does this proposal create a self-funding loop? How?
5. COMPARISON
Compare against the cost of Edgar running blind for 30 more days without this.
Use real numbers where available. Estimate clearly where not.
Note: actual costs unknown because CLO does not exist yet.
- type: think
max_tokens: 1200
output_key: risk_analysis
hint: |
Write the RISK ANALYSIS AND ALTERNATIVES CONSIDERED section.
Include:
1. RISKS OF PROCEEDING
- Could this company create scope creep or distraction?
- Could it duplicate work already handled by an existing subsidiary?
- Is the proposed company more complex than the problem requires?
Rate each risk: Low / Medium / High
2. RISKS OF NOT PROCEEDING
- What keeps getting worse if we wait another 30 days?
- Are there compounding risks (e.g., financial blindness at scale)?
Rate each risk: Low / Medium / High
3. ALTERNATIVES CONSIDERED
For each alternative, explain why it was rejected:
A. Solve with a new template in an existing company
B. Solve with a one-time manual report
C. Expand an existing subsidiary's charter
D. Wait -- this is not urgent enough yet
4. RECOMMENDATION
Given the above, do you still recommend proceeding?
If yes, state the minimum viable version (what is the smallest version
of this company that solves the core problem?).
- type: think
max_tokens: 2000
output_key: company_spec
hint: |
Write the PROPOSED COMPANY SPECIFICATION section.
This is the technical blueprint David and Copilot will use to build the company.
Include:
1. COMPANY RECORD
- company_id: (leave as TBD -- David assigns)
- name: (full display name)
- slug: (lowercase, underscores, e.g. crimson_leaf_operations)
- parent_company: crimson_leaf
- mission: (one sentence)
- tagline: (marketing one-liner)
- type: (operations / research / production / marketing)
- status: active
2. PROPOSED AGENTS
For each agent:
- Role title and name
- Personality and focus in 2-3 sentences
- Primary responsibilities (bullet list)
- Model recommendation: power / standard / fast
- supported_templates list
3. PROPOSED TEMPLATES (MVP set)
For each template:
- Template name and purpose
- Key steps (2-5 sentences describing the pipeline)
- Trigger: scheduled / on-demand / spawned-by
- Estimated cost per run
4. SCHEDULE
- What scheduled tasks should run? At what frequency?
- What should run on demand vs on a schedule?
5. 90-DAY SUCCESS CRITERIA
List 3-5 measurable outcomes that would confirm this company is delivering value.
Each criterion must be verifiable without subjective judgment.
Example: "Weekly P&L report delivered to #general every Monday by 08:00 UTC"
6. DEPENDENCIES
- What must exist before this company can operate?
- Any data feeds, integrations, or other companies required?
- type: think
max_tokens: 6000
output_key: full_proposal
hint: |
Assemble the complete business plan from all sections already written.
Format as a professional document David will read and approve or reject.
REQUIRED STRUCTURE:
# Proposal: [Company Full Name]
Submitted by: Edgar Chen, CEO, Crimson Leaf Holdings
Task ID: {task.id}
Status: AWAITING DAVID'S APPROVAL
---
## Executive Summary
{exec_summary}
---
## Cost Model and Financial Projections
{cost_model}
---
## Risk Analysis and Alternatives Considered
{risk_analysis}
---
## Proposed Company Specification
{company_spec}
---
## Signature Block
Edgar Chen certifies this proposal meets the governance requirements of the
Crimson Leaf Holdings charter:
- No existing subsidiary duplicates this charter
- No existing template or tool can solve this gap
- No proposal for this company has been submitted in the last 30 days
- A full business plan is provided (not a "lick and a promise")
This proposal requires David Baity's explicit approval before any action is taken.
No company will be created until approval is received.
Output ONLY the document content. Start with the # Proposal heading.
- type: document
source_step: 4
dest_path: "deliverables/proposals/proposal-{task.id}.md"
commit_msg: "proposal: company_proposal task={task.id}"
- type: think
max_tokens: 3000
hint: |
You just wrote a company proposal. Update the proposal index.
Read the current index content:
{prior_proposals}
Append a new entry at the bottom of the "## Submitted Proposals" section.
Use this exact format:
### [Company Full Name] -- Task {task.id}
Date: 2026-04-29
Status: AWAITING DAVID'S APPROVAL
Summary: [2-3 sentences: what was proposed, what gap it fills, key differentiator
from any prior proposals]
Output the COMPLETE updated index file content from the very beginning.
Do not truncate. Do not skip sections. Include all prior entries plus the new one.
- type: document
source_step: index_update
dest_path: "deliverables/proposals/index.md"
commit_msg: "index: add proposal {task.id} to proposal index"
- type: reply
target: channel
channel_name: "crimson_leaf:general"
hint: |
Write a brief, professional message to David announcing that a company proposal
is ready for his review.
Include:
- Which company is being proposed (name and slug)
- The core gap it addresses (one sentence)
- Where to find the full proposal (Gitea: pae/crimson_leaf/deliverables/proposals/)
- A clear request for approval or feedback
Keep it to 3-5 lines. Professional tone. No fluff.
Example: "David -- proposal ready for your review: Crimson Leaf Operations (CLO).
This addresses Gap 1: financial blindness. Full plan at [path]. Please approve
or provide feedback."
adjudication:
enabled: false