Vibecode Superscribe

You are building a lean indie version of Superscribe.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# Superscribe indie build

## Goal

Build the smallest trustworthy replacement for the core Superscribe workflow for one developer or a tiny team.

## Scope

Bind a global hotkey, stream mic audio to a realtime STT API, run one LLM cleanup pass, and paste the result into whatever app has focus.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- call capture on your existing number (carrier forwarding into a CallKit softphone)
- glitch-free live word-by-word insertion tuned per app: terminals, Electron editors, browser contenteditables
- auto-filing: dictations and calls alike are matched to the right project via embeddings (enriched with GitHub repo context) plus live commit activity during the work block, so billable time lands on the right client without tagging
- the workspace around the transcripts: semantic search, invoice-ready PDF reports, CRM note drafts, a public API, and an MCP server
- Windows parity and signed, notarized auto-updating installers

If those capabilities are essential, use Handy instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build me a push-to-talk dictation tool for macOS to replace Superscribe's desktop app.
Requirements:

- Swift menu bar app, SPM only, no Xcode project. A global hotkey (default: hold
  Option+Space) records while held, stops on release.
- Capture the mic with AVAudioEngine, downsample to 16kHz mono PCM, and stream it
  over WebSocket to ElevenLabs Scribe realtime (key in .env). Show partial
  transcripts in a small floating panel while I speak.
- On release, run one LLM cleanup pass over the final transcript (fix punctuation,
  drop filler words; key in the same .env), then paste it into the focused app via
  NSPasteboard + CGEvent Cmd-V and restore my previous clipboard afterwards.
- Fallback: with no ElevenLabs key, record to a temp wav and transcribe locally
  with whisper.cpp instead. Slower is fine.
- Menu bar icon shows idle/recording/transcribing states; a history window lists
  the last 20 transcripts with copy buttons, persisted to ~/Dictation/history.jsonl.
- Ad-hoc codesign for my own machine only. README documents the Microphone and
  Accessibility permission prompts and the whisper.cpp model download.
- Out of scope: live word-by-word typing into the field (paste on release only),
  Windows support, accounts and billing, and the phone-call capture product. If I
  want call notes I will upload recordings by hand.

## Required capabilities

- macOS microphone + accessibility permissions
- streaming STT API key (ElevenLabs Scribe or Deepgram) or local whisper.cpp
- LLM API key for transcript cleanup
- Twilio account, a number, and an iOS device if you attempt the call-capture half

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a lean indie version of Superscribe.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# Superscribe indie build

## Goal

Build the smallest trustworthy replacement for the core Superscribe workflow for one developer or a tiny team.

## Scope

Bind a global hotkey, stream mic audio to a realtime STT API, run one LLM cleanup pass, and paste the result into whatever app has focus.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- call capture on your existing number (carrier forwarding into a CallKit softphone)
- glitch-free live word-by-word insertion tuned per app: terminals, Electron editors, browser contenteditables
- auto-filing: dictations and calls alike are matched to the right project via embeddings (enriched with GitHub repo context) plus live commit activity during the work block, so billable time lands on the right client without tagging
- the workspace around the transcripts: semantic search, invoice-ready PDF reports, CRM note drafts, a public API, and an MCP server
- Windows parity and signed, notarized auto-updating installers

If those capabilities are essential, use Handy instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build me a push-to-talk dictation tool for macOS to replace Superscribe's desktop app.
Requirements:

- Swift menu bar app, SPM only, no Xcode project. A global hotkey (default: hold
  Option+Space) records while held, stops on release.
- Capture the mic with AVAudioEngine, downsample to 16kHz mono PCM, and stream it
  over WebSocket to ElevenLabs Scribe realtime (key in .env). Show partial
  transcripts in a small floating panel while I speak.
- On release, run one LLM cleanup pass over the final transcript (fix punctuation,
  drop filler words; key in the same .env), then paste it into the focused app via
  NSPasteboard + CGEvent Cmd-V and restore my previous clipboard afterwards.
- Fallback: with no ElevenLabs key, record to a temp wav and transcribe locally
  with whisper.cpp instead. Slower is fine.
- Menu bar icon shows idle/recording/transcribing states; a history window lists
  the last 20 transcripts with copy buttons, persisted to ~/Dictation/history.jsonl.
- Ad-hoc codesign for my own machine only. README documents the Microphone and
  Accessibility permission prompts and the whisper.cpp model download.
- Out of scope: live word-by-word typing into the field (paste on release only),
  Windows support, accounts and billing, and the phone-call capture product. If I
  want call notes I will upload recordings by hand.

## Required capabilities

- macOS microphone + accessibility permissions
- streaming STT API key (ElevenLabs Scribe or Deepgram) or local whisper.cpp
- LLM API key for transcript cleanup
- Twilio account, a number, and an iOS device if you attempt the call-capture half

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a production product version of Superscribe.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== PRODUCT.md =====
# Superscribe product brief

## Problem

The desktop dictation half is a solved one-sitting build with complete open-source clones to fork. The hero product is not that: live-transcribing calls on your existing iPhone number takes carrier call forwarding, a pooled Twilio number, a CallKit/PushKit softphone, and a dual-track media-stream pipeline that can only be debugged against live phone calls. And a clone gets you a transcript file, not the workspace around it: roughly 45k lines of API and web app that embed every recording, time block, and project (with synced GitHub repo context), auto-file notes and billable time to the right client, and expose it all as reports, semantic search, a public API, and an MCP server. Each piece is a documented recipe; shipping all of them integrated is the multi-week part even before telephony.

## Product outcome

Bind a global hotkey, stream mic audio to a realtime STT API, run one LLM cleanup pass, and paste the result into whatever app has focus.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- macOS microphone + accessibility permissions
- streaming STT API key (ElevenLabs Scribe or Deepgram) or local whisper.cpp
- LLM API key for transcript cleanup
- Twilio account, a number, and an iOS device if you attempt the call-capture half

## Explicit non-goals for v1

- call capture on your existing number (carrier forwarding into a CallKit softphone)
- glitch-free live word-by-word insertion tuned per app: terminals, Electron editors, browser contenteditables
- auto-filing: dictations and calls alike are matched to the right project via embeddings (enriched with GitHub repo context) plus live commit activity during the work block, so billable time lands on the right client without tagging
- the workspace around the transcripts: semantic search, invoice-ready PDF reports, CRM note drafts, a public API, and an MCP server
- Windows parity and signed, notarized auto-updating installers

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

===== ARCHITECTURE.md =====
# Architecture

## Starting brief

Build me a push-to-talk dictation tool for macOS to replace Superscribe's desktop app.
Requirements:

- Swift menu bar app, SPM only, no Xcode project. A global hotkey (default: hold
  Option+Space) records while held, stops on release.
- Capture the mic with AVAudioEngine, downsample to 16kHz mono PCM, and stream it
  over WebSocket to ElevenLabs Scribe realtime (key in .env). Show partial
  transcripts in a small floating panel while I speak.
- On release, run one LLM cleanup pass over the final transcript (fix punctuation,
  drop filler words; key in the same .env), then paste it into the focused app via
  NSPasteboard + CGEvent Cmd-V and restore my previous clipboard afterwards.
- Fallback: with no ElevenLabs key, record to a temp wav and transcribe locally
  with whisper.cpp instead. Slower is fine.
- Menu bar icon shows idle/recording/transcribing states; a history window lists
  the last 20 transcripts with copy buttons, persisted to ~/Dictation/history.jsonl.
- Ad-hoc codesign for my own machine only. README documents the Microphone and
  Accessibility permission prompts and the whisper.cpp model download.
- Out of scope: live word-by-word typing into the field (paste on release only),
  Windows support, accounts and billing, and the phone-call capture product. If I
  want call notes I will upload recordings by hand.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

===== AGENTS.md =====
# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

===== MILESTONES.md =====
# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

===== OPERATIONS.md =====
# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted Superscribe capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# Superscribe indie build

## Goal

Build the smallest trustworthy replacement for the core Superscribe workflow for one developer or a tiny team.

## Scope

Bind a global hotkey, stream mic audio to a realtime STT API, run one LLM cleanup pass, and paste the result into whatever app has focus.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- call capture on your existing number (carrier forwarding into a CallKit softphone)
- glitch-free live word-by-word insertion tuned per app: terminals, Electron editors, browser contenteditables
- auto-filing: dictations and calls alike are matched to the right project via embeddings (enriched with GitHub repo context) plus live commit activity during the work block, so billable time lands on the right client without tagging
- the workspace around the transcripts: semantic search, invoice-ready PDF reports, CRM note drafts, a public API, and an MCP server
- Windows parity and signed, notarized auto-updating installers

If those capabilities are essential, use Handy instead of pretending the gap is solved.

# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

# Build plan

## Original build brief

Build me a push-to-talk dictation tool for macOS to replace Superscribe's desktop app.
Requirements:

