Snapshot Plus Archive¶
Recordkeeping pattern — instantiates Accumulation Compaction
Keeps a compact current-state snapshot next to everyday work while filing the full underlying detail, unaltered, into recoverable storage — with a retrieval path and a restore procedure for when the detail is needed again.
Snapshot Plus Archive is the recordkeeping pattern that splits accumulated history into two tiers: a compact snapshot of the current state kept close to everyday work, and the full underlying detail moved, unchanged, into recoverable storage. Its defining feature is that it is mechanical, not editorial — it captures the present state as-is and files the rest verbatim; it makes no judgment about which content is "correct" and merges nothing. What makes it more than a backup is that the archived detail stays reachable: the pattern always pairs the snapshot with a retrieval path to find the archived detail and a rehydration procedure to restore it. The snapshot answers the everyday question cheaply; the archive answers the rare, deep question when it arises.
Example¶
A company closes its books each month. At period end, the accounting system captures a snapshot: the trial balance — each account's closing figure — which is what management, auditors, and next month's opening entries actually need day to day. The tens of thousands of individual transactions behind those figures are not deleted; they are archived to a separate, lower-cost store, exactly as recorded. Everyday reporting runs against the compact snapshot and stays fast; the ledger detail sits out of the way.
Then a supplier disputes an invoice from eight months ago. Because the archive carries a retrieval path — indexed by period and account — the controller locates the relevant batch, and a rehydration procedure pulls the full transaction detail back into a working view for investigation. The dispute is settled against the original records, then the detail returns to the archive. Month-to-month work stayed light, and not one transaction was lost or altered — the pattern simply changed where each tier lives and how it is reached.
How it works¶
What distinguishes it from a plain summary or a plain backup is the two-tier split with a live path between them:
- Capture the current state. Snapshot the present figures or state that daily work depends on, kept close and cheap to read.
- Archive the detail verbatim. Move the full underlying records, unaltered, into recoverable lower-cost storage — no merging, no editorial change.
- Maintain the retrieval path. Index the archive so a specific slice of detail can be located later without scanning everything.
- Provide rehydration. Keep a tested procedure to pull archived detail back into a working form when a deep question demands it.
Tuning parameters¶
- Snapshot frequency — how often a current-state snapshot is taken (per period, per release, per milestone). Frequent snapshots give fine-grained current views but multiply what must be maintained; sparse ones are lean but coarser.
- Archive tier depth — how far the detail is moved (near-line vs. cold storage). Deeper tiers cost less to hold but take longer to rehydrate; shallower tiers are pricier but faster to reach.
- Retrieval-path granularity — how finely the archive is indexed. Fine indexing makes rare lookups fast but costs upkeep; coarse indexing is cheap but turns retrieval into a hunt.
- Rehydration readiness — whether restore is a routine, tested operation or a best-effort scramble. Tested rehydration guarantees the detail is truly recoverable; untested archives quietly rot into unusable ballast.
When it helps, and when it misleads¶
Its strength is that it makes the common case cheap and the rare case still possible: everyday work reads a light snapshot while the full detail remains recoverable, and — unlike a lossy summary — nothing is discarded or reinterpreted. It is the recordkeeping expression of hierarchical storage management: keep the working set hot and near, push the cold detail to cheaper storage behind a stub that can fetch it back.[n1]
It misleads when the archive half is neglected. An archive whose retrieval path has rotted — moved to an unreadable format, an index no one maintains, a system since decommissioned — is the archetype's broken-retrieval failure: the detail is technically preserved and practically gone. Untested rehydration is the same trap discovered only in the emergency that needed it. A subtler misuse is treating the snapshot as if it were the whole truth and letting the archive quietly decay, so the two tiers drift apart. The discipline is to test rehydration on a schedule, keep the retrieval path and index alive as systems change, and remember that the snapshot's cheapness is only legitimate while the archive behind it is genuinely recoverable.
How it implements the components¶
Snapshot Plus Archive fills the two-tier recordkeeping side of the archetype — a light current view backed by recoverable full detail:
summary_layer— the current-state snapshot (trial balance, latest state) that everyday work reads instead of the full detail.archive_rule— the movement of full underlying detail, unaltered, into recoverable lower-cost storage.retrieval_path— the index that lets a specific slice of archived detail be located later without a full scan.rehydration_or_rollback_path— the tested procedure that restores archived detail into a working form on demand.
It does NOT reconcile conflicting content or maintain a layer_index and provenance_preservation crosswalk of what merged into what — that editorial merge is Documentation Consolidation — nor run a bias_review over what the snapshot represents — that is Retrospective Synthesis; this pattern captures state and files detail verbatim, without editorial judgment.
Related¶
- Instantiates: Accumulation Compaction — it is the archetype applied as a durable two-tier recordkeeping split.
- Sibling mechanisms: Documentation Consolidation · Archival Summarization · Retrospective Synthesis · Knowledge Base Pruning · Backlog Consolidation · Deduplication Pass · Database Vacuum or Compaction · Log Compaction · Retention Schedule
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Snapshot Plus Archive operates as a persistent ledger, log, register, or case record that preserves history and traceability because it keeps a compact current-state snapshot next to everyday work while filing the full underlying detail, unaltered, into recoverable storage — with a retrieval path and a restore procedure for when the detail is needed again.
Independent corroboration: The frozen evidence defines Snapshot Plus Archive as 'Keeps a compact current-state snapshot next to everyday work while filing the full underlying detail, unaltered, into recoverable storage — with a retrieval path and a restore procedure for when the detail is needed again', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Pairing a compact working surrogate with preserved full records and a retrieval path is records and archival management.
Related originating lineages:
- Accounting & Auditing — Unaltered underlying detail supports later verification.
- Computer Science & Software Engineering — Snapshots, object storage, and restore procedures implement the pattern digitally.
- Organizational & Management Science — Current-state summaries reduce operational burden while owners retain deep evidence.
Review resolution: The blind reviewers agree that library_information_science is the primary origin and differ only on alternate origin disagreement, origin mode disagreement, domain reach disagreement, encyclopedia synthesis disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain convergent because the combined evidence shows independent disciplinary development. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Hierarchical storage management (HSM) automatically moves infrequently used data from fast, expensive storage to slower, cheaper tiers while leaving a stub or index so the data can be transparently retrieved when accessed. The concept is referenced here as an established storage practice, not as a cited authority. ↩