feat(50c): Crimson Leaf company factory — agents, templates, RAG, pipeline

Agents: Peter (CEO), David (CTO), Sarah (Market Intel), Elena (Ops Architect)
Templates: market_research, company_design, design_review, design_roundtable, design_polish, bootstrap_company
RAG: business_plan.md, core_directives.md (5 immutable directives)
Pipeline: 6-phase incubation protocol with dependency chain and kill conditions

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

rag/business_plan.md

@@ -0,0 +1,32 @@
+# Crimson Leaf LLC — Business Plan
+
+## Mission Statement
+Crimson Leaf is the Genesis Node of the PAE ecosystem. Our sole purpose is to research market inefficiencies, design hyper-specialized autonomous business units (Tenants) to exploit them, and deploy them with perfect standard operating procedures.
+
+## What We Do
+We manufacture companies. A successful Crimson Leaf product is a fully scaffolded autonomous business unit with:
+- Its own CEO agent and 3–7 specialized staff agents
+- A complete set of procured templates matched to its workflow
+- A documented Pipeline SOP defining the exact execution sequence
+- A populated RAG knowledge base with its business plan and directives
+- Discord channels for communication and live-feed monitoring
+
+## What We Do NOT Do
+- We do not execute client work ourselves.
+- We do not write books, articles, code, or any end-product.
+- We do not manage the companies we create after deployment.
+- We are the factory, not the assembly line.
+
+## Strategy
+1. **Discovery:** Sarah uses web search and analysis to identify profitable, underserved niches where autonomous AI agents can deliver value.
+2. **Design:** The full board (Peter, David, Sarah, Elena) debates the opportunity in a structured boardroom. Elena designs the operations. David specifies the technology. Peter makes the Go/No-Go call.
+3. **Review:** Each board member independently reviews the company design specification, identifying risks, gaps, and improvements.
+4. **Alignment:** The board reconvenes in a roundtable to debate the reviews and reach consensus on the final design.
+5. **Polish:** The design specification is refined based on review feedback.
+6. **Bootstrap:** The approved design is packaged into API payloads that create the company, hire its agents, and procure its templates — all automatically.
+
+## Success Metrics
+- **Deployment Rate:** Number of companies successfully bootstrapped per quarter.
+- **Self-Sufficiency Score:** Percentage of spawned companies that operate without manual intervention for 30+ days.
+- **Revenue Diversity:** Number of distinct industries represented in the portfolio.
+- **Operational Efficiency:** Average number of agents per company (target: 5–6).

rag/core_directives.md

@@ -0,0 +1,18 @@
+# Crimson Leaf LLC — Core Directives
+
+These directives are immutable. They govern every decision Crimson Leaf makes.
+
+## Directive 1: Efficiency
+Never design a company with more than 8 agents. The sweet spot is 5–6. Every agent must have a clear, non-overlapping role. If two agents could be merged without losing capability, they must be merged.
+
+## Directive 2: Sovereignty
+Every spawned company must be 100% self-contained within its own Gitea repository. At runtime, a company's workers look ONLY inside their own tenant folder for templates, agents, and RAG data. If a resource is missing, the worker throws a hard exception — it does not fall back to global. All resources must be explicitly procured during bootstrap.
+
+## Directive 3: Standardization
+Every new company MUST have a documented Pipeline SOP before bootstrap. The pipeline defines the exact sequence of task types, agent assignments, and dependencies that govern the company's operations from intake to deliverable. No company ships without a pipeline.
+
+## Directive 4: Quality Gates
+Every company design must pass through independent review before bootstrap. The board reviews the design specification, debates it in a roundtable, and reaches consensus. Peter's Go/No-Go is the final gate. No company ships on enthusiasm alone.
+
+## Directive 5: Reproducibility
+Every company Crimson Leaf creates must be rebuildable from its Gitea repository alone. If the database is wiped, the Genesis Bootstrapper reconstructs Crimson Leaf. If a tenant's database record is lost, its Gitea repo contains everything needed to rebuild it. The repository IS the company.