Vibecode Zernio

You are building a lean indie version of Zernio.

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

## Goal

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

## Scope

Expose a small REST API that accepts a post with media and a schedule time, queues it, and publishes to networks with open APIs (Bluesky, Mastodon, Telegram, Discord, Reddit) with retries and per-target status.

## 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:
- publishing to approval-gated networks at all (Instagram, TikTok, LinkedIn, Threads, YouTube) without your own reviewed apps
- token lifecycle handling: refresh, revocation detection, reconnect flows across 15 networks
- platform error remediation, retry logic, and rate-limit cooldowns that keep queues alive
- the media pipeline: per-platform validation, compression, transcoding, re-hosting
- the entire messaging stack: phone numbers provisioned per country with KYC handled, WhatsApp Business templates and broadcasts, SMS, RCS, and voice calling
- everything else beyond posting: unified DM/comment/review inbox, contacts, analytics, ads APIs, conversion tracking

If those capabilities are essential, use Postiz 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 social publishing API to replace Zernio. Requirements:

- Node + Fastify + better-sqlite3, single API key from .env, runs on my
  always-on box.
- Adapters ONLY for networks that hand out credentials on signup: Bluesky
  (app password via @atproto/api), Mastodon (access token), Telegram channel
  (bot token), Discord (webhook URL), Reddit (script app). One small adapter
  file per network so a sixth is addable later; scaffold nothing I don't use.
- POST /posts accepts text, image URLs, scheduledFor (ISO, my timezone), and
  a list of target accounts; media is downloaded once to media/ and checked
  for type and size before the post is accepted.
- A node-cron tick every minute publishes due posts: mark a row as sending
  before publishing so nothing ever double-posts, per-target status, 3
  retries with backoff, partial failures don't block other targets.
- GET /posts and GET /posts/:id return queue state and per-network
  permalinks; a plain localhost page lists the queue and recent failures.
- Optional webhook: POST to a URL from .env on published and failed.
- Binds to localhost only. No accounts, no telemetry.
- Out of scope: the approval-gated networks (Instagram, TikTok, LinkedIn,
  Threads, YouTube, Pinterest), DMs, comments, analytics, and ads. Skip
  anything that needs a phone number (WhatsApp, SMS, calls): numbers,
  carrier access, and KYC cannot be vibecoded.
- README: how to get each credential (Bluesky app password, Mastodon token,
  Telegram bot via BotFather, Reddit script app), plus an honest note that
  the closed networks need app review or paid API tiers.

## Required capabilities

- reviewed developer app per closed platform (Meta App Review, TikTok audit, LinkedIn partner program, Pinterest; X API paid tier)
- OAuth flows plus token storage, refresh, and revocation handling
- hosted scheduler, database, and job queue
- media storage with per-platform validation and transcoding
- webhook receivers for platform callbacks
- for messaging: WhatsApp Business API access, phone numbers with per-country KYC, and SMS/voice carrier contracts (or reselling Twilio, the kind of subscription you were replacing)

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

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

## Goal

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

## Scope

Expose a small REST API that accepts a post with media and a schedule time, queues it, and publishes to networks with open APIs (Bluesky, Mastodon, Telegram, Discord, Reddit) with retries and per-target status.

## 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:
- publishing to approval-gated networks at all (Instagram, TikTok, LinkedIn, Threads, YouTube) without your own reviewed apps
- token lifecycle handling: refresh, revocation detection, reconnect flows across 15 networks
- platform error remediation, retry logic, and rate-limit cooldowns that keep queues alive
- the media pipeline: per-platform validation, compression, transcoding, re-hosting
- the entire messaging stack: phone numbers provisioned per country with KYC handled, WhatsApp Business templates and broadcasts, SMS, RCS, and voice calling
- everything else beyond posting: unified DM/comment/review inbox, contacts, analytics, ads APIs, conversion tracking

If those capabilities are essential, use Postiz 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 social publishing API to replace Zernio. Requirements:

- Node + Fastify + better-sqlite3, single API key from .env, runs on my
  always-on box.
