Meaning Version Snapshot¶
Recordkeeping artifact — instantiates Contextual Selective Propagation
Freezes a dated record of a term's active definitions, source evidence, and transfer decisions so anyone can later reconstruct which sense was authoritative when.
Meaning moves, and without a record of where it stood, every later argument about "what the term meant" becomes unwinnable. The Meaning Version Snapshot is the archival artifact that stops that: a dated, immutable record capturing, as of this date, the term's active definitions, the evidence they rested on, and the transfer decisions in force (what could propagate where, what was held local). Its defining move is temporal traceability — it does not try to fix the meaning or watch it change; it stamps the state so that a future reader can reconstruct which sense was authoritative at any past moment, and diff two snapshots to see exactly what shifted. It is to meaning what a version tag is to a codebase: not the thing that changes it, but the thing that makes the change legible and reversible.
Example¶
The clearest real illustration is the word "planet." For most of the twentieth century the operating definition was informal, and Pluto counted. In 2006 the International Astronomical Union adopted an explicit definition — a body that orbits the Sun, is round under its own gravity, and has "cleared its orbital neighbourhood" — and under it Pluto was reclassified as a dwarf planet.[n1] A meaning version snapshot is exactly the artifact that makes such a shift navigable.
Imagine the term maintained this way. The pre-2006 snapshot records the active definition, the evidence (historical usage, textbooks), and the transfer decision (the informal sense may propagate freely to education and the public). The 2006 snapshot records the new formal definition, the resolution that established it, and a transfer decision: the new sense is authoritative for professional catalogs, while curricula and museum labels get a translated bridge note explaining the reclassification. Years later, a curator confused by an old label can pull the dated snapshots, see that the label predates the redefinition, and know precisely which sense it was written under — instead of arguing about whether the label is "wrong."
How it works¶
- Capture the state, not the change. Record the term's active definitions, the source evidence behind them, and the transfer decisions in force at the snapshot moment — a still photograph, not a monitor.
- Date and freeze. Timestamp the record and make it immutable; a snapshot that can be silently edited later is worthless as a version trace.
- Preserve supersession, don't overwrite. When meaning moves, write a new snapshot rather than editing the old one, so the history remains reconstructable.
- Enable diffing. Structure snapshots so two dates can be compared field-by-field, turning "the meaning changed somehow" into a precise before/after.
Tuning parameters¶
- Snapshot trigger — what prompts a new version (a fixed cadence, or an event like a redefinition or a monitored drift threshold). Event-driven snapshots are lean and meaningful; calendar snapshots guarantee coverage but accumulate near-duplicates.
- Field set — how much each snapshot records (definition only, or definition + evidence + contexts + transfer decisions). Rich snapshots reconstruct more but cost more to author and can go unread.
- Granularity of "active" — whether one snapshot holds a single canonical sense or a plurality of active senses with their contexts. Plural snapshots are honest about living language but heavier; singular ones are crisp but can pretend to a consensus that is not there.
- Immutability strictness — whether corrections are appended or edited in. Strict append-only preserves the audit trail; permitting edits is convenient but erodes trust in old versions.
- Retention depth — how far back snapshots are kept. Deep history serves long-lived terms; aggressive pruning saves space but discards the reconstruction the artifact exists to provide.
When it helps, and when it misleads¶
Its strength is settling otherwise circular disputes: with dated snapshots, "which sense was authoritative when we wrote this?" becomes a lookup rather than a debate, and a diff makes a redefinition auditable instead of mysterious. It is the archetype's memory, and the thing that lets translation notes and scope rules refer to a stable "as-of" state.
Its failure mode is snapshot rot — versions proliferate, nobody consults them, and the archive becomes a write-only graveyard that gives false comfort that meaning is "under control" while real usage runs elsewhere. A subtler misuse is treating a dated definition as settled — reifying a still photograph of living language into a decree, so people cite an old snapshot to police current usage the language has already moved past. The guarding discipline is to trigger snapshots on genuine events rather than reflexively, keep them findable and diff-able so they are actually used, and label every snapshot as a record of what was active then, never as a ruling on what must be true now.
How it implements the components¶
The version snapshot fills the record-and-preserve components — the ones that give propagation a memory:
focal_signifier_or_practice_record— each snapshot records the focal term and the definitions active as of its date.meaning_version_trace— the dated, immutable, diff-able sequence of snapshots is the version trace, its core contribution.selective_transfer_boundary_rules— each snapshot preserves the transfer decisions in force at that moment (what propagated, what stayed local), archiving the boundary state.
It does not diagnose the current sense shift (Sense-Boundary Comparison Table, meaning_shift_profile), run the live feedback loop (Uptake Sentinel Monitoring, uptake_and_misinterpretation_feedback_loop), or conduct the harm review (Bridge-Context Interview, semantic_harm_review); it archives their outputs rather than producing them.
Related¶
- Instantiates: Contextual Selective Propagation — the snapshot is the archetype's dated memory of which sense and which transfer rules were authoritative when.
- Consumes: Sense-Boundary Comparison Table and Channel-Specific Scope Note supply the definitions and transfer decisions each snapshot freezes.
- Sibling mechanisms: Context Sampling Audit · Sense-Boundary Comparison Table · Propagation Pathway Graph · Channel-Specific Scope Note · Bridge-Context Interview · Uptake Sentinel Monitoring · Semantic Quarantine Marker
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Meaning Version Snapshot operates as a durable record, ledger, register, or trace whose value depends on preserving actual state or history because it freezes a dated record of a term's active definitions, source evidence, and transfer decisions so anyone can later reconstruct which sense was authoritative when.
Independent corroboration: The frozen evidence defines Meaning Version Snapshot as 'Freezes a dated record of a term's active definitions, source evidence, and transfer decisions so anyone can later reconstruct which sense was authoritative when', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: A dated snapshot of authoritative definitions, evidence, and transfer decisions is a records-and-provenance artifact. Linguistics supplies theories of meaning and sense change, while historiography supplies temporal source criticism.
Related originating lineages:
- History & Historiography — For Meaning Version Snapshot, source criticism, archival silences, provenance, and reconstruction of past context materially shaped the mechanism's characteristic form.
- Linguistics & Semiotics — Retained as a formative lineage independently identified as primary: Tracking active senses and contextual meaning is rooted in semantics and terminological analysis.
Review resolution: W3C PROV treats revisions as distinct entities connected by provenance so prior states can be reconstructed. That information-governance pattern is the mechanism's defining form; linguistic meaning analysis and historical reconstruction remain formative lineages. The alternates are retained only as formative or independently established origins, not because the mechanism can be applied there. origin_mode=cross_disciplinary_synthesis states the provenance relationship; domain_reach=multi_domain separately records breadth because independent established uses occur in several fields. confidence=high reflects the strength and specificity of the evidence; encyclopedia_synthesis=true because the entry deliberately composes those documented lineages into this exact artifact.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- https://www.w3.org/TR/prov-primer/ — The W3C provenance standard explains entities, revisions, derivations, and reconstruction of prior states.
- https://committee.iso.org/sites/tc46sc11/home/news/content-left-area/news-about-standarization-in-t-1/core-concepts-and-vocabulary-add.html — ISO records-management material situates authoritative records and metadata within information governance.
Notes¶
[n1] The discipline of semantic versioning — tagging successive states so any consumer can tell which version they are pinned to and what changed between them — is the direct analogue. A meaning version snapshot brings the same "pin the state, diff the change" logic to definitions, which is what turns a redefinition like Pluto's from a source of confusion into a documented, navigable transition. ↩