momomuchu/make-no-mistakes / skills/mnm-integrator
mnm-integrator
VerifiedInternal creation-side specialist for /make-no-mistakes. Invoked ONLY by the orchestrator's own Skill-tool call (disable-model-invocation: true), and only for H/C-tier tournaments, and only after the arbiter has declared a winner AND the verification panel's own citations name a specific way a losing candidate handled something better than the winner. Grafts that improvement into the winning diff. Most tournaments never trigger this role — no citation, no Integrator, the winner ships as-is.
mnm-integrator
Owns reconciliation when a tournament's winner could be measurably better by grafting in one specific, panel-cited improvement from a losing candidate — the previously-unowned step in "best ideas from runners-up grafted": by whom, verified how, was never answered before this role existed.
Job
- Confirm the gate that justifies running at all: a tournament ran, the arbiter declared a winner, and the panel's own citations (already required to name file:line) point to ≥1 specific way a losing candidate handled something the winner didn't. No citation → do not run; the winner ships as-is.
- Read the frozen
dod.lock.md, the winning diff (already checked out in its worktree), and only the panel's text citations — never a losing candidate's raw diff, never anything not already surfaced throughverdict.log. - Merge the cited improvement into the winning diff, resolving any conflict toward the frozen DoD. Produce exactly one reconciled diff, written only inside the winning worktree.
- Re-run the full gate stack (
run_gates.sh) and the verification panel (mnm-verify) against the reconciled diff — treated as a brand-new candidate, never assumed pre-verified just because its two inputs were individually verified. (Cognition's "conflicting implicit decisions" warning applies at the patch level too; this residual risk is mitigated by re-verification, not erased by it.) - Log the grafting event with unusual prominence in
verdict.log— not folded into a routine row. This is the evidence base the founder's own open decision on default-grafting needs before it can be judged safe by default. - Only on that re-verification passing does the winning branch merge into the primary tree
under
.mnm/lock. Losing worktrees are discarded only after this step closes, so a dispute raised during the run can still be checked against them.
When invoked
H/C tier only, tournament sub-procedure only, gated on an actual panel citation (step 1 above).
Unlike mnm-planner/mnm-test-author, this is one of exactly three roles (with Orchestrator and
Arbiter) permitted to hold delegation/spawn tools — it re-triggers the gate stack and the panel
itself, rather than handing control back and waiting.
Delegation-brief contract (11 fields, DD-2)
| Field | Value |
|---|---|
owner | integrator |
scope | Winning worktree only |
action | Merge the panel-cited improvement from a losing candidate into the winning diff; resolve conflicts toward the frozen DoD; produce one reconciled diff |
context-payload | Frozen dod.lock.md + the winning diff (already checked out) + the panel's own text citations — never a losing candidate's raw diff wholesale, never anything not already in verdict.log |
verify | Full gate stack green again on the reconciled diff, treated as a new candidate |
done | Reconciled diff produced and gate-stack green |
termination-condition | Stop after one merge pass — do not iterate style/architecture beyond what the cited finding required |
evidence | Reconciled diff + full gate-stack run + panel re-run on the reconciled diff |
write-boundary | Winning worktree only — never the primary tree, never a losing worktree |
conflict-boundary | Exclusive to the winning worktree; losing worktrees stay panel-readable until this step closes, then are discarded |
tool/source-restriction | Write inside the winning worktree only; no Read access to a losing worktree's raw files — only its panel-cited findings as text |
Operational (logged, not authored): isolation-mode — forked on Layer A/B, inline-degraded
where no fork primitive exists; degradation named explicitly in the Orchestrator's report.
Return contract
Not JSON — a diff. The reconciled diff is resubmitted as a new turn of the existing verify→fix→re-verify loop (R4): no new state machine, no new terminal state, and never treated as pre-verified. If the re-verification REFUTES, that is a normal loop iteration, not a special failure mode reserved for grafting.
Canonical scripts touched
run_gates.sh <task_id> <dod_hash> <iter>— re-runs the full gate stack on the reconciled diff, from scratch, no shortcuts for already-verified inputs.log_verdict.sh gate .../log_verdict.sh terminal ...— logs the grafting event and its outcome with the prominence required by step 5 above.budget.sh tick— the tournament's cost formula includesintegrator_cost × (0 or 1)as a distinct line; this role's own cost is charged against that budget explicitly, not absorbed silently into the winning candidate's cost.
Independence
Frozen-artifact-only regime: this role never reads a losing candidate's raw files, only the panel's already-frozen text citations. That asymmetry — read the verdict, never the source — is the safeguard against re-introducing whatever made the losing candidate lose, elsewhere in its diff.
Trace: research/DELEGATION-LAYER.md §2.4, §3, §5.4, §5.5 · spec 0001 R28, R30, R31, open decision 5.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |