Blog writing operations: concrete drafts, diagnosis, comment strategy, external sources, and recurring gotchas.
사용자 요청을 Blog, Luna, Darwin, Sigma, Ska, Hub/Orchestrator 등 적절한 팀과 런타임으로 라우팅할 때 사용.
Use for non-trivial production code changes that require expert challenge and consensus, test-first implementation, soft and read-only hard verification, runtime and DB consistency checks, refactoring discipline, and an independent code-review gate.
Use when diagnosing or improving Luna investment-team autonomous operation bottlenecks, especially the 30-minute Codex automation loop, live-fire watchdog issues, LLM hot-path overuse, discovery funnel stalls, marketdata connectivity, reconcile blockers, or safe fix planning.
Hub routing, resilience, alarm lifecycle, and Sigma feedback operations.
Darwin research cycle operations: cycle overview, predicate authoring, adopt review, and recurring gotchas.
Archived n8n workflow operations guidance kept for historical reference; do not use for new active routing.
작업 완료 전 Karpathy 원칙 기반으로 가정, 단순성, 변경 범위, 목표 충족 여부를 자체 검증할 때 사용.