Vibecode Thrumble

You are building a lean indie version of Thrumble.

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 =====
# Thrumble indie build

## Goal

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

## Scope

Answer one inbound number with a realtime STT → LLM → TTS agent, look something up, and log the call outcome.

## 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:
- hosted agent builder, knowledge bases, tools, and transfer destinations
- outbound campaign dialer and contact workflows
- managed phone numbers, concurrency, and telephony debugging
- call logs, recordings, post-call extraction, and analytics
- uptime, support, and multi-tenant workspace polish

If those capabilities are essential, use LiveKit Agents + SIP 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 focused self-hosted alternative to Thrumble for one inbound business number.
Requirements:

- Python 3.12 + livekit-agents with one AgentServer worker.
  Direct provider plugins only · no managed agent host.
- Docker Compose: LiveKit Server, Redis, LiveKit SIP, Caddy for HTTPS/WSS.
  Expose only documented SIP and UDP media ports.
- One Telnyx DID + credential SIP trunk. Checked-in inbound-trunk and
  dispatch-rule JSON that routes calls to receptionist-agent.
- AgentSession: Silero VAD, Deepgram STT, gpt-4.1-mini (OpenAI plugin),
  Cartesia TTS. Secrets only from .env.
- Narrow receptionist prompt: answer FAQs from a local knowledge.md,
  book a callback into SQLite after confirmation, transfer is out of scope.
- Persist call id, timestamps, transcript, and outcome to SQLite.
  JSON logs + /healthz. Recording off by default.
- Unit tests for FAQ lookup and callback confirmation; scripted agent tests
  for interruption and refusal to invent facts.
- make setup / make dev / make smoke + docker compose up -d.
  Smoke test must pass in the LiveKit agent console before a real PSTN call.
- README: DNS, TLS, firewall, Telnyx, trunk, keys, test-call steps,
  and common one-way-audio / SIP auth failures.
- Out of scope: outbound campaigns, multi-tenant dashboard, knowledge-base
  crawler, tool marketplace, call transfer, billing, HA, compliance claims.

## Required capabilities

- public VM with TLS and correctly opened SIP / WebRTC / RTP ports
- SIP trunk and phone number (e.g. Telnyx)
- STT, LLM, and TTS API keys
- consent and recording rules for your country before real traffic

## 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 Thrumble.

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 =====
# Thrumble indie build

## Goal

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

## Scope

Answer one inbound number with a realtime STT → LLM → TTS agent, look something up, and log the call outcome.

## 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:
- hosted agent builder, knowledge bases, tools, and transfer destinations
- outbound campaign dialer and contact workflows
- managed phone numbers, concurrency, and telephony debugging
- call logs, recordings, post-call extraction, and analytics
- uptime, support, and multi-tenant workspace polish

If those capabilities are essential, use LiveKit Agents + SIP 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 focused self-hosted alternative to Thrumble for one inbound business number.
Requirements:

- Python 3.12 + livekit-agents with one AgentServer worker.
  Direct provider plugins only · no managed agent host.
- Docker Compose: LiveKit Server, Redis, LiveKit SIP, Caddy for HTTPS/WSS.
  Expose only documented SIP and UDP media ports.
- One Telnyx DID + credential SIP trunk. Checked-in inbound-trunk and
  dispatch-rule JSON that routes calls to receptionist-agent.
- AgentSession: Silero VAD, Deepgram STT, gpt-4.1-mini (OpenAI plugin),
  Cartesia TTS. Secrets only from .env.
- Narrow receptionist prompt: answer FAQs from a local knowledge.md,
  book a callback into SQLite after confirmation, transfer is out of scope.
- Persist call id, timestamps, transcript, and outcome to SQLite.
  JSON logs + /healthz. Recording off by default.
- Unit tests for FAQ lookup and callback confirmation; scripted agent tests
  for interruption and refusal to invent facts.
- make setup / make dev / make smoke + docker compose up -d.
  Smoke test must pass in the LiveKit agent console before a real PSTN call.
