Vibecode CineSend

You are building a lean indie version of CineSend.

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

## Goal

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

## Scope

The honest floor: expiring private screener links with a visible per-viewer burn-in, view limits, and an access log. Deterrence, not security.

## 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:
- NexGuard forensic watermarking that survives re-encoding and a phone pointed at the screen
- Widevine, FairPlay, and PlayReady DRM, which require licensed keys issued to companies
- the studio and festival trust that makes anyone send you a master in the first place
- Aspera acceleration for moving finished masters across continents
- branded Apple TV, Roku, Fire TV, and smart TV apps for the screening room
- the audit trail and chain of custody a distribution contract asks for

If those capabilities are essential, use Nextcloud 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 watermarked private screener site for footage I own: my own film,
a rough cut for producers, a festival submission I control. This is the
deliberately low-stakes floor of CineSend, never a substitute for it when
someone else's unreleased master is involved. Requirements:

- Node + Express + better-sqlite3 on a VPS, media in Cloudflare R2, hls.js for
  playback. Server-rendered pages, no frontend framework.
- I invite viewers by name and email. Each gets a single-use /s/<random-id> link tied
  to that address, with an expiry date and a max view count I set per invite.
- ffmpeg burns the viewer's name, email, and the date into the picture as a semi
  transparent overlay, one encode per viewer, cached in R2 and deleted on expiry. It
  is visible and it is meant to be, deterrence is the entire mechanism.
- Every play logs timestamp, IP, user agent, and how far they watched, shown on an
  /admin page behind basic auth. I can revoke any link instantly.
- Downloads are off, right click is off, and the manifest URL is signed and short
  lived. State plainly in the UI that none of this stops a screen recording.
- SQLite holds invites and the access log, R2 keys and the SMTP credentials come from
  .env. No accounts for viewers, no telemetry, no third party analytics.
- Out of scope: DRM, forensic watermarking, and TV apps. Do not claim to implement
  any of them and do not build a fake watermark that only sounds forensic.
- README: R2 and signed URL setup, per-viewer encode cost and time, and one blunt
  paragraph saying this is deterrence only and must never be used for a title under
  someone else's security requirements.

## Required capabilities

- ffmpeg
- object storage plus a CDN
- a VPS for the screener pages
- an email sender for invites
- an accurate understanding of what a visible watermark does and does not stop

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

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

## Goal

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

## Scope

The honest floor: expiring private screener links with a visible per-viewer burn-in, view limits, and an access log. Deterrence, not security.

## 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:
- NexGuard forensic watermarking that survives re-encoding and a phone pointed at the screen
- Widevine, FairPlay, and PlayReady DRM, which require licensed keys issued to companies
- the studio and festival trust that makes anyone send you a master in the first place
- Aspera acceleration for moving finished masters across continents
- branded Apple TV, Roku, Fire TV, and smart TV apps for the screening room
- the audit trail and chain of custody a distribution contract asks for

If those capabilities are essential, use Nextcloud 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 watermarked private screener site for footage I own: my own film,
a rough cut for producers, a festival submission I control. This is the
deliberately low-stakes floor of CineSend, never a substitute for it when
someone else's unreleased master is involved. Requirements:

- Node + Express + better-sqlite3 on a VPS, media in Cloudflare R2, hls.js for
  playback. Server-rendered pages, no frontend framework.
- I invite viewers by name and email. Each gets a single-use /s/<random-id> link tied
  to that address, with an expiry date and a max view count I set per invite.
- ffmpeg burns the viewer's name, email, and the date into the picture as a semi
  transparent overlay, one encode per viewer, cached in R2 and deleted on expiry. It
  is visible and it is meant to be, deterrence is the entire mechanism.
- Every play logs timestamp, IP, user agent, and how far they watched, shown on an
  /admin page behind basic auth. I can revoke any link instantly.
- Downloads are off, right click is off, and the manifest URL is signed and short
  lived. State plainly in the UI that none of this stops a screen recording.
- SQLite holds invites and the access log, R2 keys and the SMTP credentials come from
  .env. No accounts for viewers, no telemetry, no third party analytics.
- Out of scope: DRM, forensic watermarking, and TV apps. Do not claim to implement
  any of them and do not build a fake watermark that only sounds forensic.
