README.md

---
title: Loop-Gated OAM Pressure Engine
emoji: 🧭
colorFrom: blue
colorTo: indigo
sdk: static
app_file: index.html
pinned: false
license: cc-by-nc-sa-4.0
thumbnail: social-card.png
short_description: Reviewer workflow authority map
tags:
  - static
  - digital-forensics
  - evidence-review
  - dfir
  - topology-map
  - forensic-adapters
  - firmware
  - drivers
  - resource-burden
  - sonification
  - auditory-review
  - symphonic-fingerprint
  - oam
  - pressure-review
  - provenance
  - media-provenance
  - content-authenticity
  - c2pa
  - source-return
  - media-integrity
---
# Loop-Gated OAM Pressure Engine

![Loop-Gated OAM Pressure Engine](social-card.png)

Offline forensic and media provenance comparison with reviewer workflow onboarding: external report adapters, reverse-backtrace pressure read, replayable topology map, symphonic pressure fingerprinting, source-return/transformation pressure mapping, differential source-return comparison, extraction bundles, dual-time topology, authority movement mapping, claim-boundary review, and bounded receipt console.


## v0.3.2.4.15.2.40 — Reviewer Workflow + Authority Movement Onboarding Patch

This package immediately extends v0.3.2.4.15.2.39.1. It makes no detector, harness, route, topology, symphonic, media provenance, or comparator logic changes.

The patch adds a reviewer workflow layer that makes the current engine easier for outside reviewers to enter without weakening the claim boundary.

Core workflow:

```text
evidence -> topology -> comparator -> pressure state -> claim boundary -> authority movement -> receipt
```

Core lockline:

```text
Documentation is not repair. Escalation is not repair. Awareness is not repair. Repair begins when authority moves.
```

New UI / runtime surfaces:

1. Start Here / Reviewer Workflow + Authority Movement section.
2. 30-second workflow diagram from evidence to receipt.
3. Reviewer mode selector for DFIR/cybersecurity, media provenance/C2PA-adjacent review, creator/artist protection, Little Wren parked preview, legal/compliance, and research/academic review.
4. Low-context domain entry panel asking what happened, who saw it first, who received the signal, who can act, where authority is blocked, what is being treated as closure, and what actual repair requires.
5. Authority Movement Map with signal owner, evidence holder, decision authority, repair authority, blocked authority, and handoff route.
6. Comparator Quickstart explaining Artifact A, Artifact B, anchor matrix, extraction bundle, and comparative receipt export.
7. Plain-language glossary for OAM, HIR, settlement, source-return, extraction bundle, and dual-time topology.
8. Parked Little Wren bridge card that acknowledges child-safety relevance while keeping the operational child-protection layer parked for proper scoped implementation.

Boundary: this patch does not crawl platforms, call external APIs, execute files, modify systems, determine legal status, confirm theft/infringement/authorship/source-origin/AI-generation/plagiarism/deception/intent/guilt, claim C2PA certification, operationalize child-safety monitoring, handle unsafe material, or replace human review, legal process, platform trust-and-safety teams, forensic analysts, or lawful authorities.

## v0.3.2.4.15.2.39.1 — Active Receipt + README Current-Surface Closure Patch

This package immediately extends v0.3.2.4.15.2.39. It makes no functional engine, comparator, topology, symphonic, detector, harness, route, or media-provenance logic changes.

Closure scope:

1. Close final ZIP receipt drift by marking the v39 release guard ZIP integrity status as verified after final ZIP creation.
2. Move the current v39 comparator release surface to the top of the README so the active public release is encountered before retained history.
3. Add the v39.1 active receipt metadata, guard status/report, source inventory, and checksum ledger.
4. Preserve v39 Media Provenance Comparator / Source-Return Comparison behavior unchanged.
5. Preserve v38.1 Media Provenance Pressure Adapter, v37.1 Symphonic Pressure Fingerprint, v35 external evidence adapters, v34 topology map, bridge renderer, and claim-boundary/settlement logic.

Boundary: this is an active receipt and README current-surface closure only. It does not crawl platforms, call external APIs, execute files, modify systems, determine legal status, confirm theft/infringement/authorship/source-origin/AI-generation/plagiarism, claim C2PA certification, or alter detector/harness behavior.

## v0.3.2.4.15.2.39 — Media Provenance Comparator / Source-Return Comparison Layer