- README: DNS, TLS, firewall, Telnyx, trunk, keys, test-call steps,
  and common one-way-audio / SIP auth failures.
- Out of scope: outbound campaigns, multi-tenant dashboard, knowledge-base
  crawler, tool marketplace, call transfer, billing, HA, compliance claims.

## Required capabilities

- public VM with TLS and correctly opened SIP / WebRTC / RTP ports
- SIP trunk and phone number (e.g. Telnyx)
- STT, LLM, and TTS API keys
- consent and recording rules for your country before real traffic

## 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 Thrumble.

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 =====
# Thrumble product brief

## Problem

A single inbound receptionist agent is a credible weekend build with LiveKit Agents or Pipecat plus a SIP trunk. Thrumble as a product is larger: agent config UI, knowledge bases, tools, call transfer, outbound campaigns, phone numbers, transcripts, and production telephony. You can DIY the core conversation loop; you still own carriers, media ports, failed calls, and ops.

## Product outcome

Answer one inbound number with a realtime STT → LLM → TTS agent, look something up, and log the call outcome.

## Target user

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

## Required capabilities

- public VM with TLS and correctly opened SIP / WebRTC / RTP ports
- SIP trunk and phone number (e.g. Telnyx)
- STT, LLM, and TTS API keys
- consent and recording rules for your country before real traffic

## Explicit non-goals for v1

- hosted agent builder, knowledge bases, tools, and transfer destinations
- outbound campaign dialer and contact workflows
- managed phone numbers, concurrency, and telephony debugging
- call logs, recordings, post-call extraction, and analytics
- uptime, support, and multi-tenant workspace polish

## 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 focused self-hosted alternative to Thrumble for one inbound business number.
Requirements:

- Python 3.12 + livekit-agents with one AgentServer worker.
  Direct provider plugins only · no managed agent host.
- Docker Compose: LiveKit Server, Redis, LiveKit SIP, Caddy for HTTPS/WSS.
  Expose only documented SIP and UDP media ports.
- One Telnyx DID + credential SIP trunk. Checked-in inbound-trunk and
  dispatch-rule JSON that routes calls to receptionist-agent.
- AgentSession: Silero VAD, Deepgram STT, gpt-4.1-mini (OpenAI plugin),
  Cartesia TTS. Secrets only from .env.
- Narrow receptionist prompt: answer FAQs from a local knowledge.md,
  book a callback into SQLite after confirmation, transfer is out of scope.
- Persist call id, timestamps, transcript, and outcome to SQLite.
  JSON logs + /healthz. Recording off by default.
- Unit tests for FAQ lookup and callback confirmation; scripted agent tests
  for interruption and refusal to invent facts.
- make setup / make dev / make smoke + docker compose up -d.
  Smoke test must pass in the LiveKit agent console before a real PSTN call.
- README: DNS, TLS, firewall, Telnyx, trunk, keys, test-call steps,
  and common one-way-audio / SIP auth failures.
- Out of scope: outbound campaigns, multi-tenant dashboard, knowledge-base
  crawler, tool marketplace, call transfer, billing, HA, compliance claims.

## 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 Thrumble capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# Thrumble indie build

## Goal

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

## Scope

Answer one inbound number with a realtime STT → LLM → TTS agent, look something up, and log the call outcome.

## 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:
- hosted agent builder, knowledge bases, tools, and transfer destinations
- outbound campaign dialer and contact workflows
- managed phone numbers, concurrency, and telephony debugging
- call logs, recordings, post-call extraction, and analytics
- uptime, support, and multi-tenant workspace polish

If those capabilities are essential, use LiveKit Agents + SIP 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 focused self-hosted alternative to Thrumble for one inbound business number.
Requirements:

- Python 3.12 + livekit-agents with one AgentServer worker.
  Direct provider plugins only · no managed agent host.
- Docker Compose: LiveKit Server, Redis, LiveKit SIP, Caddy for HTTPS/WSS.
  Expose only documented SIP and UDP media ports.
