yunchan/d3ro-voice
1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions
d3ro-voice/docs/map/00-index.md
Yun Chan 2d585bfc29 feat(desktop): make local speech transcription work end to end 
Local dictation had never produced a transcript on an installed build. The
engine itself was healthy; every connection to it was broken.

Installed builds shipped no speech engine at all: the packaging config had no
entry for the faster-whisper sidecar and no pipeline step built one, so the app
always fell back to a system Python without the runtime. Development was broken
too, because the sidecar and SoX paths were resolved against the Vite output
directory instead of the app root, which also meant recording failed with a SoX
ENOENT. On hosts where localhost resolves only to IPv6, every local request was
refused outright, which silently disabled both local transcription and the local
LLM.

The sidecar is now built and bundled (including the Silero VAD data it needs),
gated by a packaging check that fails when the engine or its data is missing.
Paths are discovered from the app root and fail loudly when the engine is
absent. Local engine URLs are normalized to the IPv4 loopback, decoding is tuned
so repeated hallucinations cannot compound (the same transcript now takes about
a fifth of the time), the engine is warmed up at startup, and holding the hotkey
now shows the text forming live in the recording tip.
2026-09-18 00:48:47 +09:00

4.5 KiB
Raw Blame History

D3RO Voice — Feature & Infrastructure Map (Index)

Status: ACTIVE Last full audit: 2026-09-13 Scope: entire monorepo D:/workspace/D3ROVoice at product version 1.3.0 Purpose: let any agent (or human) answer two questions in under a minute:

  1. What infrastructure exists? (build, CI, services, APIs, data, packages, deploy)
  2. How far is each feature developed? (per surface, with file anchors and status)

This is the entry point. Read the index, then open only the sub-document you need. Do not read all files every time.

1. How to use this map

You need to know… Open
The product, its IA, platforms, identity/data model 01-system-overview.md
Repo layout, build, CI/CD, Docker, deploy, scripts, docs 02-infrastructure.md
Shared packages (@d3ro/core, ui, ui-native, i18n, api-client) 03-shared-packages.md
Desktop (Electron) services, IPC, pages, popups, status 04-desktop-app.md
Web (Next.js) routes, components, clients, status 05-web-app.md
Mobile (React Native) screens, features, tabs, status 06-mobile-app.md
.NET cloud API: controllers, services, tables, auth 07-api-server.md
Admin back office (Next.js) routes, guards, status 08-admin-console.md
Supabase migrations, Edge Functions, Cloudflare worker 09-supabase-backend.md
The feature map — every feature, per platform, with status 10-feature-catalog.md
Known gaps / under-developed / backlog 11-gap-backlog.md
Mandatory rules for keeping this map current 12-update-protocol.md

An agent starting a task should:

  1. Read the relevant surface doc (04–09) for infrastructure.
  2. Read 10-feature-catalog.md for the feature's current status and platform coverage.
  3. Read 11-gap-backlog.md to see if the feature is already tracked as backlog.
  4. After finishing, follow 12-update-protocol.md before the work is considered done.

2. Status legend

Feature rows in 10-feature-catalog.md use this scale:

Symbol Meaning
[x] Implemented and verified on this platform (code + tests / evidence exist in-repo).
[~] Implemented but partial, unverified, or blocked on an external/console gate.
[ ] Planned or absent on this platform.
[!] Blocked on something outside the repo (external console, secret, physical device, store review).
[-] Not applicable to this platform (with a one-line reason).

Status is per platform. A feature can be [x] on desktop, [~] on mobile, [ ] on web.

3. One-paragraph system summary

D3RO Voice is a multi-platform AI voice assistant (transcription, LLM command execution, meeting intelligence, RAG, voice conversation) sold as Free / Pro / Pro+ / Team / Enterprise tiers. It ships as an Electron desktop app (local-first: bundled SoX, faster-whisper sidecar, Ollama, local SQLite), a React Native mobile app (apps/mobile-rn, cloud-first: Supabase auth + Edge Functions + on-device Whisper fallback), a Next.js web console, a Next.js admin back office, and a .NET cloud API (AI proxy + back office backend). The shared backend is Supabase (Postgres + RLS + Auth + Storage + ~27 Deno Edge Functions), deployed to a Synology NAS via Docker with a Cloudflare edge worker and tunnel. Shared code lives in packages/*. Distribution: Windows NSIS + macOS DMG (GitLab/Forgejo feed + electron-updater), Android APK/AAB via Google Play.

4. Reading order for a brand-new agent

  1. AGENTS.md (root) — operating rules + the obligation to update this map.
  2. docs/map/01-system-overview.md — the big picture and IA.
  3. The surface doc for your task (04–09).
  4. docs/map/10-feature-catalog.md — find the feature and its status.
  5. docs/map/11-gap-backlog.md — check for existing backlog notes.

Deeper design history (not required to start): docs/design/*, docs/phases/*, docs/v2/*, docs/v3/*, memory/*, CHANGELOG.md. The mobile SSOT is docs/v3/MOBILE_APP_COMPLETION_SSOT.md.

5. Maintenance

This map must change whenever a feature is added, removed, changed, or deferred. See 12-update-protocol.md for the exact checklist and AGENTS.md for the agent obligation.