Add reviewed physical-reference relationship layer (#29)

- Add reviewed physical-reference relationship layer (b7372af00fb899f178470619ad4d7eca1fcfd362)

Archive_Specifications.md

@@ -17,13 +17,19 @@ post-processing history.
 
 ## Capture Configuration
 
-The documented standard acquisition intent is:
+The owner-confirmed default workflow since July 13, 2025 is:
 
-- Capture orientation: Landscape
+- Device: Samsung Galaxy S23 Ultra, model `SM-S918U`
+- Application: Framelapse 2; observed current version 11.7
+- Logical camera: Rear (Main), 1.8x
+- Nominal capture interval: 0.2 seconds
+- Capture orientation intent: Landscape
 - Capture resolution class: 2160p UHD (4K)
 - Still-image size: 4000 × 3000
-- Exposure: Locked
-- White balance: Locked
+
+AE/WB lock, autofocus, and stabilization are owner-reported for certainly the
+majority of this period, not confirmed as universal per-record facts. Deviations
+must be recorded prospectively and must not be filled retrospectively by guess.
 
 ### Capture versus published encoding
 
@@ -36,6 +42,19 @@ landscape sources.
 Do not infer a rotation, crop, or transcode solely from dimensions. Such a
 transformation should be asserted only when supported by provenance evidence.
 
+### Acquisition evidence and canonical assembly
+
+Framelapse source fragments are retained unchanged as acquisition evidence. One
+verified chronological InShot assembly remains the canonical media object for
+each drawing record. Dynamic browser previews and physical-reference photographs
+are noncanonical access or evidence layers linked through persistent identity.
+
+A 2160 × 3840 portrait H.264, 30-fps InShot processing profile is documented as
+a candidate. It does not become a canonical protocol boundary until one complete
+natural drawing passes fragment-order, join, duration, stream, hash, and manifest
+verification and receives explicit creator approval. Existing 60-fps canonical
+records remain unchanged.
+
 ## Timing and Calibration Status
 
 The current protocol documentation does not yet provide a complete calibrated

Physical_References/CAPTURE_AND_INGEST_PROTOCOL.md

@@ -0,0 +1,129 @@
+# Candidate Capture and Ingest Protocol
+
+Status: documented candidate; requires an explicitly approved first natural
+record before becoming a canonical processing-profile boundary.
+
+## Authority model
+
+1. **Framelapse source fragments** are acquisition evidence. Preserve them
+   unchanged with original filename, byte size, duration, stream properties,
+   order, and SHA-256.
+2. **One chronological InShot assembly** remains the canonical public media
+   object for a drawing record.
+3. **Dynamic browser previews** are noncanonical access derivatives bound to
+   `record_id`, integrity identity, and a pinned source revision.
+4. **Drawing-reference photographs** are separate noncanonical physical-state
+   evidence linked through the sidecar only after review.
+
+Making every Framelapse fragment a canonical row would change the archive's
+unit of observation from one drawing record to an editing fragment. This
+candidate rejects that change.
+
+## Current documented acquisition profile
+
+The following is supported for the current workflow but must not be silently
+applied to every historical file:
+
+- device: Samsung Galaxy S23 Ultra, model `SM-S918U`
+- current documented environment: Android 14 / One UI 6.1
+- application: Framelapse 2, observed version 11.7
+- logical camera: Rear (Main), owner-confirmed at 1.8x since 2025-07-13
+- interval: 0.2 seconds; nominal capture metadata: 5 captures per real-world second
+- current controls: AE/WB lock, autofocus, and stabilization
+- source class: 2160p UHD/4K HEVC; tested source files have no audio stream
+
+Retrospective boundary: AE/WB lock, autofocus, and stabilization are
+owner-reported for certainly the majority since 2025-07-13, not confirmed for
+every record. Exact physical sensor/lens, camera-to-paper distance, angle,
+lighting geometry, and spatial calibration remain unresolved.
+
+The nominal five-captures-per-second tag is not proof of a perfectly calibrated
+time base, zero jitter, or zero dropped capture moments.
+
+## Candidate processing profile
+
+- application: InShot, observed version 2.222.1548
+- assemble source fragments in verified chronological order
+- export 2160 x 3840 portrait MP4, H.264 High, 30-fps encoded playback
+- no intentional trimming, speed change, crop, filter, transition, inserted
+  frame, or reordering
+- no soundtrack or intentional audio; verify the stream because tested InShot
+  exports add an encoded silent AAC track
+- preserve every Framelapse source fragment unchanged
+- never re-encode the existing 60-fps corpus simply for uniformity
+
+Controlled testing found that the 30-fps InShot output removed systematic
+duplicate-frame pairs present in the tested 60-fps export and reduced assembled
+file size by about half. It did not increase the underlying real-world sampling
+rate. This remains a candidate until a naturally produced drawing passes the
+full gate below.
+
+## Daily ritual: create, record, preserve, assemble, verify, ingest, repeat
+
+### Create
+
+Make the drawing. Record only deviations that would otherwise be forgotten;
+do not interrupt the practice to classify the archive.
+
+### Record
+
+Use the documented Framelapse profile. Multiple chronological fragments are
+acceptable when needed.
+
+### Preserve
+
+Retain every fragment unchanged before assembly. Never rename or transcode the
+only copy. Record original filename, bytes, duration, streams, and SHA-256.
+
+### Assemble
+
+Place fragments in observed chronological order in InShot. Apply the candidate
+4K/30-fps profile without presentation edits.
+
+### Verify
+
+Confirm all expected fragments occur exactly once, order is correct, joins
+omit nothing and add no transition, output duration agrees with the source sum,
+output properties match the candidate profile, and source fragments remain
+unchanged.
+
+### Manifest
+
+Write one assembly manifest with `record_id`, ordered fragment identities,
+source/output hashes, capture and processing settings, software versions,
+evidence state, and explicit nulls for unresolved variables.
+
+### Ingest
+
+Upload only the reviewed InShot assembly as canonical record media with the
+normal 29-field metadata row. Keep detailed fragment relationships in a
+separate manifest. Ingest physical-reference photographs only as noncanonical
+linked media with their own hashes and privacy review.
+
+### Derive
+
+Generate previews only from the reviewed canonical record and bind them to
+`record_id`, an integrity reference, and the pinned source revision.
+
+### Repeat
+
+Begin the next drawing. Version the protocol only when the change is intentional
+and documented.
+
+## Promotion gate
+
+The 4K/30-fps candidate becomes canonical only after:
+
+1. one complete drawing is naturally produced under this workflow;
+2. its complete fragment set and assembly pass verification;
+3. a finalized manifest binds all sources to the assembly;
+4. the creator explicitly approves the result and boundary date;
+5. archive specifications and the README are updated;
+6. existing 60-fps records remain documented and unchanged.
+
+## Privacy gate
+
+Public derivatives must exclude phone numbers, serial numbers, IMEIs, precise
+location metadata, and other private device/account identifiers. Original setup
+photographs with GPS metadata are not publication-safe without metadata removal
+and visual review.

Physical_References/MANIFEST.json

@@ -0,0 +1,40 @@
+{
+  "layer_name": "physical-reference-relationships-v0.1",
+  "release_state": "reviewed_relationship_table_reference_media_not_bundled",
+  "created_date": "2026-08-26",
+  "dataset_id": "maxwellinked/time-lapse-artifacts",
+  "source_hub_revision": "ba7e7903901767f2d5a4367d7ae22c2546366d6d",
+  "canonical_metadata_path": "metadata.csv",
+  "sidecar_path": "Physical_References/endpoint_references.csv",
+  "sidecar_sha256": "f0071876769ed4d90ba577ce76535cdc62b44ab27b5a1c575c2542eb60b62152",
+  "schema_path": "Physical_References/SCHEMA.md",
+  "capture_protocol_path": "Physical_References/CAPTURE_AND_INGEST_PROTOCOL.md",
+  "canonical_schema_field_count": 29,
+  "record_identity": "record_id",
+  "reference_identity": "reference_id",
+  "reference_media_bundled": false,
+  "internal_review_ledgers_bundled": false,
+  "counts": {
+    "standard_records_at_source_revision": 363,
+    "owner_confirmed_reference_links": 309,
+    "standard_records_without_current_reference_link": 54,
+    "relationship_types": {
+      "endpoint_photograph": 52,
+      "longitudinal_continuation": 1,
+      "owner_confirmed_record_reference": 232,
+      "two_sided_work_reference": 24
+    },
+    "reference_image_hash_state": {
+      "missing": 13,
+      "present": 296
+    }
+  },
+  "review_basis": "Owner-confirmed visual audit against canonical videos and retained physical-reference photographs; supporting review ledgers remain local and are not public dataset records.",
+  "limitations": [
+    "Reference photographs are not bundled in version 0.1 and are not downloadable from the Hub.",
+    "The table does not create frame labels, calibrated trajectories, or an official benchmark split.",
+    "Encoded playback rate is not real drawing time.",
+    "Exact temporal endpoint equivalence is asserted only where endpoint_claim_state supports it.",
+    "The corpus represents one creator and must not be generalized broadly without external validation."
+  ]
+}

Physical_References/SCHEMA.md

@@ -0,0 +1,83 @@
+# Physical Reference Sidecar Schema
+
+## Contract
+
+`Physical_References/endpoint_references.csv` is a derived relational sidecar. It is not a third
+canonical media index and it does not modify the 29-field video metadata
+contract. Join it to `metadata.csv` on `record_id` after pinning both artifacts
+to the same repository revision.
+
+Each row represents one active, owner-confirmed relationship between a
+canonical Standard video record and a photographed state or side of a physical
+work. Version 0.1 has one row per linked `record_id`.
+
+## Identity fields
+
+| Field | Type | Meaning |
+| --- | --- | --- |
+| `reference_id` | string | Stable derived identity: `tlar-` plus 16 lowercase hex characters. |
+| `record_id` | string | Persistent canonical video identity. |
+| `canonical_file_name` | string | Repository-relative video path at `source_hub_revision`. |
+| `source_hub_revision` | 40-char hex | Exact Hub revision used for the join. |
+
+## Record context
+
+`record_date`, `record_time`, `dimensions`, `tool`, `medium`, and `support` are
+copied from the pinned canonical metadata for review convenience. They must not
+be independently edited in the sidecar. Blank time remains unknown.
+
+## Reference fields
+
+| Field | Type | Meaning |
+| --- | --- | --- |
+| `reference_image_filename` | string | Source photograph filename; descriptive, not identity. |
+| `reference_image_number` | string | Retained source number token. |
+| `reference_image_role` | enum-like string | Literal role from the reviewed owner ledger. |
+| `paired_image_filename` | string or blank | Associated back/opposite-side evidence when present. |
+| `reference_image_sha256` | hex or blank | SHA-256 only when found in a current source ledger. |
+| `paired_image_sha256` | hex or blank | SHA-256 only when found in a current source ledger. |
+| `hash_state` | string | Explicit complete, missing, or conflict state. |
+| `source_photo_collection` | semicolon list | Local source-ledger origin, not a public URL. |
+
+## Relationship fields
+
+| Field | Meaning |
+| --- | --- |
+| `relationship_type` | Conservative relationship category derived from explicit evidence. |
+| `surface_scope` | Front, side A/B, unresolved side, or later front state. |
+| `temporal_scope` | Whether endpoint, longitudinal, or temporally unspecified. |
+| `endpoint_claim_state` | Explicitly states whether an endpoint claim is supported. |
+| `pairing_state` | State of the associated paired/back image. |
+| `owner_confirmation_state` | Owner-confirmed record link in every current row. |
+| `evidence_state` | Lossless semicolon list copied from the active mapping ledger. |
+| `owner_evidence` | Human-readable creator confirmation. |
+| `paired_image_evidence` | Human-readable reverse/back qualification. |
+
+Allowed `relationship_type` values in this candidate:
+
+- `endpoint_photograph`
+- `endpoint_side_reference`
+- `longitudinal_continuation`
+- `owner_confirmed_record_reference`
+- `two_sided_work_reference`
+
+`longitudinal_continuation` must never be used as exact endpoint supervision.
+Two-sided relationships must not be collapsed into one assumed visual surface.
+
+## Media availability
+
+`reference_media_availability` is `local_evidence_only_not_bundled_v0.1`.
+Photographs are not downloadable in this release. The two proposed-path
+columns are intentionally blank and must not be interpreted as Hub paths.
+
+## Missing values
+
+Blank means unknown, not documented, unavailable in current ledgers, or not
+applicable. It never means zero or false. Do not fill missing hashes, timestamps,
+side roles, or temporal states by visual guess.
+
+## ML boundary
+
+`machine_use_scope` and `caution` describe supported selection/alignment uses.
+They are not task labels, training splits, performance claims, or permission to
+treat encoded video time as physical drawing time.

README.md

@@ -484,10 +484,31 @@ guaranteed. See `SCHEMA.md`.
 `encoded_frame_rate` is encoded playback rate. It is not the original temporal
 sampling rate of the drawing process.
 
+### Physical-reference relationship layer
+
+[`Physical_References/endpoint_references.csv`](Physical_References/endpoint_references.csv)
+links 309 Standard video records to owner-confirmed photographs of their
+physical drawings through persistent `record_id` values and the pinned source
+revision. It is a separate derived relationship table and does not alter the
+29-field canonical video index.
+
+Version 0.1 records 52 confirmed endpoint photographs, one longitudinal
+continuation, 232 owner-confirmed record references whose exact endpoint state
+is not separately asserted, and 24 two-sided references. The photographs are
+not bundled in this release. Their reviewed filenames and available hashes
+preserve relationship evidence without implying that the media are publicly
+downloadable. See the [sidecar schema](Physical_References/SCHEMA.md) and
+[manifest](Physical_References/MANIFEST.json).
+
 ## Acquisition and Stored-Video Orientation
 
 The acquisition protocol effective July 13, 2025 is documented in
-`Archive_Specifications.md`.
+`Archive_Specifications.md`. Framelapse source fragments remain unchanged
+acquisition evidence, while one verified chronological InShot assembly remains
+the canonical media object for each drawing record. A documented 4K/30-fps
+processing profile remains a candidate and does not retroactively redefine
+existing records. See the
+[capture and ingest protocol](Physical_References/CAPTURE_AND_INGEST_PROTOCOL.md).
 
 The protocol's capture orientation and a file's stored pixel orientation are
 different concepts. The `orientation`, `width_px`, and `height_px` metadata

SCHEMA.md

@@ -179,6 +179,27 @@ Observed evidence methods include:
 
 New enumerated values must be documented here before use.
 
+## Physical-reference sidecar
+
+`Physical_References/endpoint_references.csv` is an optional derived
+relationship table joined to the canonical Standard index on `record_id`. It
+must declare the exact `source_hub_revision`; it does not determine canonical
+video status or duplicate editable video metadata.
+
+Each row has a stable `reference_id`, reviewed photograph filename and role,
+explicit surface and temporal scope, evidence state, hash state, and machine-use
+caution. Blank values mean unknown or not documented. Version 0.1 does not
+bundle the reference photographs, and blank proposed-path fields must not be
+interpreted as public media locations.
+
+`longitudinal_continuation` identifies a later or otherwise changed physical
+state and is not an exact endpoint target. Two-sided references preserve
+side-specific evidence and do not imply one shared visual target. Validators
+must require unique identities, canonical filename agreement at the pinned
+revision, allowed relationship values, explicit owner-confirmation state, and
+valid SHA-256 syntax whenever a hash is present. The complete contract is in
+[`Physical_References/SCHEMA.md`](Physical_References/SCHEMA.md).
+
 ## Missing-Value Rules
 
 - Blank means unknown, not documented, or not applicable according to the field