- One Telnyx DID + credential SIP trunk. Checked-in inbound-trunk and
  dispatch-rule JSON that routes calls to receptionist-agent.
- AgentSession: Silero VAD, Deepgram STT, gpt-4.1-mini (OpenAI plugin),
  Cartesia TTS. Secrets only from .env.
- Narrow receptionist prompt: answer FAQs from a local knowledge.md,
  book a callback into SQLite after confirmation, transfer is out of scope.
- Persist call id, timestamps, transcript, and outcome to SQLite.
  JSON logs + /healthz. Recording off by default.
- Unit tests for FAQ lookup and callback confirmation; scripted agent tests
  for interruption and refusal to invent facts.
- make setup / make dev / make smoke + docker compose up -d.
  Smoke test must pass in the LiveKit agent console before a real PSTN call.
- README: DNS, TLS, firewall, Telnyx, trunk, keys, test-call steps,
  and common one-way-audio / SIP auth failures.
- Out of scope: outbound campaigns, multi-tenant dashboard, knowledge-base
  crawler, tool marketplace, call transfer, billing, HA, compliance claims.

## Required capabilities

- public VM with TLS and correctly opened SIP / WebRTC / RTP ports
- SIP trunk and phone number (e.g. Telnyx)
- STT, LLM, and TTS API keys
- consent and recording rules for your country before real traffic

## 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.

# Thrumble product brief

## Problem

A single inbound receptionist agent is a credible weekend build with LiveKit Agents or Pipecat plus a SIP trunk. Thrumble as a product is larger: agent config UI, knowledge bases, tools, call transfer, outbound campaigns, phone numbers, transcripts, and production telephony. You can DIY the core conversation loop; you still own carriers, media ports, failed calls, and ops.

## Product outcome

Answer one inbound number with a realtime STT → LLM → TTS agent, look something up, and log the call outcome.

## Target user

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

## Required capabilities

- public VM with TLS and correctly opened SIP / WebRTC / RTP ports
- SIP trunk and phone number (e.g. Telnyx)
- STT, LLM, and TTS API keys
- consent and recording rules for your country before real traffic

## Explicit non-goals for v1

- hosted agent builder, knowledge bases, tools, and transfer destinations
- outbound campaign dialer and contact workflows
- managed phone numbers, concurrency, and telephony debugging
- call logs, recordings, post-call extraction, and analytics
- uptime, support, and multi-tenant workspace polish

## 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 focused self-hosted alternative to Thrumble for one inbound business number.
Requirements:

- Python 3.12 + livekit-agents with one AgentServer worker.
  Direct provider plugins only · no managed agent host.
- Docker Compose: LiveKit Server, Redis, LiveKit SIP, Caddy for HTTPS/WSS.
  Expose only documented SIP and UDP media ports.
- One Telnyx DID + credential SIP trunk. Checked-in inbound-trunk and
  dispatch-rule JSON that routes calls to receptionist-agent.
- AgentSession: Silero VAD, Deepgram STT, gpt-4.1-mini (OpenAI plugin),
  Cartesia TTS. Secrets only from .env.
- Narrow receptionist prompt: answer FAQs from a local knowledge.md,
  book a callback into SQLite after confirmation, transfer is out of scope.
- Persist call id, timestamps, transcript, and outcome to SQLite.
  JSON logs + /healthz. Recording off by default.
- Unit tests for FAQ lookup and callback confirmation; scripted agent tests
  for interruption and refusal to invent facts.
- make setup / make dev / make smoke + docker compose up -d.
  Smoke test must pass in the LiveKit agent console before a real PSTN call.
- README: DNS, TLS, firewall, Telnyx, trunk, keys, test-call steps,
  and common one-way-audio / SIP auth failures.
- Out of scope: outbound campaigns, multi-tenant dashboard, knowledge-base
  crawler, tool marketplace, call transfer, billing, HA, compliance claims.

## 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 Thrumble 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