ecc-haiku-dispatch

Dispatch L2 atomic instincts to independent cheap-model agents via a JSON contract.

10|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill ecc-haiku-dispatch-cynthia1070711
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecc-haiku-dispatch
Source: https://github.com/Cynthia1070711/PHYCOOL_Tools/tree/main/config-templates/claude/skills/ecc-haiku-dispatch
Command: npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill ecc-haiku-dispatch-cynthia1070711

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Running small, repetitive governance actions (atomic instincts) inside the main Opus conversation window pollutes its token budget and context. This Skill routes those instinct dispatches to an independent cheap-model agent (Gemini-backed by default, Haiku optional) behind a frozen JSON contract, keeping the main window clean. ## Core Features & Use Cases - Contract-first dispatch: A frozen JSON schema (instinct-dispatch.schema.json) defines the InstinctDispatchInput/Output contract that all 10 L2 atomic instincts must follow before any implementation. - Tri-mode dispatch engine: Route dispatches via the PHYCOOL_DISPATCH_ENGINE environment variable to gemini (default), haiku (claude-haiku-4-5 subprocess), or mock (zero-token testing). - State tracking and evaluation gate: Every dispatch writes a state_diff to .context-db/ecc-state/ and appends to dispatch_log.json; the ecc-haiku-eval.cjs script computes success rate, latency, and token cost against the D4 quality gate. - Use Case: Before implementing an instinct dispatch story, read the contract schema and IInstinctDispatcher module, then call Invoke-InstinctDispatch with an instinct name and payload to get a schema-valid result plus state diff without consuming main-window tokens. ## Quick Start Ask the AI to dispatch the skill_invocation instinct with a trigger context and rule reference using the ecc-haiku-dispatch contract, then verify the returned status and state_diff.

Frequently Asked Questions about ecc-haiku-dispatch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I dispatch an L2 atomic instinct with the IInstinctDispatcher contract?

Import the IInstinctDispatcher.psm1 module and call Invoke-InstinctDispatch with an instinct name and a payload containing trigger_context and rule_reference. The result follows the InstinctDispatchOutput schema with status, result, state_diff, timestamp, and evidence fields.

What dispatch engines does the instinct dispatcher support?

Three engines are routed by the PHYCOOL_DISPATCH_ENGINE environment variable: gemini (default, via gemini-dispatcher.cjs and the Gemini REST API), haiku (claude-haiku-4-5 subprocess), and mock (in-process canned output for zero-token testing).

Can I run multiple instinct dispatches in parallel?

No. Iron Law #2 mandates one dispatch call at a time, sequentially. Each instinct executes as an independent atomic call, and its result plus state_diff must be written back before the next dispatch begins.

Why does the dispatcher use Gemini instead of running in the main Claude window?

The D2 design decision requires an independent cheap model so the Opus main window never executes dispatch logic inline, avoiding token pollution. Gemini became the default after claude -p headless started counting against a separate quota.

How is dispatch quality evaluated against the D4 gate?

Run ecc-haiku-eval.cjs to compute success rate, average and p95 latency, and average token count from dispatch_log.json. The gate passes when the current engine has at least 5 samples and a success rate of 90 percent or higher.