172ce3a0e1
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>
1.6 KiB
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.