Back to corpus
research noteexperiment writeup candidatescore 24

Directory Organization Summary

**Moved**: All UI components to Episode 1 - `dashboard.py` - Episode 1-specific dashboard (two-device balance, coherence, trajectories) - `audio_viz.py` - Audio visualization utilities - `gps_viz.py` - GPS visualization utilities

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Moved**: All UI components to Episode 1 - `dashboard.py` - Episode 1-specific dashboard (two-device balance, coherence, trajectories) - `audio_viz.py` - Audio visualization utilities - `gps_viz.py` - GPS visualization utilities **`fusion/` directory contains**: - `phase_lock.py` - Has both `PhaseLock` (general) and `DualPhaseLock` (Episode 1-specific) - `transformer.py` - ✅ Duplicate of `cc-core/cc_core/fusion/transformer.py` - `ekf.py` - ✅ Duplicate of `cc-core/cc_core/fusion/ekf.py` **`cc-core/cc_core/fusion/` already contains**: - `phase_lock.py` - Has `PhaseLock` (general-purpose) ✅ - `transformer.py` - ✅ - `ekf.py` - ✅ **`episode1/control/` already contains**: - `dual_phase_lock.py` - Episode 1-specific `DualPhaseLock` ✅ - `balance.py` - Episode 1-specific `BalanceFuser` ✅ **Files importing from `fusion/`**: - `tests/test_fusion.py` - `from fusion.balance import BalanceFuser` - `tests/test_performance.py` - `from fusion.balance import BalanceFuser` - `tests/test_ep1_pll.py` - `from fusion.phase_lock import PhaseLock` - `tests/test_ep1_balance.py` - `from fusion.balance import BalanceFuser` - `scripts/replay_episode1_session.py` - `from fusion.balance import BalanceFuser` - `scripts/run_episode1.py` - `from fusion.balance import BalanceFuser`, `from fusion.phase_lock import PhaseLock` - `inference/controller/episode1_controller.py` - `from fusion.balance import BalanceFuser`, `from fusion.phase_lock import PhaseLock, DualPhaseLock` - `inference/run_episode1_offline.py` - `from fusion.balance import BalanceFuser`

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.