# Crimson Leaf — Incubation Protocol (SOP)

> **Read by:** Peter (CEO)
> **Purpose:** Defines the exact task sequence for incubating a new company.
> **Rule:** Peter MUST follow this sequence using `insert_children: true`. No shortcuts.

---

## The Six-Phase Incubation Pipeline

When Crimson Leaf receives a prompt in `#general` to explore a new industry or business opportunity, Peter MUST spawn tasks in this exact sequence:

### Phase 1: Discovery
| Field | Value |
|-------|-------|
| Task Type | `market_research` |
| Assigned To | Sarah |
| Depends On | — (starts immediately) |
| Output | `market-pitch-{slug}.md` in `docs/` |
| Purpose | Sarah researches the market, validates demand, and produces 3 business concept seeds ranked by opportunity strength. |

### Phase 2: Board Alignment
| Field | Value |
|-------|-------|
| Task Type | `company_design` |
| Assigned To | Peter (chairs boardroom) |
| Depends On | Phase 1 (market_research) |
| Output | `company-design-spec-{slug}.md` in `docs/` |
| Purpose | The full board (Peter, David, Sarah, Elena) debates the market pitch and produces a complete Company Design Specification. |

### Phase 3: Independent Review
| Field | Value |
|-------|-------|
| Task Type | `design_review` |
| Assigned To | Peter, David, Sarah, Elena (4 parallel tasks) |
| Depends On | Phase 2 (company_design) |
| Output | Discussion replies (structured reviews) |
| Purpose | Each board member independently critiques the design from their domain expertise: market fit, technical feasibility, operational completeness, and financial viability. |

### Phase 4: Review Roundtable
| Field | Value |
|-------|-------|
| Task Type | `design_roundtable` |
| Assigned To | Peter, David, Sarah, Elena |
| Depends On | Phase 3 (all 4 design_review tasks) |
| Output | Consensus critique + key changes list |
| Purpose | The board debates the reviews, resolves disagreements, and produces a unified list of required changes. Final verdict: GO or KILL. |

### Phase 5: Design Polish
| Field | Value |
|-------|-------|
| Task Type | `design_polish` |
| Assigned To | Elena |
| Depends On | Phase 4 (design_roundtable) |
| Output | `company-design-final-{slug}.md` in `docs/` |
| Purpose | Elena incorporates all board-approved changes into the final, bootstrap-ready design specification. |

### Phase 6: Bootstrap
| Field | Value |
|-------|-------|
| Task Type | `bootstrap_company` |
| Assigned To | David |
| Depends On | Phase 5 (design_polish) |
| Output | System creation payloads (company + agents + templates) |
| Purpose | David converts the approved design into API payloads. The system creates the Gitea repo, hires agents, procures templates, and deploys the new company. |

---

## Pipeline Dependency Chain

```
Phase 1: market_research (Sarah)
    │
    ▼
Phase 2: company_design (Boardroom: all 4)
    │
    ├──► Phase 3a: design_review (Peter)
    ├──► Phase 3b: design_review (David)
    ├──► Phase 3c: design_review (Sarah)
    └──► Phase 3d: design_review (Elena)
              │ (all 4 must complete)
              ▼
         Phase 4: design_roundtable (all 4)
              │
              ▼
         Phase 5: design_polish (Elena)
              │
              ▼
         Phase 6: bootstrap_company (David)
```

---

## Kill Conditions

The pipeline STOPS and the company is NOT created if:
1. **Phase 1:** Sarah's research shows no viable market opportunity.
2. **Phase 2:** Peter issues a NO-GO during the boardroom.
3. **Phase 4:** The roundtable verdict is KILL (not GO).
4. **Phase 6:** The design specification is incomplete or missing Peter's approval.

In any kill scenario, Peter documents the reason in a close note and the task chain terminates.

---

## Post-Bootstrap

After Phase 6 succeeds:
1. The new company's `#general` project receives TASK-000.
2. The new company's CEO agent wakes up and begins executing its own Pipeline SOP.
3. Crimson Leaf's job is done. We do not manage the company after deployment.