- README: R2 and signed URL setup, per-viewer encode cost and time, and one blunt
  paragraph saying this is deterrence only and must never be used for a title under
  someone else's security requirements.

## Required capabilities

- ffmpeg
- object storage plus a CDN
- a VPS for the screener pages
- an email sender for invites
- an accurate understanding of what a visible watermark does and does not stop

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

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

## Problem

The file delivery is not the product. The product is that A24, HBO, and Sundance accept it. A screener page with an expiring link is an afternoon, and it buys you nothing, because the two things CineSend actually sells cannot be written by an agent at any price: forensic watermarking, which is a licensed product from Nagra that survives a camcorder pointed at a monitor and traces the leak back to one named viewer, and studio-grade DRM, which needs license keys Google and Apple issue to companies, not to your VPS. Underneath both sits the part no code touches · a rights holder's legal team signing off on where their unreleased master is allowed to sit. You can build a private video page. You cannot build permission to receive the film.

## Product outcome

The honest floor: expiring private screener links with a visible per-viewer burn-in, view limits, and an access log. Deterrence, not security.

## Target user

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

## Required capabilities

- ffmpeg
- object storage plus a CDN
- a VPS for the screener pages
- an email sender for invites
- an accurate understanding of what a visible watermark does and does not stop

## Explicit non-goals for v1

- NexGuard forensic watermarking that survives re-encoding and a phone pointed at the screen
- Widevine, FairPlay, and PlayReady DRM, which require licensed keys issued to companies
- the studio and festival trust that makes anyone send you a master in the first place
- Aspera acceleration for moving finished masters across continents
- branded Apple TV, Roku, Fire TV, and smart TV apps for the screening room
- the audit trail and chain of custody a distribution contract asks for

## 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 watermarked private screener site for footage I own: my own film,
a rough cut for producers, a festival submission I control. This is the
deliberately low-stakes floor of CineSend, never a substitute for it when
someone else's unreleased master is involved. Requirements:

- Node + Express + better-sqlite3 on a VPS, media in Cloudflare R2, hls.js for
  playback. Server-rendered pages, no frontend framework.
- I invite viewers by name and email. Each gets a single-use /s/<random-id> link tied
  to that address, with an expiry date and a max view count I set per invite.
- ffmpeg burns the viewer's name, email, and the date into the picture as a semi
  transparent overlay, one encode per viewer, cached in R2 and deleted on expiry. It
  is visible and it is meant to be, deterrence is the entire mechanism.
- Every play logs timestamp, IP, user agent, and how far they watched, shown on an
  /admin page behind basic auth. I can revoke any link instantly.
- Downloads are off, right click is off, and the manifest URL is signed and short
  lived. State plainly in the UI that none of this stops a screen recording.
- SQLite holds invites and the access log, R2 keys and the SMTP credentials come from
  .env. No accounts for viewers, no telemetry, no third party analytics.
- Out of scope: DRM, forensic watermarking, and TV apps. Do not claim to implement
  any of them and do not build a fake watermark that only sounds forensic.
- README: R2 and signed URL setup, per-viewer encode cost and time, and one blunt
  paragraph saying this is deterrence only and must never be used for a title under
  someone else's security requirements.

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

# CineSend indie build

## Goal

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

## Scope

The honest floor: expiring private screener links with a visible per-viewer burn-in, view limits, and an access log. Deterrence, not security.

## 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:
- NexGuard forensic watermarking that survives re-encoding and a phone pointed at the screen
- Widevine, FairPlay, and PlayReady DRM, which require licensed keys issued to companies
- the studio and festival trust that makes anyone send you a master in the first place
- Aspera acceleration for moving finished masters across continents
- branded Apple TV, Roku, Fire TV, and smart TV apps for the screening room
- the audit trail and chain of custody a distribution contract asks for

If those capabilities are essential, use Nextcloud 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 watermarked private screener site for footage I own: my own film,
a rough cut for producers, a festival submission I control. This is the
deliberately low-stakes floor of CineSend, never a substitute for it when
someone else's unreleased master is involved. Requirements:

- Node + Express + better-sqlite3 on a VPS, media in Cloudflare R2, hls.js for
  playback. Server-rendered pages, no frontend framework.
