MYND
integrated design reference
Current consolidated reference · 15 July 2026
One place to inspect the current architecture, design inputs, implementation status, Sonic reference work, evidence rules, build order, and unresolved integration decisions.
Use this as the navigation and integration layer: compare modules, check authority, open source documents, and keep working notes together.
02 · System architecture
Select a module to review its role, boundary, and evidence output. The fast control loop runs clockwise; the slower evidence path builds across sessions. AI remains outside the deterministic runtime.
03 · Current materials and status
Use the filters to separate source authority, implemented artifacts, planned work, and components that do not yet exist.
Canonical · corpus and build reference
The July 15 saved report passed 9/9 checks across 121 documents. This establishes corpus consistency, not efficacy or product completion.
Implemented · Sonic reference packet
Two Python renderers, a Web Audio study, a 7,201-row trace, the v0.1 preview, and the v0.2 24-bit ALAC study. These are open-loop reference fixtures, not biological validation.
Planned · integration work
These are documented build obligations, but they are not part of the current verifier or implemented runtime. E14 remains blocked on source recovery.
Not implemented · product runtime
The current executable work is corpus tooling and Sonic experiments. The integrated product runtime still needs to be built.
04 · Sonic Penrose reference
This conceptual viewer separates the two periodic coordinates, q and qᵣ, from the non-circular regime coordinate z. It is a reference visualization, not an audio engine.
Local pitch rises while the global field returns under octave relabeling.
A separate periodic coordinate controls local rate acceleration through tempo relabeling.
The non-circular z coordinate crosses event → flutter → roughness → repetition pitch → tone at 4 × 2ᶻ Hz.
The source describes coupling reduction, phase strain, slip/re-lock, boundary, and coherent resolve as a proposed transition sequence.
v0.2 · resolve reference
The sequence begins with a moving wideband field distributed across phase, waveform, and space.
Measurement note: analytic continuous-time coincidence is not literal sample-grid closure; the intended 1.8 ms peak falls between 48 kHz samples.
Listen · v0.1 preview
90-second AAC preview. The full 12-minute ALAC master is not present.
Listen · v0.2 study
90-second 24-bit ALAC. Most decoded QA metrics reproduced; the QA-generation pipeline is absent.
06 · Claims and evidence
Select a layer, then check the example claims below. Formal verification, acoustic measurement, sensor inference, and human experience answer different questions.
formal evidence
A bounded flow or guarded commit followed its specified constraints and emitted a valid trace.
constraint compliance, transition reason, trace validity
physiological improvement, acoustic correctness, or human benefit
Claim check
07 · Open design decisions
These are the current specification and provenance gaps. Mark each item open, working, or resolved; your states remain local to this browser.
Formally supersede stale “next command” wording so Foundation Slice 0 remains the only executable entry.
Define neighbor orientation, sign, and whether stored twist is total holonomy or per-edge α.
Add seeds, controller rate, cell phases/slips, q/qᵣ/z, frame bias, output mappings, and act labels.
Ship the v0.2 measurement pipeline and define sub-120 Hz correlation plus sample-grid closure.
Reconcile the documented 0.076–0.106 Hz range with the renderer’s actual 0.088–0.106 Hz path.
Merge E13/E14/P017 only through backlog, registry, fixtures, source recovery, and verifier updates.