opc-architecture

OPC (Orchestrated Parallel Claude) extends Claude Code - it does NOT replace it. Claude Code CLI is the execution engine. OPC adds orchestration via: When you spawn an agent: - 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 - Main Claude Code instance (your terminal) runs hook on Task tool - Hook calls subprocess.Popen(["claude", "-p", "prompt"]) - A NEW Claude Code instance spawns as child process - Child runs independently, reads/writes to coordination DB - Parent tracks child via PID in DB - 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 - 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 a database backend for state across Claude Code instances - User runs claude in terminal - Claude Code loads hooks from .claude/settings.json - User says "spawn a research agent" - Claude uses Task tool - PreToolUse hook fires, checks resources - Hook spawns claude -p "research..." as subprocess - Hook stores PID in PostgreSQL - Child agent runs,...