/meta-theory

name: meta-theory
version: 3.0.0
author: KimYx0207
user-invocable: true
trigger: "元理论|执行元理论|跑元理论|meta theory|run meta theory|execute meta theory|meta-theory|agent governance|intent amplification|governance|治理|重构|多文件|跨模块|debug|fix|验证|verification"
tools:
  - shell
  - filesystem
  - browser
  - memory
description: |
  Meta_Kim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.

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. Machine contract: `config/contracts/core-loop-contract.json` is the compact default-path contract for this skill. It binds ordinary durable work and explicit meta-theory shortcuts to `npm run meta:theory:run`, requires the eight-stage spine, and defines which gates block, warn, or stay progressive. The default governed runner remains planned-only. When the maintainer explicitly supplies `--execute-stage-dag`, the P-117 bridge executes the existing `coreLoop.stageDagPacket` in read-only shadow mode through either `--stage-runner-runtime codex` or `--stage-runner-runtime claude`, with the P-118 kernel retaining durable node commits; `--resume-stage-dag` continues only the exact bound unfinished run. The ready-set executor defaults to native concurrency. `--stage-runner-orchestrator langgraph` may dynamically load an explicitly installed, currently tested `@langchain/langgraph@1.4.8` and use only its Functional API `entrypoint` plus `task`; it consumes the scheduler-selected ready set and may not define topology or persistence. Both runtimes keep the same graph, checkpoint, and local merge authority. A native terminal result proves invocation, while Review still owns semantic acceptance. Do not claim write execution, external effects, a runtime-specific graph, LangGraph checkpoint authority, or live OpenAI/Claude SDK adapters without credential-backed evidence. The process timeout is a safety fuse, never a task/token/cost budget.

Active host and shared skills

Shared `.agents/skills` bundles are host-neutral. Identify the active host before loading `references/runtime-codex.md`, `references/runtime-claude.md`, `references/runtime-gemini.md`, `references/runtime-zcode.md` or `references/runtime-dsh.md`; use the existing Cursor/OpenClaw guidance for those clients. Canonical agent paths identify responsibility sources. Native agent paths, callable tools, Hook schemas and authority come from that runtime's actual reference and inventory. Never run another host's tool/schema examples verbatim. A generated projection is separate from native invocation evidence. DSH loads the canonical roles as native Skills and inherits the current host preset for actual delegation; a Skill name is not a registered custom-agent preset. Read all method parts and relevant resources before execution, and keep file loading, MCP observations, native delegation and final outcome evidence distinct.

For substantial software delivery, load [intent to delivery](references/intent-to-delivery.md): architecture exploration precedes the detailed module view of the same PRD; actual professional knowledge travels with selected methods; source navigation supports evidence-based cleanup. Reuse current decisions and continue the returned host action until a material user choice or real blocker requires a pause. Do not ask the user to select internal roles or manufacture a second plan.

Global-First Owner Discovery

Discovery is **global-first, capability-first**: not project-local, not agent-name-first. Start with first-party capability search (`meta:capability:search`) over the existing indexes, then inspect relevant local canonical assets, global runtime homes, package scripts and MCP / runtime configs or use `meta-scout` investigation as the current gap requires. Follow the cached-inventory, project-light, stop-on-match policy in `config/contracts/core-loop-contract.json`; use `findskill` only when installed and appropriate, without requiring a full scan or external call by default. A reusable global owner that already matches the boundary wins over creating a project-local copy. Full source-by-source guidance lives in `references/global-owner-discovery.md`; it must not override the machine contract's stage order, full-scan triggers, or stage-internal parallel policy.

The dispatcher (main thread or `meta-conductor`) is the **single merge owner** of `dispatchEnvelopePacket.capabilityInventory`. Fetch may discover independent sources concurrently after Critical has closed its intent merge, but the inventory is merged once before Thinking closes the route. This is a main-flow step, not a hook. The inventory records which relevant sources were actually scanned, which owners were considered, why one was selected, and why any route-relevant source was skipped. Discovery without a recorded inventory is fake discovery and is rejected by Review on the same chain, not by a separate gate.

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.

At run start, show a concise human-readable reason for the route. If the 8-stage spine triggers, say briefly why governan