- Swift menu bar app, SPM only, no Xcode project. A global hotkey (default: hold
  Option+Space) records while held, stops on release.
- Capture the mic with AVAudioEngine, downsample to 16kHz mono PCM, and stream it
  over WebSocket to ElevenLabs Scribe realtime (key in .env). Show partial
  transcripts in a small floating panel while I speak.
- On release, run one LLM cleanup pass over the final transcript (fix punctuation,
  drop filler words; key in the same .env), then paste it into the focused app via
  NSPasteboard + CGEvent Cmd-V and restore my previous clipboard afterwards.
- Fallback: with no ElevenLabs key, record to a temp wav and transcribe locally
  with whisper.cpp instead. Slower is fine.
- Menu bar icon shows idle/recording/transcribing states; a history window lists
  the last 20 transcripts with copy buttons, persisted to ~/Dictation/history.jsonl.
- Ad-hoc codesign for my own machine only. README documents the Microphone and
  Accessibility permission prompts and the whisper.cpp model download.
- Out of scope: live word-by-word typing into the field (paste on release only),
  Windows support, accounts and billing, and the phone-call capture product. If I
  want call notes I will upload recordings by hand.

## Required capabilities

- macOS microphone + accessibility permissions
- streaming STT API key (ElevenLabs Scribe or Deepgram) or local whisper.cpp
- LLM API key for transcript cleanup
- Twilio account, a number, and an iOS device if you attempt the call-capture half

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

# Superscribe product brief

## Problem

The desktop dictation half is a solved one-sitting build with complete open-source clones to fork. The hero product is not that: live-transcribing calls on your existing iPhone number takes carrier call forwarding, a pooled Twilio number, a CallKit/PushKit softphone, and a dual-track media-stream pipeline that can only be debugged against live phone calls. And a clone gets you a transcript file, not the workspace around it: roughly 45k lines of API and web app that embed every recording, time block, and project (with synced GitHub repo context), auto-file notes and billable time to the right client, and expose it all as reports, semantic search, a public API, and an MCP server. Each piece is a documented recipe; shipping all of them integrated is the multi-week part even before telephony.

## Product outcome

Bind a global hotkey, stream mic audio to a realtime STT API, run one LLM cleanup pass, and paste the result into whatever app has focus.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- macOS microphone + accessibility permissions
- streaming STT API key (ElevenLabs Scribe or Deepgram) or local whisper.cpp
- LLM API key for transcript cleanup
- Twilio account, a number, and an iOS device if you attempt the call-capture half

## Explicit non-goals for v1

- call capture on your existing number (carrier forwarding into a CallKit softphone)
- glitch-free live word-by-word insertion tuned per app: terminals, Electron editors, browser contenteditables
- auto-filing: dictations and calls alike are matched to the right project via embeddings (enriched with GitHub repo context) plus live commit activity during the work block, so billable time lands on the right client without tagging
- the workspace around the transcripts: semantic search, invoice-ready PDF reports, CRM note drafts, a public API, and an MCP server
- Windows parity and signed, notarized auto-updating installers

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

# Architecture

## Starting brief

Build me a push-to-talk dictation tool for macOS to replace Superscribe's desktop app.
Requirements:

- Swift menu bar app, SPM only, no Xcode project. A global hotkey (default: hold
  Option+Space) records while held, stops on release.
- Capture the mic with AVAudioEngine, downsample to 16kHz mono PCM, and stream it
  over WebSocket to ElevenLabs Scribe realtime (key in .env). Show partial
  transcripts in a small floating panel while I speak.
- On release, run one LLM cleanup pass over the final transcript (fix punctuation,
  drop filler words; key in the same .env), then paste it into the focused app via
  NSPasteboard + CGEvent Cmd-V and restore my previous clipboard afterwards.
- Fallback: with no ElevenLabs key, record to a temp wav and transcribe locally
  with whisper.cpp instead. Slower is fine.
- Menu bar icon shows idle/recording/transcribing states; a history window lists
  the last 20 transcripts with copy buttons, persisted to ~/Dictation/history.jsonl.
- Ad-hoc codesign for my own machine only. README documents the Microphone and
  Accessibility permission prompts and the whisper.cpp model download.
- Out of scope: live word-by-word typing into the field (paste on release only),
  Windows support, accounts and billing, and the phone-call capture product. If I
  want call notes I will upload recordings by hand.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted Superscribe capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

$ choose a build depth, inspect the files, then open the complete pack in your agent