kupo-esl-hop
ESL lifecycle hop — when the cortex routes a verification to Kupo in an ESL-enabled project (tonberry MCP available), Kupo is the CHECKER (maker≠checker, mechanically enforced) and owns the verified transition. Use when a change with acceptance_checks is routed for verification and a mcp__tonberry__* tool surface exists. Absent tonberry → run your normal verify (ESL opt-in); never hard-fail.
- License 许可
- Apache-2.0
- 所属仓库
- Rynaro/magicite
- 最近更新
- 2026-10-14
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- kupo-esl-hop
- metadata
- { "phase": "cross-cutting", "methodology": "Kupo" }
- description
- ESL lifecycle hop — when the cortex routes a verification to Kupo in an ESL-enabled project (tonberry MCP available), Kupo is the CHECKER (maker≠checker, mechanically enforced) and owns the verified transition. Use when a change with acceptance_checks is routed for verification and a mcp__tonberry__* tool surface exists. Absent tonberry → run your normal verify (ESL opt-in); never hard-fail.
03 SKILL.md 正文
ESL Lifecycle Hop — Kupo (the CHECKER)
When to use
Load this skill in an ESL-enabled project (mcp__tonberry__* tools available)
when the cortex routes a verification to you. You are the CHECKER, distinct
from the maker — maker ≠ checker is mechanically enforced (tonberry verify
check C4). You own the verified transition of the Eidolons Spec Lifecycle (ESL).
For the full lifecycle, stage definitions, and role bindings, see the nexus cortex
methodology/cortex/esl-protocol.md.
Your hop
You did not make this change — you check it. Run your normal external-verify
discipline against the change's declared acceptance_checks, then drive the
conformance gate and the transition:
- verify externally — load
skills/keep-or-kick/SKILL.md(triage the change is in scope to check) andskills/patch-verify/SKILL.md(run the NAMED external verifiers against the change'sacceptance_checksin a scratch copy). One green external signal per check, never self-critique. - conformance gate — call
mcp__tonberry__verify <change-dir> --mode <enforcement from the lock>. It runs the 6 mechanical checks C1–C6 (incl. C4 maker≠checker, which cross-checksverify.envelope.json'sfrom.eidolon != change.json.maker). - compose the verify envelope —
from.eidolon = kupo. This MUST differ fromchange.json.maker(else C4 fails by construction). Reuse your normal ECLPROPOSEcomposition (seeskills/patch-verify/SKILL.md"ECL emission"). - on pass → call
mcp__tonberry__transition --change_id <id> --to_status verified, then PROPOSEverify_pass. - on fail → ESCALATE with the last failure output. Do not edit the change to make it pass — the checker cannot make (you are not the maker).
Invariants
- You MUST NOT have been the maker.
change.json.makermust differ fromkupo; if Kupo authored this change, REFUSE the checker role and ESCALATE — maker≠checker is mechanically enforced (C4), not a courtesy. - Checker cannot make. On a failing check you ESCALATE; you never patch the change to flip it green. Editing-to-pass is exactly the maker≠checker violation the gate exists to stop.
- External-only verify. Correctness is a NAMED external verifier against the
declared
acceptance_checks— never self-critique, never LLM-judge (your P0). - Tonberry composes state; you provide the verdict. You supply the green
external signals and the verify envelope (
from.eidolon = kupo); tonberry runs C1–C6 and writes theverifiedstatus. - Graceful skip — if
mcp__tonberry__*tools are unavailable, run your normal verify and never hard-fail. ESL is opt-in; Kupo is EIIS-standalone-conformant and works without tonberry.
Looking ahead — ECL 2.1 verification attestation (Draft, not emitted)
ECL 2.1 (spec/ecl-2.1.md, Status: Draft — adoption-gated, not yet the
governing Published spec) introduces an OPTIONAL ise.verification
sub-block (§6.5.8) that names the verify-attestation seam: who re-checked an
artefact, from a fresh context, with what transcript access. ESL 1.1's C8
check (advisory, SHOULD-level) already reads this shape today, ahead of ECL
ratifying it (ESL 1.1 §5.4's documented forward-reference caveat) — a
verify.envelope.json whose ise.verification is {fresh_context: true, checker: "kupo", transcript_access: "artifact-only"} and whose checker
differs from change.json.maker satisfies C8 for the checker hop this skill
owns.
Once ECL 2.1 is cut to Published (the gate: ≥3 shipped Eidolons emitting
the ise block — recorded in spec/ecl-2.0.md §6.5.5), the verify envelope
Kupo composes in step 3 above will carry that same ise.verification
sub-block: fresh_context: true (Kupo checks from a session that did not see
the maker's generating transcript — exactly what maker≠checker already
guarantees structurally), checker: "kupo", transcript_access: "artifact-only" (Kupo reads only the emitted change artefact, never the
maker's transcript). This is documentation of a pending shape, not current
emission — ECL_VERSION stays 2.0 until 2.1 is cut (§7.3 of the draft),
and this skill does not emit ise.verification today. When 2.1 publishes,
wire the field into step 3's envelope composition and re-point this note at
the shipped spec section.
ESL Lifecycle Hop — Kupo (the CHECKER, maker≠checker mechanically enforced)
04 同仓库更多 Skills
wine-dxvk-cache-clear
Clear a stale DXVK shader cache that is causing graphical corruption in a Wine or Proton game. Use when: a game shows corrupted textures or shader flicker that started after a driver or DXVK version change.
steam-download-region-fix
Fix a Steam client stuck at very low download speed by changing its download region. Use when: Steam downloads are far below the local internet speed for every game, not just one.
proton-battleye-eac-toggle
Toggle BattlEye or Easy Anti-Cheat runtime support for a Steam Proton game. Use when: a multiplayer game refuses to launch with an anti-cheat error under Proton.
vivi-verify-incoming
Load when reading any upstream artefact handed off to Vivi that carries a sibling .envelope.json. BLOCKING per ECL §6.2.2: the orchestrator MUST have verified the envelope's SHA-256 (eidolons verify-envelope --block / eidolons run --verify) and recorded a verify_pass before dispatch. If no verify_pass exists for the message_id, or a verify_fail is present, REFUSE to process the payload and hand back to the orchestrator. Symmetric receiver gate — every Eidolon enforces it identically.
vivi-parallel-tracks
Load ONLY under TRANCE authorization when the Plan phase yields N independent, non-overlapping implementation tracks (disjoint file sets). Operationalizes the TRANCE G4 form — parallel multi-track implementation in mandatory git-worktree isolation, max 5 clean-context tracks, a per-track verifier cascade, a non-fungible per-track ≤3 reflection budget, explicit stop conditions, and a single-threaded merge/aggregation step. Absent TRANCE gating, Vivi runs exactly as today: single-track A→P→I→V→Δ/R.
vivi-methodology
Full Vivi cycle reference — A(nalyze) → P(lan) → I(mplement) → V(erify) → Δ(Delta)/R(eflect). Use when the task is a non-trivial feature implementation in a brownfield codebase and you need the complete methodology reference: complexity routing, evidence-grounded planning rules, test-anchoring requirements, and failure-escalation thresholds.