diff --git a/templates/company_proposal.yml b/templates/company_proposal.yml new file mode 100644 index 0000000..3b58e57 --- /dev/null +++ b/templates/company_proposal.yml @@ -0,0 +1,229 @@ +name: company_proposal +description: "Produce a complete, board-ready business plan for a proposed new Crimson Leaf subsidiary." +debug: true +model: power +system: agent_prompt + +agent_prompt: + - "= identity.md" + - "= mission.md" + +sections: + - agent + - project + - rag + - message + - instructions + +steps: + - type: think + max_tokens: 2000 + output_key: exec_summary + hint: | + You are writing a professional business plan for a proposed subsidiary. + The brief from the strategic review is in the task message above. + + Write the EXECUTIVE SUMMARY section. Include: + + 1. PROPOSED COMPANY + - Full name and slug + - 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: package + output_key: full_proposal + hint: | + Assemble the complete business plan from all sections above. + 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 + Date: {task.created_at_date} + 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. + + - type: document + output_key: full_proposal + path: "crimson_leaf/deliverables/proposals/proposal-{task.id}.md" + repo: "pae/crimson_leaf" + commit_message: "proposal: {company_spec[0:60]} (Sprint 82)" + + - type: reply + target: channel + channel_id: "1473516041249493104" + 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 \ No newline at end of file