- Adapters ONLY for networks that hand out credentials on signup: Bluesky
  (app password via @atproto/api), Mastodon (access token), Telegram channel
  (bot token), Discord (webhook URL), Reddit (script app). One small adapter
  file per network so a sixth is addable later; scaffold nothing I don't use.
- POST /posts accepts text, image URLs, scheduledFor (ISO, my timezone), and
  a list of target accounts; media is downloaded once to media/ and checked
  for type and size before the post is accepted.
- A node-cron tick every minute publishes due posts: mark a row as sending
  before publishing so nothing ever double-posts, per-target status, 3
  retries with backoff, partial failures don't block other targets.
- GET /posts and GET /posts/:id return queue state and per-network
  permalinks; a plain localhost page lists the queue and recent failures.
- Optional webhook: POST to a URL from .env on published and failed.
- Binds to localhost only. No accounts, no telemetry.
- Out of scope: the approval-gated networks (Instagram, TikTok, LinkedIn,
  Threads, YouTube, Pinterest), DMs, comments, analytics, and ads. Skip
  anything that needs a phone number (WhatsApp, SMS, calls): numbers,
  carrier access, and KYC cannot be vibecoded.
- README: how to get each credential (Bluesky app password, Mastodon token,
  Telegram bot via BotFather, Reddit script app), plus an honest note that
  the closed networks need app review or paid API tiers.

## Required capabilities

- reviewed developer app per closed platform (Meta App Review, TikTok audit, LinkedIn partner program, Pinterest; X API paid tier)
- OAuth flows plus token storage, refresh, and revocation handling
- hosted scheduler, database, and job queue
- media storage with per-platform validation and transcoding
- webhook receivers for platform callbacks
- for messaging: WhatsApp Business API access, phone numbers with per-country KYC, and SMS/voice carrier contracts (or reselling Twilio, the kind of subscription you were replacing)

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

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

## Problem

The scheduler is the easy 10 percent and an agent can build it in a sitting. The other 90 percent is approval-gated: Instagram, TikTok, LinkedIn, Threads, YouTube, and Pinterest publishing all require a reviewed developer app (Meta App Review, TikTok audit, LinkedIn partner access), and X's API starts at $200/mo. Past the gate, the real product is upkeep: OAuth token refresh and revocation handling across 15 networks, per-platform media validation and transcoding, rate-limit cooldowns, and error remediation when platforms change behavior. Then there is the half that is not software at all: Zernio provisions real phone numbers across dozens of countries and runs WhatsApp Business, SMS, RCS, and voice calling on them, which means carrier relationships, per-country regulatory documents, and Meta business verification. No coding agent can conjure a phone number or pass KYC for you. Add the rest of the surface (unified DM/comment inbox, analytics, ads management across six ad platforms) and this is infra plus compliance, not a weekend of code.

## Product outcome

Expose a small REST API that accepts a post with media and a schedule time, queues it, and publishes to networks with open APIs (Bluesky, Mastodon, Telegram, Discord, Reddit) with retries and per-target status.

## Target user

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

## Required capabilities

- reviewed developer app per closed platform (Meta App Review, TikTok audit, LinkedIn partner program, Pinterest; X API paid tier)
- OAuth flows plus token storage, refresh, and revocation handling
- hosted scheduler, database, and job queue
- media storage with per-platform validation and transcoding
- webhook receivers for platform callbacks
- for messaging: WhatsApp Business API access, phone numbers with per-country KYC, and SMS/voice carrier contracts (or reselling Twilio, the kind of subscription you were replacing)

## Explicit non-goals for v1

- publishing to approval-gated networks at all (Instagram, TikTok, LinkedIn, Threads, YouTube) without your own reviewed apps
- token lifecycle handling: refresh, revocation detection, reconnect flows across 15 networks
- platform error remediation, retry logic, and rate-limit cooldowns that keep queues alive
- the media pipeline: per-platform validation, compression, transcoding, re-hosting
- the entire messaging stack: phone numbers provisioned per country with KYC handled, WhatsApp Business templates and broadcasts, SMS, RCS, and voice calling
- everything else beyond posting: unified DM/comment/review inbox, contacts, analytics, ads APIs, conversion tracking

## 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 social publishing API to replace Zernio. Requirements:

