Vibecode Iconik

You are building a lean indie version of Iconik.

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

## Goal

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

## Scope

For one person on their own drives: walk the volumes, make ffmpeg proxies, extract metadata, and search it locally. A catalog, not a MAM.

## 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:
- storage gateways that index on-prem NAS, LTO, and cloud buckets as one library
- per-user and per-collection permissions with an audit trail
- proxy transcoding that keeps up with petabyte ingest
- Adobe and Resolve panels plus the desktop player
- shared collections and review for clients who never see your storage
- archive and restore lifecycle out to deep cloud storage

If those capabilities are essential, use ResourceSpace 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 single-user local media catalog for my own drives, the honest
personal floor of iconik. It is for exactly one person; facility-scale asset
management is what iconik is for. Requirements:

- A Node CLI plus a local web app: better-sqlite3 for the index, Express serving on
  localhost, plain server-rendered pages.
- `scan <volume>` walks the drive, records path, size, mtime, and volume label, then
  runs ffprobe for duration, codec, resolution, frame rate, and embedded timecode.
  Re-running it is incremental, keyed on path plus mtime plus size.
- Every video gets a 480p H.264 proxy and a contact sheet of 9 frames written to
  ~/MediaCatalog/proxies/<hash>/, so I can identify a clip without mounting the drive
  it lives on.
- Search across filename, path, codec, and my own notes with SQLite FTS5, plus filters
  for duration, resolution, and volume. Results play the proxy inline.
- Offline drives stay in the index and are marked offline when the volume is not
  mounted, with the volume label shown so I know which shelf to go to.
- Free-text notes and tags per clip, and a starred collection I can export as a JSON
  or CSV shot list.
- Everything is local: no accounts, no cloud, no telemetry. The SQLite file plus the
  proxies folder is the entire product and both are backupable.
- Out of scope: multi-user access, permissions, cloud storage gateways, and AI tagging.
  Do not build a login system. If a second person needs this, buy iconik.
- README: installing ffmpeg, expected first-scan time for a 20TB volume, and a warning
  to run the proxy pass overnight.

## Required capabilities

- ffmpeg
- a machine that can see every volume you want indexed
- SQLite plus FTS5
- storage for proxies
- a lot of patience for the first index

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

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

## Goal

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

## Scope

For one person on their own drives: walk the volumes, make ffmpeg proxies, extract metadata, and search it locally. A catalog, not a MAM.

## 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:
- storage gateways that index on-prem NAS, LTO, and cloud buckets as one library
- per-user and per-collection permissions with an audit trail
- proxy transcoding that keeps up with petabyte ingest
- Adobe and Resolve panels plus the desktop player
- shared collections and review for clients who never see your storage
- archive and restore lifecycle out to deep cloud storage

If those capabilities are essential, use ResourceSpace 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 single-user local media catalog for my own drives, the honest
personal floor of iconik. It is for exactly one person; facility-scale asset
management is what iconik is for. Requirements:

- A Node CLI plus a local web app: better-sqlite3 for the index, Express serving on
  localhost, plain server-rendered pages.
- `scan <volume>` walks the drive, records path, size, mtime, and volume label, then
  runs ffprobe for duration, codec, resolution, frame rate, and embedded timecode.
  Re-running it is incremental, keyed on path plus mtime plus size.
- Every video gets a 480p H.264 proxy and a contact sheet of 9 frames written to
  ~/MediaCatalog/proxies/<hash>/, so I can identify a clip without mounting the drive
  it lives on.
- Search across filename, path, codec, and my own notes with SQLite FTS5, plus filters
  for duration, resolution, and volume. Results play the proxy inline.
- Offline drives stay in the index and are marked offline when the volume is not
  mounted, with the volume label shown so I know which shelf to go to.
- Free-text notes and tags per clip, and a starred collection I can export as a JSON
  or CSV shot list.
- Everything is local: no accounts, no cloud, no telemetry. The SQLite file plus the
  proxies folder is the entire product and both are backupable.
