---
id: "prereq-version-control-revert"
type: "prereq"
source_timestamps: ["00:19:42", "00:19:54"]
tags: ["software-engineering", "safety"]
related: ["framework-safety-pillars", "concept-silent-degradation"]
reason: "Autonomous experimentation guarantees failures; instant revert capabilities are required to prevent those failures from causing extended downtime."
sources: ["s04-karpathy-agent-700"]
sourceVaultSlug: "s04-karpathy-agent-700"
originDay: 4
---
# Version Control and Instant Revert Capabilities

## Prerequisite
Version Control and Instant Revert Capabilities.

## Reason
Autonomous experimentation guarantees failures; instant revert capabilities are required to prevent those failures from causing extended downtime.

## Detail
Because auto-agents will inevitably propose changes that degrade secondary metrics (see [[concept-silent-degradation]]) or cause unexpected failures, the underlying system must have **robust version control**.

## What's Required
- All edits are versioned (git or equivalent)
- The organization can **instantly revert** to any previous stable state of the agent's harness
- No manual code rewrites are required to roll back

## Where It Fits
This is the third pillar of the [[framework-safety-pillars|Four Pillars of Reliable Automation]] — Version Control. It pairs with Tight Loops (constraint), Clear Baselines (multi-dim evals), and Human Oversight to wrap the [[framework-karpathy-loop-execution|execution cycle]] safely.

## Practical Hint
The target file (per the [[concept-karpathy-triplet|Karpathy Triplet]]'s editable surface) should live in version control from day one, with automated commit/revert hooks tied to evaluation outcomes.