- Node + Fastify + better-sqlite3, single API key from .env, runs on my
  always-on box.
- Adapters ONLY for networks that hand out credentials on signup: Bluesky
  (app password via @atproto/api), Mastodon (access token), Telegram channel
  (bot token), Discord (webhook URL), Reddit (script app). One small adapter
  file per network so a sixth is addable later; scaffold nothing I don't use.
- POST /posts accepts text, image URLs, scheduledFor (ISO, my timezone), and
  a list of target accounts; media is downloaded once to media/ and checked
  for type and size before the post is accepted.
- A node-cron tick every minute publishes due posts: mark a row as sending
  before publishing so nothing ever double-posts, per-target status, 3
  retries with backoff, partial failures don't block other targets.
- GET /posts and GET /posts/:id return queue state and per-network
  permalinks; a plain localhost page lists the queue and recent failures.
- Optional webhook: POST to a URL from .env on published and failed.
- Binds to localhost only. No accounts, no telemetry.
- Out of scope: the approval-gated networks (Instagram, TikTok, LinkedIn,
  Threads, YouTube, Pinterest), DMs, comments, analytics, and ads. Skip
  anything that needs a phone number (WhatsApp, SMS, calls): numbers,
  carrier access, and KYC cannot be vibecoded.
- README: how to get each credential (Bluesky app password, Mastodon token,
  Telegram bot via BotFather, Reddit script app), plus an honest note that
  the closed networks need app review or paid API tiers.

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

# Zernio indie build

## Goal

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

## Scope

Expose a small REST API that accepts a post with media and a schedule time, queues it, and publishes to networks with open APIs (Bluesky, Mastodon, Telegram, Discord, Reddit) with retries and per-target status.

## 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:
- publishing to approval-gated networks at all (Instagram, TikTok, LinkedIn, Threads, YouTube) without your own reviewed apps
- token lifecycle handling: refresh, revocation detection, reconnect flows across 15 networks
- platform error remediation, retry logic, and rate-limit cooldowns that keep queues alive
- the media pipeline: per-platform validation, compression, transcoding, re-hosting
- the entire messaging stack: phone numbers provisioned per country with KYC handled, WhatsApp Business templates and broadcasts, SMS, RCS, and voice calling
- everything else beyond posting: unified DM/comment/review inbox, contacts, analytics, ads APIs, conversion tracking

If those capabilities are essential, use Postiz 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 social publishing API to replace Zernio. Requirements:

- Node + Fastify + better-sqlite3, single API key from .env, runs on my
  always-on box.
- Adapters ONLY for networks that hand out credentials on signup: Bluesky
  (app password via @atproto/api), Mastodon (access token), Telegram channel
  (bot token), Discord (webhook URL), Reddit (script app). One small adapter
  file per network so a sixth is addable later; scaffold nothing I don't use.
- POST /posts accepts text, image URLs, scheduledFor (ISO, my timezone), and
  a list of target accounts; media is downloaded once to media/ and checked
  for type and size before the post is accepted.
- A node-cron tick every minute publishes due posts: mark a row as sending
  before publishing so nothing ever double-posts, per-target status, 3
  retries with backoff, partial failures don't block other targets.
- GET /posts and GET /posts/:id return queue state and per-network
  permalinks; a plain localhost page lists the queue and recent failures.
- Optional webhook: POST to a URL from .env on published and failed.
- Binds to localhost only. No accounts, no telemetry.
- Out of scope: the approval-gated networks (Instagram, TikTok, LinkedIn,
  Threads, YouTube, Pinterest), DMs, comments, analytics, and ads. Skip
  anything that needs a phone number (WhatsApp, SMS, calls): numbers,
  carrier access, and KYC cannot be vibecoded.
- README: how to get each credential (Bluesky app password, Mastodon token,
  Telegram bot via BotFather, Reddit script app), plus an honest note that
  the closed networks need app review or paid API tiers.

## Required capabilities

