AGENT SKILL

vigil-esl-hop

ESL lifecycle hop — in an ESL-enabled project (tonberry MCP available), VIGIL owns the FAILURE PATH: on a verify_fail or spec-vs-impl drift, transition the change back to the maker (in_progress) and emit an ESCALATE envelope carrying root-cause attribution. You are the failure-path checker, distinct from the maker (maker ≠ checker). Absent tonberry → run the normal V→I→G→I→L cycle (ESL opt-in).

License 许可
Apache-2.0
所属仓库
Rynaro/magicite
最近更新
2026-10-14
Stars
★ 2
Forks
0

01 前言 Front Matter

name
vigil-esl-hop
metadata
{ "phase": "post-L", "methodology": "VIGIL" }
description
ESL lifecycle hop — in an ESL-enabled project (tonberry MCP available), VIGIL owns the FAILURE PATH: on a verify_fail or spec-vs-impl drift, transition the change back to the maker (in_progress) and emit an ESCALATE envelope carrying root-cause attribution. You are the failure-path checker, distinct from the maker (maker ≠ checker). Absent tonberry → run the normal V→I→G→I→L cycle (ESL opt-in).

03 SKILL.md 正文

VIGIL — ESL Lifecycle Hop (Failure Path)

Use this skill in an ESL-enabled project (mcp__tonberry__* tools available) when a verify FAILS or the implementation diverges from the spec (your root-cause domain). You own the failure path of the Eidolons Spec Lifecycle (ESL) — a checker distinct from the maker.

For the full lifecycle, stage definitions, and role bindings, see the nexus cortex methodology/cortex/esl-protocol.md.

Your hop

  1. On verify_fail — call mcp__tonberry__transition --change_id <id> --to_status in_progress to route the change back to the maker, then emit an ESCALATE envelope carrying your root-cause attribution ([ROOT-CAUSE] + evidence anchor from the V→I→G→I→L cycle). The maker re-implements against your finding, not against the symptom.
  2. When the implementation outran the spec — run mcp__tonberry__drift_check --change_id <id> --checker vigil before archive. A mismatch (impl asserts behavior the Semantic spec never specified, or vice-versa) is a verify_fail → transition back + ESCALATE.
  3. You are the failure-path checker — a distinct identity from the maker. Your verify/drift envelopes carry from.eidolon = vigil, never the maker's identity.

Invariants

  • maker ≠ checker — VIGIL is the checker on the failure path; the change's maker (e.g. Vivi) is always a distinct identity. Self-verified changes violate the ESL C4 gate.
  • Tonberry composes artifacts; you supply signals. You provide the root-cause attribution, the drift verdict, and the verify_fail reason; tonberry writes the change.json transition and records enforcement.
  • Graceful skip — if mcp__tonberry__* tools are unavailable, run your normal V → I → G → I → L cycle and emit findings/escalations the standard way; never hard-fail. ESL is opt-in; VIGIL is EIIS-standalone-conformant and works without tonberry.

Pending: ECL 2.1 verification-attestation (not yet implemented)

ECL v2.1 (Draft, adoption-gated — spec/ecl-2.1.md §6.5.8) defines an OPTIONAL ise.verification sub-block: {fresh_context, checker, transcript_access}, the wire-shape footprint of an independent verify pass. VIGIL is exactly the kind of distinct-identity checker that sub-block is built to describe — you are the maker≠checker on this failure path already (ESL C4, above). Once ECL 2.1 is cut to Published (the gate: ≥3 shipped Eidolons emitting the ise block) and VIGIL adopts it, your ESCALATE envelope on this hop would carry ise.verification = {fresh_context: true, checker: "vigil", transcript_access: "artifact-only"} (or "none", depending on what you were handed) alongside ise.assertion_grade — the MUST-level pairing rule that a validated grade actually has a fresh-context, different-checker verification behind it is owned by ESL 1.1 C8, not ECL (ECL only shape-checks the sub-block, per §6.5.8.3).

This is documented as pending, not emitted. ECL 2.1 is Draft; ECL_VERSION stays 2.0 and VIGIL's emitted envelopes do not carry ise.verification yet. No code or template change accompanies this note — it exists so the next sweep that adopts 2.1 has the mapping already worked out.


VIGIL — ESL Lifecycle Hop (failure path)

04 同仓库更多 Skills

Rynaro
Rynaro/magicite

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.

★ 2
Rynaro
Rynaro/magicite

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.

★ 2
Rynaro
Rynaro/magicite

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.

★ 2
Rynaro
Rynaro/magicite

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.

★ 2
Rynaro
Rynaro/magicite

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.

★ 2
Rynaro
Rynaro/magicite

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.

★ 2