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

feat: 3 operator approval gates (WaitingForHuman) in incubation pipeline

Browse Source 
Gate 1: After market_research — operator selects business concept
Gate 2: After company_design — operator approves design before review cycle
Gate 3: After design_polish — operator green lights bootstrap (company creation)

Each gate is a human_action task (status: WaitingForHuman) that blocks
downstream tasks via depends_on. Operator resolves naturally via Discord.
Pipeline SOP updated with gate diagram and expanded kill conditions.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
David Baity
2026-03-01 01:13:18 -05:00
parent 63e715d570
commit fc0260bba3
4 changed files with 101 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

44
pipelines/incubation_protocol.md
View File

@@ -6,7 +6,7 @@
---
## The Six-Phase Incubation Pipeline
## The Six-Phase Incubation Pipeline (with 3 Operator Gates)
When Crimson Leaf receives a prompt in `#general` to explore a new industry or business opportunity, Peter MUST spawn tasks in this exact sequence:
@@ -19,21 +19,37 @@ When Crimson Leaf receives a prompt in `#general` to explore a new industry or b
| Output | `market-pitch-{slug}.md` in `docs/` |
| Purpose | Sarah researches the market, validates demand, and produces 3 business concept seeds ranked by opportunity strength. |
### 🛑 Gate 1: Operator Selects Concept
| Field | Value |
|-------|-------|
| Task Type | `human_action` |
| Status | `WaitingForHuman` |
| Purpose | Operator reviews the market pitch in Discord, selects which concept to pursue. Pipeline PAUSES here until operator responds. |
| Resolution | Operator replies naturally: "Go with concept #2" or "None of these, try healthcare instead" |
### Phase 2: Board Alignment
| Field | Value |
|-------|-------|
| Task Type | `company_design` |
| Assigned To | Peter (chairs boardroom) |
| Depends On | Phase 1 (market_research) |
| Depends On | Gate 1 (operator concept selection) |
| 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. |
| Purpose | The full board (Peter, David, Sarah, Elena) debates the selected concept and produces a complete Company Design Specification. |
### 🛑 Gate 2: Operator Approves Design Direction
| Field | Value |
|-------|-------|
| Task Type | `human_action` |
| Status | `WaitingForHuman` |
| Purpose | Operator reviews the design spec in Discord. Confirms the vision aligns before the review cycle burns compute. Pipeline PAUSES here. |
| Resolution | Operator replies: "Looks good, proceed" or "Change the revenue model to subscription" |
### 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) |
| Depends On | Gate 2 (operator design approval) |
| 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. |
@@ -60,7 +76,7 @@ When Crimson Leaf receives a prompt in `#general` to explore a new industry or b
|-------|-------|
| Task Type | `bootstrap_company` |
| Assigned To | David |
| Depends On | Phase 5 (design_polish) |
| Depends On | Gate 3 (operator green light) |
| 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. |
@@ -72,7 +88,13 @@ When Crimson Leaf receives a prompt in `#general` to explore a new industry or b
Phase 1: market_research (Sarah)
│
▼
🛑 Gate 1: Operator selects concept (WaitingForHuman)
│
▼
Phase 2: company_design (Boardroom: all 4)
│
▼
🛑 Gate 2: Operator approves design (WaitingForHuman)
│
├──► Phase 3a: design_review (Peter)
├──► Phase 3b: design_review (David)
@@ -86,6 +108,9 @@ Phase 2: company_design (Boardroom: all 4)
Phase 5: design_polish (Elena)
│
▼
🛑 Gate 3: Operator green lights bootstrap (WaitingForHuman)
│
▼
Phase 6: bootstrap_company (David)
```
@@ -95,9 +120,12 @@ Phase 2: company_design (Boardroom: all 4)
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.
2. **Gate 1:** Operator rejects all concepts or redirects to a different industry.
3. **Phase 2:** Peter issues a NO-GO during the boardroom.
4. **Gate 2:** Operator rejects the design direction or requests fundamental changes.
5. **Phase 4:** The roundtable verdict is KILL (not GO).
6. **Gate 3:** Operator withholds green light (the company is never created).
7. **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.