opc-architecturelisted

# OPC Architecture Understanding OPC (Orchestrated Parallel Claude) extends Claude Code - it does NOT replace it. ## Core Concept Claude Code CLI is the execution engine. OPC adds orchestration via: - **Hooks** - Intercept Claude Code events (PreToolUse, PostToolUse, SessionStart, etc.) - **Skills** - Load prompts into Claude Code - **Scripts** - Called by hooks/skills for coordination - **Database** - Store state between Claude Code instances ## How Agents Work When you spawn an agent: 1. Main Claude Code instance (your terminal) runs hook on Task tool 2. Hook calls `subprocess.Popen(["claude", "-p", "prompt"])` 3. A NEW Claude Code instance spawns as child process 4. Child runs independently, reads/writes to coordination DB 5. Parent tracks child via PID in DB ``` $ claude ← Main Claude Code (your terminal) ↓ Task tool triggers hook ↓ subprocess.Popen(["claude", "-p", "..."]) ├── claude -p "research..." ← Child agent 1 ├── claude -p "implement..." ← Child agent 2 └── claude -p "test..." ← Child agent 3 ``` ## What OPC Is NOT - OPC is NOT a separate application - OPC does NOT run without Claude Code - OPC does NOT intercept Claude API calls directly - OPC does NOT modify Claude Code's internal behavior ## What OPC IS - OPC IS hooks that Claude Code loads from `.claude/hooks/` - OPC IS skills that Claude Code loads from `.claude/skills/` - OPC IS scripts that hooks/skills call for coordination - OPC IS