- Out of scope: multi-user access, permissions, cloud storage gateways, and AI tagging.
  Do not build a login system. If a second person needs this, buy iconik.
- README: installing ffmpeg, expected first-scan time for a 20TB volume, and a warning
  to run the proxy pass overnight.

## Required capabilities

- ffmpeg
- a machine that can see every volume you want indexed
- SQLite plus FTS5
- storage for proxies
- a lot of patience for the first index

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

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

## Problem

Iconik is not a search box, it is a storage gateway network. Its job is to make an on-prem NAS in one building, an LTO library in another, and three cloud buckets behave like one library, generate proxies for all of it, and then let a producer in another timezone browse the parts they are allowed to see without ever touching the original storage. Every hard part of that is infrastructure and permissions, and none of it gets easier because an agent writes the code. A solo editor can absolutely build a personal catalog of their own drives, and that is worth doing. It is not a MAM, and the moment a second person or a second site is involved you are staffing a product, not running a script.

## Product outcome

For one person on their own drives: walk the volumes, make ffmpeg proxies, extract metadata, and search it locally. A catalog, not a MAM.

## Target user

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

## Required capabilities

- ffmpeg
- a machine that can see every volume you want indexed
- SQLite plus FTS5
- storage for proxies
- a lot of patience for the first index

## Explicit non-goals for v1

- storage gateways that index on-prem NAS, LTO, and cloud buckets as one library
- per-user and per-collection permissions with an audit trail
- proxy transcoding that keeps up with petabyte ingest
- Adobe and Resolve panels plus the desktop player
- shared collections and review for clients who never see your storage
- archive and restore lifecycle out to deep cloud storage

## 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 single-user local media catalog for my own drives, the honest
personal floor of iconik. It is for exactly one person; facility-scale asset
management is what iconik is for. Requirements:

- A Node CLI plus a local web app: better-sqlite3 for the index, Express serving on
  localhost, plain server-rendered pages.
- `scan <volume>` walks the drive, records path, size, mtime, and volume label, then
  runs ffprobe for duration, codec, resolution, frame rate, and embedded timecode.
  Re-running it is incremental, keyed on path plus mtime plus size.
- Every video gets a 480p H.264 proxy and a contact sheet of 9 frames written to
  ~/MediaCatalog/proxies/<hash>/, so I can identify a clip without mounting the drive
  it lives on.
- Search across filename, path, codec, and my own notes with SQLite FTS5, plus filters
  for duration, resolution, and volume. Results play the proxy inline.
- Offline drives stay in the index and are marked offline when the volume is not
  mounted, with the volume label shown so I know which shelf to go to.
- Free-text notes and tags per clip, and a starred collection I can export as a JSON
  or CSV shot list.
- Everything is local: no accounts, no cloud, no telemetry. The SQLite file plus the
  proxies folder is the entire product and both are backupable.
- Out of scope: multi-user access, permissions, cloud storage gateways, and AI tagging.
  Do not build a login system. If a second person needs this, buy iconik.
- README: installing ffmpeg, expected first-scan time for a 20TB volume, and a warning
  to run the proxy pass overnight.

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

# Iconik indie build

## Goal

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

## Scope

For one person on their own drives: walk the volumes, make ffmpeg proxies, extract metadata, and search it locally. A catalog, not a MAM.

## 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:
- storage gateways that index on-prem NAS, LTO, and cloud buckets as one library
- per-user and per-collection permissions with an audit trail
- proxy transcoding that keeps up with petabyte ingest
- Adobe and Resolve panels plus the desktop player
- shared collections and review for clients who never see your storage
- archive and restore lifecycle out to deep cloud storage

If those capabilities are essential, use ResourceSpace 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 single-user local media catalog for my own drives, the honest
personal floor of iconik. It is for exactly one person; facility-scale asset
management is what iconik is for. Requirements:

- A Node CLI plus a local web app: better-sqlite3 for the index, Express serving on
  localhost, plain server-rendered pages.
