rollback skillA

rollback is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Get back to a known-good state, and know in advance which parts of a release cannot come back — destructive migrations, data the old version cannot read, messages already sent, published artifacts, cache and CDN state. Use while writing a release plan, when a deploy is going wrong, or when someone asks whether a change can be undone. Not the health check that decides you should revert (release-verification), not incident coordination, and it never runs a production revert without explicit per-ac.

Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.

What the file says

# Rollback

Rollback is not the absence of a deploy. It is another deploy, made under time pressure, against a
system whose state has already moved. Most failed rollbacks fail for that reason: the code went
back and the data did not.

## When this fires

While planning a release — the rollback path is part of the plan, not a thing to invent later — and
again the moment a release is going badly. It fires before the decision to revert, not after it.

## Procedure

1. **Name the known-good state as an artifact id.** The commit, digest or build you would return
   to, confirmed still deployable — the image still present in the registry, the release still
   installable. "The previous version" is not an address, and a rollback target that was garbage
   collected is not a rollback target.

2. **Classify every part of the change** into three buckets, before you need them:
   - *Reversible* — redeploying the old artifact restores the old behavior.
   - *Forward-only* — the way back is a new fix, not the old code.
   - *Irreversible* — nothing restores the prior state; only mitigation exists.

3. **Find the one-way doors.** These are the ones that turn a rollback into an incident:
…

Read the whole file at its exact version.

How to install

mdr add nahid-sparktales/agent-dispatcher/rollback@git:20260919.a0d4f55

mdr add nahid-sparktales/agent-dispatcher/rollback@sha256:c95267f9dd5f0ddd

[![mdr](https://markdownregistry.com/badge/art_neju5lon7obvrnfj.svg)](https://markdownregistry.com/a/art_neju5lon7obvrnfj)

Versions

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_neju5lon7obvrnfj
GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/rollback
GET https://markdownregistry.com/api/v1/blob/c95267f9dd5f0ddd0f053c031d81ce4596620acd51066f486f6ea4f6ea615847

Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

More from nahid-sparktales/agent-dispatcher

Every file in nahid-sparktales/agent-dispatcher

Other files named rollback

Browse by kind, by grade A, or by owner.