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>
10 lines
1.2 KiB
Markdown
10 lines
1.2 KiB
Markdown
<!-- Source: Lumotia Master Brief — §14 Why Current Tools Fail -->
|
|
|
|
## 14. Why Current Tools Fail
|
|
|
|
- **Traditional to-do lists** list *what* needs doing without addressing *how* to start, immediately triggering overwhelm and analysis paralysis.
|
|
- **Rigid habit tracking and gamification** in existing ADHD apps feels guilt-inducing, impersonal, and overwhelming. They prioritise behaviour correction over emotional safety and flexibility.
|
|
- **Cloud latency kills focus.** Cloud-based apps require server round-trips for every action. For users with executive dysfunction, loading spinners introduce micro-distractions that break focus and frequently lead to task abandonment.
|
|
- **Cognitive overhead compounds fast.** Keystroke-Level Modelling shows that apps requiring manual syncing or custom rule-building add 4.7 seconds of cognitive overhead per interaction. After just 8 seconds of interruption, working memory traces decay beyond reliable reconstruction for ADHD neurotypes, increasing error rates by 63%.
|
|
- **App fatigue is endemic.** The market is flooded with generic productivity apps, leading to severe app fatigue among ADHD users who have tried and abandoned dozens of systems.
|