- I invite viewers by name and email. Each gets a single-use /s/<random-id> link tied
  to that address, with an expiry date and a max view count I set per invite.
- ffmpeg burns the viewer's name, email, and the date into the picture as a semi
  transparent overlay, one encode per viewer, cached in R2 and deleted on expiry. It
  is visible and it is meant to be, deterrence is the entire mechanism.
- Every play logs timestamp, IP, user agent, and how far they watched, shown on an
  /admin page behind basic auth. I can revoke any link instantly.
- Downloads are off, right click is off, and the manifest URL is signed and short
  lived. State plainly in the UI that none of this stops a screen recording.
- SQLite holds invites and the access log, R2 keys and the SMTP credentials come from
  .env. No accounts for viewers, no telemetry, no third party analytics.
- Out of scope: DRM, forensic watermarking, and TV apps. Do not claim to implement
  any of them and do not build a fake watermark that only sounds forensic.
- README: R2 and signed URL setup, per-viewer encode cost and time, and one blunt
  paragraph saying this is deterrence only and must never be used for a title under
  someone else's security requirements.

## Required capabilities

- ffmpeg
- object storage plus a CDN
- a VPS for the screener pages
- an email sender for invites
- an accurate understanding of what a visible watermark does and does not stop

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

# CineSend product brief

## Problem

The file delivery is not the product. The product is that A24, HBO, and Sundance accept it. A screener page with an expiring link is an afternoon, and it buys you nothing, because the two things CineSend actually sells cannot be written by an agent at any price: forensic watermarking, which is a licensed product from Nagra that survives a camcorder pointed at a monitor and traces the leak back to one named viewer, and studio-grade DRM, which needs license keys Google and Apple issue to companies, not to your VPS. Underneath both sits the part no code touches · a rights holder's legal team signing off on where their unreleased master is allowed to sit. You can build a private video page. You cannot build permission to receive the film.

## Product outcome

The honest floor: expiring private screener links with a visible per-viewer burn-in, view limits, and an access log. Deterrence, not security.

## Target user

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

## Required capabilities

- ffmpeg
- object storage plus a CDN
- a VPS for the screener pages
- an email sender for invites
- an accurate understanding of what a visible watermark does and does not stop

## Explicit non-goals for v1

- NexGuard forensic watermarking that survives re-encoding and a phone pointed at the screen
- Widevine, FairPlay, and PlayReady DRM, which require licensed keys issued to companies
- the studio and festival trust that makes anyone send you a master in the first place
- Aspera acceleration for moving finished masters across continents
- branded Apple TV, Roku, Fire TV, and smart TV apps for the screening room
- the audit trail and chain of custody a distribution contract asks for

## 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 watermarked private screener site for footage I own: my own film,
a rough cut for producers, a festival submission I control. This is the
deliberately low-stakes floor of CineSend, never a substitute for it when
someone else's unreleased master is involved. Requirements:

- Node + Express + better-sqlite3 on a VPS, media in Cloudflare R2, hls.js for
  playback. Server-rendered pages, no frontend framework.
- I invite viewers by name and email. Each gets a single-use /s/<random-id> link tied
  to that address, with an expiry date and a max view count I set per invite.
- ffmpeg burns the viewer's name, email, and the date into the picture as a semi
  transparent overlay, one encode per viewer, cached in R2 and deleted on expiry. It
  is visible and it is meant to be, deterrence is the entire mechanism.
- Every play logs timestamp, IP, user agent, and how far they watched, shown on an
  /admin page behind basic auth. I can revoke any link instantly.
- Downloads are off, right click is off, and the manifest URL is signed and short
  lived. State plainly in the UI that none of this stops a screen recording.
- SQLite holds invites and the access log, R2 keys and the SMTP credentials come from
  .env. No accounts for viewers, no telemetry, no third party analytics.
- Out of scope: DRM, forensic watermarking, and TV apps. Do not claim to implement
  any of them and do not build a fake watermark that only sounds forensic.
- README: R2 and signed URL setup, per-viewer encode cost and time, and one blunt
  paragraph saying this is deterrence only and must never be used for a title under
  someone else's security requirements.

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