conclave-cc

Conclave is an agentic business orchestration framework for solo founders. It transforms founder intent into a structured, executable, VC-ready business system — before any code is written. The system operates at the business coherence layer: vision, ICP, moat, revenue, brand, and legal structure. It does not replace execution — it makes execution inevitable.

Installation

npm i conclave-cc@latest

The postinstall script copies all agents, commands, and system documents into ~/.claude/, making them available globally in every Claude Code session.

Usage

/conclave "your project intention"

The Chairman runs the full intake protocol and writes VISION.md. Then:

/ceo

The CEO reads VISION.md, applies the activation matrix, writes EXECUTION_PLAN.md, and outputs the exact command sequence to run next. Follow the CEO's instructions — run each agent command in order, then re-run /ceo after each one.

Example session:

/conclave "my project"   → Chairman writes VISION.md
/ceo                     → CEO writes EXECUTION_PLAN.md, outputs: run /cto
/cto                     → CTO writes TECH.md
/ceo                     → conflict check, outputs: run /cmo
/cmo                     → CMO writes GTM.md
/ceo                     → conflict check, outputs: run /cro
...
/ceo                     → all documents complete, system status = READY

What you get

| Document | Owner | Activation | |---|---|---| | VISION.md | Chairman | Always | | EXECUTION_PLAN.md | CEO | Always | | TECH.md | CTO | Product exists | | GTM.md | CMO | Distribution undefined | | REVENUE.md | CRO | Revenue model undefined | | COMMERCIAL.md | CLO | Legal/commercial complexity medium or high | | SECURITY.md | CISO | Security-sensitive product | | PRODUCT.md | Design CTO | UX-critical for conversion |

Agent system

• Chairman — Vision extraction. Runs the two-layer intake protocol. Writes VISION.md.
• CEO — Orchestration. Reads signals, applies activation matrix, sequences agents, resolves conflicts. Writes EXECUTION_PLAN.md.
• CTO — Technical architecture. Stack, delivery model, observability, fallback, security surface.
• CMO — Go-to-market. ICP, channel, positioning, acquisition motion.
• CRO — Revenue model. Pricing, paywall, first sale target, LTV hypothesis.
• CLO — Commercial & legal. Entity structure, IP, contracts, compliance.
• CISO — Security & trust. Threat model, trust signals, minimum security posture.
• Design CTO — Experience layer. Onboarding, conversion design, perception requirements.

Philosophy

Derivation over interrogation. Agents derive decisions from documents. They ask the founder only when ambiguity blocks a confident decision.

Document ownership. Every agent owns exactly one output document. No agent writes another agent's document.

Conditional activation. The CEO reads VISION.md signals and activates only the agents the project requires.

Deterministic output. Every agent session ends in a written document — never in reflection, summary, or open loop.

Sovereignty by inevitability. Every signal is filtered through five structural questions before being recorded as a decision. Signals that fail the filter become unresolved hypotheses — not closed decisions.

MVP scope

This release includes Chairman, CEO, CTO, CMO, CRO, CLO, CISO, and Design CTO. CFO and full financial modeling (FINANCE.md) are planned for the next release (post-MVP, funding intent only).