2.1 Company Overview Virtual Companies Virtual companies are specialized AI agent teams . Each company has: A SOUL (identity, values, expertise description) A config (domain, model preferences, agent roles) Blueprints (templates for how to build things) Agents (lead, builder, reviewer — each with model assignments) Active Companies Company Type Domain Pipeline Role CodeCraft Dev Shop Backend, APIs, databases, full-stack BUILD (backend) Vizu Agency Frontend, UI/UX, design, components BUILD (frontend) Datavera Product Co. Data engineering, analytics, ML, reporting BUILD (data) Proveo Audit Firm QA, testing, code review, validation REVIEW Securion Consultancy Security auditing, pen testing, threat modeling SECURITY FlowForge Consultancy DevOps, infra, CI/CD, deployment OPS Lexicon Consultancy Legal docs, compliance, GDPR, ToS DOCS / LEGAL AgentForge AI Lab Agent development, AI tooling, model fine-tuning R&D Merged / Archived Companies Company Merged Into Reason Skybound CodeCraft Overlap with backend dev Proxima Vizu Overlap with frontend Skillforge FlowForge Overlap with DevOps HelixSupport FlowForge Overlap with ops Finverge Lexicon Overlap with compliance Company File Structure ~/companies/CodeCraft/ ├── company.json — Registration (name, type, org number) ├── config.json — Domain, models, agent definitions ├── CLAUDE.md — Soul/instructions for AI agents working as this company ├── README.md — Company description ├── agents/ — Agent-specific prompts and configs ├── blueprints/ — Project templates (nextjs-app.yaml, api-backend.yaml) ├── logs/ — Execution logs └── state/ — Current work state Routing: Which Company Gets the Task? The pi-orchestrator classifies each task and routes it: Task title/description │ ▼ Keyword matching (routing.json) │ ├── "frontend", "UI", "react" → Vizu ├── "data", "analytics", "ML" → Datavera ├── "security", "audit", "CVE" → Securion ├── "deploy", "CI/CD", "infra" → FlowForge ├── "legal", "GDPR", "ToS" → Lexicon └── default (backend, API, etc.) → CodeCraft