idg-esl-hop
ESL lifecycle hop — when the cortex routes a verified, drift-checked change to IDG in an ESL-enabled project (tonberry MCP available), the Scribe owns the archived hop: archive the change folder, chronicle the lifecycle outcome with provenance, and route the promotion-intent envelope to CRYSTALIUM. Absent tonberry → document normally (ESL opt-in).
- License 许可
- Apache-2.0
- 所属仓库
- Rynaro/magicite
- 最近更新
- 2026-10-14
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- idg-esl-hop
- metadata
- { "methodology": "IDG" }
- description
- ESL lifecycle hop — when the cortex routes a verified, drift-checked change to IDG in an ESL-enabled project (tonberry MCP available), the Scribe owns the archived hop: archive the change folder, chronicle the lifecycle outcome with provenance, and route the promotion-intent envelope to CRYSTALIUM. Absent tonberry → document normally (ESL opt-in).
03 SKILL.md 正文
IDG — ESL Lifecycle Hop
Use this skill in an ESL-enabled project (mcp__tonberry__* tools available)
when the cortex routes a change to you that is already verified and
drift-checked. You own the archived hop of the Eidolons Spec Lifecycle
(ESL) — the Scribe closes the loop by chronicling the outcome and promoting the
spec-of-record.
For the full lifecycle, stage definitions, and role bindings, see the nexus
cortex methodology/cortex/esl-protocol.md.
Your hop
- archive — call
mcp__tonberry__archive --change_id <id>. This MOVES.spectra/changes/<id>/→.spectra/changes/archive/<date>-<id>/, setsstatus=archived, and recordsarchive_path(tonberry v0.4.0: archive moves, not copies). Tonberry also composes the promotion-intent ECL envelope. - document — your scribe role. Run your normal I → D → G cycle and
chronicle the lifecycle outcome: what was proposed, implemented, verified, and
archived. Ground every claim in the change folder's artefacts (
change.json,spec.{md,yaml}, verify/drift records). Apply structural markers ([DECISION],[ACTION],[DISPUTED],[GAP]) and emit a provenance block citing thearchive_pathand the change id. - promote — route the promotion-intent envelope (composed by
archive) tomcp__crystalium__ingestif CRYSTALIUM is available. This is the durable spec-of-record promotion — the verified, archived change becomes recallable semantic memory. If CRYSTALIUM is absent, the intent stays on disk in the archive folder (graceful); a later session promotes it.
Invariants
- Tonberry moves and composes; you chronicle and promote. Tonberry performs the folder move and writes the promotion-intent envelope; you supply the document (lifecycle narrative + provenance) and forward the intent to CRYSTALIUM.
- Document from provided context only. Read the change folder's artefacts;
do not research, retrieve, or analyse code. Missing information is a
[GAP], never an invention. - Graceful skip — if
mcp__tonberry__*tools are unavailable, document the change normally via your standard cycle and never hard-fail. Likewise ifmcp__crystalium__*is unavailable, the promotion intent stays on disk. ESL is opt-in; IDG is EIIS-standalone-conformant and works without tonberry or CRYSTALIUM.
Scribe — ESL Lifecycle Hop
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.