Vibecode StocksBrew

You are building a lean indie version of StocksBrew.

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

## Goal

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

## Scope

Fetch end-of-day prices, SEC filings, and selected RSS news for a watchlist, score each stock with transparent rules, and notify the owner when a price or earnings condition changes.

## 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:
- maintained stock coverage and editorial calls
- intraday data quality and provider reliability
- managed earnings and price alert delivery
- the product's target-price methodology
- AI-agent API access

If those capabilities are essential, use OpenBB Platform 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 US-stock research cockpit to replace StocksBrew. Requirements:

- Node 22 + Express + better-sqlite3 + node-cron, server-rendered pages on
  localhost:8090, no frontend framework.
- watchlist.json holds my tickers; npm run refresh and a daily 7am cron pull
  end-of-day prices from Alpha Vantage (key in .env), filings from SEC EDGAR
  (no key needed), and items from a curated RSS list in sources.json.
- Score each stock with transparent rules in one rules.js file (price vs 50/200-day
  average, new 10-K/10-Q/8-K filings, earnings-date proximity) and show an
  add/hold/trim stance with the exact rule hits that produced it.
- Every summary line cites the filing or article URL and its timestamp; nothing
  uncited, nothing invented.
- Alerts: per-ticker price threshold and earnings-date reminder, sent by email over
  SMTP creds in .env.
- Rate-limit and cache all external calls (Alpha Vantage's free tier is 25
  requests/day, plan the refresh around it), dedupe news items, and mark stale
  data visibly.
- Dashboard: one watchlist table with price, stance, last-filing link, and next
  earnings date; one detail page per ticker with score history.
- SQLite tables: tickers, price_snapshots, filings, news_items, scores, alerts.
  One file I can back up by copying it.
- No accounts, no telemetry, everything local except the documented API calls.
- Out of scope: intraday data, brokerage connections, trading, and editorial stock
  calls. Put a clear not-investment-advice notice in the README along with setup,
  API limits, and the cron line.

## Required capabilities

- market-data API key
- SEC EDGAR data
- RSS news sources
- LLM API key
- scheduled job

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

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

## Goal

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

## Scope

Fetch end-of-day prices, SEC filings, and selected RSS news for a watchlist, score each stock with transparent rules, and notify the owner when a price or earnings condition changes.

## 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:
- maintained stock coverage and editorial calls
- intraday data quality and provider reliability
- managed earnings and price alert delivery
- the product's target-price methodology
- AI-agent API access

If those capabilities are essential, use OpenBB Platform 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 US-stock research cockpit to replace StocksBrew. Requirements:

- Node 22 + Express + better-sqlite3 + node-cron, server-rendered pages on
  localhost:8090, no frontend framework.
- watchlist.json holds my tickers; npm run refresh and a daily 7am cron pull
  end-of-day prices from Alpha Vantage (key in .env), filings from SEC EDGAR
  (no key needed), and items from a curated RSS list in sources.json.
- Score each stock with transparent rules in one rules.js file (price vs 50/200-day
  average, new 10-K/10-Q/8-K filings, earnings-date proximity) and show an
  add/hold/trim stance with the exact rule hits that produced it.
- Every summary line cites the filing or article URL and its timestamp; nothing
  uncited, nothing invented.
- Alerts: per-ticker price threshold and earnings-date reminder, sent by email over
  SMTP creds in .env.
- Rate-limit and cache all external calls (Alpha Vantage's free tier is 25
  requests/day, plan the refresh around it), dedupe news items, and mark stale
  data visibly.
- Dashboard: one watchlist table with price, stance, last-filing link, and next
  earnings date; one detail page per ticker with score history.
- SQLite tables: tickers, price_snapshots, filings, news_items, scores, alerts.
  One file I can back up by copying it.
- No accounts, no telemetry, everything local except the documented API calls.
- Out of scope: intraday data, brokerage connections, trading, and editorial stock
  calls. Put a clear not-investment-advice notice in the README along with setup,
  API limits, and the cron line.

## Required capabilities

- market-data API key
- SEC EDGAR data
- RSS news sources
- LLM API key
- scheduled job

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

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

## Problem

A personal stock-research cockpit is very buildable, but StocksBrew's useful current calls depend on continuously maintained market, filings, news, and alert pipelines. A DIY version can make its evidence and rules explicit; it will not inherit the service's coverage, refresh reliability, or editorial judgment.

## Product outcome

Fetch end-of-day prices, SEC filings, and selected RSS news for a watchlist, score each stock with transparent rules, and notify the owner when a price or earnings condition changes.

## Target user

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

## Required capabilities

- market-data API key
- SEC EDGAR data
- RSS news sources
- LLM API key
- scheduled job

## Explicit non-goals for v1

- maintained stock coverage and editorial calls
- intraday data quality and provider reliability
- managed earnings and price alert delivery
- the product's target-price methodology
- AI-agent API access

## 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 US-stock research cockpit to replace StocksBrew. Requirements:

- Node 22 + Express + better-sqlite3 + node-cron, server-rendered pages on
  localhost:8090, no frontend framework.
- watchlist.json holds my tickers; npm run refresh and a daily 7am cron pull
  end-of-day prices from Alpha Vantage (key in .env), filings from SEC EDGAR
  (no key needed), and items from a curated RSS list in sources.json.
