tl;dv

Build the following focused alternative to tl;dv. This is a deliberately limited personal or small-team substitute, not parity with the paid service.

WORKING SLICE
Import or explicitly record a meeting, drop highlight markers, transcribe locally and review summary notes plus timestamped clips.

SETUP AND ARCHITECTURE
Use Node, Express, SQLite FTS5, FFmpeg and a pinned whisper.cpp worker around imported or explicitly supported captured audio. Prerequisites: Consented audio, a local speech model, FFmpeg and a documented OS-specific capture route before enabling live recording. Before integrating anything, record actual versions and permissions, plus model files or provider limits only where used, in the README; make unavailable dependencies visible rather than simulating success.

DOMAIN MODEL AND INVARIANTS
Store Meeting, AudioSource, Marker, Segment, ClipRange and NotesRevision; markers map to the original recording clock and trims retain that mapping.

IMPLEMENTATION CONTRACT
Keep original timing alongside corrected text. Speech recognition does not itself establish speaker identity; permit manual speaker labels. Show undecodable audio and uncertain passages without inventing words. Provide an input/setup view, the main work view, and a review/export view appropriate to this workflow. Preserve the last saved state if a job or save fails. Include empty, loading, permission-denied, partial and retryable-error states. Log identifiers and error categories without secret values or unnecessary private content.

APP-SPECIFIC BOUNDARY AND RECOVERY
No meeting bot is required. Live system-audio capture needs a documented OS route; distinguish local whisper.cpp transcription from optional external summary/API processing.

ACCEPTANCE SCENARIO
Add a marker near the recording start, stop early and generate its clip; clamp the range to actual media bounds and preserve the original timestamp in notes. Also reopen the app after an interrupted operation, confirm the saved record/export remains inspectable, and document the recovery action. These are implementation acceptance requirements, not a claim that this guide has been tested.

DELIVERY
Deliver a runnable repository with migrations or project-format versioning, a non-sensitive example, environment/permission setup, the exact manual acceptance steps, and a backup/export-and-restore walkthrough. Implement the working slice before optional integrations; list any deferred paid-product capabilities honestly. Do not add capabilities outside the working slice just to resemble the original product.

PROJECT RULES FOR AGENTS.md
Keep the domain invariants above executable at the write boundary. Propose scope changes before adding providers or permissions. Never fabricate source evidence, publish results, identity matches or successful delivery. Preserve user originals and require an explicit confirmation for destructive changes or external publication.

# AGENTS.md — Build guide for tl;dv

## Project scope
Import or explicitly record a meeting, drop highlight markers, transcribe locally and review summary notes plus timestamped clips.

Catalogue verdict: kinda. A DIY app can record, transcribe, summarize, and generate clips, but tl;dv's team library, CRM integrations, and meeting-bot reliability are real work.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Runtime and tools: Node, Express, SQLite FTS5, FFmpeg and a pinned whisper.cpp worker around imported or explicitly supported captured audio.
- Before starting: Consented audio, a local speech model, FFmpeg and a documented OS-specific capture route before enabling live recording.

## Stack and architecture
- Node, Express, SQLite FTS5, FFmpeg and a pinned whisper.cpp worker around imported or explicitly supported captured audio
- Data design: Store Meeting, AudioSource, Marker, Segment, ClipRange and NotesRevision; markers map to the original recording clock and trims retain that mapping.
- Setup: Consented audio, a local speech model, FFmpeg and a documented OS-specific capture route before enabling live recording

## Security and data integrity
- Keep original timing alongside corrected text. Speech recognition does not itself establish speaker identity; permit manual speaker labels. Show undecodable audio and uncertain passages without inventing words.
- No meeting bot is required. Live system-audio capture needs a documented OS route; distinguish local whisper.cpp transcription from optional external summary/API processing.
- Keep secrets outside client bundles and exported projects; document what leaves the device and make retention/deletion controls visible.

## Agent implementation rules
- Project rule — domain: Store Meeting, AudioSource, Marker, Segment, ClipRange and NotesRevision; markers map to the original recording clock and trims retain that mapping.
- Project rule — scope and recovery: No meeting bot is required. Live system-audio capture needs a documented OS route; distinguish local whisper.cpp transcription from optional external summary/API processing.
- Project rule — acceptance: Add a marker near the recording start, stop early and generate its clip; clamp the range to actual media bounds and preserve the original timestamp in notes.
- Project rule — delivery: document real setup commands and permissions; do not claim a build, accuracy level, performance result or security certification that has not been demonstrated.

