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

Syncing

Browse Source
This commit is contained in:
David Baity
2026-03-02 23:16:57 -05:00
parent 24246f9cc3
commit 2562737944
7 changed files with 298 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

73
README.md
View File

@@ -1,3 +1,72 @@
# crimson_leaf
# Crimson Leaf LLC
Crimson Leaf LLC — immutable core bootstrapper for PAE multi-tenant architecture
**Crimson Leaf is the Genesis Node** — the holding company that researches, designs, and deploys autonomous business units (Tenants) in the PAE ecosystem.
## What We Do
We manufacture companies. We do not write content, build software, or serve clients. Our sole product is fully-scaffolded autonomous business units, each with its own CEO, specialized agents, templates, pipeline SOP, and RAG knowledge base.
## The Board
| Agent | Role | Focus |
|---|---|---|
| **Victor** | CEO | Capital allocation, Go/No-Go decisions, pipeline governance |
| **Nolan** | CTO | Template procurement, technical feasibility, PAE infrastructure |
| **Sarah** | Head of Market Intelligence | Web research, trend analysis, opportunity pitches |
| **Elena** | Chief Operations Architect | Agent rosters, pipeline SOPs, operational design |
> **Note on naming:** The CEO and CTO are named Victor and Nolan (not Peter and David) to avoid confusion with the human HITL operators who share those names. See `doc/McpSprint50c.md` for details.
## The Pipeline
```
#general prompt from operator
│
▼
Phase 1: market_research (Sarah)
│
▼
🛑 Gate 1: Operator selects concept
│
▼
Phase 2: company_design (full board boardroom)
│
▼
🛑 Gate 2: Operator approves design direction
│
├──► Phase 3a: design_review (Victor)
├──► Phase 3b: design_review (Nolan)
├──► Phase 3c: design_review (Sarah)
└──► Phase 3d: design_review (Elena)
│ (all 4 complete)
▼
Phase 4: design_roundtable (all 4)
│
▼
Phase 5: design_polish (Elena)
│
▼
🛑 Gate 3: Operator green-lights bootstrap
│
▼
Phase 6: bootstrap_company (Nolan)
```
## Key Files
| Path | Purpose |
|---|---|
| `rag/business_plan.md` | Mission, strategy, and success metrics |
| `rag/core_directives.md` | 5 immutable directives governing all decisions |
| `rag/portfolio.md` | Living ledger of all incubated and killed companies |
| `pipelines/incubation_protocol.md` | Full SOP Victor follows — 6 phases, 3 gates |
| `pipelines/kill_protocol.md` | What to do when a concept is killed at any gate |
| `general/OPERATOR_GUIDE.md` | How to trigger the pipeline and navigate gates |
## Quick Start (for Operators)
Post to **#crimson-leaf-general**:
```
Explore opportunities in [industry] for AI agents
```
Victor will handle the rest. See `general/OPERATOR_GUIDE.md` for full details.

80
general/OPERATOR_GUIDE.md Normal file
View File

