Menu

Individual skill

recording-a-known-good-version

Records the version everyone agreed is correct, the evidence behind it, and what would make that record out of date. Use when a standard change ships, when prompts, models, tools, dependencies, docs, or release items are accepted, or when a lesson forces a re-record. Do not use for a tiny local edit with nothing to release or trust, or while the work is still under review.

skills/recording-a-known-good-version/SKILL.md

Read pinned source

Source commit e44af0e5811e11a3601625cf657d257915689deb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
33
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Recording a Known-Good Version

## Overview

A baseline is simply the version everyone agreed is correct and wants to protect. This skill writes down that version, the evidence that backs it, and the things that would make it out of date.

## Decision contract

- **Claim checked:** the accepted version can be rebuilt exactly from its named commit/PR/release, everything under control is either included or deliberately left out, the accepted residual risks have owners, and the triggers that force a new known-good version are recorded.
- **Artifact observed:** `controlled-items.md`, `change-impact.md`, `verification.md`, the `ship.md` decision, and the identifying commit/PR/release -> a `baseline.md` with included/excluded scope, accepted gaps, and re-record triggers.
- **Decision affected:** warn -- the accepted baseline the ship decision produced, and the triggers that invalidate it.
- **Failure class:** unrebuildable-baseline (a version recorded as accepted with missing evidence or silently dropped scope).
- **Next action:** record the missing link or excluded scope as a named gap; escalate when the version affects customers, regulated work, or outside trust.