Fieldlight Archive Method / Implementation Note 01
One Export Is Not an Archive
A platform export is a representation of one source state—not automatically the whole history it appears to contain.
01 / Finding
Technical possession is not yet archival continuity.
A person may hold several platform downloads and still lack a stable, intelligible history. Preservation, provenance, comparison, and union logic are what turn exports into an archive.
The newest export contained 608 conversations. The union across three dated source states contained 654.
02 / Source-state union
The missing history was countable.
These are structural aggregate results. No conversation titles, message text, private identifiers, or working inventory data are published here.
conversations in the three-export union
conversations in the newest export
unique message nodes across the union
nodes visible only in alternate or noncurrent branches
03 / August 21 amendment
The export union was still not the whole preservation record.
An April 2025 conversation survived in two successive local application-cache states while remaining absent from every official export in the union.
conversation created at 19:08:39 UTC
first cached state at 04:01:08 UTC
message nodes in the later cache state
earlier message nodes removed
No single preservation surface should be presumed complete.
The second cached representation is dated April 24, 2025 at 05:30:01 UTC. The record was recovered and analyzed in August 2026; the recovery date is not the conversation date. Its absence does not establish deletion, export policy, platform intent, or the completeness of the cache. It establishes that even the reconciled export union did not exhaust the locally preserved historical record.
04 / Reconstruction
Stable identity comes before interpretation.
Titles, visual order, and the current path are representations. Stable identifiers and retained provenance provide the defensible basis for comparison.
Preserve surfaces
Retain exports, caches, and other acquired surfaces as distinct evidence.
Preserve states
Keep each dated state distinct; never silently repair one from another.
Reconcile identity
Union by stable identifiers while retaining surface-only records and alternate branches.
Analyze after gaps
Record absences, conflicts, and uninspected surfaces before making longitudinal claims.
preserve surfaces → preserve states → reconcile identities → retain surface-only records → record gaps → analyze
The method boundary
Preservation surface ≠ complete history.
An export, export union, local cache, application library, filesystem copy, repository, screenshot, or public page can establish what survived there at a particular state. None should silently become the whole past.
05 / Why it matters
The screen can remain continuous while the computational record changes around it.
Tool events, system context, graph relationships, intermediate states, alternate branches, and even whole conversations may survive differently across surfaces while the visible product still appears coherent.