Provenance
The recorded origin of a change or a claim — who made it, when, and on what evidence.
Provenance is the traceable origin of an artifact: which change introduced a line, what reasoning accompanied it, and what evidence supported it. In software the provenance record is version-control history plus whatever narrative was attached to each change.
It is worth treating as a first-class output. History is the only durable answer to "why is this here", which means a change description is not paperwork — it is the permanent record that a squashed merge writes into the repository. A description containing an unverified causal claim, or a verification bullet describing something nobody actually did, becomes a false statement in the archive. See Plausible Mechanism and Squash Merge.
Provenance also makes attribution auditable in the other direction. Determining which change caused a failure requires reading check results keyed to the specific revision, not to a branch or a merge preview — a "green" run computed against a state that predates the suspect change proves nothing about it.
The same idea applies to any recorded corpus: an evaluation result, a benchmark, a research summary. Recording what produced it — the model, the prompt, the input revision — is what makes it possible to tell a stale result from a current one later. See Fingerprint.
See also6
Hand-picked in the note itself — the neighbours worth reading next.
Version Control
A system recording the history of a project's files, enabling branching, merging, and recovery.
Version Control & Delivery13 connections
Commit
A recorded snapshot of a project with a message explaining it.
Version Control & Delivery9 connections
Documentation Rot
Documentation that has drifted from the system it describes, and is now worse than none.
Method20 connections
Fingerprint
A hash over everything that determined a result, used to detect when the result has gone stale.
Agents & Language Models11 connections
Code Review
A second person reading a change before it lands, and the practices that make it worth the time.
Version Control & Delivery15 connections
Code Comment
Prose inside source code, useful only when it records a constraint the code cannot state.
Method9 connections
Related2
Nearby in the graph rather than deliberately chosen. Looser, sometimes surprising.
Linked from17
Notes elsewhere in the wiki that reach for this one.
- Adversarial ReviewAgents & Language Models
Reviewing work with an explicit mandate to refute it, from a perspective that did not produce it.
- Agent MemoryAgents & Language Models
Durable facts stored outside the context window and recalled into later sessions.
- Agent SkillAgents & Language Models
A packaged, invocable set of instructions that loads into an agent's context on demand.
- Atomic CommitVersion Control & Delivery
A commit containing exactly one logical change, complete and independently sound.
- Code CommentMethod
Prose inside source code, useful only when it records a constraint the code cannot state.
- Code ReviewVersion Control & Delivery
A second person reading a change before it lands, and the practices that make it worth the time.
- CommitVersion Control & Delivery
A recorded snapshot of a project with a message explaining it.
- Conventional CommitsVersion Control & Delivery
A lightweight convention giving commit messages a machine-readable type and scope.
- Documentation RotMethod
Documentation that has drifted from the system it describes, and is now worse than none.
- FingerprintAgents & Language Models
A hash over everything that determined a result, used to detect when the result has gone stale.
- Hash FunctionSystems & Tooling
A function mapping arbitrary input to a fixed-size digest, used for identity, integrity, and addressing.
- LLM-as-JudgeAgents & Language Models
Using a language model to score another model's output against a rubric.
- Plausible MechanismMethod
A causal explanation that was inferred rather than tested, and reads as more rigorous for being specific.
- Pull RequestVersion Control & Delivery
A proposal to merge a branch, carrying review, automated checks, and the discussion around it.
- Record and Replay TestingAgents & Language Models
Capturing a real interaction once and replaying it deterministically in later test runs.
- Squash MergeVersion Control & Delivery
Collapsing a branch's commits into one before merging, trading granularity for a clean main history.
- Version ControlVersion Control & Delivery
A system recording the history of a project's files, enabling branching, merging, and recovery.