@@ -0,0 +1,80 @@
# Crimson Leaf LLC — Operator Guide
> **For:** Human operators (Peter, David, or any authorized user)
> **Purpose:** How to interact with Crimson Leaf to start the incubation pipeline and navigate the operator gates.
---
## What Crimson Leaf Does
Crimson Leaf is a holding company that **designs and deploys autonomous business units**. It does not write content, build software, or serve clients directly. Its only product is other companies.
**The Board:**
| Agent | Role | Responsibility |
|---|---|---|
| Victor | CEO | Final Go/No-Go authority. Chairs boardrooms. Drives strategy. |
| Nolan | CTO | Maps business designs to PAE templates and tools. |
| Sarah | Head of Market Intelligence | Web research, trend analysis, opportunity pitches. |
| Elena | Chief Operations Architect | Designs agent rosters, pipelines, and SOPs. |
---
## How to Start the Pipeline
Post a message to **#crimson-leaf-general** describing what you want to explore. Be as broad or specific as you like:
**Examples:**
- `Explore opportunities in the legal services industry for AI agents`
- `Is there a market for AI-powered e-commerce product description writing?`
- `Research the home automation consulting space — what companies could we build?`
Victor will read your message and immediately spawn the Phase 1 market research task for Sarah.
---
## The 3 Operator Gates
The pipeline **pauses** three times and waits for your input before continuing:
### 🛑 Gate 1 — Select a Concept (after Phase 1: Market Research)
Sarah will present 3 business concepts ranked by opportunity strength. You choose one to proceed with.
**How to respond:**
- `"Go with concept #2"` — selects the second concept
- `"None of these, try legal tech instead"` — redirects Sarah to a new industry
- `"Kill this"` — terminates the pipeline
### 🛑 Gate 2 — Approve Design Direction (after Phase 2: Board Alignment)
The board will produce a Company Design Specification. You review the direction before 4 parallel review tasks start.
**How to respond:**
- `"Looks good, proceed"` — starts the parallel review cycle
- `"Change the revenue model to subscription"` — sends feedback; Victor may call another boardroom round
- `"Kill this"` — terminates the pipeline
### 🛑 Gate 3 — Green Light Bootstrap (after Phase 5: Design Polish)
This is the **final gate**. Saying yes creates a real company with real agents and templates. Review carefully.
**How to respond:**
- `"approved"` — creates the company
- Any other response, silence, or delay = no company is created
---
## What Happens After Bootstrap
1. A new Gitea repository is created for the company
2. The company's agents are hired
3. The company's templates are procured
4. The company's CEO receives TASK-000 and begins operating independently
**Crimson Leaf's job is then done.** We do not manage companies after deployment.
---
## Tips
- **Be patient at boardrooms.** The design phase can take several rounds of debate. This is by design.
- **Kill early, not late.** If a concept doesn't feel right at Gate 1, kill it. Phase 2 is expensive.
- **Check `docs/`** in this repository for all generated market pitches and design specs.
- **Check `rag/portfolio.md`** to see the full ledger of incubated and killed companies.

76
pipelines/kill_protocol.md Normal file
View File

@@ -0,0 +1,76 @@
# Crimson Leaf — Kill Protocol (SOP)
> **Read by:** Victor (CEO)
> **Purpose:** Defines exactly what happens when the incubation pipeline is stopped before bootstrap.
> **Rule:** A killed concept is never truly dead — it is archived for future reactivation.
---
## When Does This Protocol Apply?
A kill event occurs when ANY of the following conditions fire during the pipeline:
| Kill Condition | Phase | Trigger |
|---|---|---|
| No viable market opportunity found | Phase 1 | Sarah's research shows saturated market or no demand signal |
| Operator rejects all concepts | Gate 1 | Operator responds with rejection or redirect |
| Board issues NO-GO | Phase 2 | Victor calls NO-GO in the boardroom |
| Operator rejects design direction | Gate 2 | Operator requests fundamental changes or kills concept |
| Roundtable verdict is KILL | Phase 4 | Board reaches consensus to abandon |
| Operator withholds green light | Gate 3 | Operator does not reply with approval |
| Incomplete or unapproved design | Phase 6 | Design spec missing required sections or Victor's GO |
---
## Kill Procedure
When a kill condition fires, Victor MUST do the following in order:
### Step 1: Declare the Kill
In the current task's discussion thread, Victor posts:
```
🛑 KILL DECISION — [Company Working Title]
Kill Condition: [Which condition fired]
Phase Reached: [Phase 1 / Gate 1 / Phase 2 / etc.]
Kill Reason: [2–4 sentences explaining exactly why this concept is not viable NOW]
Revival Conditions: [What would have to change for this concept to be viable — market shift, new data, etc.]
```
### Step 2: Archive the Artifacts
Victor does NOT delete any files. All deliverables generated during the killed pipeline are preserved in `docs/` with a `killed-` prefix if they haven't been named already:
- `docs/market-pitch-{slug}.md` → preserved as-is
- `docs/company-design-spec-{slug}.md` → preserved as-is (if it exists)
### Step 3: Update the Portfolio Ledger
Victor adds a row to the **Killed Concepts** table in `rag/portfolio.md`:
- Working title
- Industry
- Phase reached
- Kill reason (one sentence)
- Date
### Step 4: Close the Task Chain
Victor closes the task with `rag_update: true`. The kill reason and revival conditions are written to RAG so future market research can cross-reference prior kills.
---
## Reactivating a Killed Concept
A killed concept may be reactivated if:
1. An operator explicitly requests it (e.g., "revisit the healthcare concept from 3 months ago")
2. New market data emerges that invalidates the original kill reason
3. Technology shifts make a previously infeasible concept technically achievable
**Reactivation procedure:** Victor spawns a fresh `market_research` task, referencing the archived `market-pitch-{slug}.md` as prior context. The pipeline starts from Phase 1 with fresh research. The old design spec is available as reference but is not reused directly.
---
## What a Kill Is NOT
- A kill is **not a failure**. It is capital preservation.
- A kill is **not permanent**. Revival conditions must always be documented.
- A kill does **not delete** files or history. Everything is preserved in `docs/`.
Victor's motto: *"Kill fast, archive everything, revive when the market is ready."*

