maxwellinked commited on
Commit
e96889d
·
verified ·
1 Parent(s): cd26dae

Document June 2026 historical file relationship

Browse files

Add one revision-pinned historical provenance note for Tim's confirmation that the 15 June 18–30, 2026 Rec01–Rec15 files document the same physical drawing and that RecNN establishes file order. The note includes the exact 15 record IDs and paths, and states that the supplied screenshot identifies the files but is not independent proof of their contents.

This is a three-file documentation-only change. It does not alter media, paths, record IDs, metadata.csv, SHA256SUMS, dates, blank times or provenance fields, acquisition protocols, relationship packets, cohort counts, releases, or tags. Internal recording and session boundaries, per-file counts, raw-source status, uninterrupted capture, shared finish timing, and overall completeness remain unasserted.

CHANGELOG.md CHANGED
@@ -2,6 +2,18 @@
2
 
3
  ## Unreleased
4
 
 
 
 
 
 
 
 
 
 
 
 
 
5
  ### September 1 finish-time correction
6
 
7
  - Corrected the creator-supplied finish label for the complete 12-fragment
 
2
 
3
  ## Unreleased
4
 
5
+ ### June 2026 historical file relationship
6
+
7
+ - Added a revision-pinned provenance note recording Tim's confirmation that the
8
+ 15 existing June 18–30, 2026 `FountainPen.Ink.IllustrationBoard.30x40`
9
+ `Rec01`-`Rec15` files document one physical drawing and that `RecNN`
10
+ establishes file order.
11
+ - Preserved all active media, paths, record IDs, metadata, checksums,
12
+ `UnknownTime` values, blank provenance fields, and protocol assignments. The
13
+ note does not assert internal recording or session boundaries, per-file
14
+ recording counts, overall completeness, shared finish timing, raw-source
15
+ status, uninterrupted capture, a global `work_id`, or new cohort membership.
16
+
17
  ### September 1 finish-time correction
18
 
19
  - Corrected the creator-supplied finish label for the complete 12-fragment