This release turns single-artifact media provenance review into bounded paired-artifact comparison. It adds side-by-side artifact rails, anchor-window alignment, extraction bundles, dual-time topology, unified overlay mapping, dimensional anchor matrices, differential inspector states, and a comparative receipt addendum.

Core lockline: the comparator preserves source chronology and presentation chronology at the same time. The source rail shows where fragments came from; the transformed rail shows how they were reassembled; the overlay shows the extraction route; the inspector explains what changed without overclaiming why.

Boundary: no platform crawling, no external APIs, no automatic plagiarism/copyright/AI-generation/theft/authorship/source-origin verdicts, no C2PA certification claim, and no legal determination.

## Retained release history

## v0.3.2.4.15.2.38.1 Media Provenance Pressure Adapter

This package immediately extends v0.3.2.4.15.2.37.1. It preserves detector logic, authored harness cases, expected route behavior, the Precision Forensic Dynamics Map, the external evidence adapters, the Symphonic Pressure Fingerprint + Auditory Review Console, the lexicon bridge, and receipt non-mutation boundaries.

The patch adds a bounded Media Provenance Pressure Adapter for safe local/static review of:

- videos and clips
- images
- audio / music
- PDFs and documents
- thumbnails, transcripts, captions, titles, and descriptions
- C2PA / content-credential-style provenance metadata
- rebranded news / synthetic-news style artifacts
- clipped, cropped, revoiced, repackaged, or source-stripped media

Core workflow:

```text
media artifact -> source-return topology -> transformation map -> operating-axiom inference -> claim boundary -> settlement state -> symphonic reference -> media provenance receipt addendum
```

Core lockline:

```text
A media artifact cannot honestly settle if it borrows authority while hiding its source-return chain.
```

New UI / runtime surfaces:

1. Media Provenance Pressure Adapter section in the root page.
2. Media intake lanes for video/clip, image, audio/music, PDF/document, C2PA/content credentials, and generic media metadata.
3. Source-return and transformation status fields.
4. Source/provenance, transformation/claim, and claim-under-review note fields.
5. Inferred operating-axiom panel.
6. Media topology nodes and edges for source-return, transformation, provenance, rebrand pressure, claim boundary, and settlement state.
7. Media map layers for media artifacts, source return, transformation path, C2PA/provenance, and rebrand/laundering pressure.
8. Media provenance receipt addendum export.
9. Four safe synthetic demos: rebranded news clip, creator work reuse, PDF claim drift, and clean provenance.
10. Symphonic bridge note preserving that audio is a cognition-translation and comparison aid only.

Boundary: this patch does not crawl platforms, call external APIs, prove copyright infringement, prove plagiarism, prove AI generation, prove theft, confirm authorship/source origin, determine legality, upload sensitive material, or claim C2PA certification. It can surface source-return gaps, provenance gaps, undeclared transformation, claim-boundary strain, rebrand pressure, media-laundering candidates, and human-review requirements.


## v0.3.2.4.15.2.37.1 Active Receipt Finalization Wording Closure

This package immediately extends v0.3.2.4.15.2.37. It makes no functional engine changes. It closes minor active receipt wording drift found during reverse backtrace and pressure read: the v37 release guard status still described ZIP integrity and JavaScript syntax checks as “pending finalization” after finalization had already completed, and contained a typo in the boundary string.

Closure scope:

1. Update active executable version surfaces to v0.3.2.4.15.2.37.1.
2. Replace pending-finalization wording with verified-after-finalization wording.
3. Correct the symphonic boundary typo.
4. Preserve the v37 Symphonic Pressure Fingerprint + Auditory Review Console behavior.
5. Preserve detector logic, authored harness cases, expected routes, topology adapters, lexicon bridge non-mutation behavior, social card, and external evidence adapter boundaries.

Boundary: this is an active receipt wording closure only. It does not add detector logic, alter route classification, modify evidence interpretation, claim malware proof, claim root-cause proof, search the internet, tune live systems, or modify files.


## v0.3.2.4.15.2.37 Symphonic Pressure Fingerprint + Auditory Review Console Foundation

This package immediately extends v0.3.2.4.15.2.36 social-card replacement and preserves v0.3.2.4.15.2.35 external evidence adapters. It adds a deterministic symphonic pressure fingerprint and auditory review console to the root page.

Symphonic workflow:

