Vibecode WasItAIGenerated

You are building a lean indie version of WasItAIGenerated.

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

## Goal

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

## Scope

Build a private workspace that pastes in text, asks one general model for an AI-likelihood judgement with reasoning, stores results, and exports them.

## 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:
- a trained classifier and the labelled corpus behind it
- a measured false-positive rate you can quote to an institution
- detection for images, audio and video, not just text
- per-sentence highlighting instead of one document-level guess
- retraining as generators change

If those capabilities are essential, use Binoculars 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 the closest honest consolation tool inspired by WasItAIGenerated. Do not claim it detects AI writing.
Use exactly this stack: Next.js 15 + TypeScript + SQLite.
Primary job: paste text, send it to one general language model, and record that model's opinion on how machine-like the writing reads, with its reasoning.
Start from an empty folder and create the complete working project.
Single-user and private by default; store everything locally.
Put every secret in .env and provide .env.example.
Show the result as an opinion with reasoning, never as a score, a percentage or a verdict - the whole point of this build is that it cannot measure what the paid product measures.
Put a permanent, non-dismissable notice in the UI and the README: this is one model's guess, it has no measured error rate, and it must never be used to accuse anyone of anything.
Include clear empty, loading, validation, success and failure states.
Add export so the user is not trapped in the app.
Accessible keyboard navigation, labels, focus states and sensible contrast.
Deliberately exclude these paid-product advantages: a trained classifier, a labelled corpus, a published false-positive rate, image/audio/video detection, per-sentence attribution.
Do not fake accuracy claims, benchmarks or compliance statements.
Write unit tests for the data model and one end-to-end smoke test of the core loop.
Create a README with setup, architecture, data location and an explicit limitations section.
Run the tests and build before finishing, then fix what fails.

## Required capabilities

- OpenAI or Anthropic API key in .env
- Node.js 22
- SQLite database
- A README stating plainly that the output is a guess, not a detector, and must never be used to accuse anyone

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

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

## Goal

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

## Scope

Build a private workspace that pastes in text, asks one general model for an AI-likelihood judgement with reasoning, stores results, and exports them.

## 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:
- a trained classifier and the labelled corpus behind it
- a measured false-positive rate you can quote to an institution
- detection for images, audio and video, not just text
- per-sentence highlighting instead of one document-level guess
- retraining as generators change

If those capabilities are essential, use Binoculars 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 the closest honest consolation tool inspired by WasItAIGenerated. Do not claim it detects AI writing.
Use exactly this stack: Next.js 15 + TypeScript + SQLite.
Primary job: paste text, send it to one general language model, and record that model's opinion on how machine-like the writing reads, with its reasoning.
Start from an empty folder and create the complete working project.
Single-user and private by default; store everything locally.
Put every secret in .env and provide .env.example.
Show the result as an opinion with reasoning, never as a score, a percentage or a verdict - the whole point of this build is that it cannot measure what the paid product measures.
Put a permanent, non-dismissable notice in the UI and the README: this is one model's guess, it has no measured error rate, and it must never be used to accuse anyone of anything.
Include clear empty, loading, validation, success and failure states.
Add export so the user is not trapped in the app.
Accessible keyboard navigation, labels, focus states and sensible contrast.
Deliberately exclude these paid-product advantages: a trained classifier, a labelled corpus, a published false-positive rate, image/audio/video detection, per-sentence attribution.
Do not fake accuracy claims, benchmarks or compliance statements.
Write unit tests for the data model and one end-to-end smoke test of the core loop.
Create a README with setup, architecture, data location and an explicit limitations section.
Run the tests and build before finishing, then fix what fails.

## Required capabilities

- OpenAI or Anthropic API key in .env
- Node.js 22
- SQLite database
- A README stating plainly that the output is a guess, not a detector, and must never be used to accuse anyone

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

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

## Problem

The interface is a text box; the product is a fine-tuned classifier. Detection quality does not come from a clever prompt. It comes from training a model on a labelled corpus and tuning it until the error rate is low enough to act on, which is months of work against a target that moves every time a new generator ships. Asking a general model "is this AI-written?" produces confident, unreliable answers, and in an academic-integrity setting that means falsely accusing real students. A one-shot build gets you the UI and none of the responsibility.

## Product outcome

Build a private workspace that pastes in text, asks one general model for an AI-likelihood judgement with reasoning, stores results, and exports them.

## Target user

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

## Required capabilities

- OpenAI or Anthropic API key in .env
- Node.js 22
- SQLite database
- A README stating plainly that the output is a guess, not a detector, and must never be used to accuse anyone

## Explicit non-goals for v1

- a trained classifier and the labelled corpus behind it
- a measured false-positive rate you can quote to an institution
- detection for images, audio and video, not just text
- per-sentence highlighting instead of one document-level guess
- retraining as generators change

