Skip to content

M2/M3: fail-closed device identity ingress and sustained native-only PCM evidence - #571

Merged
1 commit merged into
mainfrom
guard/m2-m3-control-verification-20261111
Nov 11, 2026
Merged

1 commit merged into
mainfrom
guard/m2-m3-control-verification-20261111

Conversation

@masarray

Copy link
Copy Markdown
Owner

#527 — one native CONTROL-safety vertical, compatible with live Harmony/O1 branches

Baseline main@fd2dd0c4d9cb78abd34c6f12e28f33f0e8a55b74, no changes to src/Main.cpp, LiveAudioEngine.h, LiveDryRoutingLab.h, shared FX DSP/lease, native WebView bridge or compiled /preview/ GUI.

M2 physical device ingress: NativeDeviceApplyCoordinator::parse no longer coerces untrusted JSON integer/float/bool/array names into a JUCE ASIO/WASAPI backend or playback/capture device. Backend and playback are exact strings; capture is optional string for output-only. Existing real device names, sample rate/buffer, pin mapping and device transaction API stay unchanged. C++ contract asserts invalid type rejection and output-only acceptance. This cannot grant physical output.

M3 source proof: ProductionRenderAudit::assessSeries is a pure CONTROL/read-only verifier for >=3 consecutive stable native render windows with a nonzero minimum native completed block count. Every boundary requires the same independently verified process nonce, genuine device epoch and installed ChannelId admission. A single successful callback/window, in-flight/torn counters, muted/unpatched/no-render, failed render, M4 fallback, overlap denied, swapped process, epoch change or counter reset cannot qualify a continuous native-only series. Historical M4 activity outside the window remains allowed. Targeted existing zero-JUCE CTest covers 3-window success and all unsafe negative evidence. It never retires M4, unmutes a device, or substitutes for physical ASIO/FAT.

Cross-branch compatibility: Latest O1/O2 #563 has itself reconciled old Main/bridge conflicts on its HEAD and its separate UI/FAT exact-SHA runs; this PR touches none of those paths. Harmonice #529 owns Harmony DSP/editor; no code overlap here. Integrators still must verify combined HEAD and physical ASIO separately.

CI policy: fast native first; then one exact-SHA Windows MSVC/full CTest qualification. No Chromium (zero JS/GUI changes), no duplicate FAT ZIP. No performance/crackle/listening claims. Physical proof and compatibility retirement remain PENDING.

Copy link
Copy Markdown
Owner Author

/arsonmix-ci native e1d541b

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying arsonmix with  Cloudflare Pages  Cloudflare Pages

Latest commit: e1d541b
Status: ✅  Deploy successful!
Preview URL: https://545cdb4c.arsonmix.pages.dev
Branch Preview URL: https://guard-m2-m3-control-verifica.arsonmix.pages.dev

View logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant