README.md

metadata

title: Substrate Video Atomization Runtime
emoji: 🎞️
colorFrom: blue
colorTo: indigo
sdk: gradio
sdk_version: 4.44.1
python_version: 3.11
app_file: app.py
pinned: false
license: cc-by-nc-sa-4.0
short_description: Atomized video transfer with source-return receipt
thumbnail: assets/social_card.png

Substrate Video Atomization Runtime v0.1.1

Upload a short video and run a source-bound atomization route. v0.1.1 adds browser-safe preview rehydration, social-card metadata, and Data Hologram Structure v0.2.

This Space demonstrates Video Atomization, Trace-Stack Rehydration, and source-bound Data Hologram formation as a Substrate Mesh runtime surface. The uploaded video is not treated as a monolithic compressed payload. Instead, the runtime hashes the source, samples frame atoms, detects scene intervals, records motion deltas, applies trace capsules, stacks the traces, carries provenance as part of the data, and returns a rehydrated review surface with an HIR × OAM receipt.

The demo shows how video can become a pressure-readable temporal mesh:

source video
→ source capsule
→ frame atoms
→ motion atoms
→ scene atoms
→ trace capsules
→ source-bound data hologram v0.2
→ rehydrated review surface
→ HIR × OAM receipt
→ human validation capsule

Operating law:

media pressure → atom gate → frame/scene/motion capsule → transfer route → rehydration surface → receipt → human validation / memory readiness

Boundary

This is not video compression, not a replacement for codecs, and not a physical hologram generator. This v0.1.1 Space demonstrates atomized transfer, source-return rehydration, provenance-aware receipts, and a source-bound data-hologram review layer. Physical hologram translation would require a later optical modulation layer.

Core boundary:

SOURCE_VIDEO_REMAINS_AUTHORITY
PROVENANCE_IS_PART_OF_THE_DATA
REHYDRATION_SURFACE_ONLY
HUMAN_VALIDATION_REQUIRED

What the demo proves

• The source video is hashed and held as the canonical anchor.
• The video is atomized into source-bound frame and scene atoms.
• Each sampled atom receives a trace capsule.
• Trace capsules are stacked into a Data Hologram v0.2 manifest.
• Provenance is carried as part of the data, not as a detachable afterthought.
• The rehydrated output remains a review surface, not a source replacement.
• Human validation remains required before settlement.

Core claim

Video does not have to be handled only as a compressed monolithic file. It can be atomized into source-bound trace units, stacked into a data hologram, pressure-read, and rehydrated into a reviewable route surface.

Runtime compatibility patch

This Space pins the Python runtime to 3.11 because Python 3.13 removed the stdlib audioop module used indirectly by Gradio's audio/video processing path through pydub. The requirements also include audioop-lts as a fallback compatibility shim.

Runtime compatibility patch 2

This packet pins huggingface_hub==0.25.2 because Gradio 4.44.x can import HfFolder during startup. Newer huggingface_hub releases can remove that export path, causing ImportError: cannot import name 'HfFolder' from 'huggingface_hub'.

Runtime compatibility patch 3

This packet removes type="filepath" from the gr.Video(...) upload component because Gradio 4.44.x rejects that keyword on Video.__init__. The callback still receives the uploaded video path, so the source-bound atomization route is unchanged.

Social card / X preview

This packet includes assets/social_card.png and declares it in the Space README front matter as:

thumbnail: assets/social_card.png

The image is a 1200 × 630 social-card render for link preview surfaces. It is display metadata only; it does not alter runtime atomization, trace stack, receipt, preview, or packet logic.

Data Hologram Structure v0.2

This packet adds manifests/source_bound_data_hologram_v0_2.json to every run packet.

The structure includes:

• Runtime Trail loop law
• Resonant Ingress trace law
• source-return boundary
• provenance survival state
• anti-laundering rules
• memory-readiness boundary
• human-validation questions

Review question set:

What arrived?
What held?
What degraded?
What provenance survived?
What needs repair?
What still requires human validation?

Reference documents

This release includes local reference docs under docs/:

• DATA_HOLOGRAM_STRUCTURE_v0_2.md
• runtime_trail_robot_day_loop_v0_1_reference.html
• resonant_ingress_v0_1_1_reference.txt