## 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 the closest honest consolation tool inspired by WasItAIGenerated. Do not claim it detects AI writing.
Use exactly this stack: Next.js 15 + TypeScript + SQLite.
Primary job: paste text, send it to one general language model, and record that model's opinion on how machine-like the writing reads, with its reasoning.
Start from an empty folder and create the complete working project.
Single-user and private by default; store everything locally.
Put every secret in .env and provide .env.example.
Show the result as an opinion with reasoning, never as a score, a percentage or a verdict - the whole point of this build is that it cannot measure what the paid product measures.
Put a permanent, non-dismissable notice in the UI and the README: this is one model's guess, it has no measured error rate, and it must never be used to accuse anyone of anything.
Include clear empty, loading, validation, success and failure states.
Add export so the user is not trapped in the app.
Accessible keyboard navigation, labels, focus states and sensible contrast.
Deliberately exclude these paid-product advantages: a trained classifier, a labelled corpus, a published false-positive rate, image/audio/video detection, per-sentence attribution.
Do not fake accuracy claims, benchmarks or compliance statements.
Write unit tests for the data model and one end-to-end smoke test of the core loop.
Create a README with setup, architecture, data location and an explicit limitations section.
Run the tests and build before finishing, then fix what fails.

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

# WasItAIGenerated indie build

## Goal

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

## Scope

Build a private workspace that pastes in text, asks one general model for an AI-likelihood judgement with reasoning, stores results, and exports them.

## 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:
- a trained classifier and the labelled corpus behind it
- a measured false-positive rate you can quote to an institution
- detection for images, audio and video, not just text
- per-sentence highlighting instead of one document-level guess
- retraining as generators change

If those capabilities are essential, use Binoculars 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 the closest honest consolation tool inspired by WasItAIGenerated. Do not claim it detects AI writing.
Use exactly this stack: Next.js 15 + TypeScript + SQLite.
Primary job: paste text, send it to one general language model, and record that model's opinion on how machine-like the writing reads, with its reasoning.
Start from an empty folder and create the complete working project.
Single-user and private by default; store everything locally.
Put every secret in .env and provide .env.example.
Show the result as an opinion with reasoning, never as a score, a percentage or a verdict - the whole point of this build is that it cannot measure what the paid product measures.
Put a permanent, non-dismissable notice in the UI and the README: this is one model's guess, it has no measured error rate, and it must never be used to accuse anyone of anything.
Include clear empty, loading, validation, success and failure states.
Add export so the user is not trapped in the app.
Accessible keyboard navigation, labels, focus states and sensible contrast.
Deliberately exclude these paid-product advantages: a trained classifier, a labelled corpus, a published false-positive rate, image/audio/video detection, per-sentence attribution.
Do not fake accuracy claims, benchmarks or compliance statements.
Write unit tests for the data model and one end-to-end smoke test of the core loop.
Create a README with setup, architecture, data location and an explicit limitations section.
Run the tests and build before finishing, then fix what fails.

## Required capabilities

- OpenAI or Anthropic API key in .env
- Node.js 22
- SQLite database
- A README stating plainly that the output is a guess, not a detector, and must never be used to accuse anyone

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

# WasItAIGenerated product brief

## Problem

The interface is a text box; the product is a fine-tuned classifier. Detection quality does not come from a clever prompt. It comes from training a model on a labelled corpus and tuning it until the error rate is low enough to act on, which is months of work against a target that moves every time a new generator ships. Asking a general model "is this AI-written?" produces confident, unreliable answers, and in an academic-integrity setting that means falsely accusing real students. A one-shot build gets you the UI and none of the responsibility.

## Product outcome

Build a private workspace that pastes in text, asks one general model for an AI-likelihood judgement with reasoning, stores results, and exports them.

## Target user

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

## Required capabilities

- OpenAI or Anthropic API key in .env
- Node.js 22
- SQLite database
- A README stating plainly that the output is a guess, not a detector, and must never be used to accuse anyone

## Explicit non-goals for v1

- a trained classifier and the labelled corpus behind it
- a measured false-positive rate you can quote to an institution
- detection for images, audio and video, not just text
- per-sentence highlighting instead of one document-level guess
- retraining as generators change

## 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 the closest honest consolation tool inspired by WasItAIGenerated. Do not claim it detects AI writing.
Use exactly this stack: Next.js 15 + TypeScript + SQLite.
Primary job: paste text, send it to one general language model, and record that model's opinion on how machine-like the writing reads, with its reasoning.
Start from an empty folder and create the complete working project.
Single-user and private by default; store everything locally.
Put every secret in .env and provide .env.example.
Show the result as an opinion with reasoning, never as a score, a percentage or a verdict - the whole point of this build is that it cannot measure what the paid product measures.
Put a permanent, non-dismissable notice in the UI and the README: this is one model's guess, it has no measured error rate, and it must never be used to accuse anyone of anything.
Include clear empty, loading, validation, success and failure states.
Add export so the user is not trapped in the app.
Accessible keyboard navigation, labels, focus states and sensible contrast.
Deliberately exclude these paid-product advantages: a trained classifier, a labelled corpus, a published false-positive rate, image/audio/video detection, per-sentence attribution.
Do not fake accuracy claims, benchmarks or compliance statements.
Write unit tests for the data model and one end-to-end smoke test of the core loop.
Create a README with setup, architecture, data location and an explicit limitations section.
Run the tests and build before finishing, then fix what fails.

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