Standard_Time_Lapses/Provenance/Historical_Relationships/2026-06-18--2026-06-30-fountain-pen-30x40.md ADDED
@@ -0,0 +1,44 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # June 18–30, 2026 historical file relationship
2
+
3
+ This note records a creator-confirmed relationship among 15 existing canonical
4
+ video objects. It is bound to the repository state inspected at source revision
5
+ [`cd26daea10ecc1c609fd1e5b9531fec6bd3cdcaf`](https://huggingface.co/datasets/maxwellinked/time-lapse-artifacts/commit/cd26daea10ecc1c609fd1e5b9531fec6bd3cdcaf)
6
+ and its [`metadata.csv`](https://huggingface.co/datasets/maxwellinked/time-lapse-artifacts/blob/cd26daea10ecc1c609fd1e5b9531fec6bd3cdcaf/metadata.csv).
7
+ At that revision, the 15 paths below resolve to exactly 15 unique persistent
8
+ `record_id` values and exactly `Rec01` through `Rec15`.
9
+
10
+ > These 15 files document one physical drawing. Rec01–Rec15 establishes file
11
+ > order. A file may contain multiple recordings. Internal recording and session
12
+ > boundaries and overall completeness are not asserted.
13
+
14
+ Tim's confirmation in the companion conversation is the evidence for the
15
+ same-drawing relationship and file order. The supplied screenshot identifies
16
+ the files; it is not independent proof of their contents. Tim described a
17
+ possible range of 2–10 recordings within a file, but exact per-file recording
18
+ counts have not been established.
19
+
20
+ | File order | `record_id` | Repository path |
21
+ | ---: | --- | --- |
22
+ | `Rec01` | `tla-0d3f080bcb1d686d` | `Standard_Time_Lapses/2026-06-18.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec01.mp4` |
23
+ | `Rec02` | `tla-955ee83b4b72be93` | `Standard_Time_Lapses/2026-06-21.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec02.mp4` |
24
+ | `Rec03` | `tla-6c837a1d829f47fa` | `Standard_Time_Lapses/2026-06-22.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec03.mp4` |
25
+ | `Rec04` | `tla-3f577357dec9bc96` | `Standard_Time_Lapses/2026-06-23.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec04.mp4` |
26
+ | `Rec05` | `tla-e8203d4fecb20fc4` | `Standard_Time_Lapses/2026-06-24.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec05.mp4` |
27
+ | `Rec06` | `tla-5451c51f042bbc17` | `Standard_Time_Lapses/2026-06-25.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec06.mp4` |
28
+ | `Rec07` | `tla-979661dfbb582edf` | `Standard_Time_Lapses/2026-06-26.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec07.mp4` |
29
+ | `Rec08` | `tla-7c24b693b5e0b1b7` | `Standard_Time_Lapses/2026-06-27.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec08.mp4` |
30
+ | `Rec09` | `tla-b2a9605d96f75681` | `Standard_Time_Lapses/2026-06-28.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec09.mp4` |
31
+ | `Rec10` | `tla-ee49c418e6c9f5b5` | `Standard_Time_Lapses/2026-06-28.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec10.mp4` |
32
+ | `Rec11` | `tla-8efbed822da34f95` | `Standard_Time_Lapses/2026-06-29.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec11.mp4` |
33
+ | `Rec12` | `tla-574fff5c21f270d7` | `Standard_Time_Lapses/2026-06-29.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec12.mp4` |
34
+ | `Rec13` | `tla-2b8fe7306bd03e4e` | `Standard_Time_Lapses/2026-06-29.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec13.mp4` |
35
+ | `Rec14` | `tla-9929071f366b1e04` | `Standard_Time_Lapses/2026-06-30.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec14.mp4` |
36
+ | `Rec15` | `tla-948a77db69a90bb8` | `Standard_Time_Lapses/2026-06-30.UnknownTime.FountainPen.Ink.IllustrationBoard.30x40.Rec15.mp4` |
37
+
38
+ This relationship is intentionally narrower than a complete fragment-sequence
39
+ packet. The dates and literal `UnknownTime` path values are retained as existing
40
+ file-level labels; they do not establish a shared finish date or time. This note
41
+ does not assert raw-source status, uninterrupted capture, internal recording or
42
+ session boundaries, or overall completeness. It does not create a global
43
+ `work_id`, change blank `provenance_status` values, alter acquisition-protocol
44
+ assignments, or add these files to prospective-fragment or timing cohorts.
Standard_Time_Lapses/Provenance/README.md CHANGED
@@ -28,6 +28,15 @@ Relationship sidecars can group those objects without merging their persistent
28
  The active correction resolves that label to `14:13`, for which the same
29
  retained final MP4 boundary is 21 seconds later.
30
 
 
 
 
 
 
 
 
 
 
31
  ## Dated layers
32
 
33
  - [`2026-07-31/`](2026-07-31/) preserves historical filename-to-record mappings
 
28
  The active correction resolves that label to `14:13`, for which the same
29
  retained final MP4 boundary is 21 seconds later.
30
 
31
+ ## Historical relationships
32
+
33
+ - [`Historical_Relationships/2026-06-18--2026-06-30-fountain-pen-30x40.md`](Historical_Relationships/2026-06-18--2026-06-30-fountain-pen-30x40.md)
34
+ records Tim's confirmation that 15 existing June 2026 files document one
35
+ physical drawing and that `Rec01`-`Rec15` establishes file order. It does not
36
+ assert internal recording or session boundaries, overall completeness, or a
37
+ shared finish date/time, and it remains separate from the complete
38
+ fragment-sequence packets below.
39
+
40
  ## Dated layers
41
 
42
  - [`2026-07-31/`](2026-07-31/) preserves historical filename-to-record mappings