Files

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

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>

2026-03-01 01:13:18 -05:00

5.2 KiB

Raw Blame History

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 (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:

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.

🛑 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	Gate 1 (operator concept selection)
Output	`company-design-spec-{slug}.md` in `docs/`
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	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.

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	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.

Pipeline Dependency Chain

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)
    ├──► 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)
              │
              ▼
    🛑 Gate 3: Operator green lights bootstrap (WaitingForHuman)
              │
              ▼
         Phase 6: bootstrap_company (David)

Kill Conditions

The pipeline STOPS and the company is NOT created if:

Phase 1: Sarah's research shows no viable market opportunity.
Gate 1: Operator rejects all concepts or redirects to a different industry.
Phase 2: Peter issues a NO-GO during the boardroom.
Gate 2: Operator rejects the design direction or requests fundamental changes.
Phase 4: The roundtable verdict is KILL (not GO).
Gate 3: Operator withholds green light (the company is never created).
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:

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

5.2 KiB Raw Blame History