```text
topology / event frames -> pressure vector -> HIR/OAM tuning profile -> sonic sequence -> fingerprint hash -> JSON / CSV / MIDI addendum -> receipt surface
```

The symphonic foundation adds:

1. A Symphonic Pressure Fingerprint + Auditory Review Console in the root `index.html`.
2. Deterministic topology/event-frame to sound mapping.
3. HIR/OAM tuning sliders for the sonic rendering profile: honesty/source fidelity, integrity/route continuity, respect/boundary preservation, OAM pressure sensitivity, resource-burden sensitivity, and error-cascade sensitivity.
4. Playback through browser Web Audio.
5. JSON, CSV, and MIDI export of the generated sonic sequence.
6. A symphonic fingerprint hash derived from the pressure vector, tuning profile, and sonic sequence.
7. A topology addendum node for the symphonic fingerprint without mutating route state, evidence packet, or audit receipt hash.
8. A safe synthetic demo that converts the adapter cascade demo into a sonic fingerprint.

Boundary: this patch sonifies already-mapped evidence and topology. It does not prove malware, attribution, root cause, or external recurrence; does not modify files; does not tune live systems; does not search the internet; and does not transmit a resonant pulse. It is a deterministic auditory-review addendum for comparison, cognition translation, and review.


## v0.3.2.4.15.2.35 External Forensic Report + Driver / Firmware / Error / Resource Adapter Layer

This package immediately extends v0.3.2.4.15.2.34. It preserves the Precision Forensic Dynamics Map body and adds an external evidence adapter console for imported reports and files.

Adapter workflow:

```text
PE-sieve / THOR / AIDA64 / UWC / Windows error / driver / firmware evidence -> adapter findings -> topology nodes / edges / event frames -> root-pressure candidate -> claim boundary -> settlement state -> receipt addendum
```

The adapter layer adds:

1. PE-sieve report import for process/memory anomaly pressure such as injected regions, hooks, hollowing, shellcode, and dumped artifacts.
2. THOR / THOR Lite report import for IOC/YARA/known-issue pressure.
3. AIDA64 report import for host baseline, BIOS, hardware, OS, driver, and device context.
4. UWC resource-burden import for compute/thermal/power/cooling-proxy burden fingerprints and cost-of-burden candidates.
5. Windows Event / WER / error export import for cascade origin mapping.
6. Driver / driver-package upload for static driver evidence and driver root-pressure candidates.
7. BIOS / UEFI / firmware context import for boot-chain / root-of-trust pressure candidates.
8. New map layers for external reports, known-issue matches, driver/module evidence, firmware/BIOS evidence, Windows error cascades, resource burden, and root-pressure candidates.
9. A safe synthetic adapter cascade demo linking driver, firmware, Windows error, AIDA64 baseline, and UWC burden evidence.
10. Adapter evidence and topology receipt addenda exported without mutating the canonical route or audit receipt hash.

Boundary: this patch imports and pressure-reads existing reports/files only. It does not run PE-sieve, THOR, AIDA64, UWC, Windows diagnostics, drivers, or firmware tools inside the static Space. It does not execute binaries, load drivers, modify kernels, flash BIOS/UEFI, remediate a host, call external APIs, or claim confirmed malware/root cause.

## v0.3.2.4.15.2.34 Precision Forensic Dynamics Map — Topology Foundation

This package immediately extends v0.3.2.4.15.2.33.2. It keeps the public forensic entry layer and all detector/harness behavior unchanged, then adds the first replayable topology-map body to the root page.

Topology workflow:

```text
Evidence packet -> event frames -> nodes / edges -> replay bloom -> selected-object inspector -> settlement state -> topology receipt addendum
```

The topology foundation adds:

1. A Precision Forensic Dynamics Map panel in the root `index.html`.
2. Local node, edge, event-frame, layer, and replay structures.
3. Play, pause, rewind, step forward/back, speed, zoom, fit, and timeline scrub controls.
4. Color-coded display layers: files/artifacts, file movement, metadata/structure, evidence basis, pressure flags, claim boundary, settlement state, delta changes, and hash/receipt integrity.
5. A selected-object inspector for nodes and edges.
6. Safe synthetic demos for receipt drift and ZIP -> EXE topology.
7. A topology receipt addendum exported inside the computed route JSON and as a standalone JSON download.

Boundary: this patch does not add live execution, malware scanning claims, VirusTotal/external-map comparison, threat-intelligence API integration, child-safety enforcement, or law-enforcement workflow. It is the map-body foundation that later layers can stand on.

