fix: add proposal index, wire prior proposals into edgar review + proposal templates, unblock CLO proposal
This commit is contained in:
62
deliverables/proposals/index.md
Normal file
62
deliverables/proposals/index.md
Normal file
@@ -0,0 +1,62 @@
|
||||
# Proposal Index: Crimson Leaf Holdings
|
||||
|
||||
This file is READ at the start of each company_proposal run and UPDATED at the end.
|
||||
It is the authoritative list of every proposal ever submitted.
|
||||
Edgar must read this before writing any new proposal.
|
||||
|
||||
---
|
||||
|
||||
## Submitted Proposals
|
||||
|
||||
### BATCH 1 (April 26-28, 2026): "Ink & Anchor Digital" variants -- ALL REJECTED BY DAVID
|
||||
These 20 proposals were generated by a template bug that ignored the mission charter.
|
||||
They all proposed a client-facing indie author DTC storefront called "Ink & Anchor Digital"
|
||||
or "Forge & Flux Digital." This is NOT what the mission charter authorizes.
|
||||
|
||||
David's verdict: "None of the proposals are worth reading. I am looking for full business plans."
|
||||
Status: REJECTED. Do NOT repropose this concept in any form.
|
||||
|
||||
Task IDs (all rejected, do not reference):
|
||||
- 0d80560c, 13adc48e, 348f8719, 45dfae65, 4e8bbd4e, 63136109, 6f86fbb1, 857ef6e1
|
||||
- ccb79de6, c8990e30, c7801662, a47b8efc, f7290270, 5611a2fc, d21cb28c, ac60bb87
|
||||
- 77a90934, ceaa0c81, 1550e9e3, 863cd274
|
||||
|
||||
Reason for rejection: Proposed the wrong company. Mission charter Gap 1 is CLO --
|
||||
Crimson Leaf Operations -- an INTERNAL financial visibility company, not a
|
||||
client-facing author services agency.
|
||||
|
||||
---
|
||||
|
||||
## What the Next Proposal Must Be
|
||||
|
||||
GAP 1 (AUTHORIZED BY DAVID, HIGHEST PRIORITY):
|
||||
Company: Crimson Leaf Operations (CLO)
|
||||
Slug: crimson_leaf_operations
|
||||
Mission: Give Edgar financial visibility. Track API costs, revenue, and P&L
|
||||
across all subsidiaries. Without CLO, Edgar is flying blind.
|
||||
This is an INTERNAL operations company. It does NOT serve clients.
|
||||
It does NOT build websites. It does NOT serve indie authors.
|
||||
It tracks money: what is spent, what is earned, what the margins are.
|
||||
|
||||
The next proposal MUST be for CLO. Build a serious, detailed plan:
|
||||
- How CLO tracks costs per company, per task, per model
|
||||
- How CLO generates weekly P&L reports for David
|
||||
- What agents run CLO (an internal accountant/analyst)
|
||||
- What templates it uses (cost_report, revenue_summary, etc.)
|
||||
- How it integrates with the PAE task system to capture cost data
|
||||
- 90-day success criteria: weekly P&L delivered, cost-per-chapter tracked, etc.
|
||||
|
||||
Do NOT pitch a different company. Do NOT rename it. Do NOT make it client-facing.
|
||||
|
||||
---
|
||||
|
||||
## Instructions for the company_proposal template
|
||||
|
||||
When you finish writing a proposal, append a new entry to this file under
|
||||
"## Submitted Proposals" with:
|
||||
- The company name and slug
|
||||
- The task ID
|
||||
- A 2-3 sentence summary of what was proposed
|
||||
- David's verdict (if known -- leave blank if awaiting)
|
||||
|
||||
This keeps Edgar's institutional memory intact across cycles.
|
||||
Reference in New Issue
Block a user