Vibecode Frame.io

You are building a lean indie version of Frame.io.

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 =====
# Frame.io indie build

## Goal

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

## Scope

Watch a folder, transcode a proxy with ffmpeg, serve it at an unlisted URL where reviewers leave frame-accurate comments, stack versions, and export the notes as timecode.

## 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:
- Camera to Cloud ingest straight off set
- Premiere, After Effects, and Resolve review panels that sync comments to timeline markers
- a transcode farm and global CDN, so client playback is only as good as your box
- forensic watermarking, SSO, and the security posture studios require
- the iPad and mobile review apps clients actually use
- storage, transfer tooling, and uptime bundled into the seat price

If those capabilities are essential, use Kitsu 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 video review and approval app to replace Frame.io for a one-person edit shop. Requirements:

- Node + Express + better-sqlite3 running on my own VPS behind an existing reverse
  proxy. Server-rendered pages, one vanilla JS player, no frontend framework.
- I drop a master into ./incoming/<project>/<asset>.mov; chokidar picks it up and
  ffmpeg writes a 1080p H.264 proxy and a poster frame into
  ./media/<project>/<asset>/v<N>/. Frame rate comes from ffprobe.
- Versions stack: the same asset name dropped again becomes v2, v3, and so on. The
  review page gets a version dropdown that swaps the source at the current playhead.
- Each asset has one unguessable /r/<random-id> link. A reviewer types their name
  once into localStorage, then comments; every comment stores the exact frame and
  renders as HH:MM:SS:FF at the asset's real frame rate.
- Comments list beside the player and tick along the scrubber. Clicking one seeks to
  that frame. Each has a reply thread, a resolved checkbox, and an unresolved filter.
- An export button per version writes notes.csv (timecode, author, comment, resolved)
  and a DaVinci Resolve marker .txt I can import onto the timeline.
- SQLite holds comments and versions, media stays in plain folders, so nothing is
  trapped in the app. No accounts and no telemetry: admin pages sit behind basic auth
  with the password in .env, share links are the only other way in.
- Out of scope: Camera to Cloud, NLE panels, watermarking, and a mobile app. Do not
  build accounts, teams, or roles. The unlisted link is the entire permission model.
- README: installing ffmpeg, raising the proxy upload limit, and an honest warning
  that you now own the storage bill, the egress bill, and the 2am playback outage.

## Required capabilities

- ffmpeg
- a VPS with real disk and bandwidth
- a domain plus reverse proxy with TLS
- chokidar or another folder watcher
- a storage and egress budget you now pay yourself

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

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 =====
# Frame.io indie build

## Goal

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

## Scope

Watch a folder, transcode a proxy with ffmpeg, serve it at an unlisted URL where reviewers leave frame-accurate comments, stack versions, and export the notes as timecode.

## 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:
- Camera to Cloud ingest straight off set
- Premiere, After Effects, and Resolve review panels that sync comments to timeline markers
- a transcode farm and global CDN, so client playback is only as good as your box
- forensic watermarking, SSO, and the security posture studios require
- the iPad and mobile review apps clients actually use
- storage, transfer tooling, and uptime bundled into the seat price

If those capabilities are essential, use Kitsu 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 video review and approval app to replace Frame.io for a one-person edit shop. Requirements:

- Node + Express + better-sqlite3 running on my own VPS behind an existing reverse
  proxy. Server-rendered pages, one vanilla JS player, no frontend framework.
- I drop a master into ./incoming/<project>/<asset>.mov; chokidar picks it up and
  ffmpeg writes a 1080p H.264 proxy and a poster frame into
  ./media/<project>/<asset>/v<N>/. Frame rate comes from ffprobe.
- Versions stack: the same asset name dropped again becomes v2, v3, and so on. The
  review page gets a version dropdown that swaps the source at the current playhead.
- Each asset has one unguessable /r/<random-id> link. A reviewer types their name
  once into localStorage, then comments; every comment stores the exact frame and
  renders as HH:MM:SS:FF at the asset's real frame rate.
- Comments list beside the player and tick along the scrubber. Clicking one seeks to
  that frame. Each has a reply thread, a resolved checkbox, and an unresolved filter.
- An export button per version writes notes.csv (timecode, author, comment, resolved)
  and a DaVinci Resolve marker .txt I can import onto the timeline.
- SQLite holds comments and versions, media stays in plain folders, so nothing is
  trapped in the app. No accounts and no telemetry: admin pages sit behind basic auth
  with the password in .env, share links are the only other way in.
