control-feeder

Load rule: This file owns rewrite + route + Feed emit. Outer phases live in control-graph. EVA Inner lives in eva-emptiness. Triage modes live in agent-orchestrator. Do not paste Card, EVA DAG, or orchestrator checklists here.

// Signature
Feed     : this skill (pre-graph)
Dump     : paste | --prompt-file | --prompt-json | -p/--single | chat dump
Route    ∈ { light, cg-outer, eva-inner }
Light    : agent-orchestrator single_shot | light  — skip Card
CG       : control-graph Outer + Card
EVA      : eva-emptiness Inner only when emptiness gate fires (CG owns Outer)

// Axioms
A1  Rewrite before route — never open Card on the raw dump
A2  One home: route only; do not restate CG/EVA/orchestrator bodies
A3  Harness gap ≠ graph  — permissions / AGENTS.md / MCP / 8192 stay harness
A4  EVA never inlined; never nested grok / grok -p from a live session
A5  Emit a Feed block, then load exactly one next owner

Headless -p / --prompt-file / --prompt-json are ingress only. This skill is the rewrite-and-route step in front of them.

When to use

Steps

1. Ingest

Treat the user text (or file body) as Dump. Do not execute tools yet except to read a named --prompt-file.

2. Rewrite (word choices)

Emit a tighter goal. Rules:

Keep: named paths, verify commands, constraints, explicit non-goals.

3. Route (first match that holds)

Do not count EVA Skip rows toward the ≥2. Exact EVA fields and Inner DAG: eva-emptiness. Exact Card fields: control-graph/references/control-card.md.

4. Pick (names only)

• skills: description-trigger matches only — no catalog dump.
• tools: built-ins first (grep, read_file, search_replace, bash, …). MCP as server__tool only if Dump needs a connected server.
• technique: single_shot | light | cg-outer+standard | cg-outer+eva

5. Emit, then hand off

Print the Feed block. Then load one next owner. If cg-outer or eva-inner, copy goal / success / verify / unknowns onto a new Card — do not paste the raw Dump.

Feed (emit schema — this skill is SoT)

## Feed
| Field | Value |
|-------|--------|
| **goal** | (one rewritten sentence) |
| **dump_source** | paste \| prompt-file \| prompt-json \| -p \| chat |
| **route** | light \| cg-outer \| eva-inner |
| **why** | (one line; cite the row that matched) |
| **technique** | single_shot \| light \| cg-outer+standard \| cg-outer+eva |
| **skills** | name name … |
| **tools** | built-in and/or server__tool … |
| **success** | (observable, if known) |
| **verify** | `cmd` … or unknown |
| **non-goals** | … |
| **unknowns** | … |
| **harness_gap** | none \| permissions \| AGENTS.md \| mcp \| 8192 |
| **next** | implement \| agent-orchestrator \| control-graph \| control-graph+eva-emptiness |

Done when

• Feed block printed with rewritten goal, route, why, next
• Exactly one next owner named; Card opened only if route is cg-outer or eva-inner
• No CG/EVA bodies pasted; no nested grok

Do not

• Open a Control Card on the raw dump
• Inline EVA into control-graph or this file
• Treat harness gaps as a reason to start a graph
• Spawn a skill crowd “just in case”
• Run grok / grok -p from a live session

Related

Skills: control-graph · eva-emptiness · odysseus-navigator (judgment after Feed; hooks only) · agent-orchestrator · grok-host-prep
Plugin: eva-emptiness (Grok marketplace / ../plugins/eva-emptiness) — Inner only; never paste into this file.

Notes in grok-build intelli-arch-designs/ (why, not copies):