51
rag/portfolio.md Normal file
View File

@@ -0,0 +1,51 @@
# Crimson Leaf LLC — Company Portfolio
> **Maintained by:** Victor (CEO)
> **Updated:** After every successful bootstrap and on every quarterly review.
> **Purpose:** This is the authoritative ledger of all companies Crimson Leaf has incubated.
> Victor must update this file as part of the `close` step in `bootstrap_company`.
---
## Active Portfolio
| Company Name | Slug | Industry | Bootstrapped | Agents | Status | Revenue Model |
|---|---|---|---|---|---|---|
| *(none yet)* | — | — | — | — | — | — |
---
## Killed Concepts
> Concepts that reached Phase 2+ but were killed before bootstrap. Preserved for institutional memory.
| Working Title | Industry | Phase Killed | Kill Reason | Date |
|---|---|---|---|---|
| *(none yet)* | — | — | — | — |
---
## Portfolio Health Metrics
| Metric | Target | Current |
|---|---|---|
| Active companies | Growing | 0 |
| Avg agents per company | 5–6 | — |
| Avg time Discovery → Bootstrap | < 1 week | — |
| Companies operating 30+ days autonomously | 100% | — |
| Industries represented | Diversified | 0 |
---
## How to Update This File
After a successful **Phase 6 (bootstrap_company)**, Victor adds a row to **Active Portfolio** with:
- **Company Name** — the human-readable name from the design spec
- **Slug** — the machine-readable slug used in the Gitea repository
- **Industry** — the market vertical (e.g., "Legal AI", "E-commerce Content")
- **Bootstrapped** — ISO date (YYYY-MM-DD)
- **Agents** — count of agents hired
- **Status** — `Operational`, `Warming Up`, `Under Review`, or `Stalled`
- **Revenue Model** — one-line summary
When a company is killed at any gate (see `kill_protocol.md`), Victor adds a row to **Killed Concepts**.

4
templates/design_polish.yml
View File

@@ -29,8 +29,8 @@ steps:
DESIGN VERDICT: {design_verdict}
Victor (CEO): {peter_final}
Nolan (CTO): {david_final}
Victor (CEO): {victor_final}
Nolan (CTO): {nolan_final}
Sarah (Market Intelligence): {sarah_final}
ORIGINAL DESIGN SPECIFICATION:

8
templates/design_review.yml
View File

@@ -3,10 +3,15 @@ description: >
Independent review of a company design specification. Each board member
critiques the design from their domain expertise.
model: power
system: agent_prompt
agent_prompt:
- "= identity.md"
sections:
- agent
- project
- history
- rag
- deliverables
- message
@@ -15,8 +20,7 @@ sections:
steps:
- type: think
hint: |
You are {agent.name}.
{agent.identity}
You are {agent.name}, {agent.title}.
You are reviewing a COMPANY DESIGN SPECIFICATION produced by the Crimson Leaf boardroom.
The full design document is in the deliverables above.

18
templates/design_roundtable.yml
View File

@@ -12,9 +12,15 @@ participants:
iteration_limit: 3
convergence_signal: "CONSENSUS REACHED"
participant_prompt:
- "= identity.md"
sections:
- agent
- project
- history
- participants
- participants_prompt
- rag
- deliverables
- message
@@ -37,8 +43,8 @@ steps:
{this_agent_review}
OTHER REVIEWS:
[Victor] {peter_review}
[Nolan] {david_review}
[Victor] {victor_review}
[Nolan] {nolan_review}
[Sarah] {sarah_review}
[Elena] {elena_review}
@@ -64,8 +70,8 @@ steps:
schema:
consensus_critique: string
design_verdict: string
peter_final: string
david_final: string
victor_final: string
nolan_final: string
sarah_final: string
elena_final: string
key_changes: list
@@ -78,7 +84,7 @@ steps:
consensus_critique: "{consensus_critique}"
key_changes: "{key_changes}"
design_verdict: "{design_verdict}"
peter_final: "{peter_final}"
david_final: "{david_final}"
victor_final: "{victor_final}"
nolan_final: "{nolan_final}"
sarah_final: "{sarah_final}"
elena_final: "{elena_final}"