agentic-orchestration

# Agentic Orchestration (Experimental Working-Model Protocol) > **Status — experimental, instrumented, validation in progress.** This > skill is shipped to begin collecting evidence about whether a structured > verifiability-router protocol changes Claude's behavior in ways that > measurably help users. `memesh patterns` exposes a local counter so you > can see how often the banner is injected and how often > `verify_agent_work` is invoked in your real usage. None of that data > ever leaves your machine. > **The roles, suggested:** > - **User = CTO / PM.** Owns understanding, strategy, product taste, "what is worth building." > - **Claude = Orchestrator / engineering manager.** Routes work, dispatches agents, reviews diffs, surfaces decisions, never the bottleneck. > - **Background agents = engineering interns.** Execute high-verifiability technical work in parallel. The hypothesis behind this skill: Claude as a single-threaded synchronous coding partner spends a meaningful portion of the user's time on work that could run in the background. If that hypothesis holds, this skill should noticeably reduce wall-clock time on multi-step technical tasks. We do not yet have field data either way. **Announce at start:** "Using agentic-orchestration (experimental protocol) to route this work." --- ## Why this ships with memesh memesh is a local memory layer **and** a working-model activator. Three parts compose: 1. **This skill** — the protocol document. Loaded by Claude Code'...