Datasets:

---

maxwellinked

/

time-lapse-artifacts

Like 3

Summary

Draft ingest of one creator-confirmed complete drawing represented by 23
unchanged Framelapse source recordings.

• Canonical stem: 2026-09-17.1140.Pencil.Graphite.FountainPen.Ink.Paper.9x12
• Sequence: Rec01 through Rec23
• Group finish label: September 17, 2026 at 11:40 (creator-supplied local label)
• Source payload: 10,419,300,996 bytes; 2,010.846325 encoded seconds
• Frame receipts: 60,326 container-declared/stored packets and 60,325
  presentation-read/decoded frames
• Materials: Pencil and FountainPen / Graphite and Ink / Paper / 9x12

The 11:40 value is the creator-supplied completion label for the whole drawing,
not an individual fragment end time. RecNN records chronological source order
only. Exact transferred filenames remain in original_filename; filename,
container, and filesystem times remain separate audit observations. The 22
literal VID_* sources are followed by the descriptively named final clip as
Rec23, even though that filename sorts alphabetically first.

This is the first relationship packet for the September 17 calendar date, at
Standard_Time_Lapses/Provenance/2026-09-17/. All earlier provenance packets
remain byte-identical.

Verification plan

The local audit passed 23/23 ordinary SHA-256 checks, 23/23 full HEVC decodes,
and 69/69 sampled frame decodes with zero decoder errors. Rec05 has 4,291
container-declared/stored frames and 4,290 presentation-read/decoded frames.
Its single MP4 edit list begins at media time 3000 on a 1/90000 time base,
omitting one 1/30-second stored sample from presentation. This is a documented
presentation-timeline trim, not payload corruption; no exception is accepted
for any other source. All originals remain untouched.

Publication is staged so Hub Xet identities are captured only after media
upload. The relationship sidecar will then pin a distinct immutable
metadata-bearing revision, avoiding circular self-reference. The final
candidate must pass metadata, checksum, relationship, timing-compatibility,
exact-scope, and full regression gates before merge.

This remains a draft during assembly and validation. No tag, release, mirror
update, deployment, or source cleanup is included in this pull request.