Define prospective fragment-sequence protocol boundary
#46
by maxwellinked - opened
Summary
- define
standard-2025-07-13as the earlier Standard workflow - define
standard-2026-08-27as the prospective canonical fragment-sequence workflow - apply the prospective version only to the 186 canonical
record_idvalues listed in the six datedfragment_sequence_relationships.csvsidecars from 2026-08-27 through 2026-09-02 - retain
standard-2025-07-13for the 19 historical RecNN rows outside those sidecars - document and validate that every RecNN member of one prospective grouping shares the finish date and time of the complete grouping/physical work; RecNN records chronological group position, not an individual fragment end time
- extend metadata and semantic validation for the focused boundary
Preserved invariants
- no MP4 was modified, renamed, moved, uploaded, or re-encoded
- no
record_id, file path,hub_xet_hash,size_bytes, technical field, or provenance relationship changed - no fragment relationship sidecar changed
SHA256SUMSis byte-identical
Validation
- regression suite: 35/35 passed
- metadata/protocol/current inventory: 0 errors; 363 earlier Standard rows and 186 prospective rows
- six current fragment relationship joins: 0 errors; 186 canonical fragments across 25 groupings
- six pinned-revision relationship receipts: 0 errors
- checksum coverage: 0 errors; 683 payloads, including 682 MP4 and one ZIP
- physical-reference relationships: 0 errors; 309 unique record relationships
- protected-field audit: 186 protocol cells changed; all other metadata fields unchanged
This PR is intentionally left as a draft pending exact remote-head review and separate merge authorization.
Publishing after exact-head, conflict, remote-tree, and validation checks; merge explicitly authorized by the repository owner.
maxwellinked changed pull request status to open
Merging after exact-head validation: base 9cfe7996247900b3b3f69ef3cc78cf54ce734266, reviewed PR head ba99777d0fc11accb3b236b4820c08e9a13891a0, zero conflicts, identical reviewed tree, and all validation suites passing.
maxwellinked changed pull request status to merged