- Score each stock with transparent rules in one rules.js file (price vs 50/200-day
  average, new 10-K/10-Q/8-K filings, earnings-date proximity) and show an
  add/hold/trim stance with the exact rule hits that produced it.
- Every summary line cites the filing or article URL and its timestamp; nothing
  uncited, nothing invented.
- Alerts: per-ticker price threshold and earnings-date reminder, sent by email over
  SMTP creds in .env.
- Rate-limit and cache all external calls (Alpha Vantage's free tier is 25
  requests/day, plan the refresh around it), dedupe news items, and mark stale
  data visibly.
- Dashboard: one watchlist table with price, stance, last-filing link, and next
  earnings date; one detail page per ticker with score history.
- SQLite tables: tickers, price_snapshots, filings, news_items, scores, alerts.
  One file I can back up by copying it.
- No accounts, no telemetry, everything local except the documented API calls.
- Out of scope: intraday data, brokerage connections, trading, and editorial stock
  calls. Put a clear not-investment-advice notice in the README along with setup,
  API limits, and the cron line.

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

# StocksBrew indie build

## Goal

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

## Scope

Fetch end-of-day prices, SEC filings, and selected RSS news for a watchlist, score each stock with transparent rules, and notify the owner when a price or earnings condition changes.

## 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:
- maintained stock coverage and editorial calls
- intraday data quality and provider reliability
- managed earnings and price alert delivery
- the product's target-price methodology
- AI-agent API access

If those capabilities are essential, use OpenBB Platform 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 US-stock research cockpit to replace StocksBrew. Requirements:

- Node 22 + Express + better-sqlite3 + node-cron, server-rendered pages on
  localhost:8090, no frontend framework.
- watchlist.json holds my tickers; npm run refresh and a daily 7am cron pull
  end-of-day prices from Alpha Vantage (key in .env), filings from SEC EDGAR
  (no key needed), and items from a curated RSS list in sources.json.
- Score each stock with transparent rules in one rules.js file (price vs 50/200-day
  average, new 10-K/10-Q/8-K filings, earnings-date proximity) and show an
  add/hold/trim stance with the exact rule hits that produced it.
- Every summary line cites the filing or article URL and its timestamp; nothing
  uncited, nothing invented.
- Alerts: per-ticker price threshold and earnings-date reminder, sent by email over
  SMTP creds in .env.
- Rate-limit and cache all external calls (Alpha Vantage's free tier is 25
  requests/day, plan the refresh around it), dedupe news items, and mark stale
  data visibly.
- Dashboard: one watchlist table with price, stance, last-filing link, and next
  earnings date; one detail page per ticker with score history.
- SQLite tables: tickers, price_snapshots, filings, news_items, scores, alerts.
  One file I can back up by copying it.
- No accounts, no telemetry, everything local except the documented API calls.
- Out of scope: intraday data, brokerage connections, trading, and editorial stock
  calls. Put a clear not-investment-advice notice in the README along with setup,
  API limits, and the cron line.

## Required capabilities

- market-data API key
- SEC EDGAR data
- RSS news sources
- LLM API key
- scheduled job

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

# StocksBrew product brief

## Problem

A personal stock-research cockpit is very buildable, but StocksBrew's useful current calls depend on continuously maintained market, filings, news, and alert pipelines. A DIY version can make its evidence and rules explicit; it will not inherit the service's coverage, refresh reliability, or editorial judgment.

## Product outcome

Fetch end-of-day prices, SEC filings, and selected RSS news for a watchlist, score each stock with transparent rules, and notify the owner when a price or earnings condition changes.

## Target user

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

## Required capabilities

- market-data API key
- SEC EDGAR data
- RSS news sources
- LLM API key
- scheduled job

## Explicit non-goals for v1

- maintained stock coverage and editorial calls
- intraday data quality and provider reliability
- managed earnings and price alert delivery
- the product's target-price methodology
- AI-agent API access

## 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 US-stock research cockpit to replace StocksBrew. Requirements:

- Node 22 + Express + better-sqlite3 + node-cron, server-rendered pages on
  localhost:8090, no frontend framework.
- watchlist.json holds my tickers; npm run refresh and a daily 7am cron pull
  end-of-day prices from Alpha Vantage (key in .env), filings from SEC EDGAR
  (no key needed), and items from a curated RSS list in sources.json.
- Score each stock with transparent rules in one rules.js file (price vs 50/200-day
  average, new 10-K/10-Q/8-K filings, earnings-date proximity) and show an
  add/hold/trim stance with the exact rule hits that produced it.
- Every summary line cites the filing or article URL and its timestamp; nothing
  uncited, nothing invented.
- Alerts: per-ticker price threshold and earnings-date reminder, sent by email over
  SMTP creds in .env.
- Rate-limit and cache all external calls (Alpha Vantage's free tier is 25
  requests/day, plan the refresh around it), dedupe news items, and mark stale
  data visibly.
- Dashboard: one watchlist table with price, stance, last-filing link, and next
  earnings date; one detail page per ticker with score history.
- SQLite tables: tickers, price_snapshots, filings, news_items, scores, alerts.
  One file I can back up by copying it.
- No accounts, no telemetry, everything local except the documented API calls.
- Out of scope: intraday data, brokerage connections, trading, and editorial stock
  calls. Put a clear not-investment-advice notice in the README along with setup,
  API limits, and the cron line.

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