- Out of scope: Camera to Cloud, NLE panels, watermarking, and a mobile app. Do not
  build accounts, teams, or roles. The unlisted link is the entire permission model.
- README: installing ffmpeg, raising the proxy upload limit, and an honest warning
  that you now own the storage bill, the egress bill, and the 2am playback outage.

## Required capabilities

- ffmpeg
- a VPS with real disk and bandwidth
- a domain plus reverse proxy with TLS
- chokidar or another folder watcher
- a storage and egress budget you now pay yourself

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

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 =====
# Frame.io product brief

## Problem

The review loop itself is not the hard part: a player, timecoded comments, version stacking, and an unlisted share link are a weekend of work for one editor and a few clients. What you cannot rebuild is the rest of the product · Camera to Cloud from set, the Premiere and Resolve panels that put comments on your timeline as markers, transcoding and CDN delivery that hold up when a client scrubs a 4K cut from a hotel wifi, and the security paperwork studios ask for. Solo and small-shop review is genuinely vibecodeable. Delivery infrastructure is not.

## Product outcome

Watch a folder, transcode a proxy with ffmpeg, serve it at an unlisted URL where reviewers leave frame-accurate comments, stack versions, and export the notes as timecode.

## Target user

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

## Required capabilities

- ffmpeg
- a VPS with real disk and bandwidth
- a domain plus reverse proxy with TLS
- chokidar or another folder watcher
- a storage and egress budget you now pay yourself

## Explicit non-goals for v1

- Camera to Cloud ingest straight off set
- Premiere, After Effects, and Resolve review panels that sync comments to timeline markers
- a transcode farm and global CDN, so client playback is only as good as your box
- forensic watermarking, SSO, and the security posture studios require
- the iPad and mobile review apps clients actually use
- storage, transfer tooling, and uptime bundled into the seat price

## 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 video review and approval app to replace Frame.io for a one-person edit shop. Requirements:

- Node + Express + better-sqlite3 running on my own VPS behind an existing reverse
  proxy. Server-rendered pages, one vanilla JS player, no frontend framework.
- I drop a master into ./incoming/<project>/<asset>.mov; chokidar picks it up and
  ffmpeg writes a 1080p H.264 proxy and a poster frame into
  ./media/<project>/<asset>/v<N>/. Frame rate comes from ffprobe.
- Versions stack: the same asset name dropped again becomes v2, v3, and so on. The
  review page gets a version dropdown that swaps the source at the current playhead.
- Each asset has one unguessable /r/<random-id> link. A reviewer types their name
  once into localStorage, then comments; every comment stores the exact frame and
  renders as HH:MM:SS:FF at the asset's real frame rate.
- Comments list beside the player and tick along the scrubber. Clicking one seeks to
  that frame. Each has a reply thread, a resolved checkbox, and an unresolved filter.
- An export button per version writes notes.csv (timecode, author, comment, resolved)
  and a DaVinci Resolve marker .txt I can import onto the timeline.
- SQLite holds comments and versions, media stays in plain folders, so nothing is
  trapped in the app. No accounts and no telemetry: admin pages sit behind basic auth
  with the password in .env, share links are the only other way in.
- Out of scope: Camera to Cloud, NLE panels, watermarking, and a mobile app. Do not
  build accounts, teams, or roles. The unlisted link is the entire permission model.
- README: installing ffmpeg, raising the proxy upload limit, and an honest warning
  that you now own the storage bill, the egress bill, and the 2am playback outage.

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

# Frame.io indie build

## Goal

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

## Scope

Watch a folder, transcode a proxy with ffmpeg, serve it at an unlisted URL where reviewers leave frame-accurate comments, stack versions, and export the notes as timecode.

## 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:
- Camera to Cloud ingest straight off set
- Premiere, After Effects, and Resolve review panels that sync comments to timeline markers
- a transcode farm and global CDN, so client playback is only as good as your box
- forensic watermarking, SSO, and the security posture studios require
- the iPad and mobile review apps clients actually use
- storage, transfer tooling, and uptime bundled into the seat price

If those capabilities are essential, use Kitsu 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 video review and approval app to replace Frame.io for a one-person edit shop. Requirements:

- Node + Express + better-sqlite3 running on my own VPS behind an existing reverse
  proxy. Server-rendered pages, one vanilla JS player, no frontend framework.