- reviewed developer app per closed platform (Meta App Review, TikTok audit, LinkedIn partner program, Pinterest; X API paid tier)
- OAuth flows plus token storage, refresh, and revocation handling
- hosted scheduler, database, and job queue
- media storage with per-platform validation and transcoding
- webhook receivers for platform callbacks
- for messaging: WhatsApp Business API access, phone numbers with per-country KYC, and SMS/voice carrier contracts (or reselling Twilio, the kind of subscription you were replacing)

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

# Zernio product brief

## Problem

The scheduler is the easy 10 percent and an agent can build it in a sitting. The other 90 percent is approval-gated: Instagram, TikTok, LinkedIn, Threads, YouTube, and Pinterest publishing all require a reviewed developer app (Meta App Review, TikTok audit, LinkedIn partner access), and X's API starts at $200/mo. Past the gate, the real product is upkeep: OAuth token refresh and revocation handling across 15 networks, per-platform media validation and transcoding, rate-limit cooldowns, and error remediation when platforms change behavior. Then there is the half that is not software at all: Zernio provisions real phone numbers across dozens of countries and runs WhatsApp Business, SMS, RCS, and voice calling on them, which means carrier relationships, per-country regulatory documents, and Meta business verification. No coding agent can conjure a phone number or pass KYC for you. Add the rest of the surface (unified DM/comment inbox, analytics, ads management across six ad platforms) and this is infra plus compliance, not a weekend of code.

## Product outcome

Expose a small REST API that accepts a post with media and a schedule time, queues it, and publishes to networks with open APIs (Bluesky, Mastodon, Telegram, Discord, Reddit) with retries and per-target status.

## Target user

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

## Required capabilities

- reviewed developer app per closed platform (Meta App Review, TikTok audit, LinkedIn partner program, Pinterest; X API paid tier)
- OAuth flows plus token storage, refresh, and revocation handling
- hosted scheduler, database, and job queue
- media storage with per-platform validation and transcoding
- webhook receivers for platform callbacks
- for messaging: WhatsApp Business API access, phone numbers with per-country KYC, and SMS/voice carrier contracts (or reselling Twilio, the kind of subscription you were replacing)

## Explicit non-goals for v1

- publishing to approval-gated networks at all (Instagram, TikTok, LinkedIn, Threads, YouTube) without your own reviewed apps
- token lifecycle handling: refresh, revocation detection, reconnect flows across 15 networks
- platform error remediation, retry logic, and rate-limit cooldowns that keep queues alive
- the media pipeline: per-platform validation, compression, transcoding, re-hosting
- the entire messaging stack: phone numbers provisioned per country with KYC handled, WhatsApp Business templates and broadcasts, SMS, RCS, and voice calling
- everything else beyond posting: unified DM/comment/review inbox, contacts, analytics, ads APIs, conversion tracking

## 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 social publishing API to replace Zernio. Requirements:

- Node + Fastify + better-sqlite3, single API key from .env, runs on my
  always-on box.
- Adapters ONLY for networks that hand out credentials on signup: Bluesky
  (app password via @atproto/api), Mastodon (access token), Telegram channel
  (bot token), Discord (webhook URL), Reddit (script app). One small adapter
  file per network so a sixth is addable later; scaffold nothing I don't use.
- POST /posts accepts text, image URLs, scheduledFor (ISO, my timezone), and
  a list of target accounts; media is downloaded once to media/ and checked
  for type and size before the post is accepted.
- A node-cron tick every minute publishes due posts: mark a row as sending
  before publishing so nothing ever double-posts, per-target status, 3
  retries with backoff, partial failures don't block other targets.
- GET /posts and GET /posts/:id return queue state and per-network
  permalinks; a plain localhost page lists the queue and recent failures.
- Optional webhook: POST to a URL from .env on published and failed.
- Binds to localhost only. No accounts, no telemetry.
- Out of scope: the approval-gated networks (Instagram, TikTok, LinkedIn,
  Threads, YouTube, Pinterest), DMs, comments, analytics, and ads. Skip
  anything that needs a phone number (WhatsApp, SMS, calls): numbers,
  carrier access, and KYC cannot be vibecoded.
- README: how to get each credential (Bluesky app password, Mastodon token,
  Telegram bot via BotFather, Reddit script app), plus an honest note that
  the closed networks need app review or paid API tiers.

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