Vibecode Inbox Zero
track this build5 phases, 16 steps, beginner friendly0%KINDA · weekend project
The personal Gmail loop is a weekend project: classify new mail, apply labels, draft replies, and surface bulk cleanup. The gap is making it trustworthy enough to sit inside a real inbox every day: OAuth setup and review, token refresh, provider quirks, continuous sync, retries, rate limits, security, and integrations. Inbox Zero itself is open source, so anyone wanting the full product should self-host the official code instead of rebuilding all of it.
the project pack5 files · written for this build, step by step
You are building a lean indie version of Inbox Zero. 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 ===== # Inbox Zero · indie build Build a read-only email triage desk with reviewed draft replies. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | | Generation | Ollama local HTTP API | A backend-only adapter with a configurable installed local model and visible failure states. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Inbox Zero acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. - Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. - [ ] **Confirm the bounded replacement** · No paid service required for this local step. - Why: The full commercial product is larger than this guide. - Get it: The deliverable is a read-only email triage desk with reviewed draft replies. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. - Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. - [ ] **Ollama with an explicitly local model** · No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Why: Generation requires a running model; ordinary editing remains usable while it is unavailable. - Get it: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. - Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` Then copy `.env.example` to `.env` and fill in the values it documents. ## Honest limits This build deliberately does not replace: - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - This is a read-only email triage desk with reviewed draft replies; full Inbox Zero feature parity, vendor hosting and support are not included. - Outlook and reliable multi-account support - battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime - reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context - Slack and Telegram chat, mobile access, meeting briefs, and attachment filing - hosted security, compliance, team administration, monitoring, and support If one of those is essential to you, that is the reason to keep paying for Inbox Zero, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · Inbox Zero The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a read-only email triage desk with reviewed draft replies as a bounded replacement for Inbox Zero. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. - Generation: Ollama local HTTP API. A backend-only adapter with a configurable installed local model and visible failure states. ### Data model (create this before Phase 1) - messages(id,message_id,subject,sender,body,received_at) - classifications(message_id,category,reason,model,revision) - rules(id,sender_pattern,category,enabled) - drafts(id,message_id,text,state) - actions(id,message_id,proposed_action,state) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Inbox Zero acceptance sample: Create synthetic sample data before implementation: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a read-only email triage desk with reviewed draft replies. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Ollama with an explicitly local model: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. Cost: No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, OLLAMA_URL, LOCAL_MODEL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a read-only email triage desk with reviewed draft replies, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: messages(id,message_id,subject,sender,body,received_at); classifications(message_id,category,reason,model,revision); rules(id,sender_pattern,category,enabled); drafts(id,message_id,text,state); actions(id,message_id,proposed_action,state). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Commands, after creating the named files: `python scripts/model_probe.py`. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start private import until these checks pass. ### Phase 2 · Private import Build: Private import for Inbox Zero: Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. - Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. - Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Importing the same mailbox sample twice preserves three messages. Then check: Viewing the hostile message makes no remote image request. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. Done when: Importing the same mailbox sample twice preserves three messages. Viewing the hostile message makes no remote image request. Do not build yet: Do not start explainable triage until these checks pass. ### Phase 3 · Explainable triage Build: Explainable triage for Inbox Zero: Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. - Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. - Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Instructions inside the hostile email cannot change app rules or access files. Then check: A malformed model reply becomes unknown rather than silently archived. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Classification is a suggestion, not authorization to delete or unsubscribe. Done when: Instructions inside the hostile email cannot change app rules or access files. A malformed model reply becomes unknown rather than silently archived. Do not build yet: Do not start draft and export until these checks pass. ### Phase 4 · Draft and export Build: Draft and export for Inbox Zero: Generate a reply draft from a selected message and user intent; show it for manual editing without sending. - Generate a reply draft from a selected message and user intent; show it for manual editing without sending. - Export approved draft text and a proposed-action CSV the user can review in their actual mail client. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: No interaction in the app sends, deletes or archives a real email. Then check: Rejecting a proposed action leaves the imported source unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. Done when: No interaction in the app sends, deletes or archives a real email. Rejecting a proposed action leaves the imported source unchanged. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Inbox Zero replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Private import; Explainable triage; Draft and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a read-only email triage desk with reviewed draft replies operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - This is a read-only email triage desk with reviewed draft replies; full Inbox Zero feature parity, vendor hosting and support are not included. - Outlook and reliable multi-account support: retain the paid product if this capability is essential; it is outside this bounded build. - battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime: retain the paid product if this capability is essential; it is outside this bounded build. - reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context: retain the paid product if this capability is essential; it is outside this bounded build. - Slack and Telegram chat, mobile access, meeting briefs, and attachment filing: retain the paid product if this capability is essential; it is outside this bounded build. - hosted security, compliance, team administration, monitoring, and support: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html ; https://docs.ollama.com/api/chat ; https://docs.ollama.com/cloud. Recheck before upgrading; freeze the versions actually tested. ===== AGENTS.md ===== # Agent instructions · Inbox Zero indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures, Ollama local HTTP API. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · Inbox Zero Build a read-only email triage desk with reviewed draft replies. Phases are in dependency order. Each ends in a "Done when" list; treat an unticked item as a blocker, not a note. ## Phase 1 · Local foundation and data contract Create the runnable local foundation for a read-only email triage desk with reviewed draft replies, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: messages(id,message_id,subject,sender,body,received_at); classifications(message_id,category,reason,model,revision); rules(id,sender_pattern,category,enabled); drafts(id,message_id,text,state); actions(id,message_id,proposed_action,state). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` 4. Verify the selected local model Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Files: `providers/local_model.py`, `scripts/model_probe.py` ```sh python scripts/model_probe.py ``` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## Phase 2 · Private import Private import for Inbox Zero: Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. ### Steps 1. Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. Files: `features/private_import.py`, `templates/private_import.html` 2. Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. Files: `features/private_import.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Importing the same mailbox sample twice preserves three messages. Then check: Viewing the hostile message makes no remote image request. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_private_import.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Importing the same mailbox sample twice preserves three messages. - [ ] Viewing the hostile message makes no remote image request. ### Watch out - Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. ## Phase 3 · Explainable triage Explainable triage for Inbox Zero: Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. ### Steps 1. Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. Files: `features/explainable_triage.py`, `templates/explainable_triage.html` 2. Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. Files: `features/explainable_triage.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Instructions inside the hostile email cannot change app rules or access files. Then check: A malformed model reply becomes unknown rather than silently archived. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_explainable_triage.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Instructions inside the hostile email cannot change app rules or access files. - [ ] A malformed model reply becomes unknown rather than silently archived. ### Watch out - Classification is a suggestion, not authorization to delete or unsubscribe. ## Phase 4 · Draft and export Draft and export for Inbox Zero: Generate a reply draft from a selected message and user intent; show it for manual editing without sending. ### Steps 1. Generate a reply draft from a selected message and user intent; show it for manual editing without sending. Generate a reply draft from a selected message and user intent; show it for manual editing without sending. Files: `features/draft_and_export.py`, `templates/draft_and_export.html` 2. Export approved draft text and a proposed-action CSV the user can review in their actual mail client. Export approved draft text and a proposed-action CSV the user can review in their actual mail client. Files: `features/draft_and_export.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: No interaction in the app sends, deletes or archives a real email. Then check: Rejecting a proposed action leaves the imported source unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_draft_and_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] No interaction in the app sends, deletes or archives a real email. - [ ] Rejecting a proposed action leaves the imported source unchanged. ### Watch out - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. ## Phase 5 · Portable delivery and clean-start proof Finish the Inbox Zero replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Private import; Explainable triage; Draft and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## Not in this build - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - This is a read-only email triage desk with reviewed draft replies; full Inbox Zero feature parity, vendor hosting and support are not included. - Outlook and reliable multi-account support - battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime - reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context - Slack and Telegram chat, mobile access, meeting briefs, and attachment filing - hosted security, compliance, team administration, monitoring, and support ## After v1, if you want it - Extend draft and export only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/inbox-zero # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000 # Required. Keep the inference service bound to loopback; the backend calls it, never the public browser. OLLAMA_URL=http://127.0.0.1:11434 # Required. Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. LOCAL_MODEL=replace-with-installed-local-model
You are building a lean indie version of Inbox Zero. 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 ===== # Inbox Zero · indie build Build a read-only email triage desk with reviewed draft replies. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | | Generation | Ollama local HTTP API | A backend-only adapter with a configurable installed local model and visible failure states. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Inbox Zero acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. - Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. - [ ] **Confirm the bounded replacement** · No paid service required for this local step. - Why: The full commercial product is larger than this guide. - Get it: The deliverable is a read-only email triage desk with reviewed draft replies. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. - Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. - [ ] **Ollama with an explicitly local model** · No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Why: Generation requires a running model; ordinary editing remains usable while it is unavailable. - Get it: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. - Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` Then copy `.env.example` to `.env` and fill in the values it documents. ## Honest limits This build deliberately does not replace: - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - This is a read-only email triage desk with reviewed draft replies; full Inbox Zero feature parity, vendor hosting and support are not included. - Outlook and reliable multi-account support - battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime - reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context - Slack and Telegram chat, mobile access, meeting briefs, and attachment filing - hosted security, compliance, team administration, monitoring, and support If one of those is essential to you, that is the reason to keep paying for Inbox Zero, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · Inbox Zero The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a read-only email triage desk with reviewed draft replies as a bounded replacement for Inbox Zero. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. - Generation: Ollama local HTTP API. A backend-only adapter with a configurable installed local model and visible failure states. ### Data model (create this before Phase 1) - messages(id,message_id,subject,sender,body,received_at) - classifications(message_id,category,reason,model,revision) - rules(id,sender_pattern,category,enabled) - drafts(id,message_id,text,state) - actions(id,message_id,proposed_action,state) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Inbox Zero acceptance sample: Create synthetic sample data before implementation: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a read-only email triage desk with reviewed draft replies. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Ollama with an explicitly local model: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. Cost: No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, OLLAMA_URL, LOCAL_MODEL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a read-only email triage desk with reviewed draft replies, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: messages(id,message_id,subject,sender,body,received_at); classifications(message_id,category,reason,model,revision); rules(id,sender_pattern,category,enabled); drafts(id,message_id,text,state); actions(id,message_id,proposed_action,state). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Commands, after creating the named files: `python scripts/model_probe.py`. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start private import until these checks pass. ### Phase 2 · Private import Build: Private import for Inbox Zero: Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. - Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. - Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Importing the same mailbox sample twice preserves three messages. Then check: Viewing the hostile message makes no remote image request. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. Done when: Importing the same mailbox sample twice preserves three messages. Viewing the hostile message makes no remote image request. Do not build yet: Do not start explainable triage until these checks pass. ### Phase 3 · Explainable triage Build: Explainable triage for Inbox Zero: Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. - Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. - Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Instructions inside the hostile email cannot change app rules or access files. Then check: A malformed model reply becomes unknown rather than silently archived. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Classification is a suggestion, not authorization to delete or unsubscribe. Done when: Instructions inside the hostile email cannot change app rules or access files. A malformed model reply becomes unknown rather than silently archived. Do not build yet: Do not start draft and export until these checks pass. ### Phase 4 · Draft and export Build: Draft and export for Inbox Zero: Generate a reply draft from a selected message and user intent; show it for manual editing without sending. - Generate a reply draft from a selected message and user intent; show it for manual editing without sending. - Export approved draft text and a proposed-action CSV the user can review in their actual mail client. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: No interaction in the app sends, deletes or archives a real email. Then check: Rejecting a proposed action leaves the imported source unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. Done when: No interaction in the app sends, deletes or archives a real email. Rejecting a proposed action leaves the imported source unchanged. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Inbox Zero replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Private import; Explainable triage; Draft and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a read-only email triage desk with reviewed draft replies operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - This is a read-only email triage desk with reviewed draft replies; full Inbox Zero feature parity, vendor hosting and support are not included. - Outlook and reliable multi-account support: retain the paid product if this capability is essential; it is outside this bounded build. - battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime: retain the paid product if this capability is essential; it is outside this bounded build. - reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context: retain the paid product if this capability is essential; it is outside this bounded build. - Slack and Telegram chat, mobile access, meeting briefs, and attachment filing: retain the paid product if this capability is essential; it is outside this bounded build. - hosted security, compliance, team administration, monitoring, and support: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html ; https://docs.ollama.com/api/chat ; https://docs.ollama.com/cloud. Recheck before upgrading; freeze the versions actually tested. ===== AGENTS.md ===== # Agent instructions · Inbox Zero indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures, Ollama local HTTP API. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · Inbox Zero Build a read-only email triage desk with reviewed draft replies. Phases are in dependency order. Each ends in a "Done when" list; treat an unticked item as a blocker, not a note. ## Phase 1 · Local foundation and data contract Create the runnable local foundation for a read-only email triage desk with reviewed draft replies, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: messages(id,message_id,subject,sender,body,received_at); classifications(message_id,category,reason,model,revision); rules(id,sender_pattern,category,enabled); drafts(id,message_id,text,state); actions(id,message_id,proposed_action,state). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` 4. Verify the selected local model Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Files: `providers/local_model.py`, `scripts/model_probe.py` ```sh python scripts/model_probe.py ``` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## Phase 2 · Private import Private import for Inbox Zero: Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. ### Steps 1. Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. Files: `features/private_import.py`, `templates/private_import.html` 2. Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. Files: `features/private_import.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Importing the same mailbox sample twice preserves three messages. Then check: Viewing the hostile message makes no remote image request. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_private_import.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Importing the same mailbox sample twice preserves three messages. - [ ] Viewing the hostile message makes no remote image request. ### Watch out - Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. ## Phase 3 · Explainable triage Explainable triage for Inbox Zero: Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. ### Steps 1. Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. Files: `features/explainable_triage.py`, `templates/explainable_triage.html` 2. Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. Files: `features/explainable_triage.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Instructions inside the hostile email cannot change app rules or access files. Then check: A malformed model reply becomes unknown rather than silently archived. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_explainable_triage.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Instructions inside the hostile email cannot change app rules or access files. - [ ] A malformed model reply becomes unknown rather than silently archived. ### Watch out - Classification is a suggestion, not authorization to delete or unsubscribe. ## Phase 4 · Draft and export Draft and export for Inbox Zero: Generate a reply draft from a selected message and user intent; show it for manual editing without sending. ### Steps 1. Generate a reply draft from a selected message and user intent; show it for manual editing without sending. Generate a reply draft from a selected message and user intent; show it for manual editing without sending. Files: `features/draft_and_export.py`, `templates/draft_and_export.html` 2. Export approved draft text and a proposed-action CSV the user can review in their actual mail client. Export approved draft text and a proposed-action CSV the user can review in their actual mail client. Files: `features/draft_and_export.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: No interaction in the app sends, deletes or archives a real email. Then check: Rejecting a proposed action leaves the imported source unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_draft_and_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] No interaction in the app sends, deletes or archives a real email. - [ ] Rejecting a proposed action leaves the imported source unchanged. ### Watch out - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. ## Phase 5 · Portable delivery and clean-start proof Finish the Inbox Zero replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Private import; Explainable triage; Draft and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## Not in this build - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - This is a read-only email triage desk with reviewed draft replies; full Inbox Zero feature parity, vendor hosting and support are not included. - Outlook and reliable multi-account support - battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime - reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context - Slack and Telegram chat, mobile access, meeting briefs, and attachment filing - hosted security, compliance, team administration, monitoring, and support ## After v1, if you want it - Extend draft and export only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/inbox-zero # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000 # Required. Keep the inference service bound to loopback; the backend calls it, never the public browser. OLLAMA_URL=http://127.0.0.1:11434 # Required. Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. LOCAL_MODEL=replace-with-installed-local-model
You are building a production product version of Inbox Zero. 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 ===== # Inbox Zero · product brief ## Problem The personal Gmail loop is a weekend project: classify new mail, apply labels, draft replies, and surface bulk cleanup. The gap is making it trustworthy enough to sit inside a real inbox every day: OAuth setup and review, token refresh, provider quirks, continuous sync, retries, rate limits, security, and integrations. Inbox Zero itself is open source, so anyone wanting the full product should self-host the official code instead of rebuilding all of it. ## Product outcome An operated version of a read-only email triage desk with reviewed draft replies, with authorized access, restore evidence and honest scope limits. ## Target user A builder who needs a maintainable product foundation, not a one-off demo. ## Required capabilities - Google Cloud OAuth client - OpenAI API key - Node 22 - always-on machine or VPS for continuous processing ## Explicit non-goals for v1 - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - This is a read-only email triage desk with reviewed draft replies; full Inbox Zero feature parity, vendor hosting and support are not included. - Outlook and reliable multi-account support - battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime - reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context - Slack and Telegram chat, mobile access, meeting briefs, and attachment filing - hosted security, compliance, team administration, monitoring, and support ## Success criteria - Importing the same mailbox sample twice preserves three messages. - Instructions inside the hostile email cannot change app rules or access files. - No interaction in the app sends, deletes or archives a real email. - A private-data authorization check passes using a second identity. - An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - README names the excluded vendor capabilities and actual provider/hosting costs. ===== BRIEF.md ===== # Build brief · Inbox Zero The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a read-only email triage desk with reviewed draft replies as a bounded replacement for Inbox Zero. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. - Generation: Ollama local HTTP API. A backend-only adapter with a configurable installed local model and visible failure states. ### Data model (create this before Phase 1) - messages(id,message_id,subject,sender,body,received_at) - classifications(message_id,category,reason,model,revision) - rules(id,sender_pattern,category,enabled) - drafts(id,message_id,text,state) - actions(id,message_id,proposed_action,state) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Inbox Zero acceptance sample: Create synthetic sample data before implementation: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a read-only email triage desk with reviewed draft replies. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Ollama with an explicitly local model: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. Cost: No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, OLLAMA_URL, LOCAL_MODEL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a read-only email triage desk with reviewed draft replies, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: messages(id,message_id,subject,sender,body,received_at); classifications(message_id,category,reason,model,revision); rules(id,sender_pattern,category,enabled); drafts(id,message_id,text,state); actions(id,message_id,proposed_action,state). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Commands, after creating the named files: `python scripts/model_probe.py`. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start private import until these checks pass. ### Phase 2 · Private import Build: Private import for Inbox Zero: Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. - Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. - Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Importing the same mailbox sample twice preserves three messages. Then check: Viewing the hostile message makes no remote image request. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. Done when: Importing the same mailbox sample twice preserves three messages. Viewing the hostile message makes no remote image request. Do not build yet: Do not start explainable triage until these checks pass. ### Phase 3 · Explainable triage Build: Explainable triage for Inbox Zero: Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. - Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. - Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Instructions inside the hostile email cannot change app rules or access files. Then check: A malformed model reply becomes unknown rather than silently archived. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Classification is a suggestion, not authorization to delete or unsubscribe. Done when: Instructions inside the hostile email cannot change app rules or access files. A malformed model reply becomes unknown rather than silently archived. Do not build yet: Do not start draft and export until these checks pass. ### Phase 4 · Draft and export Build: Draft and export for Inbox Zero: Generate a reply draft from a selected message and user intent; show it for manual editing without sending. - Generate a reply draft from a selected message and user intent; show it for manual editing without sending. - Export approved draft text and a proposed-action CSV the user can review in their actual mail client. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: No interaction in the app sends, deletes or archives a real email. Then check: Rejecting a proposed action leaves the imported source unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. Done when: No interaction in the app sends, deletes or archives a real email. Rejecting a proposed action leaves the imported source unchanged. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Inbox Zero replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Private import; Explainable triage; Draft and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a read-only email triage desk with reviewed draft replies operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - This is a read-only email triage desk with reviewed draft replies; full Inbox Zero feature parity, vendor hosting and support are not included. - Outlook and reliable multi-account support: retain the paid product if this capability is essential; it is outside this bounded build. - battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime: retain the paid product if this capability is essential; it is outside this bounded build. - reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context: retain the paid product if this capability is essential; it is outside this bounded build. - Slack and Telegram chat, mobile access, meeting briefs, and attachment filing: retain the paid product if this capability is essential; it is outside this bounded build. - hosted security, compliance, team administration, monitoring, and support: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html ; https://docs.ollama.com/api/chat ; https://docs.ollama.com/cloud. Recheck before upgrading; freeze the versions actually tested. ===== ARCHITECTURE.md ===== # Architecture · Inbox Zero ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | | Generation | Ollama local HTTP API | A backend-only adapter with a configurable installed local model and visible failure states. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | messages(id,message_id,subject,sender,body,received_at); classifications(message_id,category,reason,model,revision); rules(id,sender_pattern,category,enabled); drafts(id,message_id,text,state); actions(id,message_id,proposed_action,state) | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Private import | Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. | Keep the acceptance contract: Importing the same mailbox sample twice preserves three messages. Replace only this module after replaying its fixture; preserve ids and existing records. | | Explainable triage | Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. | Keep the acceptance contract: Instructions inside the hostile email cannot change app rules or access files. Replace only this module after replaying its fixture; preserve ids and existing records. | | Draft and export | Generate a reply draft from a selected message and user intent; show it for manual editing without sending. | Keep the acceptance contract: No interaction in the app sends, deletes or archives a real email. Replace only this module after replaying its fixture; preserve ids and existing records. | | Operations | Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. | Change host or backup destination only after an isolated restore and authorization check. | ## Configuration Every runtime setting is an environment variable documented in `.env.example`, validated at startup, with a safe local default wherever one exists. - `DATA_DIR` · required · A new private folder this application creates on first run; never serve it as static files. - `SECRET_KEY` · required, secret · Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. - `APP_MODE` · required · Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. - `SITE_URL` · required · The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. - `OLLAMA_URL` · required · Keep the inference service bound to loopback; the backend calls it, never the public browser. - `LOCAL_MODEL` · required · Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. ## Production baseline - Security: least privilege, input validation at every boundary, secret redaction in logs, rate limits on abuse-prone paths, no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore procedures that have been exercised. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, timeouts. - Observability: structured logs with request or operation ids, an error-tracking hook, and health and readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, one end-to-end test of the critical path. ## Decision records For each dependency in the stack table, keep a short note: why it was chosen, its failure mode, and how it is replaced. Do not add infrastructure until a requirement in `PRODUCT.md` justifies it. ===== AGENTS.md ===== # Agent instructions · Inbox Zero product build - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures, Ollama local HTTP API. - Implement milestone by milestone from `MILESTONES.md`; keep each change reviewable and leave the application runnable at every commit. - 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 check pass. - Put every external service behind an interface with a deterministic fake for tests. - Add migrations and rollback or recovery notes for every persistent data change. - Log useful operational context without credentials, tokens, passwords or personal data. - Update documentation and run every check before completing a milestone. ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - Export without an import or restore rehearsal is not verified portability. - Product mode is additional engineering, not a switch that makes a local prototype production-ready. ===== MILESTONES.md ===== # Delivery milestones · Inbox Zero Estimated effort: **multi-day** for the indie phases; the production-only milestones add the trust and operability layer. ## M1 · Local foundation and data contract Create the runnable local foundation for a read-only email triage desk with reviewed draft replies, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: messages(id,message_id,subject,sender,body,received_at); classifications(message_id,category,reason,model,revision); rules(id,sender_pattern,category,enabled); drafts(id,message_id,text,state); actions(id,message_id,proposed_action,state). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` 4. Verify the selected local model Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Files: `providers/local_model.py`, `scripts/model_probe.py` ```sh python scripts/model_probe.py ``` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## M2 · Private import Private import for Inbox Zero: Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. ### Steps 1. Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. Files: `features/private_import.py`, `templates/private_import.html` 2. Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. Files: `features/private_import.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Importing the same mailbox sample twice preserves three messages. Then check: Viewing the hostile message makes no remote image request. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_private_import.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Importing the same mailbox sample twice preserves three messages. - [ ] Viewing the hostile message makes no remote image request. ### Watch out - Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. ## M3 · Explainable triage Explainable triage for Inbox Zero: Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. ### Steps 1. Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. Files: `features/explainable_triage.py`, `templates/explainable_triage.html` 2. Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. Files: `features/explainable_triage.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Instructions inside the hostile email cannot change app rules or access files. Then check: A malformed model reply becomes unknown rather than silently archived. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_explainable_triage.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Instructions inside the hostile email cannot change app rules or access files. - [ ] A malformed model reply becomes unknown rather than silently archived. ### Watch out - Classification is a suggestion, not authorization to delete or unsubscribe. ## M4 · Draft and export Draft and export for Inbox Zero: Generate a reply draft from a selected message and user intent; show it for manual editing without sending. ### Steps 1. Generate a reply draft from a selected message and user intent; show it for manual editing without sending. Generate a reply draft from a selected message and user intent; show it for manual editing without sending. Files: `features/draft_and_export.py`, `templates/draft_and_export.html` 2. Export approved draft text and a proposed-action CSV the user can review in their actual mail client. Export approved draft text and a proposed-action CSV the user can review in their actual mail client. Files: `features/draft_and_export.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: No interaction in the app sends, deletes or archives a real email. Then check: Rejecting a proposed action leaves the imported source unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_draft_and_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] No interaction in the app sends, deletes or archives a real email. - [ ] Rejecting a proposed action leaves the imported source unchanged. ### Watch out - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. ## M5 · Portable delivery and clean-start proof Finish the Inbox Zero replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Private import; Explainable triage; Draft and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## M6 · Operate and share with access controls (production only) Product-builder only: make a read-only email triage desk with reviewed draft replies operable for its stated audience before allowing remote access. ### Steps 1. Establish owner access before exposure Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. Files: `ARCHITECTURE.md`, `OPERATIONS.md` 2. Deploy a monitored service Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Files: `Caddyfile`, `OPERATIONS.md` ```sh waitress-serve --listen=127.0.0.1:5000 app:app ``` 3. Rehearse loss and recovery Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. Files: `OPERATIONS.md`, `release-checklist.md` ### Done when - [ ] An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. - [ ] A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. - [ ] Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. ### Watch out - Product mode is additional engineering, not a switch that makes a local prototype production-ready. ===== OPERATIONS.md ===== # Operations · Inbox Zero ## Backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Do a restore drill before the first real user, and write the date here when it passes. ## Monitoring Check HTTP availability, free disk, backup age and domain failures for Private import, Explainable triage, Draft and export. Alert without logging private payloads. ## Incident checklist Pause outbound jobs and public intake as appropriate, preserve redacted diagnostics, restore an isolated verified backup, rotate affected credentials and reconcile uncertain effects before reopening. 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 backup when needed. 5. Document the root cause, the remediation and the regression test. ## Release gate - [ ] Importing the same mailbox sample twice preserves three messages. - [ ] Instructions inside the hostile email cannot change app rules or access files. - [ ] No interaction in the app sends, deletes or archives a real email. - [ ] A private-data authorization check passes using a second identity. - [ ] An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - [ ] README names the excluded vendor capabilities and actual provider/hosting costs. ## Launch constraint Do not market omitted Inbox Zero capabilities as implemented. The non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/inbox-zero # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000 # Required. Keep the inference service bound to loopback; the backend calls it, never the public browser. OLLAMA_URL=http://127.0.0.1:11434 # Required. Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. LOCAL_MODEL=replace-with-installed-local-model
README.md
# Inbox Zero · indie build Build a read-only email triage desk with reviewed draft replies. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | | Generation | Ollama local HTTP API | A backend-only adapter with a configurable installed local model and visible failure states. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Inbox Zero acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. - Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. - [ ] **Confirm the bounded replacement** · No paid service required for this local step. - Why: The full commercial product is larger than this guide. - Get it: The deliverable is a read-only email triage desk with reviewed draft replies. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. - Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. - [ ] **Ollama with an explicitly local model** · No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Why: Generation requires a running model; ordinary editing remains usable while it is unavailable. - Get it: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. - Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` Then copy `.env.example` to `.env` and fill in the values it documents. ## Honest limits This build deliberately does not replace: - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - This is a read-only email triage desk with reviewed draft replies; full Inbox Zero feature parity, vendor hosting and support are not included. - Outlook and reliable multi-account support - battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime - reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context - Slack and Telegram chat, mobile access, meeting briefs, and attachment filing - hosted security, compliance, team administration, monitoring, and support If one of those is essential to you, that is the reason to keep paying for Inbox Zero, and the README should say so rather than pretend.
BRIEF.md
# Build brief · Inbox Zero The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a read-only email triage desk with reviewed draft replies as a bounded replacement for Inbox Zero. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. - Generation: Ollama local HTTP API. A backend-only adapter with a configurable installed local model and visible failure states. ### Data model (create this before Phase 1) - messages(id,message_id,subject,sender,body,received_at) - classifications(message_id,category,reason,model,revision) - rules(id,sender_pattern,category,enabled) - drafts(id,message_id,text,state) - actions(id,message_id,proposed_action,state) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Inbox Zero acceptance sample: Create synthetic sample data before implementation: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a read-only email triage desk with reviewed draft replies. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Ollama with an explicitly local model: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. Cost: No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, OLLAMA_URL, LOCAL_MODEL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a read-only email triage desk with reviewed draft replies, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: messages(id,message_id,subject,sender,body,received_at); classifications(message_id,category,reason,model,revision); rules(id,sender_pattern,category,enabled); drafts(id,message_id,text,state); actions(id,message_id,proposed_action,state). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Commands, after creating the named files: `python scripts/model_probe.py`. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start private import until these checks pass. ### Phase 2 · Private import Build: Private import for Inbox Zero: Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. - Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. - Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Importing the same mailbox sample twice preserves three messages. Then check: Viewing the hostile message makes no remote image request. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. Done when: Importing the same mailbox sample twice preserves three messages. Viewing the hostile message makes no remote image request. Do not build yet: Do not start explainable triage until these checks pass. ### Phase 3 · Explainable triage Build: Explainable triage for Inbox Zero: Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. - Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. - Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Instructions inside the hostile email cannot change app rules or access files. Then check: A malformed model reply becomes unknown rather than silently archived. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Classification is a suggestion, not authorization to delete or unsubscribe. Done when: Instructions inside the hostile email cannot change app rules or access files. A malformed model reply becomes unknown rather than silently archived. Do not build yet: Do not start draft and export until these checks pass. ### Phase 4 · Draft and export Build: Draft and export for Inbox Zero: Generate a reply draft from a selected message and user intent; show it for manual editing without sending. - Generate a reply draft from a selected message and user intent; show it for manual editing without sending. - Export approved draft text and a proposed-action CSV the user can review in their actual mail client. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: No interaction in the app sends, deletes or archives a real email. Then check: Rejecting a proposed action leaves the imported source unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. Done when: No interaction in the app sends, deletes or archives a real email. Rejecting a proposed action leaves the imported source unchanged. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Inbox Zero replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Private import; Explainable triage; Draft and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a read-only email triage desk with reviewed draft replies operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - This is a read-only email triage desk with reviewed draft replies; full Inbox Zero feature parity, vendor hosting and support are not included. - Outlook and reliable multi-account support: retain the paid product if this capability is essential; it is outside this bounded build. - battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime: retain the paid product if this capability is essential; it is outside this bounded build. - reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context: retain the paid product if this capability is essential; it is outside this bounded build. - Slack and Telegram chat, mobile access, meeting briefs, and attachment filing: retain the paid product if this capability is essential; it is outside this bounded build. - hosted security, compliance, team administration, monitoring, and support: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html ; https://docs.ollama.com/api/chat ; https://docs.ollama.com/cloud. Recheck before upgrading; freeze the versions actually tested.
AGENTS.md
# Agent instructions · Inbox Zero indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures, Ollama local HTTP API. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - Export without an import or restore rehearsal is not verified portability.
BUILD_PLAN.md
# Build plan · Inbox Zero Build a read-only email triage desk with reviewed draft replies. Phases are in dependency order. Each ends in a "Done when" list; treat an unticked item as a blocker, not a note. ## Phase 1 · Local foundation and data contract Create the runnable local foundation for a read-only email triage desk with reviewed draft replies, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: messages(id,message_id,subject,sender,body,received_at); classifications(message_id,category,reason,model,revision); rules(id,sender_pattern,category,enabled); drafts(id,message_id,text,state); actions(id,message_id,proposed_action,state). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` 4. Verify the selected local model Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Files: `providers/local_model.py`, `scripts/model_probe.py` ```sh python scripts/model_probe.py ``` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## Phase 2 · Private import Private import for Inbox Zero: Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. ### Steps 1. Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. Files: `features/private_import.py`, `templates/private_import.html` 2. Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. Files: `features/private_import.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Importing the same mailbox sample twice preserves three messages. Then check: Viewing the hostile message makes no remote image request. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_private_import.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Importing the same mailbox sample twice preserves three messages. - [ ] Viewing the hostile message makes no remote image request. ### Watch out - Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. ## Phase 3 · Explainable triage Explainable triage for Inbox Zero: Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. ### Steps 1. Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. Files: `features/explainable_triage.py`, `templates/explainable_triage.html` 2. Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. Files: `features/explainable_triage.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Instructions inside the hostile email cannot change app rules or access files. Then check: A malformed model reply becomes unknown rather than silently archived. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_explainable_triage.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Instructions inside the hostile email cannot change app rules or access files. - [ ] A malformed model reply becomes unknown rather than silently archived. ### Watch out - Classification is a suggestion, not authorization to delete or unsubscribe. ## Phase 4 · Draft and export Draft and export for Inbox Zero: Generate a reply draft from a selected message and user intent; show it for manual editing without sending. ### Steps 1. Generate a reply draft from a selected message and user intent; show it for manual editing without sending. Generate a reply draft from a selected message and user intent; show it for manual editing without sending. Files: `features/draft_and_export.py`, `templates/draft_and_export.html` 2. Export approved draft text and a proposed-action CSV the user can review in their actual mail client. Export approved draft text and a proposed-action CSV the user can review in their actual mail client. Files: `features/draft_and_export.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: No interaction in the app sends, deletes or archives a real email. Then check: Rejecting a proposed action leaves the imported source unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_draft_and_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] No interaction in the app sends, deletes or archives a real email. - [ ] Rejecting a proposed action leaves the imported source unchanged. ### Watch out - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. ## Phase 5 · Portable delivery and clean-start proof Finish the Inbox Zero replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Private import; Explainable triage; Draft and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## Not in this build - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - This is a read-only email triage desk with reviewed draft replies; full Inbox Zero feature parity, vendor hosting and support are not included. - Outlook and reliable multi-account support - battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime - reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context - Slack and Telegram chat, mobile access, meeting briefs, and attachment filing - hosted security, compliance, team administration, monitoring, and support ## After v1, if you want it - Extend draft and export only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links.
.env.example
# Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/inbox-zero # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000 # Required. Keep the inference service bound to loopback; the backend calls it, never the public browser. OLLAMA_URL=http://127.0.0.1:11434 # Required. Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. LOCAL_MODEL=replace-with-installed-local-model
PRODUCT.md
# Inbox Zero · product brief ## Problem The personal Gmail loop is a weekend project: classify new mail, apply labels, draft replies, and surface bulk cleanup. The gap is making it trustworthy enough to sit inside a real inbox every day: OAuth setup and review, token refresh, provider quirks, continuous sync, retries, rate limits, security, and integrations. Inbox Zero itself is open source, so anyone wanting the full product should self-host the official code instead of rebuilding all of it. ## Product outcome An operated version of a read-only email triage desk with reviewed draft replies, with authorized access, restore evidence and honest scope limits. ## Target user A builder who needs a maintainable product foundation, not a one-off demo. ## Required capabilities - Google Cloud OAuth client - OpenAI API key - Node 22 - always-on machine or VPS for continuous processing ## Explicit non-goals for v1 - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - This is a read-only email triage desk with reviewed draft replies; full Inbox Zero feature parity, vendor hosting and support are not included. - Outlook and reliable multi-account support - battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime - reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context - Slack and Telegram chat, mobile access, meeting briefs, and attachment filing - hosted security, compliance, team administration, monitoring, and support ## Success criteria - Importing the same mailbox sample twice preserves three messages. - Instructions inside the hostile email cannot change app rules or access files. - No interaction in the app sends, deletes or archives a real email. - A private-data authorization check passes using a second identity. - An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - README names the excluded vendor capabilities and actual provider/hosting costs.
BRIEF.md
# Build brief · Inbox Zero The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a read-only email triage desk with reviewed draft replies as a bounded replacement for Inbox Zero. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. - Generation: Ollama local HTTP API. A backend-only adapter with a configurable installed local model and visible failure states. ### Data model (create this before Phase 1) - messages(id,message_id,subject,sender,body,received_at) - classifications(message_id,category,reason,model,revision) - rules(id,sender_pattern,category,enabled) - drafts(id,message_id,text,state) - actions(id,message_id,proposed_action,state) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Inbox Zero acceptance sample: Create synthetic sample data before implementation: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a read-only email triage desk with reviewed draft replies. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Ollama with an explicitly local model: Install Ollama from the official site, choose a locally runnable model from its library that fits available RAM, download it, and copy its exact installed name into LOCAL_MODEL. Use the documented local-only configuration, exclude cloud model names, and record model license, download size and tested memory use. Verify: ollama list shows the chosen model; a short local prompt succeeds with network access disabled after download. Cost: No cloud inference fee for this local configuration; you supply disk space, compute and electricity. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, OLLAMA_URL, LOCAL_MODEL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a read-only email triage desk with reviewed draft replies, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: messages(id,message_id,subject,sender,body,received_at); classifications(message_id,category,reason,model,revision); rules(id,sender_pattern,category,enabled); drafts(id,message_id,text,state); actions(id,message_id,proposed_action,state). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Commands, after creating the named files: `python scripts/model_probe.py`. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start private import until these checks pass. ### Phase 2 · Private import Build: Private import for Inbox Zero: Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. - Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. - Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Importing the same mailbox sample twice preserves three messages. Then check: Viewing the hostile message makes no remote image request. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. Done when: Importing the same mailbox sample twice preserves three messages. Viewing the hostile message makes no remote image request. Do not build yet: Do not start explainable triage until these checks pass. ### Phase 3 · Explainable triage Build: Explainable triage for Inbox Zero: Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. - Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. - Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Instructions inside the hostile email cannot change app rules or access files. Then check: A malformed model reply becomes unknown rather than silently archived. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Classification is a suggestion, not authorization to delete or unsubscribe. Done when: Instructions inside the hostile email cannot change app rules or access files. A malformed model reply becomes unknown rather than silently archived. Do not build yet: Do not start draft and export until these checks pass. ### Phase 4 · Draft and export Build: Draft and export for Inbox Zero: Generate a reply draft from a selected message and user intent; show it for manual editing without sending. - Generate a reply draft from a selected message and user intent; show it for manual editing without sending. - Export approved draft text and a proposed-action CSV the user can review in their actual mail client. - Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: No interaction in the app sends, deletes or archives a real email. Then check: Rejecting a proposed action leaves the imported source unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. Done when: No interaction in the app sends, deletes or archives a real email. Rejecting a proposed action leaves the imported source unchanged. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Inbox Zero replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Private import; Explainable triage; Draft and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a read-only email triage desk with reviewed draft replies operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - This is a read-only email triage desk with reviewed draft replies; full Inbox Zero feature parity, vendor hosting and support are not included. - Outlook and reliable multi-account support: retain the paid product if this capability is essential; it is outside this bounded build. - battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime: retain the paid product if this capability is essential; it is outside this bounded build. - reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context: retain the paid product if this capability is essential; it is outside this bounded build. - Slack and Telegram chat, mobile access, meeting briefs, and attachment filing: retain the paid product if this capability is essential; it is outside this bounded build. - hosted security, compliance, team administration, monitoring, and support: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html ; https://docs.ollama.com/api/chat ; https://docs.ollama.com/cloud. Recheck before upgrading; freeze the versions actually tested.
ARCHITECTURE.md
# Architecture · Inbox Zero ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | | Generation | Ollama local HTTP API | A backend-only adapter with a configurable installed local model and visible failure states. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | messages(id,message_id,subject,sender,body,received_at); classifications(message_id,category,reason,model,revision); rules(id,sender_pattern,category,enabled); drafts(id,message_id,text,state); actions(id,message_id,proposed_action,state) | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Private import | Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. | Keep the acceptance contract: Importing the same mailbox sample twice preserves three messages. Replace only this module after replaying its fixture; preserve ids and existing records. | | Explainable triage | Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. | Keep the acceptance contract: Instructions inside the hostile email cannot change app rules or access files. Replace only this module after replaying its fixture; preserve ids and existing records. | | Draft and export | Generate a reply draft from a selected message and user intent; show it for manual editing without sending. | Keep the acceptance contract: No interaction in the app sends, deletes or archives a real email. Replace only this module after replaying its fixture; preserve ids and existing records. | | Operations | Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. | Change host or backup destination only after an isolated restore and authorization check. | ## Configuration Every runtime setting is an environment variable documented in `.env.example`, validated at startup, with a safe local default wherever one exists. - `DATA_DIR` · required · A new private folder this application creates on first run; never serve it as static files. - `SECRET_KEY` · required, secret · Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. - `APP_MODE` · required · Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. - `SITE_URL` · required · The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. - `OLLAMA_URL` · required · Keep the inference service bound to loopback; the backend calls it, never the public browser. - `LOCAL_MODEL` · required · Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. ## Production baseline - Security: least privilege, input validation at every boundary, secret redaction in logs, rate limits on abuse-prone paths, no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore procedures that have been exercised. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, timeouts. - Observability: structured logs with request or operation ids, an error-tracking hook, and health and readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, one end-to-end test of the critical path. ## Decision records For each dependency in the stack table, keep a short note: why it was chosen, its failure mode, and how it is replaced. Do not add infrastructure until a requirement in `PRODUCT.md` justifies it.
AGENTS.md
# Agent instructions · Inbox Zero product build - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures, Ollama local HTTP API. - Implement milestone by milestone from `MILESTONES.md`; keep each change reviewable and leave the application runnable at every commit. - 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 check pass. - Put every external service behind an interface with a deterministic fake for tests. - Add migrations and rollback or recovery notes for every persistent data change. - Log useful operational context without credentials, tokens, passwords or personal data. - Update documentation and run every check before completing a milestone. ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. - Classification is a suggestion, not authorization to delete or unsubscribe. - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. - Export without an import or restore rehearsal is not verified portability. - Product mode is additional engineering, not a switch that makes a local prototype production-ready.
MILESTONES.md
# Delivery milestones · Inbox Zero Estimated effort: **multi-day** for the indie phases; the production-only milestones add the trust and operability layer. ## M1 · Local foundation and data contract Create the runnable local foundation for a read-only email triage desk with reviewed draft replies, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: messages(id,message_id,subject,sender,body,received_at); classifications(message_id,category,reason,model,revision); rules(id,sender_pattern,category,enabled); drafts(id,message_id,text,state); actions(id,message_id,proposed_action,state). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` 4. Verify the selected local model Create providers/local_model.py with a POST /api/chat adapter using the configured local model and stream:false. Validate structured output, bound input/output, set a timeout and reject cloud models or non-loopback inference URLs. Add a probe that sends one harmless prompt and a test double for deterministic tests. Missing model setup must disable generation with a specific error while leaving editing usable. Files: `providers/local_model.py`, `scripts/model_probe.py` ```sh python scripts/model_probe.py ``` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## M2 · Private import Private import for Inbox Zero: Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. ### Steps 1. Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. Parse manually exported .eml files and deduplicate Message-ID while preserving raw originals outside the public directory. Files: `features/private_import.py`, `templates/private_import.html` 2. Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. Render text bodies with remote images disabled and strip active HTML; do not connect mailbox mutation permissions. Files: `features/private_import.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Importing the same mailbox sample twice preserves three messages. Then check: Viewing the hostile message makes no remote image request. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_private_import.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Importing the same mailbox sample twice preserves three messages. - [ ] Viewing the hostile message makes no remote image request. ### Watch out - Manual import is the deliberate v1 boundary; no background mailbox cleanup is performed. ## M3 · Explainable triage Explainable triage for Inbox Zero: Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. ### Steps 1. Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. Apply explicit sender rules first and optionally ask the local model for one of receipt/action/newsletter/unknown with a reason. Files: `features/explainable_triage.py`, `templates/explainable_triage.html` 2. Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. Treat message contents as untrusted input, validate category JSON and expose a review queue for uncertain decisions. Files: `features/explainable_triage.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: Instructions inside the hostile email cannot change app rules or access files. Then check: A malformed model reply becomes unknown rather than silently archived. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_explainable_triage.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Instructions inside the hostile email cannot change app rules or access files. - [ ] A malformed model reply becomes unknown rather than silently archived. ### Watch out - Classification is a suggestion, not authorization to delete or unsubscribe. ## M4 · Draft and export Draft and export for Inbox Zero: Generate a reply draft from a selected message and user intent; show it for manual editing without sending. ### Steps 1. Generate a reply draft from a selected message and user intent; show it for manual editing without sending. Generate a reply draft from a selected message and user intent; show it for manual editing without sending. Files: `features/draft_and_export.py`, `templates/draft_and_export.html` 2. Export approved draft text and a proposed-action CSV the user can review in their actual mail client. Export approved draft text and a proposed-action CSV the user can review in their actual mail client. Files: `features/draft_and_export.py` 3. Exercise the acceptance fixture Use Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Check: No interaction in the app sends, deletes or archives a real email. Then check: Rejecting a proposed action leaves the imported source unchanged. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_draft_and_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] No interaction in the app sends, deletes or archives a real email. - [ ] Rejecting a proposed action leaves the imported source unchanged. ### Watch out - Automatic Gmail cleanup, outbound delivery and continuously maintained OAuth integrations are excluded. ## M5 · Portable delivery and clean-start proof Finish the Inbox Zero replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Private import; Explainable triage; Draft and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## M6 · Operate and share with access controls (production only) Product-builder only: make a read-only email triage desk with reviewed draft replies operable for its stated audience before allowing remote access. ### Steps 1. Establish owner access before exposure Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. Files: `ARCHITECTURE.md`, `OPERATIONS.md` 2. Deploy a monitored service Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Files: `Caddyfile`, `OPERATIONS.md` ```sh waitress-serve --listen=127.0.0.1:5000 app:app ``` 3. Rehearse loss and recovery Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. Files: `OPERATIONS.md`, `release-checklist.md` ### Done when - [ ] An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. - [ ] A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. - [ ] Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. ### Watch out - Product mode is additional engineering, not a switch that makes a local prototype production-ready.
OPERATIONS.md
# Operations · Inbox Zero ## Backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for inbox-zero. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Three exported .eml messages: a receipt, a personal request and a message containing malicious model instructions. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Do a restore drill before the first real user, and write the date here when it passes. ## Monitoring Check HTTP availability, free disk, backup age and domain failures for Private import, Explainable triage, Draft and export. Alert without logging private payloads. ## Incident checklist Pause outbound jobs and public intake as appropriate, preserve redacted diagnostics, restore an isolated verified backup, rotate affected credentials and reconcile uncertain effects before reopening. 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 backup when needed. 5. Document the root cause, the remediation and the regression test. ## Release gate - [ ] Importing the same mailbox sample twice preserves three messages. - [ ] Instructions inside the hostile email cannot change app rules or access files. - [ ] No interaction in the app sends, deletes or archives a real email. - [ ] A private-data authorization check passes using a second identity. - [ ] An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - [ ] README names the excluded vendor capabilities and actual provider/hosting costs. ## Launch constraint Do not market omitted Inbox Zero capabilities as implemented. The non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
.env.example
# Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/inbox-zero # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000 # Required. Keep the inference service bound to loopback; the backend calls it, never the public browser. OLLAMA_URL=http://127.0.0.1:11434 # Required. Copy the exact non-cloud name from ollama list; preflight must reject this placeholder. LOCAL_MODEL=replace-with-installed-local-model
$ choose a build depth, inspect the files, then open the complete pack in your agent
They pay for the two-click setup and the confidence that a security-sensitive inbox integration will stay synced, recover from provider failures, and keep its integrations working. People who prefer to own the infrastructure can self-host the official open-source product instead of maintaining a smaller rewrite.
xOutlook and reliable multi-account support
xbattle-tested token refresh, push sync, retries, rate-limit handling, and background uptime
xreply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context
xSlack and Telegram chat, mobile access, meeting briefs, and attachment filing
xhosted security, compliance, team administration, monitoring, and support
share on X ↗"I just replaced Inbox Zero ($20/mo) with one prompt"
Don't feel like building it? These folks already made it free.
Inbox ZeroThe exact organizer, drafter and cold-email blocker, free to self-host below five business users; OAuth and Docker remain unpaid labor.free↗no votes, no pay-to-list · just what's real
Inbox Zero pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| starter | $20/user | — | 1 paid user seat; limited knowledge base; no published email-volume or AI-action quota. |
| plus | $35/user | — | 2 email accounts included per user; unlimited knowledge base; no published email-volume or AI-action quota. |
| professional | $50/user | — | At least the 2 accounts/user included in Plus; team-wide analytics; no published email-volume or AI-action quota. |
| enterprise | custom | — | Custom plan for SSO, SCIM, on-premise deployment and dedicated account management; numeric caps not published. |
free tierno permanent hosted free tier; 7-day trial on hosted plans; the open-source edition can be self-hosted with Docker and Node.js 24+ but requires your own infrastructure and AI provider
billingmonthly + annual (vendor says annual saves up to 20%, but exact annual plan amounts were not exposed); changes are prorated; cancel anytime; 14-day refund window
hidden costsSelf-hosting avoids the hosted subscription but shifts cost to your own server, database/queue services and LLM usage. Hosted tiers publish no email-volume or AI-usage allowances, so potential usage limits or extra-account pricing could not be verified.
verified 2026-08-12 · source ↗
Vibecode Inbox Zero
Kinda. The core of Inbox Zero is buildable in a weekend with the prompt on this page, but there are real gaps: Outlook and reliable multi-account support, battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime. Read the honest list above before committing.
How much does Inbox Zero cost?
Inbox Zero costs about $20/month (Starter, checked 2026-07-30), which is $240 per year.
What do I lose by replacing Inbox Zero?
Honestly: Outlook and reliable multi-account support; battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime; reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context; Slack and Telegram chat, mobile access, meeting briefs, and attachment filing; hosted security, compliance, team administration, monitoring, and support. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Inbox Zero?
Yes: Inbox Zero (The exact organizer, drafter and cold-email blocker, free to self-host below five business users; OAuth and Docker remain unpaid labor.) The prompt is for when you want it exactly your way.