Back to corpus
proposalexperiment writeup candidatescore 32

Echelon Phase 3 Detailed To-Do List

- [ ] **Whisper-rs Integration** (Phase 3) - [ ] Download Whisper model files - [ ] Complete voice recognizer implementation - [ ] Test voice recognition accuracy - [ ] Optimize for real-time performance

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

## Status Overview - **Phase 1**: ✅ Complete (Audio Engine) - **Phase 2**: ✅ Complete (Scheduler & Safety) - **Phase 3**: 🚧 In Progress (Motion, Voice & Phrase Intelligence) - Week 13: ✅ Complete (Motion Stream Integration) - Week 14: ✅ Complete (Voice Control Integration) - Week 15: ⏳ In Progress (Phrase Intelligence Service) - Week 16: ⏳ Pending (UI Foundation & Deck Lanes) - Week 17: ⏳ Pending (Phrase Browser & Automation) - Week 18: ⏳ Pending (Integration & Beta Review) ### 15.1 Phrase Database Service - [ ] **Create phrase-intelligence crate** - [ ] Add crate to workspace - [ ] Set up dependencies (FAISS bindings or alternative ANN) - [ ] Define `Phrase` struct with metadata - [ ] Define `PhraseDatabase` struct - [ ] Implement database loading from Episode 1 format - [ ] Implement FAISS index building - [ ] Implement `search_similar()` method - [ ] Add unit tests for phrase loading - [ ] Add unit tests for similarity search - **Dependencies:** FAISS Rust bindings or manual ANN implementation - **Deliverable:** Phrase database loads and searches phrases ### 15.2 Recommendation Engine - [ ] **Create PhraseRecommender struct** - [ ] Define `RecommendationContext` struct - [ ] Implement context-based recommendation strategy - [ ] Implement motion-driven recommendation strategy - [ ] Implement tempo-matched recommendation strategy - [ ] Implement mood-based recommendation strategy - [ ] Add `recommend()` method returning top-K phrases - [ ] Implement recommendation scoring algorithm - [ ] Add unit tests for recommendation strategies - **Dependencies:** Phrase database (15.1) - **Deliverable:** Recommendation engine suggests contextually appropriate phrases ### 15.3 Online Recommendation Service - [ ] **Create HTTP/gRPC service wrapper** - [ ] Define service endpoints (`POST /recommend`, `GET /phrase/{id}`) - [ ] Implement request/response types - [ ] Add caching layer for recent recommendations - [ ] Implement cache invalidation logic - [ ] Add latency tracking (<5 ms target) - [ ] Integrate with scheduler (motion events → recommendations) - [ ] Add integration tests - **Dependencies:** Recommendation engine (15.2) - **Deliverable:** Online service provides <5 ms phrase recommendations ### 16.1 UI Framework Setup - [ ] **Choose and set up UI framework** - [ ] Evaluate egui vs iced for performance/features - [ ] Create `echelon-ui` crate - [ ] Set up window management (main window, phrase browser, settings) - [ ] Implement IPC between UI and engine (channels or shared memory) - [ ] Add UI telemetry (FPS, render time tracking) - [ ] Create basic window layout - **Dependencies:** egui or iced crate - **Deliverable:** UI window opens and displays basic layout

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.