Skill rollbacks

2 min readReferenceUpdated 2026-05-19

What you'll find here

The reviewable path for reverting promoted skill updates when a promoted version causes regressions or violates policy — target, request, and decision contracts.

Rollbacks don't invent guidance.

Rollbacks point at a prior promoted version. They do not invent replacement guidance — that requires a new proposal.

Target

SkillRollbackTarget:

Skill package id

Promoted version id

Rollback version id

Promoted proposal id

Promoted receipt id

The rollback version must be distinct from the promoted version.

Request

SkillRollbackRequest:

Task id

Rollback target

Rollback reason

Rationale

Policy envelope id

Evidence ids

Receipt ids

Replay result ids

Requester & request timestamp

Requests require policy, evidence, and receipt references so reviewers can audit why the rollback was proposed.

Decision gate

Replay context required.

decide_skill_rollback approves a rollback only when the request has replay-result context and the decision records its own receipt. Missing replay context or a missing decision receipt produces a denied SkillRollbackDecision.

Decision

Preserves

Notes

Approved

version + receipt

Rollback version id and decision receipt id.

Denied

reasons

Explicit denial reasons.

What's next

ReferenceSkill promotion gatesThe decision rollbacks undo.ReferenceSkill replayThe replay result rollback decisions require.ReferenceLearning receiptsRecord rollback decisions with the rollback action.