Mimir

Realtime cameras, microphones, chirplets, and field evidence organized into one coherent stream machine.

Reading Guide

2 min read

Reading Guide

Purpose

This directory is now large enough to need its own map. Use this guide when entering a future implementation pass cold.

If You Are Building The Active Decoder

Read in order:

  1. Chirplet Transform Deep Dive
  2. Decoder Architecture Options
  3. Microsecond Sync Math
  4. Current Hotspot Audit
  5. Optimization Ledger
  6. Low-Level Implementation Notes
  7. Benchmark Plan
  8. sample sketches:
    • samples/StreamingChirpBinDecoderSketch.cs
    • samples/BatchedChirpScoreAbiSketch.h
    • samples/CalibrationWeightedChirpLikelihoodSketch.cs
    • samples/Avx2DechirpGoertzelSketch.cpp
    • samples/ChirpBinScore.compute.hlsl

Decision:

  • implement streaming state first;
  • preserve the existing window decoder as oracle;
  • promote native/GPU scoring only after benchmarks.

If You Are Building Meatspace Calibration

Read in order:

  1. Volumetric Audio Field
  2. Acoustic Field Models
  3. Calibration Session Spec
  4. Prior Research Synthesis
  5. Benchmark Plan
  6. References

Decision:

  • learn usable bands per path;
  • shape symbol likelihood before codebook solving;
  • correct magnitude and phase/group delay;
  • adapt the emitted alphabet rather than filtering failure afterward.

If You Are Building The Audio Actuator

Read in order:

  1. Prior Research Synthesis
  2. Optimization Ledger
  3. Benchmark Plan
  4. sample sketches:
    • samples/FarrowFractionalDelaySketch.cpp
    • samples/SroPllAsrcControllerSketch.cpp

Decision:

  • delay and SRO are separate loops;
  • the runtime estimates state;
  • Faust/native DSP moves samples.

If You Are Building Camera Ingest

Read in order:

  1. Native Boundary Map
  2. Visual Fusion 4DGS Study
  3. Low-Level Implementation Notes
  4. Current Hotspot Audit
  5. Benchmark Plan
  6. Native Capture Cadence
  7. Native Rebuild Plan

Decision:

  • JSON probes are diagnostics;
  • production capture is native workers plus payload handles;
  • Fensalir owns GPU import and resource lifetime.

If You Are Building Fensalir Integration

Read in order:

  1. Fensalir Integration Map
  2. Native Boundary Map
  3. Visual Fusion 4DGS Study
  4. sample sketches:
    • samples/AquariumGpuSensorFrameBridgeSketch.cs
    • samples/AcousticConstraintLoweringSketch.cs
    • samples/TemporalEvidenceCandidateSketch.cs

Decision:

  • Mimir lowers observations/constraints;
  • Fensalir owns temporal evidence and render state;
  • the render tick must not run capture or analysis.

If You Are Looking For The Next Cut

Read in order:

  1. Implementation Roadmap
  2. Option Matrix
  3. Research Claims Digest
  4. Questions And Hypotheses
  5. Distributed Receiver Spec
  6. Current Hotspot Audit

Recommended next code cut:

  • streaming active decoder state with calibration-weighted likelihood;
  • benchmark it against the current window decoder;
  • then wire the actuator.

If You Are Updating Public Docs

Read:

  1. Perfect Machine Domain Index
  2. Code Algorithm Map
  3. Current System Map
  4. this directory’s Study Index

Rule:

  • public docs describe the live machine and current constraints;
  • research docs may hold scars, rejected paths, and implementation options.

Backlinks