Vibecode Vernigo

You are building a lean indie version of Vernigo.

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

## Goal

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

## Scope

Track a curated list of YouTube channels, compare each video's views with that channel's recent average, and browse the resulting outliers with filters and bookmark folders.

## 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:
- the 10M-video historical and continuously updating database
- broad discovery beyond channels you already know
- unsaturated niche rankings across the wider YouTube market
- community interaction signals from more than 2,000 users
- ranking quality improved by accumulated usage data
- coverage and freshness without managing YouTube API quotas

If those capabilities are essential, use Vernigo 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 personal YouTube outlier research tool inspired by Vernigo. Requirements:

- Django + PostgreSQL, one self-hosted web app; Google login is out of scope,
  use a single admin password from .env.
- Let me add YouTube channel IDs manually or import them from a CSV seed list.
- Pull each channel's recent videos through the official YouTube Data API and
  store title, thumbnail, views, duration, publish date, and channel stats.
- Calculate an outlier multiplier as video views divided by the average views
  of that channel's previous five videos available in the database.
- A searchable video grid with filters for multiplier, views, subscribers,
  duration, publish date, category, and channel age; sortable by multiplier,
  views, or newest.
- Bookmark folders: create, rename, and delete folders, and save or remove
  videos without duplicating them.
- A niche page that groups imported channels by a manually assigned niche and
  ranks niches using median views per video divided by videos published.
- Run refresh jobs with Celery + Redis once per day, respect API quota errors,
  and show the last successful refresh time for every channel.
- Store all secrets in .env; include Docker Compose for Django, PostgreSQL,
  Redis, Celery worker, and scheduler.
- Out of scope: crawling all of YouTube, a 10M-video corpus, community ranking
  signals, automatic niche classification, and claims that this finds the
  best opportunities market-wide. It only analyzes the channels I seed.
- README: YouTube API setup, quota limits, CSV format, calculation details,
  backup steps, and the limits of a small personal dataset.

## Required capabilities

- YouTube Data API key
- curated channel seed list
- scheduled data collection
- database
- always-on box for refresh jobs

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

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

## Goal

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

## Scope

Track a curated list of YouTube channels, compare each video's views with that channel's recent average, and browse the resulting outliers with filters and bookmark folders.

## 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:
- the 10M-video historical and continuously updating database
- broad discovery beyond channels you already know
- unsaturated niche rankings across the wider YouTube market
- community interaction signals from more than 2,000 users
- ranking quality improved by accumulated usage data
- coverage and freshness without managing YouTube API quotas

If those capabilities are essential, use Vernigo 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 personal YouTube outlier research tool inspired by Vernigo. Requirements:

- Django + PostgreSQL, one self-hosted web app; Google login is out of scope,
  use a single admin password from .env.
- Let me add YouTube channel IDs manually or import them from a CSV seed list.
- Pull each channel's recent videos through the official YouTube Data API and
  store title, thumbnail, views, duration, publish date, and channel stats.
- Calculate an outlier multiplier as video views divided by the average views
  of that channel's previous five videos available in the database.
- A searchable video grid with filters for multiplier, views, subscribers,
  duration, publish date, category, and channel age; sortable by multiplier,
  views, or newest.
- Bookmark folders: create, rename, and delete folders, and save or remove
  videos without duplicating them.
- A niche page that groups imported channels by a manually assigned niche and
  ranks niches using median views per video divided by videos published.
- Run refresh jobs with Celery + Redis once per day, respect API quota errors,
  and show the last successful refresh time for every channel.
- Store all secrets in .env; include Docker Compose for Django, PostgreSQL,
  Redis, Celery worker, and scheduler.
- Out of scope: crawling all of YouTube, a 10M-video corpus, community ranking
  signals, automatic niche classification, and claims that this finds the
  best opportunities market-wide. It only analyzes the channels I seed.
- README: YouTube API setup, quota limits, CSV format, calculation details,
  backup steps, and the limits of a small personal dataset.

## Required capabilities

- YouTube Data API key
- curated channel seed list
- scheduled data collection
- database
- always-on box for refresh jobs

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

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

## Problem

You can build filters, bookmarks, and an outlier score over a small set of YouTube channels, but Vernigo's product is the continuously refreshed corpus: millions of videos, channel baselines, niche-level supply and demand signals, and ranking data improved by how thousands of users interact with the library. A one-shot app can reproduce the interface and formula, not the dataset that makes the results useful.

## Product outcome

Track a curated list of YouTube channels, compare each video's views with that channel's recent average, and browse the resulting outliers with filters and bookmark folders.

## Target user

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

## Required capabilities

- YouTube Data API key
- curated channel seed list
- scheduled data collection
- database
- always-on box for refresh jobs

## Explicit non-goals for v1

- the 10M-video historical and continuously updating database
- broad discovery beyond channels you already know
- unsaturated niche rankings across the wider YouTube market
- community interaction signals from more than 2,000 users
- ranking quality improved by accumulated usage data
- coverage and freshness without managing YouTube API quotas

## 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 personal YouTube outlier research tool inspired by Vernigo. Requirements:

- Django + PostgreSQL, one self-hosted web app; Google login is out of scope,
  use a single admin password from .env.
- Let me add YouTube channel IDs manually or import them from a CSV seed list.
- Pull each channel's recent videos through the official YouTube Data API and
  store title, thumbnail, views, duration, publish date, and channel stats.
