fix: anchor proposal brief to mission charter -- CLO is internal ops, not a DTC agency
This commit is contained in:
@@ -16,10 +16,14 @@ steps:
|
|||||||
You are writing a professional business plan for a proposed subsidiary.
|
You are writing a professional business plan for a proposed subsidiary.
|
||||||
The brief from the strategic review is in the task message above.
|
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.
|
||||||
|
|
||||||
Write the EXECUTIVE SUMMARY section. Include:
|
Write the EXECUTIVE SUMMARY section. Include:
|
||||||
|
|
||||||
1. PROPOSED COMPANY
|
1. PROPOSED COMPANY
|
||||||
- Full name and slug
|
- Full name and slug (EXACTLY as given in the brief -- do not invent a new name)
|
||||||
- One-sentence purpose statement
|
- One-sentence purpose statement
|
||||||
- Which existing gap it closes (reference the mission charter)
|
- Which existing gap it closes (reference the mission charter)
|
||||||
|
|
||||||
|
|||||||
@@ -142,14 +142,26 @@ steps:
|
|||||||
Otherwise, write the task message for the company_proposal pipeline.
|
Otherwise, write the task message for the company_proposal pipeline.
|
||||||
This brief becomes the input that drives the full business plan.
|
This brief becomes the input that drives the full business plan.
|
||||||
|
|
||||||
Include:
|
CRITICAL: Do NOT invent a company name. Use EXACTLY the company defined
|
||||||
- Which company to propose (name, slug, purpose in one sentence)
|
in the mission charter for the top-priority gap. The mission charter
|
||||||
- What gap it fills (specific -- what Edgar cannot do today without it)
|
specifies the proposed solution for each gap by name and slug.
|
||||||
- Why now (cost of waiting another 30 days)
|
You are reporting what the mission says, not brainstorming a new concept.
|
||||||
- Proposed 90-day success criteria (measurable)
|
|
||||||
- Known constraints or dependencies
|
|
||||||
|
|
||||||
Be specific. This brief drives the entire proposal document.
|
GAP 1 (CLO) is defined in the mission charter as:
|
||||||
|
Company: Crimson Leaf Operations (CLO)
|
||||||
|
Slug: crimson_leaf_operations
|
||||||
|
Purpose: INTERNAL financial visibility -- give Edgar the ability to see
|
||||||
|
API costs, revenue, and operational expenses.
|
||||||
|
This is NOT a client-facing agency. NOT a storefront. NOT a DTC product.
|
||||||
|
It is an internal accounting and reporting company for Crimson Leaf Holdings.
|
||||||
|
|
||||||
|
Your brief must:
|
||||||
|
- Name the company EXACTLY as the mission defines it (no renaming, no rebranding)
|
||||||
|
- Describe the specific gap it fills from the mission charter
|
||||||
|
- Explain what Edgar cannot do today without it (financial blindness)
|
||||||
|
- State why now (cost of waiting another 30 days)
|
||||||
|
- Include 90-day success criteria (measurable, e.g. "weekly P&L report delivered")
|
||||||
|
- Note known constraints or dependencies
|
||||||
|
|
||||||
Output ONLY the brief text. No labels. No preamble.
|
Output ONLY the brief text. No labels. No preamble.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user