## Optional agent skills and references
- Recommended skill: [web-design-guidelines](https://github.com/vercel-labs/agent-skills/blob/main/skills/web-design-guidelines/SKILL.md) — review keyboard access, focus, validation, error recovery and the readable work/review interface or HTML report. Follow the maintainer's installation instructions and match its requirements to the chosen runtime.
- Recommended skill: [sharp-edges](https://github.com/trailofbits/skills/blob/main/plugins/sharp-edges/skills/sharp-edges/SKILL.md) — review configuration and API defaults against the app-specific invariants and recovery boundaries above; this is not a security certification. Follow the maintainer's installation instructions and match its requirements to the chosen runtime.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this working slice using synthetic or explicitly authorized non-sensitive examples: Import or explicitly record a meeting, drop highlight markers, transcribe locally and review summary notes plus timestamped clips.
- Share a synthetic example export and the acceptance walkthrough; keep real customer, health, financial and source data private: Add a marker near the recording start, stop early and generate its clip; clamp the range to actual media bounds and preserve the original timestamp in notes.
- State the limits before asking someone to replace their existing tool: No meeting bot is required. Live system-audio capture needs a documented OS route; distinguish local whisper.cpp transcription from optional external summary/API processing.

## Engineering roadmap
1. Phase 1 — Pin the working slice and create its example input: Import or explicitly record a meeting, drop highlight markers, transcribe locally and review summary notes plus timestamped clips. Confirm setup: Consented audio, a local speech model, FFmpeg and a documented OS-specific capture route before enabling live recording.
2. Phase 2 — Implement persistence and write-time invariants before decorating the UI: Store Meeting, AudioSource, Marker, Segment, ClipRange and NotesRevision; markers map to the original recording clock and trims retain that mapping.
3. Phase 3 — Connect the working view to real saved state. Keep original timing alongside corrected text. Speech recognition does not itself establish speaker identity; permit manual speaker labels. Show undecodable audio and uncertain passages without inventing words.
4. Phase 4 — Expose the app-specific limits and recovery path in context: No meeting bot is required. Live system-audio capture needs a documented OS route; distinguish local whisper.cpp transcription from optional external summary/API processing.
5. Phase 5 — Walk through this concrete acceptance case and preserve its exported evidence: Add a marker near the recording start, stop early and generate its clip; clamp the range to actual media bounds and preserve the original timestamp in notes. Finish the README and backup/restore instructions; report unfinished capabilities explicitly.

## Paid-product capabilities outside this build
- meeting bot upkeep
- team/shared library
- CRM integrations
- admin controls
- polished clip sharing

## Implementation prompt
Build the following focused alternative to tl;dv. This is a deliberately limited personal or small-team substitute, not parity with the paid service.

WORKING SLICE
Import or explicitly record a meeting, drop highlight markers, transcribe locally and review summary notes plus timestamped clips.

SETUP AND ARCHITECTURE
Use Node, Express, SQLite FTS5, FFmpeg and a pinned whisper.cpp worker around imported or explicitly supported captured audio. Prerequisites: Consented audio, a local speech model, FFmpeg and a documented OS-specific capture route before enabling live recording. Before integrating anything, record actual versions and permissions, plus model files or provider limits only where used, in the README; make unavailable dependencies visible rather than simulating success.

DOMAIN MODEL AND INVARIANTS
Store Meeting, AudioSource, Marker, Segment, ClipRange and NotesRevision; markers map to the original recording clock and trims retain that mapping.

IMPLEMENTATION CONTRACT
Keep original timing alongside corrected text. Speech recognition does not itself establish speaker identity; permit manual speaker labels. Show undecodable audio and uncertain passages without inventing words. Provide an input/setup view, the main work view, and a review/export view appropriate to this workflow. Preserve the last saved state if a job or save fails. Include empty, loading, permission-denied, partial and retryable-error states. Log identifiers and error categories without secret values or unnecessary private content.

APP-SPECIFIC BOUNDARY AND RECOVERY
No meeting bot is required. Live system-audio capture needs a documented OS route; distinguish local whisper.cpp transcription from optional external summary/API processing.

ACCEPTANCE SCENARIO
Add a marker near the recording start, stop early and generate its clip; clamp the range to actual media bounds and preserve the original timestamp in notes. Also reopen the app after an interrupted operation, confirm the saved record/export remains inspectable, and document the recovery action. These are implementation acceptance requirements, not a claim that this guide has been tested.

DELIVERY
Deliver a runnable repository with migrations or project-format versioning, a non-sensitive example, environment/permission setup, the exact manual acceptance steps, and a backup/export-and-restore walkthrough. Implement the working slice before optional integrations; list any deferred paid-product capabilities honestly. Do not add capabilities outside the working slice just to resemble the original product.

PROJECT RULES FOR AGENTS.md
Keep the domain invariants above executable at the write boundary. Propose scope changes before adding providers or permissions. Never fabricate source evidence, publish results, identity matches or successful delivery. Preserve user originals and require an explicit confirmation for destructive changes or external publication.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.