Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Version Control for Audit Evidence Without Editing the Past
Short answer
Version control in an evidence room means the opposite of overwriting: when an artifact must be corrected, the corrected file is imported or uploaded as a new artifact with its own seal and date, the original stays, and the room's thread records which supersedes which and why. The manifest then shows the pair transparently. Auditors read visible version history as functioning quality control — and read its absence, in any real operation, as a question. Name versions clearly, narrate supersession once, and let the sealed pair tell the story forever.
What is evidence versioning?
Evidence versioning is the practice of managing corrected or updated artifacts inside an immutable evidence room on AI Audit Exchange: new versions enter as new artifacts (suite re-exports through import, replacements through direct upload where appropriate), each SHA-256 sealed at its own intake and listed separately in the manifest, with supersession relationships recorded in the room's question thread rather than by altering or removing the original.
Why overwrite is the one unforgivable edit
Every evidence failure taxonomy has a top entry, and it is silent replacement. A file that changes without a trace retroactively falsifies every statement ever made about it — every sampling that cited it, every answer that pointed at it, every meeting that relied on it. That is why rooms store artifacts immutably: the mechanism refuses the edit, so the temptation never becomes an incident. Versioning is the honest alternative the refusal forces, and it turns out to be better in every way: the record keeps its memory, the correction gets its own date and seal, and the pair together demonstrate the thing auditors most want to see — an organisation whose errors surface, get fixed, and stay visible. Version control for evidence is not a filing preference; it is the difference between a record and a rumour.
The supersession pattern, step by step
When a correction is needed: fix the source first — in the producing product for suite evidence, so the re-export is that product's own new record. Import the corrected artifact into the same room through the same path the original took. Then, in the room's thread, post one supersession note: the original's manifest identity (filename, source, import date), the replacement's identity, the reason for the correction, and the date. One note, permanently threaded, findable from either file's story. Do not rename the original, do not annotate the artifact itself, do not delete anything. The manifest will list both artifacts with their own hashes and dates; the note binds them into a version pair any future reader can interpret without you.
Naming versions so strangers can read them
Filenames are the version system's user interface. Keep the producing product's own export names for imports — the badge and manifest carry the provenance, and invented renames only add noise. For direct uploads you control, adopt a stable stem with an explicit version or date suffix that sorts correctly and never recycles: a policy record named with its adoption date reads honestly forever. The anti-patterns are familiar to anyone who has audited a drive: 'final', 'final2', 'REAL final' — names that assert status instead of stating facts. In a room, status lives in the supersession note and the thread; names should confine themselves to identity and date.
What auditors do with version pairs
Examiners treat version pairs as evidence about your control environment, in both directions. A pair with a crisp supersession note — source fixed, re-export imported, reason stated — is positive evidence: detection worked, correction was honest, the record kept its memory. A pair without a note is a research project the auditor must fund with questions. Multiple pairs around the same artifact suggest a producing process that needs attention upstream, and a good auditor will say so as a process observation, which is a gift if you let it be one. And a room with zero corrections across years of operation invites the deepest scepticism of all: either the operation is miraculous, or its corrections are happening somewhere the record cannot see.
Versions across periods
Period boundaries discipline versioning the way they discipline everything else. A correction belonging to a closed period is filed in that period's room as a new artifact — with its true, current import date honestly showing when the correction arrived — and narrated in that room's thread. Do not file period-one corrections into period-two's room to keep the old room pristine; pristine closed rooms are exactly what examiners distrust. Conversely, a new period's updated policy is not a 'version' of last period's: it is that period's own artifact, filed in its own room, related by content rather than by supersession. The thread note is the tool for expressing relationships the manifest cannot; use it in the room where the relationship matters.
Retention of versions: keep the whole story
Superseded originals stay for the room's retained life — up to 10 years on paid plans — because the version story is part of the evidence. Deleting the original after supersession would recreate the silent-replacement problem at one remove: the correction would stand alone, its claims about what it corrected unverifiable. Storage is not the constraint here; a room's artifacts are documents, not video. The constraint to manage is readability: a room with many pairs stays readable precisely because supersession notes exist. If a room's version count grows large, that is information about the producing process to act on upstream — fix the source's configuration, template or review step — not a reason to thin the record downstream.
Five actions to take
- Fix corrections at the source product first, then import the re-export as a new artifact — never edit or overwrite in place.
- Post one supersession note per correction in the room's thread: original, replacement, reason, date.
- Name direct uploads with stable stems and date or version suffixes; ban 'final' from filenames.
- File closed-period corrections into that period's room with honest current import dates.
- Retain superseded originals for the room's full life; act on version volume upstream, not by thinning the record.
Worked example
A fictional fleet-software firm, Mesquite Miles Systems, accumulates 5 version pairs in its SB 1119 room across a year: two ReviewDesk re-exports after a template fix, one CompanionGuard set after a configuration correction, one ProvenanceGuard re-export, and one direct-upload policy record superseded by its amended successor. Each pair carries a thread note of two or three lines. The manifest lists 74 artifacts; the notes index the 5 pairs among them.
The auditor samples 3 of the 5 pairs unprompted — pairs attract examiners — verifies both seals in each, reads the notes, and closes all three in one session. Her summary includes the sentence the pattern exists to earn: corrections were identified, corrected at source, and preserved transparently. In the same quarter, a peer firm's audit reportedly stalled for weeks over a single replaced file nobody could date. Same species of error, opposite handling, opposite outcomes — versioning is where the difference was decided, months earlier, in filing habits.
Frequently asked questions
Can't I just delete the wrong file and upload the right one?
That recreates silent replacement: the record loses the fact of the error and the correction's context. File the correction alongside, note the supersession, and the pair strengthens rather than weakens your record.
Which file does the auditor treat as current?
The one your supersession note designates — supported by the dates and seals in the manifest. Without a note, the auditor must ask, and 'we forgot to say' is a poor answer about your own record.
Do version pairs hurt our completeness or freshness picture?
No. Completeness counts organisational steps, and freshness judges each artifact's recorded date on its own terms. A current corrected artifact answers freshness exactly as any current artifact does.
Should the superseded original keep its badge?
Yes — badges record provenance at intake and never change. The original keeps its source badge; the correction carries its own. Supersession is narrated in the thread, not by relabelling history.
What if the correction is to a direct upload?
Upload the corrected document as a new artifact with a clear versioned name, and post the same supersession note. The pattern is identical; only the intake path differs.
Keep reading
All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: How to Hand Over Evidence to a New Auditor · Next: What Is Source Badging on Audit Evidence?
Importing ProvenanceGuard Evidence Into an Audit Room · Importing ReviewDesk — ADMT Decision Review Evidence Into an Audit Room · Importing CompanionGuard Evidence Into an Audit Room