README.md

metadata

title: Holographic Trace Stack Reassembly Harness
emoji: 🧬
colorFrom: indigo
colorTo: blue
sdk: gradio
sdk_version: 6.5.1
app_file: app.py
pinned: false
license: cc-by-nc-sa-4.0
short_description: Trace-stack proof for reassembling atomized source data
thumbnail: >-
  https://huggingface.co/spaces/HirModel/holographic-trace-stack/resolve/main/assets/holographic_trace_stack_x_card.png

Holographic Trace Stack Reassembly Harness

Stack the traces. Reassemble the account.

Version: v0.2.0

This is a standalone Hugging Face Gradio Space proof harness for testing whether atomized source traces can be stacked midstream to reassemble a coherent, honest account of a source.

Boundary

This is not optical holography.

This is not a 3D hologram.

This is not a cinematic visual engine.

This is not a live mycelium/geometry renderer.

The phrase holographic dataset means one trace object can be projected through multiple accountable views:

• source view
• atom view
• timeline view
• object continuity view
• motion route view
• pressure state view
• receipt view
• reassembly view

The harness does not claim full source truth. It evaluates trace support, route integrity, source-return, boundary respect, and receipt quality.

Core thesis

If a source is atomized into trace-bearing components, and those traces preserve enough relational structure, then the system can stack the traces midstream and reassemble a coherent account of the source without relying on the original surface form alone.

Core route

source
→ atomization
→ trace capsule
→ holographic dataset
→ trace stack
→ midstream reassembly
→ reprojected dataset
→ receipt

v0.2 update

v0.2 keeps the v0.1 bounded synthetic proof harness stable and adds a scoped forensic layer for live inspection:

• per-contribution score breakdown
• weighted support panel
• compact motion-route segment ledger
• color-coded route statuses
• segment-level coverage and return contribution
• affected atom IDs
• receipt-facing reason line for each segment

The new motion-route ledger converts motion_route_score from a single number into an inspectable route-integrity map.

Segment states:

• returned — motion segment points back to the expected prior frame/object state
• missing — expected motion atom is absent
• shuffled — stack order or return route is out of expected sequence
• reversed — route direction is inconsistent
• conflicting — source/hash identity conflict touches the segment

Color convention in the UI:

• green = returned
• amber = shuffled / reversed
• red = missing / conflicting

What the harness proves

The harness starts with controlled synthetic sources rather than arbitrary user video. This gives ground truth and makes the proof measurable.

Synthetic examples include:

• moving circle
• moving square
• color changes
• frame order
• object identity
• motion path
• optional occlusion
• optional missing frame

The source is atomized into trace packets:

• frame atoms
• object atoms
• edge / shape atoms
• color atoms
• motion atoms
• time atoms
• source-return atoms
• receipt atoms

Required tests

The built-in validation runner executes all six required tests:

1. FULL_STACK_REASSEMBLY
2. PARTIAL_STACK_REASSEMBLY
3. SHUFFLED_TRACE_TEST
4. MIXED_SOURCE_FALSE_STACK
5. ROUND_TRIP_TEST
6. CROSS_PROJECTION_TEST

Metrics

The cockpit reports:

• source_return_score
• trace_completeness_score
• temporal_continuity_score
• object_continuity_score
• motion_route_score
• reassembly_confidence
• false_settlement_risk
• pressure_state

v0.2 also exports:

• contribution_breakdown
• motion_route_diagnostics
• per-segment coverage delta
• per-segment return delta
• per-segment weighted contribution
• per-segment receipt line

Pressure and boundary states

Possible states:

• HELD
• REASSEMBLED
• STRAINED
• REPAIRING
• CONFLICT
• QUARANTINED
• MUST_STOP
• CLOSED_FOR_CURRENT_SCOPE

The system must not falsely claim clean reassembly when trace support is incomplete, shuffled, mixed, missing, or corrupted.

Files

Required Hugging Face Space root files:

• app.py
• requirements.txt
• runtime.txt
• README.md

Additional release files:

• VALIDATION_REPORT.json
• VALIDATION_REPORT.md
• package .zip
• package .sha256

Local validation

Run:

python -m py_compile app.py
python -c "import app"
python - <<'PY'
import app
report = app.run_required_tests()
print(report['required_tests_run'])
print(report['summary'])
PY

Expected: all six tests run and return explicit receipt-bearing states. Partial, shuffled, and mixed-source conditions should mark strain, repair, conflict, quarantine, or refusal rather than false closure.

License

cc-by-nc-sa-4.0