Vibecode Sentry
track this build5 phases, 16 steps, beginner friendly0%KINDA · weekend project
The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Sentry, receive bounded error events, group them, link releases, and notify one team. The hard boundary is sdk ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations, plus independent infrastructure and reliable alerting.
the project pack5 files · written for this build, step by step
You are building a lean indie version of Sentry. 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 ===== # Sentry · indie build Build a private error collector with deterministic grouping and one alert channel. 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. | ## 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. - [ ] **Sentry 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: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel. 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. - [ ] **An SMTP relay and one verified test recipient** · Provider-specific relay fees and domain costs; no free tier or delivery guarantee is assumed. - Why: Outbound confirmations or replies need a delivery provider; a fake adapter covers automated tests. - Get it: Obtain SMTP host, port, username and password from your chosen relay dashboard under SMTP settings. Verify the sender/domain using that provider DNS instructions. Use only your own test recipient initially and record the actual plan and rate limit in OPERATIONS.md. - Verify: The supplied smtp_probe.py sends one labelled test message to your own inbox and reports the relay response without logging credentials. ## 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: - This is a private error collector with deterministic grouping and one alert channel; full Sentry feature parity, vendor hosting and support are not included. - SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations - global probe network - phone and SMS delivery - massive retention - advanced incident response and support If one of those is essential to you, that is the reason to keep paying for Sentry, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · Sentry 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 private error collector with deterministic grouping and one alert channel as a bounded replacement for Sentry. 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. ### Data model (create this before Phase 1) - projects(id,name,ingest_key_hash) - events(id,project_id,event_key,release,message,frames_json,at) - issues(id,project_id,fingerprint,state) - occurrences(event_id,issue_id) - alert_outbox(id,issue_id,state,attempts) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. ### 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. - Sentry acceptance sample: Create synthetic sample data before implementation: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel. 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. - An SMTP relay and one verified test recipient: Obtain SMTP host, port, username and password from your chosen relay dashboard under SMTP settings. Verify the sender/domain using that provider DNS instructions. Use only your own test recipient initially and record the actual plan and rate limit in OPERATIONS.md. Verify: The supplied smtp_probe.py sends one labelled test message to your own inbox and reports the relay response without logging credentials. Cost: Provider-specific relay fees and domain costs; no free tier or delivery guarantee is assumed. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, MAIL_FROM, MAIL_TEST_TO. 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 private error collector with deterministic grouping and one alert channel, 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: projects(id,name,ingest_key_hash); events(id,project_id,event_key,release,message,frames_json,at); issues(id,project_id,fingerprint,state); occurrences(event_id,issue_id); alert_outbox(id,issue_id,state,attempts). 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: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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/mail.py using smtplib with a timeout, verified TLS/STARTTLS and an EmailMessage. Refuse placeholder credentials and non-test recipients until the owner enables sending. Implement scripts/smtp_probe.py to send one labelled message only to MAIL_TEST_TO, and provide a fake adapter for tests. Store no password or full message body in logs. Commands, after creating the named files: `python scripts/smtp_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 bounded ingestion until these checks pass. ### Phase 2 · Bounded ingestion Build: Bounded ingestion for Sentry: Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. - Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. - Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: Replaying an event id stores one event. Then check: The fixture secret is absent from stored event data and request logs. 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: Ingest credentials only permit event submission, never dashboard reads. Done when: Replaying an event id stores one event. The fixture secret is absent from stored event data and request logs. Do not build yet: Do not start grouping and release views until these checks pass. ### Phase 3 · Grouping and release views Build: Grouping and release views for Sentry: Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. - Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. - Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: The two matching exceptions form one issue and the distinct exception forms another. Then check: A new occurrence after resolution reopens the issue once. 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: A deterministic heuristic will over-group or split some errors; make manual inspection possible. Done when: The two matching exceptions form one issue and the distinct exception forms another. A new occurrence after resolution reopens the issue once. Do not build yet: Do not start alerts and retention until these checks pass. ### Phase 4 · Alerts and retention Build: Alerts and retention for Sentry: Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. - Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. - Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: A burst of 100 repeated occurrences produces one new-issue alert. Then check: Deleting expired events leaves current events queryable and updates counts consistently. 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: SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. Done when: A burst of 100 repeated occurrences produces one new-issue alert. Deleting expired events leaves current events queryable and updates counts consistently. 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 Sentry replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Bounded ingestion; Grouping and release views; Alerts and retention. 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 sentry. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel 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 sentry. 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) - This is a private error collector with deterministic grouping and one alert channel; full Sentry feature parity, vendor hosting and support are not included. - SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations: retain the paid product if this capability is essential; it is outside this bounded build. - global probe network: retain the paid product if this capability is essential; it is outside this bounded build. - phone and SMS delivery: retain the paid product if this capability is essential; it is outside this bounded build. - massive retention: retain the paid product if this capability is essential; it is outside this bounded build. - advanced incident response 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.python.org/3/library/smtplib.html. Recheck before upgrading; freeze the versions actually tested. ===== AGENTS.md ===== # Agent instructions · Sentry 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. 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. - Ingest credentials only permit event submission, never dashboard reads. - A deterministic heuristic will over-group or split some errors; make manual inspection possible. - SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · Sentry Build a private error collector with deterministic grouping and one alert channel. 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 private error collector with deterministic grouping and one alert channel, 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: projects(id,name,ingest_key_hash); events(id,project_id,event_key,release,message,frames_json,at); issues(id,project_id,fingerprint,state); occurrences(event_id,issue_id); alert_outbox(id,issue_id,state,attempts). 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: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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. Implement and test the email adapter Create providers/mail.py using smtplib with a timeout, verified TLS/STARTTLS and an EmailMessage. Refuse placeholder credentials and non-test recipients until the owner enables sending. Implement scripts/smtp_probe.py to send one labelled message only to MAIL_TEST_TO, and provide a fake adapter for tests. Store no password or full message body in logs. Files: `providers/mail.py`, `scripts/smtp_probe.py` ```sh python scripts/smtp_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 · Bounded ingestion Bounded ingestion for Sentry: Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. ### Steps 1. Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. Files: `features/bounded_ingestion.py`, `templates/bounded_ingestion.html` 2. Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. Files: `features/bounded_ingestion.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: Replaying an event id stores one event. Then check: The fixture secret is absent from stored event data and request logs. 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_bounded_ingestion.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Replaying an event id stores one event. - [ ] The fixture secret is absent from stored event data and request logs. ### Watch out - Ingest credentials only permit event submission, never dashboard reads. ## Phase 3 · Grouping and release views Grouping and release views for Sentry: Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. ### Steps 1. Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. Files: `features/grouping_and_release_views.py`, `templates/grouping_and_release_views.html` 2. Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. Files: `features/grouping_and_release_views.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: The two matching exceptions form one issue and the distinct exception forms another. Then check: A new occurrence after resolution reopens the issue once. 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_grouping_and_release_views.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] The two matching exceptions form one issue and the distinct exception forms another. - [ ] A new occurrence after resolution reopens the issue once. ### Watch out - A deterministic heuristic will over-group or split some errors; make manual inspection possible. ## Phase 4 · Alerts and retention Alerts and retention for Sentry: Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. ### Steps 1. Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. Files: `features/alerts_and_retention.py`, `templates/alerts_and_retention.html` 2. Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. Files: `features/alerts_and_retention.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: A burst of 100 repeated occurrences produces one new-issue alert. Then check: Deleting expired events leaves current events queryable and updates counts consistently. 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_alerts_and_retention.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A burst of 100 repeated occurrences produces one new-issue alert. - [ ] Deleting expired events leaves current events queryable and updates counts consistently. ### Watch out - SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. ## Phase 5 · Portable delivery and clean-start proof Finish the Sentry 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: Bounded ingestion; Grouping and release views; Alerts and retention. 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 sentry. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 - This is a private error collector with deterministic grouping and one alert channel; full Sentry feature parity, vendor hosting and support are not included. - SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations - global probe network - phone and SMS delivery - massive retention - advanced incident response and support ## After v1, if you want it - Extend alerts and retention 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/sentry # 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. Copy the SMTP hostname from the relay dashboard. SMTP_HOST=replace-with-relay-host # Required. Use a relay supporting STARTTLS on this port; confirm it in its setup instructions. SMTP_PORT=587 # Required · secret. Copy the relay username; it may differ from your sign-in email. SMTP_USER=replace-with-smtp-user # Required · secret. Create SMTP credentials in the relay dashboard, not your personal mailbox password. SMTP_PASSWORD=replace-with-smtp-password # Required. Your relay-verified sender address; replace before real sends. MAIL_FROM=owner@example.com # Required. An inbox you control for the explicit preflight test. MAIL_TEST_TO=owner@example.com
You are building a lean indie version of Sentry. 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 ===== # Sentry · indie build Build a private error collector with deterministic grouping and one alert channel. 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. | ## 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. - [ ] **Sentry 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: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel. 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. - [ ] **An SMTP relay and one verified test recipient** · Provider-specific relay fees and domain costs; no free tier or delivery guarantee is assumed. - Why: Outbound confirmations or replies need a delivery provider; a fake adapter covers automated tests. - Get it: Obtain SMTP host, port, username and password from your chosen relay dashboard under SMTP settings. Verify the sender/domain using that provider DNS instructions. Use only your own test recipient initially and record the actual plan and rate limit in OPERATIONS.md. - Verify: The supplied smtp_probe.py sends one labelled test message to your own inbox and reports the relay response without logging credentials. ## 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: - This is a private error collector with deterministic grouping and one alert channel; full Sentry feature parity, vendor hosting and support are not included. - SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations - global probe network - phone and SMS delivery - massive retention - advanced incident response and support If one of those is essential to you, that is the reason to keep paying for Sentry, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · Sentry 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 private error collector with deterministic grouping and one alert channel as a bounded replacement for Sentry. 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. ### Data model (create this before Phase 1) - projects(id,name,ingest_key_hash) - events(id,project_id,event_key,release,message,frames_json,at) - issues(id,project_id,fingerprint,state) - occurrences(event_id,issue_id) - alert_outbox(id,issue_id,state,attempts) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. ### 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. - Sentry acceptance sample: Create synthetic sample data before implementation: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel. 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. - An SMTP relay and one verified test recipient: Obtain SMTP host, port, username and password from your chosen relay dashboard under SMTP settings. Verify the sender/domain using that provider DNS instructions. Use only your own test recipient initially and record the actual plan and rate limit in OPERATIONS.md. Verify: The supplied smtp_probe.py sends one labelled test message to your own inbox and reports the relay response without logging credentials. Cost: Provider-specific relay fees and domain costs; no free tier or delivery guarantee is assumed. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, MAIL_FROM, MAIL_TEST_TO. 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 private error collector with deterministic grouping and one alert channel, 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: projects(id,name,ingest_key_hash); events(id,project_id,event_key,release,message,frames_json,at); issues(id,project_id,fingerprint,state); occurrences(event_id,issue_id); alert_outbox(id,issue_id,state,attempts). 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: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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/mail.py using smtplib with a timeout, verified TLS/STARTTLS and an EmailMessage. Refuse placeholder credentials and non-test recipients until the owner enables sending. Implement scripts/smtp_probe.py to send one labelled message only to MAIL_TEST_TO, and provide a fake adapter for tests. Store no password or full message body in logs. Commands, after creating the named files: `python scripts/smtp_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 bounded ingestion until these checks pass. ### Phase 2 · Bounded ingestion Build: Bounded ingestion for Sentry: Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. - Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. - Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: Replaying an event id stores one event. Then check: The fixture secret is absent from stored event data and request logs. 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: Ingest credentials only permit event submission, never dashboard reads. Done when: Replaying an event id stores one event. The fixture secret is absent from stored event data and request logs. Do not build yet: Do not start grouping and release views until these checks pass. ### Phase 3 · Grouping and release views Build: Grouping and release views for Sentry: Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. - Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. - Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: The two matching exceptions form one issue and the distinct exception forms another. Then check: A new occurrence after resolution reopens the issue once. 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: A deterministic heuristic will over-group or split some errors; make manual inspection possible. Done when: The two matching exceptions form one issue and the distinct exception forms another. A new occurrence after resolution reopens the issue once. Do not build yet: Do not start alerts and retention until these checks pass. ### Phase 4 · Alerts and retention Build: Alerts and retention for Sentry: Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. - Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. - Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: A burst of 100 repeated occurrences produces one new-issue alert. Then check: Deleting expired events leaves current events queryable and updates counts consistently. 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: SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. Done when: A burst of 100 repeated occurrences produces one new-issue alert. Deleting expired events leaves current events queryable and updates counts consistently. 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 Sentry replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Bounded ingestion; Grouping and release views; Alerts and retention. 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 sentry. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel 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 sentry. 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) - This is a private error collector with deterministic grouping and one alert channel; full Sentry feature parity, vendor hosting and support are not included. - SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations: retain the paid product if this capability is essential; it is outside this bounded build. - global probe network: retain the paid product if this capability is essential; it is outside this bounded build. - phone and SMS delivery: retain the paid product if this capability is essential; it is outside this bounded build. - massive retention: retain the paid product if this capability is essential; it is outside this bounded build. - advanced incident response 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.python.org/3/library/smtplib.html. Recheck before upgrading; freeze the versions actually tested. ===== AGENTS.md ===== # Agent instructions · Sentry 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. 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. - Ingest credentials only permit event submission, never dashboard reads. - A deterministic heuristic will over-group or split some errors; make manual inspection possible. - SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · Sentry Build a private error collector with deterministic grouping and one alert channel. 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 private error collector with deterministic grouping and one alert channel, 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: projects(id,name,ingest_key_hash); events(id,project_id,event_key,release,message,frames_json,at); issues(id,project_id,fingerprint,state); occurrences(event_id,issue_id); alert_outbox(id,issue_id,state,attempts). 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: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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. Implement and test the email adapter Create providers/mail.py using smtplib with a timeout, verified TLS/STARTTLS and an EmailMessage. Refuse placeholder credentials and non-test recipients until the owner enables sending. Implement scripts/smtp_probe.py to send one labelled message only to MAIL_TEST_TO, and provide a fake adapter for tests. Store no password or full message body in logs. Files: `providers/mail.py`, `scripts/smtp_probe.py` ```sh python scripts/smtp_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 · Bounded ingestion Bounded ingestion for Sentry: Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. ### Steps 1. Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. Files: `features/bounded_ingestion.py`, `templates/bounded_ingestion.html` 2. Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. Files: `features/bounded_ingestion.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: Replaying an event id stores one event. Then check: The fixture secret is absent from stored event data and request logs. 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_bounded_ingestion.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Replaying an event id stores one event. - [ ] The fixture secret is absent from stored event data and request logs. ### Watch out - Ingest credentials only permit event submission, never dashboard reads. ## Phase 3 · Grouping and release views Grouping and release views for Sentry: Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. ### Steps 1. Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. Files: `features/grouping_and_release_views.py`, `templates/grouping_and_release_views.html` 2. Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. Files: `features/grouping_and_release_views.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: The two matching exceptions form one issue and the distinct exception forms another. Then check: A new occurrence after resolution reopens the issue once. 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_grouping_and_release_views.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] The two matching exceptions form one issue and the distinct exception forms another. - [ ] A new occurrence after resolution reopens the issue once. ### Watch out - A deterministic heuristic will over-group or split some errors; make manual inspection possible. ## Phase 4 · Alerts and retention Alerts and retention for Sentry: Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. ### Steps 1. Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. Files: `features/alerts_and_retention.py`, `templates/alerts_and_retention.html` 2. Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. Files: `features/alerts_and_retention.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: A burst of 100 repeated occurrences produces one new-issue alert. Then check: Deleting expired events leaves current events queryable and updates counts consistently. 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_alerts_and_retention.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A burst of 100 repeated occurrences produces one new-issue alert. - [ ] Deleting expired events leaves current events queryable and updates counts consistently. ### Watch out - SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. ## Phase 5 · Portable delivery and clean-start proof Finish the Sentry 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: Bounded ingestion; Grouping and release views; Alerts and retention. 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 sentry. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 - This is a private error collector with deterministic grouping and one alert channel; full Sentry feature parity, vendor hosting and support are not included. - SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations - global probe network - phone and SMS delivery - massive retention - advanced incident response and support ## After v1, if you want it - Extend alerts and retention 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/sentry # 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. Copy the SMTP hostname from the relay dashboard. SMTP_HOST=replace-with-relay-host # Required. Use a relay supporting STARTTLS on this port; confirm it in its setup instructions. SMTP_PORT=587 # Required · secret. Copy the relay username; it may differ from your sign-in email. SMTP_USER=replace-with-smtp-user # Required · secret. Create SMTP credentials in the relay dashboard, not your personal mailbox password. SMTP_PASSWORD=replace-with-smtp-password # Required. Your relay-verified sender address; replace before real sends. MAIL_FROM=owner@example.com # Required. An inbox you control for the explicit preflight test. MAIL_TEST_TO=owner@example.com
You are building a production product version of Sentry. 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 ===== # Sentry · product brief ## Problem The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Sentry, receive bounded error events, group them, link releases, and notify one team. The hard boundary is sdk ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations, plus independent infrastructure and reliable alerting. ## Product outcome An operated version of a private error collector with deterministic grouping and one alert channel, 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 - server outside the monitored failure domain - PostgreSQL - optional ClickHouse - email or webhook destination - public HTTPS ## Explicit non-goals for v1 - This is a private error collector with deterministic grouping and one alert channel; full Sentry feature parity, vendor hosting and support are not included. - SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations - global probe network - phone and SMS delivery - massive retention - advanced incident response and support ## Success criteria - Replaying an event id stores one event. - The two matching exceptions form one issue and the distinct exception forms another. - A burst of 100 repeated occurrences produces one new-issue alert. - 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 · Sentry 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 private error collector with deterministic grouping and one alert channel as a bounded replacement for Sentry. 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. ### Data model (create this before Phase 1) - projects(id,name,ingest_key_hash) - events(id,project_id,event_key,release,message,frames_json,at) - issues(id,project_id,fingerprint,state) - occurrences(event_id,issue_id) - alert_outbox(id,issue_id,state,attempts) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. ### 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. - Sentry acceptance sample: Create synthetic sample data before implementation: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel. 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. - An SMTP relay and one verified test recipient: Obtain SMTP host, port, username and password from your chosen relay dashboard under SMTP settings. Verify the sender/domain using that provider DNS instructions. Use only your own test recipient initially and record the actual plan and rate limit in OPERATIONS.md. Verify: The supplied smtp_probe.py sends one labelled test message to your own inbox and reports the relay response without logging credentials. Cost: Provider-specific relay fees and domain costs; no free tier or delivery guarantee is assumed. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, MAIL_FROM, MAIL_TEST_TO. 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 private error collector with deterministic grouping and one alert channel, 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: projects(id,name,ingest_key_hash); events(id,project_id,event_key,release,message,frames_json,at); issues(id,project_id,fingerprint,state); occurrences(event_id,issue_id); alert_outbox(id,issue_id,state,attempts). 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: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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/mail.py using smtplib with a timeout, verified TLS/STARTTLS and an EmailMessage. Refuse placeholder credentials and non-test recipients until the owner enables sending. Implement scripts/smtp_probe.py to send one labelled message only to MAIL_TEST_TO, and provide a fake adapter for tests. Store no password or full message body in logs. Commands, after creating the named files: `python scripts/smtp_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 bounded ingestion until these checks pass. ### Phase 2 · Bounded ingestion Build: Bounded ingestion for Sentry: Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. - Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. - Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: Replaying an event id stores one event. Then check: The fixture secret is absent from stored event data and request logs. 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: Ingest credentials only permit event submission, never dashboard reads. Done when: Replaying an event id stores one event. The fixture secret is absent from stored event data and request logs. Do not build yet: Do not start grouping and release views until these checks pass. ### Phase 3 · Grouping and release views Build: Grouping and release views for Sentry: Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. - Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. - Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: The two matching exceptions form one issue and the distinct exception forms another. Then check: A new occurrence after resolution reopens the issue once. 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: A deterministic heuristic will over-group or split some errors; make manual inspection possible. Done when: The two matching exceptions form one issue and the distinct exception forms another. A new occurrence after resolution reopens the issue once. Do not build yet: Do not start alerts and retention until these checks pass. ### Phase 4 · Alerts and retention Build: Alerts and retention for Sentry: Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. - Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. - Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: A burst of 100 repeated occurrences produces one new-issue alert. Then check: Deleting expired events leaves current events queryable and updates counts consistently. 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: SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. Done when: A burst of 100 repeated occurrences produces one new-issue alert. Deleting expired events leaves current events queryable and updates counts consistently. 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 Sentry replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Bounded ingestion; Grouping and release views; Alerts and retention. 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 sentry. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel 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 sentry. 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) - This is a private error collector with deterministic grouping and one alert channel; full Sentry feature parity, vendor hosting and support are not included. - SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations: retain the paid product if this capability is essential; it is outside this bounded build. - global probe network: retain the paid product if this capability is essential; it is outside this bounded build. - phone and SMS delivery: retain the paid product if this capability is essential; it is outside this bounded build. - massive retention: retain the paid product if this capability is essential; it is outside this bounded build. - advanced incident response 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.python.org/3/library/smtplib.html. Recheck before upgrading; freeze the versions actually tested. ===== ARCHITECTURE.md ===== # Architecture · Sentry ## 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. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | projects(id,name,ingest_key_hash); events(id,project_id,event_key,release,message,frames_json,at); issues(id,project_id,fingerprint,state); occurrences(event_id,issue_id); alert_outbox(id,issue_id,state,attempts) | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Bounded ingestion | Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. | Keep the acceptance contract: Replaying an event id stores one event. Replace only this module after replaying its fixture; preserve ids and existing records. | | Grouping and release views | Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. | Keep the acceptance contract: The two matching exceptions form one issue and the distinct exception forms another. Replace only this module after replaying its fixture; preserve ids and existing records. | | Alerts and retention | Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. | Keep the acceptance contract: A burst of 100 repeated occurrences produces one new-issue alert. 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 sentry. | 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. - `SMTP_HOST` · required · Copy the SMTP hostname from the relay dashboard. - `SMTP_PORT` · required · Use a relay supporting STARTTLS on this port; confirm it in its setup instructions. - `SMTP_USER` · required, secret · Copy the relay username; it may differ from your sign-in email. - `SMTP_PASSWORD` · required, secret · Create SMTP credentials in the relay dashboard, not your personal mailbox password. - `MAIL_FROM` · required · Your relay-verified sender address; replace before real sends. - `MAIL_TEST_TO` · required · An inbox you control for the explicit preflight test. ## 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 · Sentry 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. - 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. - Ingest credentials only permit event submission, never dashboard reads. - A deterministic heuristic will over-group or split some errors; make manual inspection possible. - SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. - 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 · Sentry 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 private error collector with deterministic grouping and one alert channel, 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: projects(id,name,ingest_key_hash); events(id,project_id,event_key,release,message,frames_json,at); issues(id,project_id,fingerprint,state); occurrences(event_id,issue_id); alert_outbox(id,issue_id,state,attempts). 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: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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. Implement and test the email adapter Create providers/mail.py using smtplib with a timeout, verified TLS/STARTTLS and an EmailMessage. Refuse placeholder credentials and non-test recipients until the owner enables sending. Implement scripts/smtp_probe.py to send one labelled message only to MAIL_TEST_TO, and provide a fake adapter for tests. Store no password or full message body in logs. Files: `providers/mail.py`, `scripts/smtp_probe.py` ```sh python scripts/smtp_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 · Bounded ingestion Bounded ingestion for Sentry: Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. ### Steps 1. Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. Files: `features/bounded_ingestion.py`, `templates/bounded_ingestion.html` 2. Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. Files: `features/bounded_ingestion.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: Replaying an event id stores one event. Then check: The fixture secret is absent from stored event data and request logs. 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_bounded_ingestion.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Replaying an event id stores one event. - [ ] The fixture secret is absent from stored event data and request logs. ### Watch out - Ingest credentials only permit event submission, never dashboard reads. ## M3 · Grouping and release views Grouping and release views for Sentry: Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. ### Steps 1. Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. Files: `features/grouping_and_release_views.py`, `templates/grouping_and_release_views.html` 2. Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. Files: `features/grouping_and_release_views.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: The two matching exceptions form one issue and the distinct exception forms another. Then check: A new occurrence after resolution reopens the issue once. 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_grouping_and_release_views.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] The two matching exceptions form one issue and the distinct exception forms another. - [ ] A new occurrence after resolution reopens the issue once. ### Watch out - A deterministic heuristic will over-group or split some errors; make manual inspection possible. ## M4 · Alerts and retention Alerts and retention for Sentry: Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. ### Steps 1. Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. Files: `features/alerts_and_retention.py`, `templates/alerts_and_retention.html` 2. Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. Files: `features/alerts_and_retention.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: A burst of 100 repeated occurrences produces one new-issue alert. Then check: Deleting expired events leaves current events queryable and updates counts consistently. 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_alerts_and_retention.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A burst of 100 repeated occurrences produces one new-issue alert. - [ ] Deleting expired events leaves current events queryable and updates counts consistently. ### Watch out - SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. ## M5 · Portable delivery and clean-start proof Finish the Sentry 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: Bounded ingestion; Grouping and release views; Alerts and retention. 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 sentry. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel 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 sentry. 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 · Sentry ## 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 sentry. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 Bounded ingestion, Grouping and release views, Alerts and retention. 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 - [ ] Replaying an event id stores one event. - [ ] The two matching exceptions form one issue and the distinct exception forms another. - [ ] A burst of 100 repeated occurrences produces one new-issue alert. - [ ] 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 Sentry 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/sentry # 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. Copy the SMTP hostname from the relay dashboard. SMTP_HOST=replace-with-relay-host # Required. Use a relay supporting STARTTLS on this port; confirm it in its setup instructions. SMTP_PORT=587 # Required · secret. Copy the relay username; it may differ from your sign-in email. SMTP_USER=replace-with-smtp-user # Required · secret. Create SMTP credentials in the relay dashboard, not your personal mailbox password. SMTP_PASSWORD=replace-with-smtp-password # Required. Your relay-verified sender address; replace before real sends. MAIL_FROM=owner@example.com # Required. An inbox you control for the explicit preflight test. MAIL_TEST_TO=owner@example.com
README.md
# Sentry · indie build Build a private error collector with deterministic grouping and one alert channel. 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. | ## 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. - [ ] **Sentry 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: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel. 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. - [ ] **An SMTP relay and one verified test recipient** · Provider-specific relay fees and domain costs; no free tier or delivery guarantee is assumed. - Why: Outbound confirmations or replies need a delivery provider; a fake adapter covers automated tests. - Get it: Obtain SMTP host, port, username and password from your chosen relay dashboard under SMTP settings. Verify the sender/domain using that provider DNS instructions. Use only your own test recipient initially and record the actual plan and rate limit in OPERATIONS.md. - Verify: The supplied smtp_probe.py sends one labelled test message to your own inbox and reports the relay response without logging credentials. ## 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: - This is a private error collector with deterministic grouping and one alert channel; full Sentry feature parity, vendor hosting and support are not included. - SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations - global probe network - phone and SMS delivery - massive retention - advanced incident response and support If one of those is essential to you, that is the reason to keep paying for Sentry, and the README should say so rather than pretend.
BRIEF.md
# Build brief · Sentry 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 private error collector with deterministic grouping and one alert channel as a bounded replacement for Sentry. 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. ### Data model (create this before Phase 1) - projects(id,name,ingest_key_hash) - events(id,project_id,event_key,release,message,frames_json,at) - issues(id,project_id,fingerprint,state) - occurrences(event_id,issue_id) - alert_outbox(id,issue_id,state,attempts) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. ### 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. - Sentry acceptance sample: Create synthetic sample data before implementation: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel. 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. - An SMTP relay and one verified test recipient: Obtain SMTP host, port, username and password from your chosen relay dashboard under SMTP settings. Verify the sender/domain using that provider DNS instructions. Use only your own test recipient initially and record the actual plan and rate limit in OPERATIONS.md. Verify: The supplied smtp_probe.py sends one labelled test message to your own inbox and reports the relay response without logging credentials. Cost: Provider-specific relay fees and domain costs; no free tier or delivery guarantee is assumed. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, MAIL_FROM, MAIL_TEST_TO. 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 private error collector with deterministic grouping and one alert channel, 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: projects(id,name,ingest_key_hash); events(id,project_id,event_key,release,message,frames_json,at); issues(id,project_id,fingerprint,state); occurrences(event_id,issue_id); alert_outbox(id,issue_id,state,attempts). 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: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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/mail.py using smtplib with a timeout, verified TLS/STARTTLS and an EmailMessage. Refuse placeholder credentials and non-test recipients until the owner enables sending. Implement scripts/smtp_probe.py to send one labelled message only to MAIL_TEST_TO, and provide a fake adapter for tests. Store no password or full message body in logs. Commands, after creating the named files: `python scripts/smtp_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 bounded ingestion until these checks pass. ### Phase 2 · Bounded ingestion Build: Bounded ingestion for Sentry: Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. - Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. - Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: Replaying an event id stores one event. Then check: The fixture secret is absent from stored event data and request logs. 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: Ingest credentials only permit event submission, never dashboard reads. Done when: Replaying an event id stores one event. The fixture secret is absent from stored event data and request logs. Do not build yet: Do not start grouping and release views until these checks pass. ### Phase 3 · Grouping and release views Build: Grouping and release views for Sentry: Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. - Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. - Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: The two matching exceptions form one issue and the distinct exception forms another. Then check: A new occurrence after resolution reopens the issue once. 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: A deterministic heuristic will over-group or split some errors; make manual inspection possible. Done when: The two matching exceptions form one issue and the distinct exception forms another. A new occurrence after resolution reopens the issue once. Do not build yet: Do not start alerts and retention until these checks pass. ### Phase 4 · Alerts and retention Build: Alerts and retention for Sentry: Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. - Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. - Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: A burst of 100 repeated occurrences produces one new-issue alert. Then check: Deleting expired events leaves current events queryable and updates counts consistently. 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: SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. Done when: A burst of 100 repeated occurrences produces one new-issue alert. Deleting expired events leaves current events queryable and updates counts consistently. 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 Sentry replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Bounded ingestion; Grouping and release views; Alerts and retention. 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 sentry. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel 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 sentry. 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) - This is a private error collector with deterministic grouping and one alert channel; full Sentry feature parity, vendor hosting and support are not included. - SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations: retain the paid product if this capability is essential; it is outside this bounded build. - global probe network: retain the paid product if this capability is essential; it is outside this bounded build. - phone and SMS delivery: retain the paid product if this capability is essential; it is outside this bounded build. - massive retention: retain the paid product if this capability is essential; it is outside this bounded build. - advanced incident response 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.python.org/3/library/smtplib.html. Recheck before upgrading; freeze the versions actually tested.
AGENTS.md
# Agent instructions · Sentry 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. 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. - Ingest credentials only permit event submission, never dashboard reads. - A deterministic heuristic will over-group or split some errors; make manual inspection possible. - SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. - Export without an import or restore rehearsal is not verified portability.
BUILD_PLAN.md
# Build plan · Sentry Build a private error collector with deterministic grouping and one alert channel. 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 private error collector with deterministic grouping and one alert channel, 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: projects(id,name,ingest_key_hash); events(id,project_id,event_key,release,message,frames_json,at); issues(id,project_id,fingerprint,state); occurrences(event_id,issue_id); alert_outbox(id,issue_id,state,attempts). 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: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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. Implement and test the email adapter Create providers/mail.py using smtplib with a timeout, verified TLS/STARTTLS and an EmailMessage. Refuse placeholder credentials and non-test recipients until the owner enables sending. Implement scripts/smtp_probe.py to send one labelled message only to MAIL_TEST_TO, and provide a fake adapter for tests. Store no password or full message body in logs. Files: `providers/mail.py`, `scripts/smtp_probe.py` ```sh python scripts/smtp_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 · Bounded ingestion Bounded ingestion for Sentry: Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. ### Steps 1. Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. Files: `features/bounded_ingestion.py`, `templates/bounded_ingestion.html` 2. Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. Files: `features/bounded_ingestion.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: Replaying an event id stores one event. Then check: The fixture secret is absent from stored event data and request logs. 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_bounded_ingestion.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Replaying an event id stores one event. - [ ] The fixture secret is absent from stored event data and request logs. ### Watch out - Ingest credentials only permit event submission, never dashboard reads. ## Phase 3 · Grouping and release views Grouping and release views for Sentry: Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. ### Steps 1. Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. Files: `features/grouping_and_release_views.py`, `templates/grouping_and_release_views.html` 2. Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. Files: `features/grouping_and_release_views.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: The two matching exceptions form one issue and the distinct exception forms another. Then check: A new occurrence after resolution reopens the issue once. 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_grouping_and_release_views.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] The two matching exceptions form one issue and the distinct exception forms another. - [ ] A new occurrence after resolution reopens the issue once. ### Watch out - A deterministic heuristic will over-group or split some errors; make manual inspection possible. ## Phase 4 · Alerts and retention Alerts and retention for Sentry: Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. ### Steps 1. Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. Files: `features/alerts_and_retention.py`, `templates/alerts_and_retention.html` 2. Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. Files: `features/alerts_and_retention.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: A burst of 100 repeated occurrences produces one new-issue alert. Then check: Deleting expired events leaves current events queryable and updates counts consistently. 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_alerts_and_retention.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A burst of 100 repeated occurrences produces one new-issue alert. - [ ] Deleting expired events leaves current events queryable and updates counts consistently. ### Watch out - SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. ## Phase 5 · Portable delivery and clean-start proof Finish the Sentry 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: Bounded ingestion; Grouping and release views; Alerts and retention. 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 sentry. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 - This is a private error collector with deterministic grouping and one alert channel; full Sentry feature parity, vendor hosting and support are not included. - SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations - global probe network - phone and SMS delivery - massive retention - advanced incident response and support ## After v1, if you want it - Extend alerts and retention 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/sentry # 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. Copy the SMTP hostname from the relay dashboard. SMTP_HOST=replace-with-relay-host # Required. Use a relay supporting STARTTLS on this port; confirm it in its setup instructions. SMTP_PORT=587 # Required · secret. Copy the relay username; it may differ from your sign-in email. SMTP_USER=replace-with-smtp-user # Required · secret. Create SMTP credentials in the relay dashboard, not your personal mailbox password. SMTP_PASSWORD=replace-with-smtp-password # Required. Your relay-verified sender address; replace before real sends. MAIL_FROM=owner@example.com # Required. An inbox you control for the explicit preflight test. MAIL_TEST_TO=owner@example.com
PRODUCT.md
# Sentry · product brief ## Problem The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Sentry, receive bounded error events, group them, link releases, and notify one team. The hard boundary is sdk ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations, plus independent infrastructure and reliable alerting. ## Product outcome An operated version of a private error collector with deterministic grouping and one alert channel, 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 - server outside the monitored failure domain - PostgreSQL - optional ClickHouse - email or webhook destination - public HTTPS ## Explicit non-goals for v1 - This is a private error collector with deterministic grouping and one alert channel; full Sentry feature parity, vendor hosting and support are not included. - SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations - global probe network - phone and SMS delivery - massive retention - advanced incident response and support ## Success criteria - Replaying an event id stores one event. - The two matching exceptions form one issue and the distinct exception forms another. - A burst of 100 repeated occurrences produces one new-issue alert. - 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 · Sentry 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 private error collector with deterministic grouping and one alert channel as a bounded replacement for Sentry. 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. ### Data model (create this before Phase 1) - projects(id,name,ingest_key_hash) - events(id,project_id,event_key,release,message,frames_json,at) - issues(id,project_id,fingerprint,state) - occurrences(event_id,issue_id) - alert_outbox(id,issue_id,state,attempts) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. ### 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. - Sentry acceptance sample: Create synthetic sample data before implementation: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel. 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. - An SMTP relay and one verified test recipient: Obtain SMTP host, port, username and password from your chosen relay dashboard under SMTP settings. Verify the sender/domain using that provider DNS instructions. Use only your own test recipient initially and record the actual plan and rate limit in OPERATIONS.md. Verify: The supplied smtp_probe.py sends one labelled test message to your own inbox and reports the relay response without logging credentials. Cost: Provider-specific relay fees and domain costs; no free tier or delivery guarantee is assumed. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL, SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, MAIL_FROM, MAIL_TEST_TO. 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 private error collector with deterministic grouping and one alert channel, 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: projects(id,name,ingest_key_hash); events(id,project_id,event_key,release,message,frames_json,at); issues(id,project_id,fingerprint,state); occurrences(event_id,issue_id); alert_outbox(id,issue_id,state,attempts). 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: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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/mail.py using smtplib with a timeout, verified TLS/STARTTLS and an EmailMessage. Refuse placeholder credentials and non-test recipients until the owner enables sending. Implement scripts/smtp_probe.py to send one labelled message only to MAIL_TEST_TO, and provide a fake adapter for tests. Store no password or full message body in logs. Commands, after creating the named files: `python scripts/smtp_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 bounded ingestion until these checks pass. ### Phase 2 · Bounded ingestion Build: Bounded ingestion for Sentry: Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. - Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. - Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: Replaying an event id stores one event. Then check: The fixture secret is absent from stored event data and request logs. 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: Ingest credentials only permit event submission, never dashboard reads. Done when: Replaying an event id stores one event. The fixture secret is absent from stored event data and request logs. Do not build yet: Do not start grouping and release views until these checks pass. ### Phase 3 · Grouping and release views Build: Grouping and release views for Sentry: Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. - Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. - Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: The two matching exceptions form one issue and the distinct exception forms another. Then check: A new occurrence after resolution reopens the issue once. 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: A deterministic heuristic will over-group or split some errors; make manual inspection possible. Done when: The two matching exceptions form one issue and the distinct exception forms another. A new occurrence after resolution reopens the issue once. Do not build yet: Do not start alerts and retention until these checks pass. ### Phase 4 · Alerts and retention Build: Alerts and retention for Sentry: Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. - Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. - Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. - Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: A burst of 100 repeated occurrences produces one new-issue alert. Then check: Deleting expired events leaves current events queryable and updates counts consistently. 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: SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. Done when: A burst of 100 repeated occurrences produces one new-issue alert. Deleting expired events leaves current events queryable and updates counts consistently. 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 Sentry replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Bounded ingestion; Grouping and release views; Alerts and retention. 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 sentry. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel 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 sentry. 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) - This is a private error collector with deterministic grouping and one alert channel; full Sentry feature parity, vendor hosting and support are not included. - SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations: retain the paid product if this capability is essential; it is outside this bounded build. - global probe network: retain the paid product if this capability is essential; it is outside this bounded build. - phone and SMS delivery: retain the paid product if this capability is essential; it is outside this bounded build. - massive retention: retain the paid product if this capability is essential; it is outside this bounded build. - advanced incident response 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.python.org/3/library/smtplib.html. Recheck before upgrading; freeze the versions actually tested.
ARCHITECTURE.md
# Architecture · Sentry ## 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. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | projects(id,name,ingest_key_hash); events(id,project_id,event_key,release,message,frames_json,at); issues(id,project_id,fingerprint,state); occurrences(event_id,issue_id); alert_outbox(id,issue_id,state,attempts) | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Bounded ingestion | Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. | Keep the acceptance contract: Replaying an event id stores one event. Replace only this module after replaying its fixture; preserve ids and existing records. | | Grouping and release views | Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. | Keep the acceptance contract: The two matching exceptions form one issue and the distinct exception forms another. Replace only this module after replaying its fixture; preserve ids and existing records. | | Alerts and retention | Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. | Keep the acceptance contract: A burst of 100 repeated occurrences produces one new-issue alert. 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 sentry. | 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. - `SMTP_HOST` · required · Copy the SMTP hostname from the relay dashboard. - `SMTP_PORT` · required · Use a relay supporting STARTTLS on this port; confirm it in its setup instructions. - `SMTP_USER` · required, secret · Copy the relay username; it may differ from your sign-in email. - `SMTP_PASSWORD` · required, secret · Create SMTP credentials in the relay dashboard, not your personal mailbox password. - `MAIL_FROM` · required · Your relay-verified sender address; replace before real sends. - `MAIL_TEST_TO` · required · An inbox you control for the explicit preflight test. ## 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 · Sentry 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. - 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. - Ingest credentials only permit event submission, never dashboard reads. - A deterministic heuristic will over-group or split some errors; make manual inspection possible. - SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. - 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 · Sentry 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 private error collector with deterministic grouping and one alert channel, 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: projects(id,name,ingest_key_hash); events(id,project_id,event_key,release,message,frames_json,at); issues(id,project_id,fingerprint,state); occurrences(event_id,issue_id); alert_outbox(id,issue_id,state,attempts). 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: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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. Implement and test the email adapter Create providers/mail.py using smtplib with a timeout, verified TLS/STARTTLS and an EmailMessage. Refuse placeholder credentials and non-test recipients until the owner enables sending. Implement scripts/smtp_probe.py to send one labelled message only to MAIL_TEST_TO, and provide a fake adapter for tests. Store no password or full message body in logs. Files: `providers/mail.py`, `scripts/smtp_probe.py` ```sh python scripts/smtp_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 · Bounded ingestion Bounded ingestion for Sentry: Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. ### Steps 1. Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. Accept a small JSON event schema using a project-scoped ingest token and per-token limits; cap payload and frame counts. Files: `features/bounded_ingestion.py`, `templates/bounded_ingestion.html` 2. Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. Redact configured sensitive fields before persistence and reject duplicate event ids using a unique constraint. Files: `features/bounded_ingestion.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: Replaying an event id stores one event. Then check: The fixture secret is absent from stored event data and request logs. 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_bounded_ingestion.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Replaying an event id stores one event. - [ ] The fixture secret is absent from stored event data and request logs. ### Watch out - Ingest credentials only permit event submission, never dashboard reads. ## M3 · Grouping and release views Grouping and release views for Sentry: Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. ### Steps 1. Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. Fingerprint normalized exception type plus top application frames; exclude timestamps and line numbers from the chosen rule. Files: `features/grouping_and_release_views.py`, `templates/grouping_and_release_views.html` 2. Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. Show issue counts, first/last seen and releases and allow resolve/reopen; retain the grouping rule version. Files: `features/grouping_and_release_views.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: The two matching exceptions form one issue and the distinct exception forms another. Then check: A new occurrence after resolution reopens the issue once. 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_grouping_and_release_views.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] The two matching exceptions form one issue and the distinct exception forms another. - [ ] A new occurrence after resolution reopens the issue once. ### Watch out - A deterministic heuristic will over-group or split some errors; make manual inspection possible. ## M4 · Alerts and retention Alerts and retention for Sentry: Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. ### Steps 1. Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. Create one email alert outbox item for a new or reopened issue and throttle repeated occurrences. Files: `features/alerts_and_retention.py`, `templates/alerts_and_retention.html` 2. Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. Add retention deletion for old events and keep explicit issue summaries; expose failed/unknown delivery for owner review. Files: `features/alerts_and_retention.py` 3. Exercise the acceptance fixture Use Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. Check: A burst of 100 repeated occurrences produces one new-issue alert. Then check: Deleting expired events leaves current events queryable and updates counts consistently. 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_alerts_and_retention.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A burst of 100 repeated occurrences produces one new-issue alert. - [ ] Deleting expired events leaves current events queryable and updates counts consistently. ### Watch out - SMTP acknowledgement is not proof of inbox delivery; do not promise exactly-once notifications. ## M5 · Portable delivery and clean-start proof Finish the Sentry 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: Bounded ingestion; Grouping and release views; Alerts and retention. 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 sentry. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 private error collector with deterministic grouping and one alert channel 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 sentry. 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 · Sentry ## 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 sentry. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two exceptions with matching application frames, a distinct exception, a repeated event id and a secret in context. 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 Bounded ingestion, Grouping and release views, Alerts and retention. 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 - [ ] Replaying an event id stores one event. - [ ] The two matching exceptions form one issue and the distinct exception forms another. - [ ] A burst of 100 repeated occurrences produces one new-issue alert. - [ ] 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 Sentry 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/sentry # 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. Copy the SMTP hostname from the relay dashboard. SMTP_HOST=replace-with-relay-host # Required. Use a relay supporting STARTTLS on this port; confirm it in its setup instructions. SMTP_PORT=587 # Required · secret. Copy the relay username; it may differ from your sign-in email. SMTP_USER=replace-with-smtp-user # Required · secret. Create SMTP credentials in the relay dashboard, not your personal mailbox password. SMTP_PASSWORD=replace-with-smtp-password # Required. Your relay-verified sender address; replace before real sends. MAIL_FROM=owner@example.com # Required. An inbox you control for the explicit preflight test. MAIL_TEST_TO=owner@example.com
$ choose a build depth, inspect the files, then open the complete pack in your agent
People still pay for Sentry because monitoring must continue working during the exact outage it reports, which makes independent infrastructure and alert delivery the real product. The recurring cost buys probe geography, clocks, retries, deduplication, sampling, storage, paging, notification delivery, on-call rules, and its own uptime, not just the visible interface.
xSDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations
xglobal probe network
xphone and SMS delivery
xmassive retention
xadvanced incident response and support
share on X ↗"I just replaced Sentry with one prompt"
Don't feel like building it? These folks already made it free.
ExceptionlessA mature error tracker with a strong .NET accent and a real server to maintain.open source↗
GlitchTipSentry's SDK protocol with fewer moving parts and fewer debugging toys.open source↗
BugsinkFifteen thousand hosted errors a month for one user; free self-hosting exists, but it is not open source.free↗all 3 free alternatives to Sentry →· no votes, no pay-to-list · just what's real
Sentry pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| developer | $0/workspace | $0/workspace | 1 user; unlimited projects; 5,000 errors; 5 GB logs; 5 GB app metrics; 5 million spans; 50 replays; 30-day retention |
| team | — | $26/workspace | Unlimited users/projects; 50,000 errors; 5 GB logs; 5 GB app metrics; 5 million spans; 50 replays; up to 90-day retention |
| business | — | $80/workspace | Unlimited users/projects; Team base event allowances; 1,000 metric monitors; unlimited dashboards; business controls |
| enterprise | custom | — | Custom event volumes, support, retention, security and contract terms |
free tier1 user; unlimited projects; 5,000 errors, 5 GB logs, 5 GB app metrics, 5 million spans and 50 replays/month; 1 uptime monitor, 1 cron monitor, 20 metric monitors, 1 GB attachments and 100 builds
billingmonthly + annual; published annual equivalents for Team and Business
hidden costsErrors, spans, replays and other event categories can overage separately; logs/app metrics are $0.50/GB, uptime alerts $1 each, cron monitors $0.78 each, profiling is metered, and Seer AI is a separate usage charge
verified 2026-08-14 · source ↗
Vibecode Sentry
Kinda. The core of Sentry is buildable in a weekend with the prompt on this page, but there are real gaps: SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations, global probe network. Read the honest list above before committing.
How much does Sentry cost?
Sentry's pricing is usage-based or varies by plan · Official Team monthly base price before event usage..
What do I lose by replacing Sentry?
Honestly: SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations; global probe network; phone and SMS delivery; massive retention; advanced incident response and support. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Sentry?
Yes: Exceptionless (A mature error tracker with a strong .NET accent and a real server to maintain.) GlitchTip (Sentry's SDK protocol with fewer moving parts and fewer debugging toys.) Bugsink (Fifteen thousand hosted errors a month for one user; free self-hosting exists, but it is not open source.) All 3 curated free alternatives are at vibecodeit.com/sentry/alternatives. The prompt is for when you want it exactly your way.