Mimir/docs/implementation-plan.md

Implementation Plan

Current Cut Line

Mimir is now a C# app/runtime plus native reservoir project. The live stream machine must be direct-driver and native-buffer first.

For the source-level ownership map, read code-algorithm-map.

• src/Mimir.App hosts Fensalir for windowing, rendering, and the D3D12 bridge.
• src/Mimir.Runtime owns stream descriptors, source polling, direct push ingest, one rolling buffer per configured audio/video stream, and the synchronization hub Fensalir can inspect.
• The default five-second window is an intentional latency/memory trade: use it to line up streams and extract the volumetric audio/video field before OBS sees program output.
• native/reservoir owns the lower native rolling-buffer invariant for Fensalir/Faust integration.
• PowerShell/FFmpeg/SRT remains a bridge utility for LAN OBS feeds. It is not the synchronized program authority.

Fensalir is not a conventional renderer bolted onto Mimir. It is the engine-side field/evidence machine. Mimir must submit synchronized buffers, constraints, surface intent, and calibration evidence; Fensalir lowers them into claims with travel/depth, metadata, control, and reservoir-guide lanes. Any path that only paints pixels is a fallback/debug draw and must not be mistaken for the spatiotemporal machine. The shared Fensalir spatiotemporal reservoir is the organ that owns temporally reused field presentation; TubeField is only the current rolling-buffer tube claim/candidate producer feeding that organ. Because Fensalir often samples visible field candidates directly rather than lighting samples after a known primary hit, claim producers may need deterministic local visibility generation before reservoir reuse. Reservoir resolve owns temporal antialiasing and reconstruction; TAA is not a separate hidden owner of field identity.

The first depth-compute target should be a D3D12 stereo disparity lane modeled on permissive SGM provenance, with libSGM as the current north-star reference. The research ledger is research/d3d12-stereo-depth-provenance-2026-05-29. That note is not a dependency grant: CUDA implementations, TensorRT ports, and monocular model demos are provenance only. The live owner is Fensalir D3D12 compute over Mimir-declared texture resources and calibration state. The first live Leap slice now exists in MimirStereoDepthConfigurations and MimirFensalirFieldLowering. The generic BuildStereoDepthCandidateFrame still lowers caller-declared rectified left/right textures into a GPU-resident compute-writable R16F disparity SurfacePage, an R8 confidence texture, a Height FieldEvidence claim, and an AquariumFieldStereoDepthLowering sidecar. The live BuildLeapPackedStereoDepthCandidateFrame path now recognizes the current LeapStereoIr rolling video window, reuses its declared packed R8G8 texture as both left and right input resources, names the R/G lane observations, and emits the same Height/depth lowering automatically from the runtime frame. The calibration id is explicitly pending, so the output is disparity evidence, not metric geometry truth. The libSGM-provenance profile currently publishes min disparity 0, 128 disparities, four aggregation paths, census radius 2, P1 8, and P2 96. Fensalir has the first packed-Leap D3D12 compute kernel installed as a crude SAD/block-match disparity writer; it is not full SGM yet. The next socket now exists too: MimirPointCloudConfigurations records the Leap disparity-to-point-cloud projection profile, and BuildLeapPackedStereoPointCloudCandidateFrame derives a GPU-resident FieldMesh point-list resource from the live Leap disparity resource. The runtime merges that Mesh claim alongside the stereo-depth claim, and Mimir.BufferSmoke --leap-point-cloud-root-smoke proves the contract plans as one SurfacePage packet plus one Mesh packet with no deferred requests. This is the first point-cloud root. Fensalir branch codex/leap-packed-depth now has the matching native surface-claim lane: D3D12PointCloudFromDisparityCS fills the derived point-list Mesh for diagnostics and also writes approximated normal/curvature surface splats into Fensalir's existing SDF/PBR/radiosity reservoir buffers. The point-list renderer is gated as a diagnostic path; live presentation is through the shared splat/reservoir resolver. The live proof is artifacts/runtime/mimir-leap-surface-claims-clean.png: LeapUVC -> Fensalir D3D12 texture lease -> packed stereo disparity -> 19,200 generated surface claims -> visible reservoir-resolved splats, with point-list rendering still at rendered 0. A second proof, artifacts/runtime/mimir-leap-history-split-shader-visible.png, runs without AQUARIUM_DISABLE_RESERVOIR_HISTORY: Fensalir now compiles a dedicated lean D3D12ReservoirHistoryUpdate.hlsl instead of compiling the monolithic post shader for the history compute pass. That lean pass writes the current resolver sample into all four reservoir-history rows and the resolved target; temporal and spatial reuse still need their own compilable shader cut. The next truth cut is calibrated projection constants, temporal reservoir reuse, and global residual/calibration ownership, not another fake RGB depth path.

Those claims are not inherently pixel-sized. Pixel-level resolve consumes the reservoir, but claim support is chosen from the represented field. Smooth surfaces should stay broad. Aquarium-style heightfields should be quadtree surface domains with 2D brushes painting tile payloads, and SDF probes emitting surface splats only where curvature, projected error, material/brush detail, or silhouettes justify subdivision.

The current teardown/migration map lives in fensalir-rendering-rebuild-migration. Mimir's side of that rebuild is to publish typed physical observations, calibration constraints, and surface intent; Fensalir's side is to turn those into field claims, selected lowerings, reusable evidence, temporal guides, and program output.

Payload handles are now demoted to names inside a resource authority. Mimir declares live native/GPU payloads as typed Fensalir resources with shape, residency, shader access, validity, version, and native handle metadata; claims and lowering requests reference those resource keys. A string handle without a matching resource declaration is not payload truth. For live camera images, the preferred authority is Fensalir-owned texture leasing: Mimir asks the engine broker for a keyed Texture2D lease, writes decoded frames into the returned shared D3D12 texture, signals the returned fence, and commits that fence value before the resource key is sampled by shader lowerings. Foreign shared handles remain import edges only. Camera producers must choose the closest-to-device path available for each sensor and report the unavoidable copy count; convenient managed/process middlemen are diagnostic witnesses, not hot-path owners.

The old script stack is gone. Do not add a compatibility edge unless it protects a named invariant that the native runtime cannot protect yet.

Implemented

