Run any Skill in Manus with one click

idg-esl-hop

Stars1

Forks0

UpdatedJuly 19, 2026 at 20:54

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).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Rynaro

Rynaro/lararium

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	idg-esl-hop
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).
metadata	{"methodology":"IDG"}

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>/, sets status=archived, and records archive_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 the archive_path and the change id.
promote — route the promotion-intent envelope (composed by archive) to mcp__crystalium__ingest if 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 if mcp__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

More from this repository

same repository

atlas-esl-hop

Rynaro/lararium

ESL lifecycle hop — the DISCOVER hop. When a scout mission's findings surface change-worthy signal (a defect, a spec/impl drift, or a genuine gap) in an ESL-enabled project (.spectra/ present), ATLAS proposes opening an ESL change at 'proposed' by framing the scout-report + its ECL envelope it already emits as the proposal artifact — it never calls mcp__tonberry__* itself and never implements (refusal boundary intact). SPECTRA's own esl-hop owns the actual right_size/propose/specify tonberry calls on receipt, over the existing atlas-to-spectra handoff edge. Absent .spectra/ or absent change-worthy findings → hand off the scout-report normally (ESL opt-in).

2026-07-191

atlas-synthesize

Rynaro/lararium

Phase S (Synthesize) — emit the scout-report.md artifact that downstream agents (SPECTRA, APIVR-Δ, human) consume. Hard cap 3000 tokens; every factual clause cited with FINDING-XXX; every recommended action carries a handoff label. Use after Phase A (Abstract) fold is validated and DECISION_TARGET has an answer or its gaps are recorded. Final phase of an ATLAS mission.

2026-07-191

atlas-verify-incoming

Rynaro/lararium

Receiver-side ECL integrity gate (blocking, symmetric). Refuses to process any upstream artefact whose sibling .envelope.json lacks a verify_pass trace event from the orchestrator. Use when reading any upstream artefact handed off to ATLAS that carries a sibling .envelope.json. Symmetric across all Eidolons — every Eidolon enforces it identically per ECL §6.2.2.

2026-07-191

forge-checker-handoff

Rynaro/lararium

Governs the checker-handoff gate for FORGE verdicts that authorize an irreversible action. Use at the end of the Emit phase, after the verdict and recommended action are drafted, to check the recommended action against the five mechanically observable irreversibility trigger markers (deploy/release, destructive migration or data deletion, security-boundary change, external spend/commitment, public communication). On a match, set the emitted reasoning-report's requires_checker flag to true instead of letting the verdict flow straight to execution. Reversible verdicts (no marker match) are unaffected — do not fire this skill for them.

2026-07-191

forge-self-consistency

Rynaro/lararium

Governs N perspective-diverse, mutually-blind reasoning traces with structural-agreement judge-merge for gated high-stakes FORGE decisions (G2/TRANCE). Use instead of forge-deliberation when Deep depth AND a stakes flag both hold (Framing score 8–9 with irreversible/system-wide blast radius), or on explicit opt-in. Do NOT use for standard-tier decisions — self-consistency is never the default.

2026-07-191

forge-verification

Rynaro/lararium

Governs logic verification, evidence coverage, confidence calibration, and the REFORGE protocol during the FORGE Gate phase. Use when the Reasoner enters Phase G to check logical soundness (fallacy scan), verify evidence coverage, assess decision completeness, calibrate the 4-factor confidence score, and decide pass/emit or trigger a single REFORGE revision pass.

2026-07-191

name	idg-esl-hop
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).
metadata	{"methodology":"IDG"}

IDG — ESL Lifecycle Hop

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>/, sets status=archived, and records archive_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 the archive_path and the change id.
promote — route the promotion-intent envelope (composed by archive) to mcp__crystalium__ingest if 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 if mcp__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