Skip to main content

CIS launcher recovery owner expectations

Use when reporting or recovering the CIS launcher. User distinguishes shared durable-delivery launcher candidates (C8/C13/etc.) from the CIS benchmark candidate. Label updates launcher Cn — shared CIS prerequisite. Candidate numbers are successive repair attempts, not a fixed feature backlog. Report actual CIS implementation/acceptance separately from infrastructure progress. For remaining-work questions, enumerate concrete delivery stages and disclose uncertain remediation; do not imply green launcher tests mean CIS is delivered or invent an ETA.

One-off C13 contingency​

Owner authorized this narrow exception: terminal C13 acceptance/conformance/review findings trigger exact firstParty/claude-fable-5-1 diagnosis and a bounded remediation plan, followed by exact openai-codex/gpt-6-astra implementation, then a fresh independent exact Fable check of whether the repaired result works and is clean. SOL coordinates. No silent Opus substitution or planning-only Astra replacement. This is not a permanent fleet-wide routing change. Preserve productive incumbents; expected intermediate RED is not a terminal trigger. Existing security, deployment and merge limits remain. Re-read latest live instructions before dispatch.

Root-cause diagnostic reopening​

After Astra-r3 stress failed at run66 without decisive monitor evidence, owner explicitly requested Fable determine root cause. This authorized disposable by-value diagnostic harness instrumentation and real test execution, not another read-only report. Persist fence/monitor revocation/holds/sequence/persistence-failure/process identity evidence before assertions, and retain observation/bootstrap fixtures on failure. Post-assertion-only evidence publication loses the failed case. Use bounded loaded/unloaded reproduction; distinguish captured causality from hypothesis or non-reproduction. Diagnostic-only authorization does not itself authorize automatic implementation or deployment. Preserve exact model telemetry and immutable input lineage.


Source: jknash/hermes-shared-skills · branch hermes-jkdev001 @ 1d0d545c3970 · skills/launcher-cis-recovery-owner-expectations/ · view source · Imported 2026-10-04. Supporting files (references, scripts) remain in the source repository.

Published by Muse · 2026-10-04.