CoolFace
Apppublic

HirModel/pressure-adaptive-provenance-substrate-simulator

sourceHugging Facecc-by-nc-sa-4.0updated 3mo agoView on Hugging Face
0likes
App README

Pressure-Adaptive Provenance Substrate Simulator v0.2.1

Created and Developed by Collin D. Weber Primordial Calculus / HIR-OAM Systems Architect / Systems Integrity Steward

Purpose

This static Hugging Face Space is an interactive reviewer console for a pressure-adaptive provenance substrate.

It integrates:

text
PDF / Adobe-style document workflow
→ C2PA / provenance signal
→ Trace Capsule
→ Loop-Gated OAM pressure read
→ Linux / open verification logic
→ Digital Mycelium repair routing
→ Source-return / honest closure

The simulator demonstrates how provenance-bearing documents and media can move through a repair-capable substrate without becoming a brittle trust chain.

v0.2.1 polish upgrades

  • —Adds Closure status as a separate receipt field.
  • —Adds State movement to make transitions visible.
  • —Separates active Trace Capsule state from bounded closure decision.
  • —Refines Scenario 1 so the trace is HELD before it is CLOSED FOR CURRENT SCOPE.
  • —Updates Copy Receipt Markdown with the new fields.
  • —Updates local-only PDF receipts with Trace Capsule state, Closure status, State movement, and Final capsule.
  • —Clarifies HELD and CLOSED FOR CURRENT SCOPE legend language.

Existing v0.2 capabilities

  • —Interactive flow map with scenario-driven node states.
  • —Live Trace Capsule receipt panel.
  • —Eight scenario presets.
  • —Run All Scenarios / Previous / Next controls.
  • —Always-visible loop-state legend.
  • —Copy Receipt Markdown button.
  • —Local-only PDF upload receipt with SHA-256 hash and limited static marker scan.
  • —Header boundary badge: public review simulator, no endorsement claim, no authenticity certification.

Live PDF demo boundary

The PDF upload mode is local-only. It reads file bytes in the browser, computes SHA-256, checks limited PDF markers and visible metadata/provenance strings, and generates a bounded receipt.

It does not:

  • —upload or store the PDF,
  • —execute PDF content,
  • —certify authenticity,
  • —prove document truth,
  • —replace C2PA validation tools,
  • —replace PDF forensics,
  • —replace legal, journalistic, cybersecurity, scientific, or domain review.

If provenance is not detected by the limited static scan, the simulator reports that provenance was not detected in this limited static demo. It does not claim that no provenance exists.

Loop states

  • —HELD — trace is coherent enough to handle within current boundary.
  • —STRAINED — pressure or uncertainty is present; do not overclaim.
  • —ENCAPSULATED — preserve trace; pause interpretation until repair.
  • —REPAIRING — source-return, boundary, consent, or provenance repair is underway.
  • —REOPENED — previously strained trace is usable after repair.
  • —FALSE CLOSURE RISK — system is treating the loop as closed before support exists.
  • —CLOSED FOR CURRENT SCOPE — bounded closure for the current reviewed evidence only; not universal validation.
  • —MUST STOP — unsafe, unsupported, unauthorized, or unreviewable under current conditions.

Non-claim boundary

This is an independent public review simulator. It does not claim endorsement, adoption, approval, certification, production security, C2PA validation authority, Adobe implementation, Linux Foundation adoption, or internal system knowledge.

It is not an authenticity validator. It is not a truth machine. It is not a production security tool.

Core statement

HELD is not the same as closed. Closed is not universal. Closure is always bounded by current scope, current evidence, source-return, and repair state.

The chain does not survive by becoming harder. It survives by becoming accountable, adaptive, repairable, source-returning, and pressure-literate.

User guide

See USER_GUIDE.md for reviewer-facing usage instructions, scenario walkthrough, local PDF upload boundary, state meanings, and recommended demo script.