• Mimir public identity, branding, and Face memory.
• Mimir.slnx with src/Mimir.App and src/Mimir.Runtime.
• Fensalir host bootstrapping from Mimir.App.
• eve-program-output now owns the first native EVE streaming contract: Fensalir can publish the completed D3D12 backbuffer into a named shared texture when FENSALIR_PROGRAM_OUTPUT_D3D12=1, and Mimir records the EVE-facing publication profile as a native D3D12 stream rather than a WebKit/dashboard path.
• MimirSynchronizationHub, MimirRollingStreamBuffer, stream descriptors, and IMimirStreamSource.
• Configurable five-second default rolling buffers for local and network audio and video streams.
• MimirNativeIngestStreamSource for direct push ingest into runtime buffers.
• MimirProcessStreamSource for bridge/network command edges.
• MimirFrameEventProcessStreamSource for temporary JSON-line frame metadata from native probes into the same rolling buffers Fensalir inspects. One probe process can accept multiple emitted sourceId values so it does not reopen the same camera set once per stream.
• native/asio_capture plus MimirAsioStreamSource provide the first production-shaped Focusrite path: a native in-process ASIO callback source feeds sample-bearing 192 kHz Float32 blocks directly into Mimir.Runtime rolling buffers on one interface clock domain.
• MimirBioacousticProbeScheduler closes the first active-probe control loop: sync confidence and per-band frequency-response confidence decide whether a targeted probe should be emitted, and MimirRuntime publishes live telemetry for aggregate confidence, deltas, source probe counts, and weak-band pressure. The scheduler is output-device neutral; a later renderer must explicitly target Starfire Realtek for physical chirp emission in the current routing.
• Mimir.WasapiLoopback now has the first explicit Starfire Realtek render edge: it can list active render endpoints, select Speakers (Realtek(R) Audio) by friendly-name substring, and play mono Float32 probe audio through WASAPI shared mode. Mimir.BufferSmoke --targeted-bioacoustic-probe-realtk-live couples that renderer with Scarlett ASIO capture and scores the physical mic response for the scheduled probe. The targeted probe planner defaults to a 12 kHz ceiling and low/mid-band bias because the current Realtek/speaker/Scarlett-mic path does not provide useful high-band calibration evidence.
• Mimir.BufferSmoke --bioacoustic-realtk-scheduled-calibration-live is the scheduler-owned live-I/O calibration receipt: the scheduler chooses each probe step from seeded Scarlett residuals, Realtek emits it, Scarlett captures it, residuals update, and the run writes a per-band CSV plus balance plan instead of mowing the whole spectrum blindly. The remaining production cut is feeding measured runtime confidence state into the same scheduler/emitter path. Scheduler confidence/status uses the same 120 Hz-12 kHz measurable window as the targeted planner, so dead ultrasonic-ish residuals cannot keep cadence pinned to questions this room path cannot answer.
• src/Mimir.BufferSmoke loads the runtime config, polls the synchronization hub, and prints the actual rolling buffers. Use --require-samples when an empty declared sensor buffer should fail the run. Use --bioacoustic-self-test to render the active motif timeline into memory and verify that the decoder recovers direct word anchors. Use --standalone-bioacoustic-self-test to verify that a receiver with only the codebook/schedule can recover canonical source offset from delayed audio. Use --bioacoustic-train to run the indexed cepstral receiver hypothesis panel and write CultCache/audio receipts under artifacts/bioacoustic-training/.
• native/probes/wasapi_audio_cadence captures WASAPI mic or render-loopback block metadata and emits audio-block JSON events for the diagnostic runtime adapter. It can probe requested shared/exclusive formats so driver state is explicit, but Scarlett production capture belongs on ASIO.
• native/probes/asio_audio_cadence opens the registered Focusrite ASIO COM driver, reports channel counts, buffer sizing, supported sample rates, and can run a short input callback capture. Current Starfire Focusrite USB ASIO proof with the Scarlett Solo 4th Gen shows 4 inputs / 2 outputs, including Loopback 1/2, 192-frame preferred buffers, 44.1-192 kHz support, and nonzero 4-channel Int32LSB input callbacks at 192 kHz. --monitor-sweep emits low-gain ASIO output bursts and synchronously measures loopback/mic response per frequency so ultrasonic acoustic claims stay measured. The probe can also play raw mono Float32 timeline audio with --play-f32-mono and capture raw interleaved Float32 ASIO input with --record-f32-interleaved.
• MimirBioacousticTimeline owns the active runtime watermark described in bioacoustic-timeline-watermark. It renders a low-gain birdsong-like word language: 128 self-identifying word positions, left-speaker and right-speaker variants, four formant-rich syllables per word, rhythm variation, and direct word identity so a correctly decoded word identifies canonical timeline position. The active receiver is no longer a sequence decoder: each song contour should expose multiple time/frequency anchors through syllable timing, bends, formants, payload ornaments, rhythm, speaker tint, and log-mel shape. Runtime active sync now reports evidence=bioacoustic.
• MimirChirpletTimeline owns the older structured chirplet calibration stream, PCM segment rendering, matched timing trace, and per-band response kernels. It remains a reference/diagnostic path.
• MimirChirpletSymbolCodebook owns the 32 symbol definitions. Each symbol has a unique chirp shape, with inter-chirp rhythm as additional code evidence.
• MimirChirpletStreamDecoder is the first constrained chirplet-transform receiver. It owns a bounded PCM window, emits transform frames with multiple phase-invariant symbol candidates and per-candidate refined sample offsets, decodes code-valid triplet anchors through a local trellis that requires gap and clock coherence, and fits a per-source sample clock from those anchors.
• MimirAudioSynchronizationAnalyzer ports the first live sync measurement: sample-bearing audio blocks are resampled into the Scarlett loopback timeline. The analyzer derives delay only from matched decoded timeline anchors. A source without at least one matched anchor has no timing report for that window. It accepts Float32, Int16, Int24, and Int32 PCM windows so ASIO/native capture can feed true interface formats without a pre-conversion shim.
• MimirAudioSynchronizationStateTracker owns the first smoothed per-source sync state: latest fractional delay, smoothed delay, confidence, per-band response evidence, and delay-slope/SRO estimate in ppm.
• faust/mimir_alignment_actuator.dsp is the first Faust-owned sample movement surface: six channels of bounded fractional delay and gain controls. Mimir estimates delay/SRO; Faust/native DSP applies correction.
• MimirAlignmentActuatorBank is the runtime control-plane owner for those estimates: it converts smoothed per-source sync state into nonnegative holdback commands, preserves stable Faust sourceN slots for live sources, reports source overflow, and keeps the reference holdback explicit instead of pretending a measured-late stream can be advanced by a positive delay line.
• MimirRuntime updates audio sync analysis online as a bounded rotating service and can emit live sync telemetry with MIMIR_SYNC_TELEMETRY_SECONDS. UI and telemetry read cached reports/states; they do not run synchronization analysis. The same cadence now publishes the latest actuator command frame for telemetry/readout and queues it into AquariumAudioDocument as an audio control frame. Mimir also declares the faust/mimir_alignment_actuator.dsp program as an AquariumStreamingDspProgram, so Fensalir has both the persistent Faust DSP graph and the matching controls. The runtime now also queues sample-bearing AquariumStreamingAudioBlock lanes from the latest actuator source buffers, using the bank-assigned Faust sourceN slot as channel authority. Fensalir now publishes processed DSP output as AquariumAudioStemFrame records through an engine-owned IAquariumAudioStemBus, and Mimir declares deterministic aligned-source stem names with the actuator program. MimirObsStemPublicationState consumes the Fensalir stem bus without copying audio and validates ready/missing/unconfigured lanes against the alignment-actuator OBS stem profile. MimirObsStemSharedMemoryPublisher now publishes those validated stems into a fixed Windows shared-memory ABI, and native/obs_stem_source is the first OBS source plugin bundle. It registers Mimir Audio Stem, which reads one named stem and submits it to OBS as an audio source, and Mimir Program Texture, which opens Fensalir's named D3D12 program-output texture and feeds OBS through a GPU-to-GPU D3D12-to-D3D11 bridge texture. Fensalir also publishes a named D3D12 program-output fence, and the OBS source opens it before copying so the consumer is not reading blindly or depending on Fensalir's private frame fence. This avoids CPU readback and removes Spout2 as a required program-video dependency, while preserving the explicit boundary cost that libobs is D3D11 on Windows. Fensalir and the OBS source can optionally agree on a bounded publication ring using FENSALIR_PROGRAM_OUTPUT_RING_COUNT; OBS selects the latest completed slot from the program-output fence value. OBS can also publish a consumer fence, and when Fensalir is launched with FENSALIR_PROGRAM_OUTPUT_CONSUMER_FENCE_NAME, Fensalir skips publication instead of reusing a ring slot OBS has not acknowledged. scripts/build-obs-stem-plugin.ps1 stages the upstream OBS plugin template SDK under artifacts/obs-sdk/ and builds the plugin DLL locally.
• MimirSynchronizedBufferPlanner now builds one aligned presentation frame from the live rolling buffers. It chooses a canonical presentation time inside the shared retained window, applies source or clock-domain timing corrections, and returns per-stream slices for cameras, network display feeds, and audio blocks. This is the low-level Raven display/audio shape: Raven display frames can be tagged with clockDomainId: raven-sync, while a Raven audio timing signal routed into Scarlett earns the correction for that shared clock domain. The display feed remains derived evidence, not an independent timing owner. Mimir.BufferSmoke --synchronized-buffer-planner-smoke proves the aligned local-camera, Raven-display, loopback, and mic buffer shape.
• MimirFfmpegRawVideoStreamSource is the current network-pixel adapter for Raven ingest. FFmpeg owns SRT receive/decode, Mimir owns exact raw-video frame reads and synchronized buffer samples. Eve uses EveCanvas-native sensor uplinks instead: Mimir.EveSensorReceiver listens for eve-camera on WebSocket port 8793 and eve-mic on port 8794, emitting the existing frame-event shape into runtime buffers. Mimir.BufferSmoke --ffmpeg-rawvideo-source-smoke proves the local raw-video adapter without Raven online.
• MimirPresentationControlState owns operator intent for the Fensalir program surface: video feed visibility/solo/opacity/layer order, audio mute/solo/gain, and global LUT preset selection. The Mimir Program UI panel is deliberately compact and fadeable. Video choices filter production surface intents before Fensalir composition; audio choices modify Faust gain controls and the samples sent through Fensalir streaming DSP. LUT presets are typed postprocess state with preset paths and strength; until the renderer grows LUT texture sampling, preset exposure and bloom are mapped into existing GraphicsSettings. Mimir.BufferSmoke --presentation-control-smoke proves the state owner.
• MimirSceneEditorState owns the new Mimir-window editor graph. It is not the OBS program output: it owns editor camera, selected node, sensor-feed panels, SDF text-panel nodes, model placeholders, visibility, locks, transforms, reset commands, and grab/rotate/resize gizmo intent. MimirRuntime renders derived spline outlines and handle markers from that state, and the Mimir Editor panel exposes hierarchy, visibility, transform, creation, and reset controls. See scene-editor-control-surface. Mimir.BufferSmoke --scene-editor-smoke proves the graph/control/gizmo owner path. World SDF text glyph rendering, ASSIMP-style mesh import/upload, and pixel-accurate gizmo hit-testing remain Fensalir renderer cuts rather than Mimir-side fake outputs.
• MimirRuntime no longer submits the legacy direct AquariumSplineFrame spectrum dashboard. Live spectrum visualization authority is the AquariumFieldEvidenceFrame: Mimir declares the rolling resource, emits a Tube claim and AquariumFieldTubeSplineLowering, and Fensalir plans/expands the TubeField generated mesh. Mimir now normalizes current spectral frames into a row-major Float32 matrix, attaches that as a field resource upload, and Fensalir copies it into the resolved GPU structured buffer before TubeField compute reads. The old AquariumBufferFieldFrame / ReservoirSplats dashboard path is also silent. Mimir.BufferSmoke --mimir-spectrum-upload-smoke boots MimirRuntime, advances the synthetic spectrum preview path, and verifies that the frame contains the Float32 resource upload plus planned TubeField packet while legacy spline and buffer field inputs stay empty. The same runtime path declares the local blackbody ramp PNG as a GPU-resident Texture2D resource and binds it by resource key. The uploaded spectrum resource is a rolling column matrix now: physical columns are flattened (history age, source lane) pairs, and Mimir emits one Tube claim/lowering per active source. The resource uses fixed history and source-lane capacities, so frame-to-frame content versions and source topology changes do not resize the GPU buffer while the trail fills. MIMIR_SPECTRUM_SOURCE_LANES sets the lane capacity; surplus sources are truncated and reported in the runtime UI. Lowerings use that fixed capacity as ColumnStride. Physical history slots are addressed as a ring with RollingOffset, so logical age no longer requires reshuffling every column before shader sampling. Mimir emits one Float32 resource upload for the newest spectrum ring slot with an explicit element offset, rather than uploading the full fixed-capacity backing buffer every frame. Fensalir owns rolling-slot validity and clamps TubeField dispatch so invalid older slots are not sampled after renderer allocation, reset, or partial update. MIMIR_SPECTRUM_TUBE_SUBDIVISIONS controls the requested Catmull-Rom subdivision count so Fensalir's overflow report has a direct cost lever.
• MimirFensalirFieldLowering now emits AquariumFieldResourceDeclaration rows for live native/GPU payload views. Observation claims reference mimir:resource:* keys, and Fensalir validation/planning can reject or defer packets whose resources are missing, duplicated, CPU-only, or backend-incompatible. Mimir.BufferSmoke --fensalir-field-evidence-smoke proves the first hardware-free receipt with one declared resource, three claims, one planned resource-backed TubeField packet, and two deferred non-backend claims. Mimir.BufferSmoke --fensalir-field-dsl-resource-smoke proves Fensalir's DSL evidence compiler can bind a declared resource and produce one planned TubeField packet with no deferred requests.
• MimirFensalirFieldLowering.BuildCameraObservationFrame is the current camera bridge proof. It lowers latest video buffers into FieldEvidence observation claims, declares engine-owned or imported video payloads as Texture2D resources, and creates camera surface intent only when a resource exists. MimirFensalirTextureLeaseClient is the producer-side API for asking Fensalir for a keyed D3D12 texture/fence lease before decoded camera frames are written. MimirRuntime accepts AquariumRuntimeServices and commits producer fence values for leased video payloads before Fensalir samples them. MimirVideoCaptureDriverSource forwards the lease client to drivers that implement IMimirFensalirTextureLeaseReceiver, so native/direct camera drivers can allocate their Fensalir destination texture before capture/decode. If a raw single-plane device path must return CPU bytes, MimirVideoCaptureDriverSource uploads them directly into the leased texture through the broker, clears the live managed payload, and increments UnavoidableCopyCount. NV12 CPU upload is rejected until the engine owns a real planar copy path; GPU/native producers should write the shared texture themselves and stay at zero copies. Metadata-only cadence frames remain observations with empty payload handles; they do not become fake render requests. The old direct AquariumGpuSensorFrame builder has been removed from Mimir's proof path. The first production-shaped camera driver is MimirKsVideoCaptureDriver, backed by native/camera_capture/mimir_camera_capture.dll: it opens a Kernel Streaming capture pin in process, queues uncompressed UVC frame reads, returns MimirVideoFrameDescriptor samples through IMimirVideoCaptureDriver, and lets MimirVideoCaptureDriverSource upload those raw frames into Fensalir texture leases. MJPG/H264 remain outside this lane; they need a device/GPU decode producer rather than a CPU convenience detour. PS3 Eyes use the sibling MimirPs3EyeVideoCaptureDriver backed by native/camera_capture/mimir_ps3eye_capture.dll; it opens the existing WinUSB/libusb PS3EYEDriver path in process and emits Bayer8 frames through the same source/upload/copy-count machinery. Current direct-driver smokes prove real-frame upload for LeapUVC 640x240 YUY2, both PS3 Eyes at 320x240 Bayer8, Kiyo Pro 1920x1080 YUY2, and regular Kiyo 640x480 YUY2. Regular Kiyo 1280x720 YUY2 did not open. config/mimir-runtime.perfect-machine.local.json is the current local all-sensor blast profile: Leap packed stereo IR, both PS3 Eyes at 320x240@187, Kiyo Pro RGB, and regular Kiyo RGB. Mimir.BufferSmoke --perfect-machine-live-smoke opens all five configured video sources, attaches Fensalir texture leases, and passes only when at least five live camera textures, a Leap stereo-depth lowering, a disparity SurfacePage, and a derived point-cloud Mesh are present. Fensalir now plans the camera texture Feature requests through its GpuSensorFusion backend instead of deferring them. The current dispatch samples LeapStereoIr, both Bayer8 PS3 Eyes, Kiyo Pro YUY2, and regular Kiyo YUY2. Fensalir binds YUY2 through the Microsoft-documented R8G8B8A8_UNORM SRV view over DXGI_FORMAT_YUY2 and decodes Y0/U/Y1/V in compute before scoring features. MimirMediaFoundationGpuVideoCaptureDriver is the first compressed camera path: native/camera_capture/mimir_mf_gpu_capture.dll uses Media Foundation SourceReader with a D3D11 device manager, selects MJPG/H264 camera modes, decodes on the GPU, copies the decoded GPU surface into a shared BGRA D3D11 texture, and publishes only a shared-d3d11-texture handle. Live payload bytes stay empty. Kiyo Pro 1920x1080 MJPG->RGB32 and H264->RGB32 smokes both produced GPU handles and valid Fensalir camera resources. NV12 sharing was rejected by D3D11 in this path, so planar NV12 remains future plane-aware interop or GPU bridge-copy work. Fensalir can still resolve imported shared Texture2D resources by native D3D12 handle and accepts Mimir video format names. Mimir.BufferSmoke --fensalir-camera-observation-smoke verifies the split, and --fensalir-texture-lease-smoke verifies the engine-owned lease path. Mimir.BufferSmoke --stereo-depth-contract-smoke verifies the next visual socket: libSGM-provenance D3D12 SGM is represented as a non-dependency profile, and synthetic rectified Leap stereo depth lowers through caller-declared left/right input textures, one stereo-depth lowering sidecar, and one planned SurfacePage packet with no CUDA, CPU disparity image, or monocular metric authority.
• Mimir's active proof path no longer uses the direct AquariumAcousticFieldFrame builder either. Sync states lower into FieldEvidence calibration constraints through MapCalibrationConstraints, and Fensalir selects audio-path Phase and Confidence claims as DebugOverlay backend packets. --perfect-machine-profile-smoke now proves the acoustic constraint is planned through FieldEvidence instead of deferred through a parallel acoustic packet. The same smoke now also proves the first Phase 5 synthetic audio-source candidate: an SRP/PHAT-style localization result is lowered with calibration/source identity and a world-space confidence envelope, then planned as a FieldEvidence DebugOverlay packet. It also proves a synthetic multi-camera marker candidate using the same FieldEvidence authority: deterministic marker features plan as DebugOverlay packets while ambiguous raw camera features still defer. LED strip calibration now has the same typed evidence path: MimirLedSplineFieldCandidate stores ordered per-camera bright-curve samples in image pixels plus local clipspace/frustum coordinates, temporal-code/index stability flags, and shared calibration/spline identity. BuildLedSplineCandidateFrame lowers that curve as deterministic camera-sensor Feature evidence, and --led-spline-calibration-smoke proves Fensalir plans it as one DebugOverlay packet with no deferred request. MimirLedSplineCurveSolver now owns the first per-sensor curve solve from bright LED detections into ordered image/clipspace samples. MimirCameraRigCalibrationSolver owns the next bounded pose step: given stable LED indices plus a scene-space LED curve anchor, it fits camera translation updates by minimizing ray-to- curve distance from each local frustum. The smoke synthesizes a scene curve, projects it through two camera frustums, solves the curves back out of the detections, and recovers bounded camera-position updates with near-zero ray residual. Rotation and intrinsics fitting remain explicit future work. Exact correspondence requires coded or otherwise stable LED identity; uncoded repeated lights remain curve constraints until the global residual solver resolves them. Exposure/gain sweeps must optimize recovered spline quality, not generic contrast or brightness. MimirLedSplineQualityScorer scores each setting by detected LED count, curve coverage, spacing coherence, smoothness, exposure fitness, and saturation penalty. --led-spline-quality-sweep-smoke proves the selector chooses the balanced setting over both underexposed missing-LED detections and overexposed saturated halos. MimirLedSplineFrameAnalyzer is the frame-level bridge for physical sweeps: it reads luma frames, extracts bright connected components as LED candidates, solves the per-sensor curve, and emits the same spline quality report. --led-spline-frame-analysis-smoke proves clipped blobs can still be detected while scoring as unusable calibration evidence. Mimir.BufferSmoke --led-spline-live-score now runs that score against live direct sensor feeds. For KS/UVC cameras it sweeps manual exposure/gain, drains stale frames after each write, scores the live luma frames for spline quality, and prints a best setting per source. Current Starfire proof with --expected-leds 38 --minimum-luma 0.55 selected exposure -9, gain 8 for both kiyo-pro-rgb (score 0.666, 41 detections) and kiyo-basic-rgb (score 0.650, 38 detections). LeapUVC rejected the generic KS exposure/gain writes and only recovered two LED components; both PS3 Eye feeds currently score fixed-control frames because their native wrapper does not yet expose gain/exposure. PS Move is now a concrete active-marker input candidate rather than a lore object on a cable. Mimir.PsMoveProbe enumerates Sony VID_054C / PID_03D5 over Windows HID with no third-party dependency. The connected controller exposes three HID collections: one generic desktop gamepad collection with 49-byte input/output/feature reports, plus two vendor-defined feature-report collections. The safe --read path uses overlapped ReadFile plus CancelIoEx so idle input reads time out instead of hanging the probe. --pair-host <bdaddr> writes a target Bluetooth host address through the PS Move 0x05 feature report on the col02 collection, following PS Move API's pairing contract. The first live controller 00:06:f5:23:e2:d1 was assigned to Nightwing's BlueZ adapter 5c:93:a2:9c:a8:a8. Nightwing now carries the matching BlueZ persistent device/cache records from PS Move API's Linux registration path, accepts the PS-button wireless connection, and exposes the controller as /dev/input/js0, /dev/input/event14, and /dev/hidraw1. tools/nightwing_psmove_music_pulse.py is the current controlled LED/sphere command proof: Starfire owns the Scarlett ASIO loopback envelope, computes a thresholdable tiny-FFT onset novelty function using the old Perlines-style adaptive whitening pattern: fast/slow scrubbed spectrum, positive delta scrubbed against slow delta, rapidly decaying adaptive min/max normalization, and warm-up/refractory gating. It fits a provisional fundamental, folds spectral bin energy into one octave around that fundamental, and streams dark-idle, high-saturation RGB report 0x06 bursts over SSH to Nightwing's hidraw writer. The current whitened-delta broadband rise is ranked against a recent rolling history, and onset brightness is percentile^exponent so exponent 2 maps a median notable frame to 25% brightness while top recent-window rises approach full brightness. Steady-state material falls back toward black between emitted peak frames. The ASIO reader drains the native capture queue to the newest loopback blocks before each LED frame; stale queued audio was the plausible cause of multi-second music-pulse lag, not Bluetooth or the hidraw LED command path. tools/move_latency_probe.py is the current diagnostic latency receipt: PS3 Eye is the default fast visual witness, Scarlett cardioid is the default chirp timing witness, and the event train uses an order-3 de Bruijn schedule with symbol-coded chirp bands, LED colors, and small variable gaps. It writes event-schedule.json, arms the Nightwing LED script before playback, fits detected audio/video events back to the known schedule, and marks receipts invalid when the Move sphere is not sufficiently visible. A live encoded PS3 Eye run recovered all eight visual events with schedule residuals within about 4 ms; ffplay/DirectShow audio startup is still too soft for final physical latency authority, so native timestamped Scarlett playback/capture remains the production timing cut. The music-keyed calibration planner now owns articulated multimodal words: mimir.music_keyed_move_chirp_plan.v1 carries beat/key analysis, chirp frequency contours, de Bruijn symbols, and per-Move sampled RGB visual contour words. tools/sync_sweep.py --music-plan consumes that same plan instead of inventing square flashes, sends the exact RGB samples over Nightwing HID, and writes RGB video visual_contour decoder scores (brightness correlation plus color-chroma error) into summary.json. With a music plan, the sweep also runs Mimir perfect-machine live receipts for the local Leap/Kiyo runtime and Raven/Eve receiver runtime unless explicitly disabled, so the all-sensor run cannot accidentally omit Leap or Eve merely because FFmpeg cannot archive them directly. MimirMoveControllerTracker is the first Mimir-native overlay owner for the streamable product shape: it tracks bright PS Move sphere observations from PS3 Eye luma frames, keeps a bounded history per controllerId, preserves the commanded/expected RGB identity for multiple controllers, and lowers the histories through the existing Feature evidence path. Synthetic smoke --move-controller-overlay-smoke proves two independent controller histories become one valid FieldEvidence claim/candidate without claiming 6DoF pose. config/mimir-runtime.stream-proof.local.json names the current stream-proof profile: Kiyo Pro AR program view, Leap stereo IR depth root, Raven screen and Raven Realtek loopback from one muxed Raven NVENC/AAC MPEG-TS SRT stream on port 5200. Starfire demuxes that single Raven transport locally into raven-display on port 5210 and raven-realtk-loopback f32 PCM on port 5212 because Mimir's current source adapters ingest raw video and PCM separately. Scarlett ASIO channels remain labeled as shotgun/cardioid/local Raven loopback evidence. Nightwing PS3 Eyes no longer appear as Starfire raw video sources in this proof; they publish compact Eye/Move observations. MimirFfmpegPcmAudioStreamSource is the network PCM audio owner after local Raven demux. config/mimir-runtime.move-stream.local.json remains a local/raw-Eye show reference, not the current split-host authority. The distributed authority split is now explicit: Nightwing owns the local PS3 Eye USB reads, PS Move Bluetooth/HID link, LED schedules, device timestamps, and compact marker/feature extraction receipts. Starfire owns the canonical rolling window, Scarlett timing, global calibration residuals, Kiyo/Raven program sync, and OBS publication. Fensalir owns D3D12 dense feature/fusion work, surface claims, and splat/reservoir program pixels. MimirDistributedWitnessConfigurations.NightwingEyesMoves and the nightwing-eyes-moves Perfect Machine profile encode this: Nightwing emits typed mimir.move_controller_observation_state, mimir.camera_feature_track_state, and mimir.visual_marker_state rather than becoming a raw-media or camera-placement authority. Eve now follows the same rule for its own device body: MimirDistributedWitnessConfigurations.EveLocalSensors and the eve-local-sensors Perfect Machine profile make Eve responsible for local camera/mic chirp and flash solves, then shipping compact acoustic path, feature-track, visual-marker, and local-frustum-hint state to Starfire. Starfire still owns global camera placement and the canonical clock. MimirCameraFrustumCalibrationSolver is the first global frustum solve: it consumes stable LED/marker correspondences, scene-space marker points, and seed frustums, then emits per-source position, rotation, horizontal/vertical tangent half-FOV, correspondence count, clipspace reprojection residual, and confidence. The same solver accepts MimirFeatureTrackFieldCandidate plus scene-space TrackId anchors, so PS Move sphere histories, sparse Eye tracks, and Eve-local marker tracks use the same Starfire frustum authority as the LED strip. mimir.local_frustum_hint_state.v1 is the compact CultMesh state document for local witness solves: producer node, calibration id, marker set id, per-camera pose/frustum snapshot, residual, point count, and confidence. Synthetic smoke --frustum-calibration-smoke solves both LED-spline and feature-track frustums for both Eyes, Kiyo Pro, Leap stereo IR, and Eve camera, then emits the feature-track solve as a local frustum hint state, establishing the first fusion-ready frustum surface before dense surface fusion. Next useful cut is direct report decoding plus optical sphere observations from PS3 Eyes/Kiyos/Eve entering the same calibration-evidence path as LED spline constraints. PS3 Eyes now have the first sparse tracking surface: MimirSparseFeatureTracker detects grid-suppressed Bayer/luma corner features, links them frame-to-frame by bounded nearest-neighbor motion, and emits sensor-local MimirFeatureTrackCameraObservation records with track ids, image/clipspace coordinates, velocity, age, and confidence. MimirFeatureTrackFieldCandidate lowers those observations as camera-sensor Feature claims through BuildFeatureTrackCandidateFrame. The CPU tracker is a live diagnostic/bootstrap owner; Fensalir D3D12 feature extraction remains the production owner. --ps3eye-tracking-live proved both Eyes can produce stable tracks at 320x240@187: with sensitive wide tracking defaults, each Eye returned 160 live tracks from each Eye in a one-second pass, with 160 stable tracks from ps3-eye-0 and 156 stable tracks from ps3-eye-1. A full Fensalir headless proof using that all-sensor profile now runs the actual D3D12 host path. The 2026-05-31 run started all five video sources, declared eight field resources, resolved six Texture2D resources, dispatched one packed-Leap stereo-depth kernel, generated one point-cloud/surface stream, and reported 19,200 visible reservoir splats. The captured proof is artifacts/runtime/mimir-perfect-machine-all-sensors-headless.png. The follow-up Fensalir compute proof captured artifacts/runtime/mimir-perfect-machine-gpu-feature-extraction-headless.png: Mimir planned 12 FieldEvidence packets with zero deferred requests, and Fensalir dispatched GPU sensor fusion over three sampleable live camera textures, generating 49,152 sparse gaussians. The YUY2 follow-up proof captured artifacts/runtime/mimir-perfect-machine-yuy2-gpu-feature-extraction-headless.png: all five camera textures dispatched with zero unsupported field textures, producing 81,920 sparse gaussians at about 0.08 ms/frame sensor-fusion GPU time. Phase 6 program-output receipts are also structurally complete: Fensalir publishes the final program surface through named shared D3D12 texture/fence resources, the OBS plugin consumes that surface with an explicit D3D12-to- libobs-D3D11 GPU copy, optional producer/consumer fences prevent blind ring reuse, and audio stems cross through the fixed OBS stem shared-memory ABI.
• Fensalir now owns the first in-process D3D12 field resource resolver cut: shared structured/curve buffer resources import/alias GPU-resident handles, and Fensalir-owned resources allocate GPU slots only when Fensalir is the producer. Texture2D local assets can now be declared as field resources and bound automatically by DSL handles, so TubeField ramps use resource keys rather than raw paths as live authority. Mimir-declared rendering buffers are Fensalir GPU resources in the same runtime and should not round-trip through CPU payloads. The TubeField DSL can now describe a 2D rolling float buffer as Catmull-Rom XY tubes with modulo column addressing, amplitude power/ normalization, radius, ramp texture resource, and emission scale. D3D12 now expands and renders those tubes from GPU-resident buffers, samples material per pixel, binds declared local ramp textures, and executes GPU-emitted indirect draw argument packets. Surface-page resources can now be declared and resolved as GPU-resident shader-readable 2D pages; render lowerings that consume those pages as height/SDF/material domains remain future engine cuts. VolumeTexture resources can now be declared and resolved as GPU-resident shader-readable 3D textures for future density/extinction/SDF3D lowerings. Mesh resources now have that explicit ownership contract: Mesh.Vertices and Mesh.Indices package the vertex/index GPU buffers with topology, index format, bounds, submesh count, and version. The Fensalir DSL can declare a mesh package, and the D3D12 registry allocates/reuses its GPU-resident vertex and index buffers under the mesh resource key. This is resolver authority only; mesh draw/material lowerings remain future engine work. Fensalir's evidence DSL can also create generic resource-backed claims, so mesh/page/ volume resources can plan into backend packets before their selected render lowerings exist. Mesh layout authority is split by source: imported/user meshes use the standard PositionNormalUvColor vertex layout, while generated meshes declare PipelinePrivate and let the selected lowering own the minimal bytes it emits and consumes. TubeField is the first explicit generated-mesh render consumer: its compute path emits private vertex/index/indirect buffers, and render binds them as a D3D12PipelinePrivateGeneratedMesh before applying TubeField source/ramp/material state. The DrawIndexed indirect command signature is now generated-mesh-owned rather than TubeField-owned, so future generated lowerings can reuse the same draw ABI with their own producer buffers and material bindings. TubeField dispatch now obeys the selected backend packet plan; unplanned TubeSplineLowering records are counted but not expanded. TubeField now writes stable field ids, real tube normals, coverage/confidence, and domain-validity guide data into the same scene metadata/control/reservoir-guide targets that reservoir resolve uses for spatiotemporal reconstruction. The shared field candidate inlet now keeps four fixed candidate slots per pixel, so TubeField and later producers compete through the same resolver-owned budget instead of naming a private winner. Reservoir history update is now a shared Fensalir compute pass over a ping-ponged structured buffer with the same four rows per pixel; it emits the resolved HDR field texture that bloom and presentation consume. The presentation shader is no longer a hidden history/TAA owner. TubeField now feeds the shared reservoir from rolling-buffer column packets instead of generated segment packets: expansion emits one GPU-resident column record per logical history/source column, ReSTIR tile binning admits those columns, and candidate evaluation samples the Catmull-Rom tube SDF/material directly from the source buffer. Generated mesh draw args are zeroed for the live path and remain only a diagnostic reference. Fensalir validation also rejects TubeSpline lowering metadata whose claim is not Tube-encoded or whose resource differs from the claim payload. Mimir's typed surface-intent lowering now emits the matching AquariumFieldTubeSplineLowering for audio spectrum/waveform Tube claims, so the real Mimir producer supplies both the planned packet and the generated mesh producer metadata.
• MimirRuntime queues bioacoustic timeline PCM through Fensalir audio when the active timing witness is allowed. MimirAudioSynchronizationSettings.Mode selects chirp-only, passive, or hybrid; passive disables active emission, chirp-only emits the active witness continuously, and hybrid emits the active pilot only while passive confidence is below threshold.
• MimirPassiveAudioSynchronizationEstimator is the first program-audio timing path. It estimates loopback-to-mic delay with PHAT-weighted cross-spectrum correlation so music can act as the default timing witness before any audible watermark is needed.
• MimirChirpBinTimeline is the old chirp-bin calibration path. It renders a fixed-slope chirp-bin codebook and decodes symbols with cheap event-energy proposals, dechirp plus fixed Goertzel bins, and the same de Bruijn triplet timeline-anchor machine. The detector keeps time/frequency ambiguity as candidate symbol/offset pairs so code constraints can choose the coherent path. The analyzer refines the final fractional delay with constrained local waveform correlation around the decoded active delay. Each classified chirp carries the full bin-energy response surface, and stream decodes aggregate that into per-band calibration evidence for frequency response normalization. MimirChirpBinCalibrationModel now preserves usable bands, expected-symbol versus observed-bin confusion observations, timing residuals, delay hypotheses, phase summaries, and an adaptive codebook plan. The reference decoder can consume that model as learned response weighting, phase-coherence weighting, first-order group-delay correction, and joint global delay/bin-shift hypotheses. The runtime emitter also consumes the model's emission plan, rendering the smaller reliable symbol alphabet at the higher recommended de Bruijn order when the physical path cannot support all 32 bins. Reports/states expose delay in microseconds as well as fractional samples. Hybrid now emits the bioacoustic watermark as low-gain half-second bursts only while passive confidence is weak; chirp-bin remains available for ASIO calibration/replay commands. Use --bioacoustic-self-test and --standalone-bioacoustic-self-test to prove the active motif decoder. Use --chirp-only-sync-self-test to prove that the analyzer can recover fractional delay from the bioacoustic runtime watermark. The current synthetic active proof recovers a 317.375-sample delay with printed 0.000 us error.
• Mimir.BufferSmoke --render-chirp-bin-f32 and --analyze-asio-f32 provide the retained Scarlett calibration artifact proof. A 192 kHz chirp-bin run decoded Focusrite Loopback 1 -> Loopback 2 at 0.000 us with 12 matched anchors and 0.999 confidence. --calibrate-chirp-bin-asio-f32 can render/capture/analyze a calibration session and persist the response/confusion/delay model under calibration/chirp-bin/. --analyze-asio-f32 --calibration ... loads that model into the chirp-bin reference decoder. Physical input 1 still failed pairwise timing in the stored artifact, but it produced a useful response/confusion model with two reliable symbols. Acoustic robustness remains separate from the clean loopback timing proof, but failed timing windows now leave usable response evidence instead of silence.
• Mimir.BufferSmoke --calibrate-contestant-asio-f32 persists the active packet-song physical calibration model under calibration/bioacoustic/. It learns per-channel schedule offset, polarity, payload reliability, response-normalization bands, gain, confidence, and pairwise propagation delay from the same 192 kHz ASIO capture. The latest Scarlett receipt calibration/bioacoustic/scarlett-canary-packet-192k-rerun.json clears the current hot-loop budget at 10.7x realtime across four channels. Loopback channels decode 37/37 with 2.524 us MAE; the co-streamer shotgun decodes 37/37 payload with 58.785 us MAE; the cardioid decodes 26/37 with 90.558 us MAE. This is a real response/propagation-delay model, but not yet microsecond-accurate physical mic sync.
• config/mimir-runtime.asio.example.json is the minimal continuous Scarlett runtime ingest proof. It loads native/asio_capture in process at 192 kHz and declares asio-ch0 through asio-ch3 as accepted audio sources. A two-second BufferSmoke run ingested more than 12,000 sample-bearing blocks and retained 2,048 blocks per channel, proving loopback and mic channels enter Mimir.Runtime together in one ASIO clock domain without stdout/base64 transport. BufferSmoke does not emit speaker calibration audio, so that proof is ingest-only rather than a sync report. The active bioacoustic standalone receiver test recovers a delayed audio stream to below printed microsecond precision using only the motif codebook and schedule state. --bioacoustic-actuator-self-test estimates a synthetic 317.375-sample bioacoustic delay, applies the fractional correction, and remeasures the residual below printed microsecond precision.
• src/Mimir.Runtime/Synchronization now contains the reusable Perfect Machine module library distilled from the research pass: node profiles, decoder profiles, language/emission profiles, path-learning sessions, benchmark panels, audio actuator strategies, native capture profiles, camera ingest strategies, reservoir strategies, audio/visual field profiles, compute offload profiles, OBS publication profiles, CultMesh contracts, Fensalir lowering, and assembly plans. Use Mimir.BufferSmoke --perfect-machine-profile-smoke to prove the catalog assembles, --perfect-machine-contract-smoke to write a CultCache contract proof, --perfect-machine-manifest to export the module manifest for tooling/UI/remote witness use, and --perfect-machine-lowering-benchmark to measure the Mimir-to-Fensalir lowering path. The current six-camera/two-audio synthetic lowering benchmark now measures FieldEvidence camera/resource lowering rather than the retired direct GPU sensor DTO path.
• MimirVideoFrameDescriptor for dimensions, pixel format, stride, device timestamp, and native/GPU handle metadata.
• IMimirVideoCaptureDriver and MimirVideoCaptureDriverSource as the live driver-facing seam for Leap, Media Foundation, DirectShow, libusb, LeapC, or shared texture capture.
• native/reservoir with one shared-edge rolling buffer, typed views, C ABI, source-id hashing, producer helpers, and typed audio/render payload descriptors.
• Windows bridge scripts for sender discovery/start/stop and simple OBS Media Source ingest.
• Documentation for OBS receiver setup, native rebuild boundaries, the viable stream app, and the Mimir Face.

