Jake
26c7307607
Phase 9 of the rebrand cascade. Sweep covers everything the Phase 8
frontend pass deliberately skipped: docs/, root markdown, scripts,
Cargo.toml descriptions, code comments that survived earlier
word-boundary sed, plus a handful of identifiers caught on the final
verify pass.
transcription-app changes:
- README.md, HANDOVER.md, KNOWN-ISSUES.md, run.sh — magnotia/Magnotia
-> lumotia/Lumotia.
- docs/ — sweep across all subdirs except docs/handovers/ (preserved
as immutable audit trail). Includes architecture-map references
to magnotia_core::*, magnotia_storage::*, etc. now pointing at
lumotia_*; dev-setup.md tracing output examples (lumotia_startup
target); brief/ + superpowers/ + issues/ + whisper-ecosystem/ +
audit/.
- Cargo.toml descriptions on 9 crates (core, audio, cloud-providers,
hotkey, llm, mcp, plus referenced others).
- crates/core/src/{error,hardware,recommendation,paths}.rs +
crates/audio/src/wav.rs + crates/llm/src/model_manager.rs +
crates/cloud-providers/src/keystore.rs + crates/mcp/src/lib.rs —
doc comments and a model-manager user-agent string.
- Caught on final pass: BroadcastChannel("magnotia_task_sync") -> ...
("lumotia_task_sync"); magnotia_locale i18n localStorage key
renamed + migration shim added; CSS keyframe names
magnotiaPulse / magnotiaBar / magnotiaFade renamed in the design-
system kit; magnotia_viewer_item / magnotia_viewer_mode handoff
keys renamed in HistoryPage + viewer/+page.svelte; src/assets/
wordmark.svg text.
- src-tauri/src/lib.rs comment cleanup ("magnotia era" was sed'd
to "lumotia era" earlier — restored).
Preserved (intentional):
- crates/core/src/paths.rs — keeps "magnotia" / "Magnotia" / ".magnotia"
legacy detection strings in legacy_and_target_paths() so the
migration shim can still find user data from the magnotia era.
- src/lib/stores/{page,focusTimer}.svelte.ts + src/lib/i18n/index.ts
— migration call sites reference the legacy magnotia keys
deliberately.
- docs/handovers/ — historical audit trail.
cargo build --workspace passes. npm run check: 0 errors / 0 warnings
(3958 files). cargo test --workspace: 339 pass / 0 fail.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2.6 KiB
2.6 KiB
10. Open Questions
Resolved (decisions made — see relevant sections)
Sync architecture→ cr-sqlite + iroh selected (section 3)Minimum hardware specs→ 8GB RAM, 2020+ CPU (section 3)CRDT library evaluation→ cr-sqlite for SQL-level CRDTs, iroh for networking (section 3)Whisper model selection→ ggml-base.en desktop, ggml-tiny.en mobile (section 3)LLM model selection→ Phi-4-mini (8GB), Qwen 3 7B (16GB), Llama 3.2 1B (mobile) (section 3)Waitlist tool→ LaunchList £65 one-time (section 7)Payment processor→ Lemon Squeezy 5% + 50p (section 7)Pricing validation method→ Van Westendorp survey via Tally (section 5)Bionic Reading implementation→ CSS regex (bold first N chars), text-vide npm package or custom, MIT licensedNudging delivery mechanism→ tauri-plugin-notification + Web Audio API chimes + context-aware suppression (section 4)
Still open
- Exact free tier limitations (number of tasks? transcriptions? time limit?)
- Which frontier AI model for cloud tier (Claude, GPT-4o, other?)
- App store submission timeline and requirements for Android/iOS
- Sensory preference persistence ("sensory cookies") — save user's baseline motion/contrast/typography settings across sessions. MVP or v2?
- Emotionally adaptive UI (detect frustration/fatigue, auto-simplify interface) — v2+ feature, but worth architecting for early
- Mac App Store sandboxing compatibility with Tauri — needs hands-on testing
- Access to Work approval process for specific software products — exact requirements TBD
- Search volume data for "ADHD desktop app", "ADHD app for Windows" etc. — validate with Ahrefs/SEMrush before committing to SEO strategy
- Tiimo's B2B pricing (not publicly available) — competitive intelligence via test enquiry
- Visual timeline implementation — time blocks, Gantt-style, or simpler countdown view? Validate with beta testers.
- Smartwatch integration for haptic nudges — Tauri v2 wearable support? Or companion app?
- Low-fi body doubling: would showing anonymised user count ("3 others in deep work") require any server component? Could use iroh peer count from paired devices, but broader anonymous count needs a lightweight coordination mechanism.
- Start/shutdown ritual UX: how prescriptive should the morning triage be? Fully AI-driven or user-guided? Beta test both approaches.
- cr-sqlite development pace risk: monitor vlcn.io activity. If stalled, migrate to Automerge + SQLite BLOB storage (networking layer unchanged).