- `scan <volume>` walks the drive, records path, size, mtime, and volume label, then
  runs ffprobe for duration, codec, resolution, frame rate, and embedded timecode.
  Re-running it is incremental, keyed on path plus mtime plus size.
- Every video gets a 480p H.264 proxy and a contact sheet of 9 frames written to
  ~/MediaCatalog/proxies/<hash>/, so I can identify a clip without mounting the drive
  it lives on.
- Search across filename, path, codec, and my own notes with SQLite FTS5, plus filters
  for duration, resolution, and volume. Results play the proxy inline.
- Offline drives stay in the index and are marked offline when the volume is not
  mounted, with the volume label shown so I know which shelf to go to.
- Free-text notes and tags per clip, and a starred collection I can export as a JSON
  or CSV shot list.
- Everything is local: no accounts, no cloud, no telemetry. The SQLite file plus the
  proxies folder is the entire product and both are backupable.
- Out of scope: multi-user access, permissions, cloud storage gateways, and AI tagging.
  Do not build a login system. If a second person needs this, buy iconik.
- README: installing ffmpeg, expected first-scan time for a 20TB volume, and a warning
  to run the proxy pass overnight.

## Required capabilities

- ffmpeg
- a machine that can see every volume you want indexed
- SQLite plus FTS5
- storage for proxies
- a lot of patience for the first index

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

# Iconik product brief

## Problem

Iconik is not a search box, it is a storage gateway network. Its job is to make an on-prem NAS in one building, an LTO library in another, and three cloud buckets behave like one library, generate proxies for all of it, and then let a producer in another timezone browse the parts they are allowed to see without ever touching the original storage. Every hard part of that is infrastructure and permissions, and none of it gets easier because an agent writes the code. A solo editor can absolutely build a personal catalog of their own drives, and that is worth doing. It is not a MAM, and the moment a second person or a second site is involved you are staffing a product, not running a script.

## Product outcome

For one person on their own drives: walk the volumes, make ffmpeg proxies, extract metadata, and search it locally. A catalog, not a MAM.

## Target user

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

## Required capabilities

- ffmpeg
- a machine that can see every volume you want indexed
- SQLite plus FTS5
- storage for proxies
- a lot of patience for the first index

## Explicit non-goals for v1

- storage gateways that index on-prem NAS, LTO, and cloud buckets as one library
- per-user and per-collection permissions with an audit trail
- proxy transcoding that keeps up with petabyte ingest
- Adobe and Resolve panels plus the desktop player
- shared collections and review for clients who never see your storage
- archive and restore lifecycle out to deep cloud storage

## 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 single-user local media catalog for my own drives, the honest
personal floor of iconik. It is for exactly one person; facility-scale asset
management is what iconik is for. Requirements:

- A Node CLI plus a local web app: better-sqlite3 for the index, Express serving on
  localhost, plain server-rendered pages.
- `scan <volume>` walks the drive, records path, size, mtime, and volume label, then
  runs ffprobe for duration, codec, resolution, frame rate, and embedded timecode.
  Re-running it is incremental, keyed on path plus mtime plus size.
- Every video gets a 480p H.264 proxy and a contact sheet of 9 frames written to
  ~/MediaCatalog/proxies/<hash>/, so I can identify a clip without mounting the drive
  it lives on.
- Search across filename, path, codec, and my own notes with SQLite FTS5, plus filters
  for duration, resolution, and volume. Results play the proxy inline.
- Offline drives stay in the index and are marked offline when the volume is not
  mounted, with the volume label shown so I know which shelf to go to.
- Free-text notes and tags per clip, and a starred collection I can export as a JSON
  or CSV shot list.
- Everything is local: no accounts, no cloud, no telemetry. The SQLite file plus the
  proxies folder is the entire product and both are backupable.
- Out of scope: multi-user access, permissions, cloud storage gateways, and AI tagging.
  Do not build a login system. If a second person needs this, buy iconik.
- README: installing ffmpeg, expected first-scan time for a 20TB volume, and a warning
  to run the proxy pass overnight.

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