Temporary

• Audio and video may still traverse separate OBS/SRT endpoints during bridge testing so OBS can preserve independent controls.
• Process-backed stream sources are only acceptable for network bridge feeds or diagnostics. Six-camera local ingest belongs behind direct capture drivers.
• Frame-event process sources are diagnostic only. They prove source cadence and runtime plumbing without dragging stdout bytes into the pixel hot loop.
• Calibration artifacts may remain on disk as evidence, but live state must be in memory inside Mimir/Fensalir/native runtime surfaces.

Next

1. Replace the frame-event diagnostic bridge with concrete direct capture drivers for Leap stereo IR first, then the other cameras. Each driver must state its device API, destination resource, and unavoidable copy count.
2. Feed those drivers into MimirVideoCaptureDriverSource and prove sustained frame cadence in the rolling buffers.
3. Promote the packet-song physical calibration receipt into the runtime receiver. The live decoder should keep its ear open for self-identifying song contours, extract intra-call time/frequency anchors from log-mel parts, apply learned per-output/mic path weighting, and feed a global delay/clock/path hypothesis. Keep chirp-bin calibration artifacts as reference data, not the runtime target.
4. Add the synchronization actuator: drive a variable-rate resampler and fractional delay line per non-reference stream from the smoothed MimirAudioSynchronizationState. First, prove the bioacoustic motif decoder through real loopback and microphone paths so every correctly heard word becomes a deterministic timeline anchor before the actuator moves samples.
5. Prove the bioacoustic hybrid fallback through real loopback and microphones with probe durations long enough to keep loopback and mic windows live.
6. Bind Fensalir UI to the synchronization hub so buffer depth, stream cadence, source timestamps, and output settings are visible and adjustable.
7. Tighten the spectrum spline tube temporal path until it behaves like a production debug surface: shader-owned tube SDF coverage, correct camera-travel metadata, deterministic direct rendering, and temporal accumulation from stable frame budgets. Do not route this dashboard back through fractal point splats.
8. Move GPU feature extraction, fusion, material fitting, render budgeting, and Spout2 publication into Fensalir. The D3D12 packet/resource resolver now has first authority for structured buffers, local textures, surface pages, volume textures, and mesh packages, and the evidence DSL can plan generic resource-backed claims against those resources. The next engine cuts are selected render lowerings that consume those resources as mesh geometry, camera/feature textures, height/SDF/material pages, and density/extinction/SDF3D volumes. The generic imported mesh ABI is no longer the blocker; TubeField now occupies the first generated-mesh lowering lane. The next renderer decisions are how to expose additional generated mesh producers and which camera/page/volume/material lowering should follow. The first depth-specific cut should be a Fensalir-owned D3D12 stereo SGM lane over rectified synchronized camera texture pairs, emitting GPU-resident disparity/depth/confidence resources and FieldEvidence claims. Keep libSGM as provenance for algorithm shape and benchmark pressure, not as imported CUDA authority. The typed contract, live packed-Leap disparity path, Leap point-cloud Mesh socket, and first Fensalir point render lane exist; the next cuts are live editor verification, full HLSL/D3D12 SGM aggregation, calibrated projection constants, and then a global residual/calibration owner.
9. Move mic alignment, room suppression, voice separation, spatialization, and stem generation into Faust/native DSP. The C# diagnostic bridge now exists as MimirCalibratedAudioCompositeBuilder: it consumes synchronization states and measured band responses, emits a corrected composite plus scores, and is proved by --calibrated-audio-composite-smoke. It now also scores calibrated-band coherence and suppresses incoherent measured-band components before summing; --dual-mic-coherence-cancellation-smoke proves the two-mic case by cutting a mic-local 3.52 kHz interferer while preserving coherent shared tones. scripts/record-kiyo-dual-mic-composite.ps1 is the first listenable bridge: it records Kiyo video plus Scarlett ASIO raw channels, renders the channels 0/1 composite WAV with --asio-dual-mic-composite-wav, and muxes the computed mono composite into the Kiyo MP4. The bridge defaults now cap measured-band boost at 1.18x, apply stronger incoherent-band suppression, and do not enable the choppy C# residual expander by default. The Faust hot-lane target now exists as faust/mimir_dual_mic_dialogue_cleaner.dsp; Mimir queues it as dual-mic-dialogue-cleaner, consuming the alignment actuator's published aligned_source_* stem frame rather than raw mic buffers, and emitting host_voice plus a rejected residual witness. The routing smoke is --dialogue-cleaner-routing-smoke: it verifies post-alignment stems queue the cleaner program/block and that program publication belongs to the cleaner output, not the raw alignment lanes. Treat the C# bridge as the contract and offline scorer for the native/Faust implementation, not as a parallel live mixer authority. The next matching probe loop also exists as MimirTargetedBioacousticProbePlanner: residuals and mic pathology notes select gain-bounded shaped probe bands for the bioacoustic renderer. Start with the 192 kHz shotgun/cardioid pair; only widen to every connected mic once those two paths have credible direct-path and frequency-response confidence.
10. Keep the OBS bridge witness ledger as evidence before expanding receiver machinery.