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 when the user calls /meta-theory, names meta-theory, asks for governance, multi-file execution, agent design, capability discovery, runtime/platform compatibility, public-ready validation, complex debugging, or durable evolution writeback.

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.