CL research: add research mode templates + web research to proposals and market intel
- company_proposal.yml: add 2 research phases (market + revenue) before exec summary; all think steps now require [Title](URL) citations; add Sources section to document - market_intelligence.yml: add web search step (research mode) before analysis think; package schema adds sources array; adjudication evidence_quality now checks for citations - research_brief.yml: new standalone 4-query deep research template; searches market, competitors, trends, cases; assembles annotated brief with Source Index section; saves to deliverables/research/; adjudication checks citation_quality (40% weight)
This commit is contained in:
David Baity
@@ -1,5 +1,5 @@
|
||||
name: company_proposal
|
||||
description: "Produce a complete, board-ready business plan for a proposed new Crimson Leaf subsidiary."
|
||||
description: "Produce a complete, board-ready business plan for a proposed new Crimson Leaf subsidiary. Includes web research with cited sources."
|
||||
debug: true
|
||||
model: power
|
||||
sections:
|
||||
@@ -16,6 +16,330 @@ steps:
|
||||
output_key: prior_proposals
|
||||
optional: true
|
||||
|
||||
- type: think
|
||||
max_tokens: 800
|
||||
output_key: research_queries
|
||||
hint: |
|
||||
You are preparing to write a business plan.
|
||||
The brief from the strategic review is in the task message above.
|
||||
|
||||
Generate 3 precise web search queries to gather real market data for this plan.
|
||||
Focus on:
|
||||
1. Market size and growth rate for this type of business
|
||||
2. Competitor landscape and pricing in this niche
|
||||
3. Trends and demand signals supporting this opportunity
|
||||
|
||||
Output ONLY a numbered list of 3 search queries. No explanation. No commentary.
|
||||
Example:
|
||||
1. AI content publishing market size 2025
|
||||
2. automated ebook publishing competitors pricing
|
||||
3. self-publishing AI tools demand trends
|
||||
|
||||
- type: tool
|
||||
capability: Tool_WebSearcher
|
||||
input_from: last_text
|
||||
mode: research
|
||||
max_results: 6
|
||||
fetch_pages: 3
|
||||
optional: true
|
||||
output_key: market_research_1
|
||||
|
||||
- type: think
|
||||
max_tokens: 600
|
||||
output_key: research_query_2
|
||||
hint: |
|
||||
Your previous research covered market size and competitors.
|
||||
Now formulate ONE focused search query to find:
|
||||
- Revenue models and monetization strategies in this exact niche
|
||||
- Pricing benchmarks or average deal sizes
|
||||
- Customer pain points or unmet needs documented online
|
||||
|
||||
Output ONLY the search query. Nothing else.
|
||||
|
||||
- type: tool
|
||||
capability: Tool_WebSearcher
|
||||
input_from: last_text
|
||||
mode: research
|
||||
max_results: 5
|
||||
fetch_pages: 2
|
||||
optional: true
|
||||
output_key: market_research_2
|
||||
|
||||
- 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.
|
||||
|
||||
IMPORTANT: Use the company name, slug, and purpose EXACTLY as stated in
|
||||
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.
|
||||
|
||||
=== MARKET RESEARCH (primary) ===
|
||||
{market_research_1}
|
||||
=== END RESEARCH ===
|
||||
|
||||
=== MARKET RESEARCH (revenue/monetization) ===
|
||||
{market_research_2}
|
||||
=== END RESEARCH ===
|
||||
|
||||
Write the EXECUTIVE SUMMARY section. Cite specific research findings inline
|
||||
using [Title](URL) markdown format wherever you reference external data.
|
||||
|
||||
Include:
|
||||
|
||||
1. PROPOSED COMPANY
|
||||
- Full name and slug (EXACTLY as given in the brief)
|
||||
- One-sentence purpose statement
|
||||
- Which existing gap it closes
|
||||
|
||||
2. PROBLEM STATEMENT
|
||||
What is Crimson Leaf Holdings unable to do today without this company?
|
||||
Be specific. Give examples of decisions we cannot make.
|
||||
|
||||
3. MARKET OPPORTUNITY
|
||||
Use data from the research above. Cite every statistic.
|
||||
What is the addressable market? What is the growth trajectory?
|
||||
What do competitors charge? What are they missing?
|
||||
|
||||
4. PROPOSED SOLUTION
|
||||
How does this company close the gap?
|
||||
What would it do in the first 30 days? First 90 days?
|
||||
|
||||
5. 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.
|
||||
Every factual claim should be backed by a citation from the research.
|
||||
|
||||
- type: think
|
||||
max_tokens: 1500
|
||||
output_key: cost_model
|
||||
hint: |
|
||||
Write the COST MODEL AND FINANCIAL PROJECTIONS section.
|
||||
Reference any pricing or market data from the research to ground your projections.
|
||||
|
||||
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?
|
||||
- Cite any relevant market benchmarks from the research above.
|
||||
|
||||
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?
|
||||
|
||||
Use real numbers from research where available. Estimate clearly where not.
|
||||
|
||||
- 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?
|
||||
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?
|
||||
Rate each risk: Low / Medium / High
|
||||
|
||||
3. COMPETITIVE RISK
|
||||
Reference the competitor research above. Which competitors are already in this space?
|
||||
What is their moat? Can we out-specialize them? Cite with [Title](URL).
|
||||
|
||||
4. 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
|
||||
|
||||
5. RECOMMENDATION
|
||||
Given the above, do you still recommend proceeding?
|
||||
If yes, state the minimum viable version.
|
||||
|
||||
- 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.
|
||||
|
||||
6. DEPENDENCIES
|
||||
- What must exist before this company can operate?
|
||||
- Any data feeds, integrations, or other companies required?
|
||||
|
||||
- type: think
|
||||
max_tokens: 7000
|
||||
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}
|
||||
|
||||
---
|
||||
|
||||
## Market Research Sources
|
||||
List all sources cited in this document as a reference section:
|
||||
- [Title](URL) -- brief note on what data was drawn from this source
|
||||
|
||||
---
|
||||
|
||||
## 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 with market research is provided
|
||||
|
||||
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: 9
|
||||
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)
|
||||
- Key market data found (one statistic with citation)
|
||||
- Where to find the full proposal (Gitea: pae/crimson_leaf/deliverables/proposals/)
|
||||
- A clear request for approval or feedback
|
||||
|
||||
Keep it to 4-6 lines. Professional tone. No fluff.
|
||||
|
||||
adjudication:
|
||||
enabled: false
|
||||
- type: tool
|
||||
action: git_read_file
|
||||
params:
|
||||
path: "deliverables/proposals/index.md"
|
||||
output_key: prior_proposals
|
||||
optional: true
|
||||
|
||||
- type: think
|
||||
max_tokens: 2000
|
||||
output_key: exec_summary
|
||||
|
||||
Reference in New Issue
Block a user