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

Cleaned

Browse Source
This commit is contained in:
David Baity
2026-03-09 22:15:10 -04:00
parent c3a4d2f6f9
commit a07a372093
26 changed files with 0 additions and 1283 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
rag/business_plan.md
View File

@@ -1,32 +0,0 @@
# 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 (Victor, Nolan, Sarah, Elena) debates the opportunity in a structured boardroom. Elena designs the operations. Nolan specifies the technology. Victor 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).

18
rag/core_directives.md
View File

@@ -1,18 +0,0 @@
# 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. Victor'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.

51
rag/portfolio.md
View File

@@ -1,51 +0,0 @@
# Crimson Leaf LLC — Company Portfolio
> **Maintained by:** Victor (CEO)
> **Updated:** After every successful bootstrap and on every quarterly review.
> **Purpose:** This is the authoritative ledger of all companies Crimson Leaf has incubated.
> Victor must update this file as part of the `close` step in `bootstrap_company`.
---
## Active Portfolio
| Company Name | Slug | Industry | Bootstrapped | Agents | Status | Revenue Model |
|---|---|---|---|---|---|---|
| *(none yet)* | — | — | — | — | — | — |
---
## Killed Concepts
> Concepts that reached Phase 2+ but were killed before bootstrap. Preserved for institutional memory.
| Working Title | Industry | Phase Killed | Kill Reason | Date |
|---|---|---|---|---|
| *(none yet)* | — | — | — | — |
---
## Portfolio Health Metrics
| Metric | Target | Current |
|---|---|---|
| Active companies | Growing | 0 |
| Avg agents per company | 5–6 | — |
| Avg time Discovery → Bootstrap | < 1 week | — |
| Companies operating 30+ days autonomously | 100% | — |
| Industries represented | Diversified | 0 |
---
## How to Update This File
After a successful **Phase 6 (bootstrap_company)**, Victor adds a row to **Active Portfolio** with:
- **Company Name** — the human-readable name from the design spec
- **Slug** — the machine-readable slug used in the Gitea repository
- **Industry** — the market vertical (e.g., "Legal AI", "E-commerce Content")
- **Bootstrapped** — ISO date (YYYY-MM-DD)
- **Agents** — count of agents hired
- **Status** — `Operational`, `Warming Up`, `Under Review`, or `Stalled`
- **Revenue Model** — one-line summary
When a company is killed at any gate (see `kill_protocol.md`), Victor adds a row to **Killed Concepts**.