meta-theory

# Meta-Theory Dispatcher ## Purpose Run Meta_Kim as an executable governance system, not a theory essay. The main thread locks intent, gathers evidence, chooses route, delegates bounded work, reviews, verifies, and synthesizes. It must not become a generic implementation worker for non-trivial work. ## Trigger Activate from ordinary natural-language durable work, not only from command words. If the user asks to plan and start work, organize priorities, produce repair suggestions, build a verification checklist, fix a non-trivial issue, handle multi-file execution, run review/verification, or resolve subjective/taste-dependent quality, classify the entry and choose the governed route automatically. Explicit `/meta-theory`, `meta-theory`, or `元理论` mentions are maintainer shortcuts, not required human behavior. ## Path classification - `fast_path`: read-only query, no mutation, no durable artifact. Output may be direct, but evidence claims still need source. - `standard_path`: ordinary executable work. Use the 8-stage spine and capability-first route. - `regulated_path`: governance, security, runtime, dependency, release, public-ready, or cross-platform work. Require full spine, Review, Meta-Review, Verification, and Evolution. ## Canonical spine Critical -> Fetch -> Thinking -> Execution -> Review -> Meta-Review -> Verification -> Evolution. You are the DISPATCHER, not the executor. Use Agent tool / `Agent(...)` dispatch only after Fetch evidence and Thinking owner resolut...