- I drop a master into ./incoming/<project>/<asset>.mov; chokidar picks it up and
  ffmpeg writes a 1080p H.264 proxy and a poster frame into
  ./media/<project>/<asset>/v<N>/. Frame rate comes from ffprobe.
- Versions stack: the same asset name dropped again becomes v2, v3, and so on. The
  review page gets a version dropdown that swaps the source at the current playhead.
- Each asset has one unguessable /r/<random-id> link. A reviewer types their name
  once into localStorage, then comments; every comment stores the exact frame and
  renders as HH:MM:SS:FF at the asset's real frame rate.
- Comments list beside the player and tick along the scrubber. Clicking one seeks to
  that frame. Each has a reply thread, a resolved checkbox, and an unresolved filter.
- An export button per version writes notes.csv (timecode, author, comment, resolved)
  and a DaVinci Resolve marker .txt I can import onto the timeline.
- SQLite holds comments and versions, media stays in plain folders, so nothing is
  trapped in the app. No accounts and no telemetry: admin pages sit behind basic auth
  with the password in .env, share links are the only other way in.
- Out of scope: Camera to Cloud, NLE panels, watermarking, and a mobile app. Do not
  build accounts, teams, or roles. The unlisted link is the entire permission model.
- README: installing ffmpeg, raising the proxy upload limit, and an honest warning
  that you now own the storage bill, the egress bill, and the 2am playback outage.

## Required capabilities

- ffmpeg
- a VPS with real disk and bandwidth
- a domain plus reverse proxy with TLS
- chokidar or another folder watcher
- a storage and egress budget you now pay yourself

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

# Frame.io product brief

## Problem

The review loop itself is not the hard part: a player, timecoded comments, version stacking, and an unlisted share link are a weekend of work for one editor and a few clients. What you cannot rebuild is the rest of the product · Camera to Cloud from set, the Premiere and Resolve panels that put comments on your timeline as markers, transcoding and CDN delivery that hold up when a client scrubs a 4K cut from a hotel wifi, and the security paperwork studios ask for. Solo and small-shop review is genuinely vibecodeable. Delivery infrastructure is not.

## Product outcome

Watch a folder, transcode a proxy with ffmpeg, serve it at an unlisted URL where reviewers leave frame-accurate comments, stack versions, and export the notes as timecode.

## Target user

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

## Required capabilities

- ffmpeg
- a VPS with real disk and bandwidth
- a domain plus reverse proxy with TLS
- chokidar or another folder watcher
- a storage and egress budget you now pay yourself

## Explicit non-goals for v1

- Camera to Cloud ingest straight off set
- Premiere, After Effects, and Resolve review panels that sync comments to timeline markers
- a transcode farm and global CDN, so client playback is only as good as your box
- forensic watermarking, SSO, and the security posture studios require
- the iPad and mobile review apps clients actually use
- storage, transfer tooling, and uptime bundled into the seat price

## 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 video review and approval app to replace Frame.io for a one-person edit shop. Requirements:

- Node + Express + better-sqlite3 running on my own VPS behind an existing reverse
  proxy. Server-rendered pages, one vanilla JS player, no frontend framework.
- I drop a master into ./incoming/<project>/<asset>.mov; chokidar picks it up and
  ffmpeg writes a 1080p H.264 proxy and a poster frame into
  ./media/<project>/<asset>/v<N>/. Frame rate comes from ffprobe.
- Versions stack: the same asset name dropped again becomes v2, v3, and so on. The
  review page gets a version dropdown that swaps the source at the current playhead.
- Each asset has one unguessable /r/<random-id> link. A reviewer types their name
  once into localStorage, then comments; every comment stores the exact frame and
  renders as HH:MM:SS:FF at the asset's real frame rate.
- Comments list beside the player and tick along the scrubber. Clicking one seeks to
  that frame. Each has a reply thread, a resolved checkbox, and an unresolved filter.
- An export button per version writes notes.csv (timecode, author, comment, resolved)
  and a DaVinci Resolve marker .txt I can import onto the timeline.
- SQLite holds comments and versions, media stays in plain folders, so nothing is
  trapped in the app. No accounts and no telemetry: admin pages sit behind basic auth
  with the password in .env, share links are the only other way in.
- Out of scope: Camera to Cloud, NLE panels, watermarking, and a mobile app. Do not
  build accounts, teams, or roles. The unlisted link is the entire permission model.
- README: installing ffmpeg, raising the proxy upload limit, and an honest warning
  that you now own the storage bill, the egress bill, and the 2am playback outage.

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