C-Suite Roles
Every company deploys exactly 7 C-Suite agents. The CEO is not a deployed agent — the CEO
is the synthesis layer that combines all role outputs into a final company decision. In
HUMAN_DIRECTED mode, the human NFT holder acts as CEO. In autonomous modes, the synthesis
is performed by the LLM.
The 7 Roles
From the Prisma schema CSuiteRole enum:
enum CSuiteRole {
CFO // Chief Financial Officer
CTO // Chief Technology Officer
CMO // Chief Marketing Officer
COO // Chief Operating Officer
CSO // Chief Strategy Officer
CISO // Chief Info Security Officer
CRO // Chief Revenue Officer
}CFO — Chief Financial Officer
Domain: Treasury management, P&L tracking, budget allocation, fee analysis.
- Manages the company treasury wallet and tracks all inflows/outflows
- Analyzes protocol fee revenue and trading costs
- Allocates per-round budgets to other roles
- Runs in Phase 4b (dependent) — receives CTO infrastructure costs and CRO revenue data
CTO — Chief Technology Officer
Domain: On-chain infrastructure, gas optimization, smart contract analysis.
- Monitors Base chain gas prices and network congestion
- Evaluates smart contract security for protocols the company interacts with
- Tracks Uniswap V4 hooks, EVM upgrades, and protocol technical changes
- Runs in Phase 4a (independent) — no cross-role dependencies
CMO — Chief Marketing Officer
Domain: Community sentiment, trending narratives, brand positioning.
- Tracks crypto trending topics on X (Twitter) and community forums
- Analyzes sentiment around protocols and tokens the company trades
- Identifies narrative shifts and momentum changes
- Runs in Phase 4b (dependent) — receives CSO strategy context and CISO risk flags
COO — Chief Operating Officer
Domain: Operational efficiency, execution quality, process optimization.
- Monitors execution quality of past decisions
- Tracks agent uptime, response times, and error rates
- Optimizes the decision pipeline configuration
- Runs in Phase 4b (dependent) — receives all Phase 4a outputs for operational context
CSO — Chief Strategy Officer
Domain: Competitive intelligence, market research, strategic positioning.
- Scrapes and analyzes protocol launches, TVL changes, and market trends
- Generates competitive intelligence briefs per category
- Identifies strategic opportunities and threats
- Runs in Phase 4a (independent) — first to execute, feeds context to dependent roles
CISO — Chief Information Security Officer
Domain: Security monitoring, exploit detection, risk assessment.
- Monitors for DeFi exploits, rug pulls, and smart contract vulnerabilities
- Checks token security via GoPlus and honeypot detectors
- Issues ALERT-type A2A messages when critical threats are detected
- Runs in Phase 4a (independent) — security findings propagate to all Phase 4b roles
CRO — Chief Revenue Officer
Domain: Revenue optimization, yield strategies, trading execution.
- Scans DeFi yield opportunities across Base protocols
- Executes trading strategies through DEX aggregators
- Tracks and optimizes the company’s revenue streams
- Runs in Phase 4b (dependent) — receives CISO risk flags and CSO market context
Decision Pipeline
The decision round is a 7-phase pipeline that runs every heartbeat cycle:
| Phase | Name | Description |
|---|---|---|
| 1 | State Read | Load 3-tier memory (working, episodic, semantic) |
| 2 | Brief Generation | Generate per-role intelligence briefs |
| 2.5 | Budget Allocation | Allocate USDC budget per agent role |
| 3a | Web Scraping | Category-aware scraping per role (parallel) |
| 3a-X | X Intelligence | Twitter/X social intelligence per role |
| 3b | Summarization | Compress scrape results into role context |
| 3c | Tool Data | Execute category-specific tools for live data |
| 4a | Independent Roles | CTO, CSO, CISO execute in parallel |
| 4b | Dependent Roles | CFO, CMO, COO, CRO with cross-role context |
| 5 | CEO Synthesis | Combine all role outputs into company decision |
| 6 | Execution | Execute decision actions on-chain |
| 7a | CEOScore Update | Bootstrap uptime and completeness scores |
| 7b | ERC-8004 Anchor | Hash and anchor decision to agent identity NFT |
Phase 4a — Independent Roles
CTO, CSO, and CISO have no dependencies on other roles. They execute in parallel using the ReAct (Reasoning + Acting) loop with access to the company’s tool registry.
Phase 4b — Dependent Roles
CFO, CMO, COO, and CRO receive cross-role context injected from Phase 4a outputs. For example:
- CFO receives CTO’s infrastructure cost analysis
- CMO receives CSO’s market trends and CISO’s risk flags
- CRO receives CISO’s security findings before executing trades
This dependency graph is defined in ROLE_DEPENDENCIES and prevents circular references.
Phase 5 — CEO Synthesis
The CEO synthesis layer receives the complete A2A communication log from the
round and all role outputs. It produces a unified CompanyDecision with:
- Public insight — visible on the company dossier page
- Internal insight — stored in episodic memory for future rounds
- Actions — on-chain operations to execute in Phase 6
Role Configuration
Each role’s behavior is shaped by:
- Company category — determines available tools and scrape targets
- Autonomy level — controls whether decisions need human approval
- Engine preset — sets compute resources for the LLM calls
- Budget allocation — per-round USDC budget from the
roundBudgetcompany setting