- Calculate an outlier multiplier as video views divided by the average views
  of that channel's previous five videos available in the database.
- A searchable video grid with filters for multiplier, views, subscribers,
  duration, publish date, category, and channel age; sortable by multiplier,
  views, or newest.
- Bookmark folders: create, rename, and delete folders, and save or remove
  videos without duplicating them.
- A niche page that groups imported channels by a manually assigned niche and
  ranks niches using median views per video divided by videos published.
- Run refresh jobs with Celery + Redis once per day, respect API quota errors,
  and show the last successful refresh time for every channel.
- Store all secrets in .env; include Docker Compose for Django, PostgreSQL,
  Redis, Celery worker, and scheduler.
- Out of scope: crawling all of YouTube, a 10M-video corpus, community ranking
  signals, automatic niche classification, and claims that this finds the
  best opportunities market-wide. It only analyzes the channels I seed.
- README: YouTube API setup, quota limits, CSV format, calculation details,
  backup steps, and the limits of a small personal dataset.

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

# Vernigo indie build

## Goal

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

## Scope

Track a curated list of YouTube channels, compare each video's views with that channel's recent average, and browse the resulting outliers with filters and bookmark folders.

## 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:
- the 10M-video historical and continuously updating database
- broad discovery beyond channels you already know
- unsaturated niche rankings across the wider YouTube market
- community interaction signals from more than 2,000 users
- ranking quality improved by accumulated usage data
- coverage and freshness without managing YouTube API quotas

If those capabilities are essential, use Vernigo 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 personal YouTube outlier research tool inspired by Vernigo. Requirements:

- Django + PostgreSQL, one self-hosted web app; Google login is out of scope,
  use a single admin password from .env.
- Let me add YouTube channel IDs manually or import them from a CSV seed list.
- Pull each channel's recent videos through the official YouTube Data API and
  store title, thumbnail, views, duration, publish date, and channel stats.
- Calculate an outlier multiplier as video views divided by the average views
  of that channel's previous five videos available in the database.
- A searchable video grid with filters for multiplier, views, subscribers,
  duration, publish date, category, and channel age; sortable by multiplier,
  views, or newest.
- Bookmark folders: create, rename, and delete folders, and save or remove
  videos without duplicating them.
- A niche page that groups imported channels by a manually assigned niche and
  ranks niches using median views per video divided by videos published.
- Run refresh jobs with Celery + Redis once per day, respect API quota errors,
  and show the last successful refresh time for every channel.
- Store all secrets in .env; include Docker Compose for Django, PostgreSQL,
  Redis, Celery worker, and scheduler.
- Out of scope: crawling all of YouTube, a 10M-video corpus, community ranking
  signals, automatic niche classification, and claims that this finds the
  best opportunities market-wide. It only analyzes the channels I seed.
- README: YouTube API setup, quota limits, CSV format, calculation details,
  backup steps, and the limits of a small personal dataset.

## Required capabilities

- YouTube Data API key
- curated channel seed list
- scheduled data collection
- database
- always-on box for refresh jobs

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

# Vernigo product brief

## Problem

You can build filters, bookmarks, and an outlier score over a small set of YouTube channels, but Vernigo's product is the continuously refreshed corpus: millions of videos, channel baselines, niche-level supply and demand signals, and ranking data improved by how thousands of users interact with the library. A one-shot app can reproduce the interface and formula, not the dataset that makes the results useful.

## Product outcome

Track a curated list of YouTube channels, compare each video's views with that channel's recent average, and browse the resulting outliers with filters and bookmark folders.

## Target user

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

## Required capabilities

- YouTube Data API key
- curated channel seed list
- scheduled data collection
- database
- always-on box for refresh jobs

## Explicit non-goals for v1

- the 10M-video historical and continuously updating database
- broad discovery beyond channels you already know
- unsaturated niche rankings across the wider YouTube market
- community interaction signals from more than 2,000 users
- ranking quality improved by accumulated usage data
- coverage and freshness without managing YouTube API quotas

## 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 personal YouTube outlier research tool inspired by Vernigo. Requirements:

- Django + PostgreSQL, one self-hosted web app; Google login is out of scope,
  use a single admin password from .env.
- Let me add YouTube channel IDs manually or import them from a CSV seed list.
- Pull each channel's recent videos through the official YouTube Data API and
  store title, thumbnail, views, duration, publish date, and channel stats.
- Calculate an outlier multiplier as video views divided by the average views
  of that channel's previous five videos available in the database.
- A searchable video grid with filters for multiplier, views, subscribers,
  duration, publish date, category, and channel age; sortable by multiplier,
  views, or newest.
- Bookmark folders: create, rename, and delete folders, and save or remove
  videos without duplicating them.
- A niche page that groups imported channels by a manually assigned niche and
  ranks niches using median views per video divided by videos published.
- Run refresh jobs with Celery + Redis once per day, respect API quota errors,
  and show the last successful refresh time for every channel.
- Store all secrets in .env; include Docker Compose for Django, PostgreSQL,
  Redis, Celery worker, and scheduler.
- Out of scope: crawling all of YouTube, a 10M-video corpus, community ranking
  signals, automatic niche classification, and claims that this finds the
  best opportunities market-wide. It only analyzes the channels I seed.
- README: YouTube API setup, quota limits, CSV format, calculation details,
  backup steps, and the limits of a small personal dataset.

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