## v0.3.2.4.15.2.33.2 Public Forensic Entry Layer

This package immediately extends v0.3.2.4.15.2.33.1. It changes the first-glance entry path only: the live page now explains the practical forensic workflow before asking a visitor to decode the deeper HIR/OAM source language.

Public workflow:

```text
Drop evidence -> local metadata -> reverse backtrace -> pressure read -> claim boundary -> review receipt
```

The front-door layer adds:

1. Plain-English “What this is” forensic entry block.
2. “What this does / does not do” card above the deeper engine language.
3. Sample evidence scenarios: suspicious Windows driver, Linux module/ELF review, ZIP -> EXE package chain, and incident notes / telemetry export.
4. Clear boundary language: no uploads, no live execution, no live kernel access, no automatic compromise proof, and no C2PA/Linux/Microsoft certification or endorsement claim.

No detector logic, route logic, harness cases, expected routes, receipt logic, or bridge-rendering rules were changed.

## v0.3.2.4.15.2.33.1 UI polish + active-version surface correction patch

This retained base patch immediately extends v0.3.2.4.15.2.33. It keeps the single-page NTOS/Linux/Pressure Flight Recorder evidence intake and Primordial Lexicon Bridge Matrix v0.1.1 renderer unchanged, corrects the active version metadata surface, and polishes the Explanation Mode label, tooltip, and mobile touch targets.

The explanation-mode selector can render the same canonical pressure result through:

1. Original HIR/OAM
2. Plain English
3. Technical Systems
4. C2PA / Provenance Bridge
5. Linux / POSIX Bridge
6. Windows / Microsoft Bridge
7. Red-Team Boundary

The bridge layer is render metadata only. It may change displayed wording, tooltip density, or domain lens. It must not change route state, evidence packet, receipt hash, pressure flags, non-claims, or review recommendation.

Included bridge files:

- `primordial_lexicon_bridge_matrix_v0_1_1_seed.json` — UI-consumable bridge matrix seed.
- `review_packet/Primordial_Lexicon_Bridge_Matrix_v0_1_1.xlsx` — reviewer-readable bridge matrix workbook.

## v0.3.2.4.15.2.33 cognition / lexicon bridge integration patch

This retained base patch immediately extends v0.3.2.4.15.2.32. It keeps the single-page NTOS/Linux/Pressure Flight Recorder evidence intake unchanged and adds the Primordial Lexicon Bridge Matrix v0.1.1 as a UI explanation layer.

## v0.3.2.4.15.2.32 single-page evidence intake patch

This package keeps NTOS, Linux kernel, and Pressure Flight Recorder support inside the root Loop-Gated OAM Pressure Engine page. The adapter surfaces are no longer treated as separate pages a visitor must open. They are selectable evidence modes in `index.html`:

1. **NTOS kernel evidence mode** — accepts Windows kernel binaries or offline forensic exports and extracts bounded local metadata such as SHA-256, PE header signals, file size, entropy estimate, and analyst notes.
2. **Linux kernel evidence mode** — accepts Linux kernel/module binaries or offline exports and extracts bounded local metadata such as SHA-256, ELF header signals, file size, entropy estimate, and analyst notes.
3. **Pressure Flight Recorder bridge mode** — accepts route receipts, review packets, audit JSON, and Diamond Seed bridge context as pressure evidence.

## Claim boundary

The 261/261 harness result demonstrates internal expected-route reproduction over authored cases only. It is not calibrated accuracy, production validation, broad generalization proof, or a compromise detector.

The NTOS and Linux adapters consume offline forensic evidence exports and emit interpretive OAM route/provenance findings. They do not patch kernels, install hooks, hide modules/drivers, bypass security tooling, deploy malware, exploit systems, or remediate live systems.

The Pressure Flight Recorder records bounded session-route receipts. It does not identify a person, diagnose internal state, claim full detector parity, or create a person-frequency claim.

## Main entry

- `index.html` — live Loop-Gated OAM Pressure Engine root page with public forensic front door, evidence intake console, bridge renderer, and bounded receipt exports.

Supporting adapter/reference materials remain in `review_packet/extensions/` and `pressure_flight_recorder_bridge/`, but the public user flow is now the root page itself, not a chain of separate links.


Created and Developed by Collin D. Weber.