Vibecode ShowTrust
track this build5 phases, 15 steps, beginner friendly0%YES · one-shottable
A submission form, an approval queue, and a grid of cards you can embed elsewhere. There is no algorithm here and no network effect · an agent will produce a working version in one sitting, same as it will for the $25 and $29 tools in this category. The catch is the same one Eloqra has: the hosted version is free for a single site, with no cap on testimonials, so you'd be spending a weekend and a hosting bill to replace zero dollars. Worth building if you want the data on your own box or you enjoy the exercise. Not worth building to save money, because there isn't any to save.
the project pack5 files · written for this build, step by step
You are building a lean indie version of ShowTrust. 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 ===== # ShowTrust · indie build Build a consent-based testimonial collector with approval and an embeddable wall. 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. | | Focused libraries | Pillow | Use these only for the specific file, parsing or provider operations named in the phases; freeze tested versions. | ## 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. - [ ] **ShowTrust 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: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall. 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. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata Pillow 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 consent-based testimonial collector with approval and an embeddable wall; full ShowTrust feature parity, vendor hosting and support are not included. - a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price - the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy - the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand - did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on - X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar If one of those is essential to you, that is the reason to keep paying for ShowTrust, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · ShowTrust 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 consent-based testimonial collector with approval and an embeddable wall as a bounded replacement for ShowTrust. 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. - Focused libraries: Pillow. Use these only for the specific file, parsing or provider operations named in the phases; freeze tested versions. ### Data model (create this before Phase 1) - testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at) - moderation(id,testimonial_id,action,at) - wall_settings(id,accent,columns) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: One approved quote, one pending quote containing HTML and one withdrawn submission. ### 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. - ShowTrust acceptance sample: Create synthetic sample data before implementation: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall. 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. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. 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 consent-based testimonial collector with approval and an embeddable wall, 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 Pillow`; `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: testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at); moderation(id,testimonial_id,action,at); wall_settings(id,accent,columns). 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: One approved quote, one pending quote containing HTML and one withdrawn submission. 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. - 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 consent and intake until these checks pass. ### Phase 2 · Consent and intake Build: Consent and intake for ShowTrust: Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. - Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. - Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: A rating of 6 is rejected and creates no row. Then check: The HTML quote appears as text in the private review page. 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: Do not treat submitting a form as implicit consent to publish a name or photo. Done when: A rating of 6 is rejected and creates no row. The HTML quote appears as text in the private review page. Do not build yet: Do not start moderation and withdrawal until these checks pass. ### Phase 3 · Moderation and withdrawal Build: Moderation and withdrawal for ShowTrust: Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. - Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. - Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Only the approved fixture is returned by the public endpoint. Then check: Withdrawing it removes it from the endpoint and next widget load. 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: Never let an incoming request set its own approved status. Done when: Only the approved fixture is returned by the public endpoint. Withdrawing it removes it from the endpoint and next widget load. Do not build yet: Do not start embed and export until these checks pass. ### Phase 4 · Embed and export Build: Embed and export for ShowTrust: Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. - Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. - Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. Then check: A pending quote never appears in the embedded HTML source. 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: This supplies collection and display, not independent identity verification or authenticity certification. Done when: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. A pending quote never appears in the embedded HTML source. 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 ShowTrust replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Consent and intake; Moderation and withdrawal; Embed and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for showtrust. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall 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 showtrust. 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 consent-based testimonial collector with approval and an embeddable wall; full ShowTrust feature parity, vendor hosting and support are not included. - a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price: retain the paid product if this capability is essential; it is outside this bounded build. - the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy: retain the paid product if this capability is essential; it is outside this bounded build. - the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand: retain the paid product if this capability is essential; it is outside this bounded build. - did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on: retain the paid product if this capability is essential; it is outside this bounded build. - X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar: 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. Recheck before upgrading; freeze the versions actually tested. ===== AGENTS.md ===== # Agent instructions · ShowTrust 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, Pillow. 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. - Do not treat submitting a form as implicit consent to publish a name or photo. - Never let an incoming request set its own approved status. - This supplies collection and display, not independent identity verification or authenticity certification. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · ShowTrust Build a consent-based testimonial collector with approval and an embeddable wall. 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 consent-based testimonial collector with approval and an embeddable wall, 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 Pillow 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: testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at); moderation(id,testimonial_id,action,at); wall_settings(id,accent,columns). 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: One approved quote, one pending quote containing HTML and one withdrawn submission. 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` ### 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 · Consent and intake Consent and intake for ShowTrust: Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. ### Steps 1. Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. Files: `features/consent_and_intake.py`, `templates/consent_and_intake.html` 2. Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. Files: `features/consent_and_intake.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: A rating of 6 is rejected and creates no row. Then check: The HTML quote appears as text in the private review page. 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_consent_and_intake.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A rating of 6 is rejected and creates no row. - [ ] The HTML quote appears as text in the private review page. ### Watch out - Do not treat submitting a form as implicit consent to publish a name or photo. ## Phase 3 · Moderation and withdrawal Moderation and withdrawal for ShowTrust: Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. ### Steps 1. Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. Files: `features/moderation_and_withdrawal.py`, `templates/moderation_and_withdrawal.html` 2. Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. Files: `features/moderation_and_withdrawal.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Only the approved fixture is returned by the public endpoint. Then check: Withdrawing it removes it from the endpoint and next widget load. 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_moderation_and_withdrawal.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Only the approved fixture is returned by the public endpoint. - [ ] Withdrawing it removes it from the endpoint and next widget load. ### Watch out - Never let an incoming request set its own approved status. ## Phase 4 · Embed and export Embed and export for ShowTrust: Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. ### Steps 1. Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. Files: `features/embed_and_export.py`, `templates/embed_and_export.html` 2. Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. Files: `features/embed_and_export.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. Then check: A pending quote never appears in the embedded HTML source. 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_embed_and_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Embedding on a separate local test origin displays the approved cards at 375px and 1280px. - [ ] A pending quote never appears in the embedded HTML source. ### Watch out - This supplies collection and display, not independent identity verification or authenticity certification. ## Phase 5 · Portable delivery and clean-start proof Finish the ShowTrust 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: Consent and intake; Moderation and withdrawal; Embed and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for showtrust. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall; full ShowTrust feature parity, vendor hosting and support are not included. - a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price - the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy - the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand - did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on - X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar ## After v1, if you want it - Extend embed and export only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/showtrust # 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
You are building a lean indie version of ShowTrust. 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 ===== # ShowTrust · indie build Build a consent-based testimonial collector with approval and an embeddable wall. 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. | | Focused libraries | Pillow | Use these only for the specific file, parsing or provider operations named in the phases; freeze tested versions. | ## 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. - [ ] **ShowTrust 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: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall. 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. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata Pillow 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 consent-based testimonial collector with approval and an embeddable wall; full ShowTrust feature parity, vendor hosting and support are not included. - a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price - the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy - the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand - did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on - X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar If one of those is essential to you, that is the reason to keep paying for ShowTrust, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · ShowTrust 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 consent-based testimonial collector with approval and an embeddable wall as a bounded replacement for ShowTrust. 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. - Focused libraries: Pillow. Use these only for the specific file, parsing or provider operations named in the phases; freeze tested versions. ### Data model (create this before Phase 1) - testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at) - moderation(id,testimonial_id,action,at) - wall_settings(id,accent,columns) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: One approved quote, one pending quote containing HTML and one withdrawn submission. ### 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. - ShowTrust acceptance sample: Create synthetic sample data before implementation: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall. 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. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. 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 consent-based testimonial collector with approval and an embeddable wall, 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 Pillow`; `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: testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at); moderation(id,testimonial_id,action,at); wall_settings(id,accent,columns). 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: One approved quote, one pending quote containing HTML and one withdrawn submission. 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. - 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 consent and intake until these checks pass. ### Phase 2 · Consent and intake Build: Consent and intake for ShowTrust: Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. - Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. - Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: A rating of 6 is rejected and creates no row. Then check: The HTML quote appears as text in the private review page. 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: Do not treat submitting a form as implicit consent to publish a name or photo. Done when: A rating of 6 is rejected and creates no row. The HTML quote appears as text in the private review page. Do not build yet: Do not start moderation and withdrawal until these checks pass. ### Phase 3 · Moderation and withdrawal Build: Moderation and withdrawal for ShowTrust: Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. - Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. - Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Only the approved fixture is returned by the public endpoint. Then check: Withdrawing it removes it from the endpoint and next widget load. 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: Never let an incoming request set its own approved status. Done when: Only the approved fixture is returned by the public endpoint. Withdrawing it removes it from the endpoint and next widget load. Do not build yet: Do not start embed and export until these checks pass. ### Phase 4 · Embed and export Build: Embed and export for ShowTrust: Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. - Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. - Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. Then check: A pending quote never appears in the embedded HTML source. 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: This supplies collection and display, not independent identity verification or authenticity certification. Done when: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. A pending quote never appears in the embedded HTML source. 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 ShowTrust replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Consent and intake; Moderation and withdrawal; Embed and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for showtrust. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall 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 showtrust. 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 consent-based testimonial collector with approval and an embeddable wall; full ShowTrust feature parity, vendor hosting and support are not included. - a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price: retain the paid product if this capability is essential; it is outside this bounded build. - the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy: retain the paid product if this capability is essential; it is outside this bounded build. - the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand: retain the paid product if this capability is essential; it is outside this bounded build. - did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on: retain the paid product if this capability is essential; it is outside this bounded build. - X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar: 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. Recheck before upgrading; freeze the versions actually tested. ===== AGENTS.md ===== # Agent instructions · ShowTrust 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, Pillow. 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. - Do not treat submitting a form as implicit consent to publish a name or photo. - Never let an incoming request set its own approved status. - This supplies collection and display, not independent identity verification or authenticity certification. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · ShowTrust Build a consent-based testimonial collector with approval and an embeddable wall. 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 consent-based testimonial collector with approval and an embeddable wall, 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 Pillow 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: testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at); moderation(id,testimonial_id,action,at); wall_settings(id,accent,columns). 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: One approved quote, one pending quote containing HTML and one withdrawn submission. 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` ### 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 · Consent and intake Consent and intake for ShowTrust: Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. ### Steps 1. Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. Files: `features/consent_and_intake.py`, `templates/consent_and_intake.html` 2. Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. Files: `features/consent_and_intake.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: A rating of 6 is rejected and creates no row. Then check: The HTML quote appears as text in the private review page. 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_consent_and_intake.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A rating of 6 is rejected and creates no row. - [ ] The HTML quote appears as text in the private review page. ### Watch out - Do not treat submitting a form as implicit consent to publish a name or photo. ## Phase 3 · Moderation and withdrawal Moderation and withdrawal for ShowTrust: Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. ### Steps 1. Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. Files: `features/moderation_and_withdrawal.py`, `templates/moderation_and_withdrawal.html` 2. Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. Files: `features/moderation_and_withdrawal.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Only the approved fixture is returned by the public endpoint. Then check: Withdrawing it removes it from the endpoint and next widget load. 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_moderation_and_withdrawal.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Only the approved fixture is returned by the public endpoint. - [ ] Withdrawing it removes it from the endpoint and next widget load. ### Watch out - Never let an incoming request set its own approved status. ## Phase 4 · Embed and export Embed and export for ShowTrust: Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. ### Steps 1. Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. Files: `features/embed_and_export.py`, `templates/embed_and_export.html` 2. Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. Files: `features/embed_and_export.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. Then check: A pending quote never appears in the embedded HTML source. 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_embed_and_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Embedding on a separate local test origin displays the approved cards at 375px and 1280px. - [ ] A pending quote never appears in the embedded HTML source. ### Watch out - This supplies collection and display, not independent identity verification or authenticity certification. ## Phase 5 · Portable delivery and clean-start proof Finish the ShowTrust 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: Consent and intake; Moderation and withdrawal; Embed and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for showtrust. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall; full ShowTrust feature parity, vendor hosting and support are not included. - a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price - the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy - the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand - did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on - X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar ## After v1, if you want it - Extend embed and export only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/showtrust # 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
You are building a production product version of ShowTrust. 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 ===== # ShowTrust · product brief ## Problem A submission form, an approval queue, and a grid of cards you can embed elsewhere. There is no algorithm here and no network effect · an agent will produce a working version in one sitting, same as it will for the $25 and $29 tools in this category. The catch is the same one Eloqra has: the hosted version is free for a single site, with no cap on testimonials, so you'd be spending a weekend and a hosting bill to replace zero dollars. Worth building if you want the data on your own box or you enjoy the exercise. Not worth building to save money, because there isn't any to save. ## Product outcome An operated version of a consent-based testimonial collector with approval and an embeddable wall, 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 - a small always-on host - somewhere to put uploaded avatars (local disk is fine) ## Explicit non-goals for v1 - This is a consent-based testimonial collector with approval and an embeddable wall; full ShowTrust feature parity, vendor hosting and support are not included. - a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price - the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy - the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand - did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on - X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar ## Success criteria - A rating of 6 is rejected and creates no row. - Only the approved fixture is returned by the public endpoint. - Embedding on a separate local test origin displays the approved cards at 375px and 1280px. - 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 · ShowTrust 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 consent-based testimonial collector with approval and an embeddable wall as a bounded replacement for ShowTrust. 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. - Focused libraries: Pillow. Use these only for the specific file, parsing or provider operations named in the phases; freeze tested versions. ### Data model (create this before Phase 1) - testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at) - moderation(id,testimonial_id,action,at) - wall_settings(id,accent,columns) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: One approved quote, one pending quote containing HTML and one withdrawn submission. ### 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. - ShowTrust acceptance sample: Create synthetic sample data before implementation: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall. 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. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. 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 consent-based testimonial collector with approval and an embeddable wall, 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 Pillow`; `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: testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at); moderation(id,testimonial_id,action,at); wall_settings(id,accent,columns). 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: One approved quote, one pending quote containing HTML and one withdrawn submission. 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. - 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 consent and intake until these checks pass. ### Phase 2 · Consent and intake Build: Consent and intake for ShowTrust: Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. - Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. - Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: A rating of 6 is rejected and creates no row. Then check: The HTML quote appears as text in the private review page. 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: Do not treat submitting a form as implicit consent to publish a name or photo. Done when: A rating of 6 is rejected and creates no row. The HTML quote appears as text in the private review page. Do not build yet: Do not start moderation and withdrawal until these checks pass. ### Phase 3 · Moderation and withdrawal Build: Moderation and withdrawal for ShowTrust: Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. - Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. - Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Only the approved fixture is returned by the public endpoint. Then check: Withdrawing it removes it from the endpoint and next widget load. 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: Never let an incoming request set its own approved status. Done when: Only the approved fixture is returned by the public endpoint. Withdrawing it removes it from the endpoint and next widget load. Do not build yet: Do not start embed and export until these checks pass. ### Phase 4 · Embed and export Build: Embed and export for ShowTrust: Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. - Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. - Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. Then check: A pending quote never appears in the embedded HTML source. 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: This supplies collection and display, not independent identity verification or authenticity certification. Done when: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. A pending quote never appears in the embedded HTML source. 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 ShowTrust replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Consent and intake; Moderation and withdrawal; Embed and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for showtrust. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall 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 showtrust. 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 consent-based testimonial collector with approval and an embeddable wall; full ShowTrust feature parity, vendor hosting and support are not included. - a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price: retain the paid product if this capability is essential; it is outside this bounded build. - the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy: retain the paid product if this capability is essential; it is outside this bounded build. - the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand: retain the paid product if this capability is essential; it is outside this bounded build. - did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on: retain the paid product if this capability is essential; it is outside this bounded build. - X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar: 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. Recheck before upgrading; freeze the versions actually tested. ===== ARCHITECTURE.md ===== # Architecture · ShowTrust ## 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. | | Focused libraries | Pillow | Use these only for the specific file, parsing or provider operations named in the phases; freeze tested versions. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at); moderation(id,testimonial_id,action,at); wall_settings(id,accent,columns) | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Consent and intake | Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. | Keep the acceptance contract: A rating of 6 is rejected and creates no row. Replace only this module after replaying its fixture; preserve ids and existing records. | | Moderation and withdrawal | Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. | Keep the acceptance contract: Only the approved fixture is returned by the public endpoint. Replace only this module after replaying its fixture; preserve ids and existing records. | | Embed and export | Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. | Keep the acceptance contract: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. 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 showtrust. | 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. ## 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 · ShowTrust 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, Pillow. - 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. - Do not treat submitting a form as implicit consent to publish a name or photo. - Never let an incoming request set its own approved status. - This supplies collection and display, not independent identity verification or authenticity certification. - 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 · ShowTrust 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 consent-based testimonial collector with approval and an embeddable wall, 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 Pillow 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: testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at); moderation(id,testimonial_id,action,at); wall_settings(id,accent,columns). 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: One approved quote, one pending quote containing HTML and one withdrawn submission. 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` ### 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 · Consent and intake Consent and intake for ShowTrust: Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. ### Steps 1. Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. Files: `features/consent_and_intake.py`, `templates/consent_and_intake.html` 2. Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. Files: `features/consent_and_intake.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: A rating of 6 is rejected and creates no row. Then check: The HTML quote appears as text in the private review page. 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_consent_and_intake.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A rating of 6 is rejected and creates no row. - [ ] The HTML quote appears as text in the private review page. ### Watch out - Do not treat submitting a form as implicit consent to publish a name or photo. ## M3 · Moderation and withdrawal Moderation and withdrawal for ShowTrust: Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. ### Steps 1. Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. Files: `features/moderation_and_withdrawal.py`, `templates/moderation_and_withdrawal.html` 2. Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. Files: `features/moderation_and_withdrawal.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Only the approved fixture is returned by the public endpoint. Then check: Withdrawing it removes it from the endpoint and next widget load. 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_moderation_and_withdrawal.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Only the approved fixture is returned by the public endpoint. - [ ] Withdrawing it removes it from the endpoint and next widget load. ### Watch out - Never let an incoming request set its own approved status. ## M4 · Embed and export Embed and export for ShowTrust: Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. ### Steps 1. Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. Files: `features/embed_and_export.py`, `templates/embed_and_export.html` 2. Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. Files: `features/embed_and_export.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. Then check: A pending quote never appears in the embedded HTML source. 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_embed_and_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Embedding on a separate local test origin displays the approved cards at 375px and 1280px. - [ ] A pending quote never appears in the embedded HTML source. ### Watch out - This supplies collection and display, not independent identity verification or authenticity certification. ## M5 · Portable delivery and clean-start proof Finish the ShowTrust 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: Consent and intake; Moderation and withdrawal; Embed and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for showtrust. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall 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 showtrust. 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 · ShowTrust ## 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 showtrust. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 Consent and intake, Moderation and withdrawal, Embed and export. Alert without logging private payloads. ## Incident checklist Pause outbound jobs and public intake as appropriate, preserve redacted diagnostics, restore an isolated verified backup, rotate affected credentials and reconcile uncertain effects before reopening. 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified backup when needed. 5. Document the root cause, the remediation and the regression test. ## Release gate - [ ] A rating of 6 is rejected and creates no row. - [ ] Only the approved fixture is returned by the public endpoint. - [ ] Embedding on a separate local test origin displays the approved cards at 375px and 1280px. - [ ] 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 ShowTrust 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/showtrust # 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
README.md
# ShowTrust · indie build Build a consent-based testimonial collector with approval and an embeddable wall. 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. | | Focused libraries | Pillow | Use these only for the specific file, parsing or provider operations named in the phases; freeze tested versions. | ## 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. - [ ] **ShowTrust 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: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall. 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. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata Pillow 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 consent-based testimonial collector with approval and an embeddable wall; full ShowTrust feature parity, vendor hosting and support are not included. - a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price - the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy - the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand - did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on - X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar If one of those is essential to you, that is the reason to keep paying for ShowTrust, and the README should say so rather than pretend.
BRIEF.md
# Build brief · ShowTrust 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 consent-based testimonial collector with approval and an embeddable wall as a bounded replacement for ShowTrust. 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. - Focused libraries: Pillow. Use these only for the specific file, parsing or provider operations named in the phases; freeze tested versions. ### Data model (create this before Phase 1) - testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at) - moderation(id,testimonial_id,action,at) - wall_settings(id,accent,columns) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: One approved quote, one pending quote containing HTML and one withdrawn submission. ### 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. - ShowTrust acceptance sample: Create synthetic sample data before implementation: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall. 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. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. 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 consent-based testimonial collector with approval and an embeddable wall, 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 Pillow`; `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: testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at); moderation(id,testimonial_id,action,at); wall_settings(id,accent,columns). 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: One approved quote, one pending quote containing HTML and one withdrawn submission. 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. - 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 consent and intake until these checks pass. ### Phase 2 · Consent and intake Build: Consent and intake for ShowTrust: Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. - Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. - Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: A rating of 6 is rejected and creates no row. Then check: The HTML quote appears as text in the private review page. 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: Do not treat submitting a form as implicit consent to publish a name or photo. Done when: A rating of 6 is rejected and creates no row. The HTML quote appears as text in the private review page. Do not build yet: Do not start moderation and withdrawal until these checks pass. ### Phase 3 · Moderation and withdrawal Build: Moderation and withdrawal for ShowTrust: Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. - Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. - Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Only the approved fixture is returned by the public endpoint. Then check: Withdrawing it removes it from the endpoint and next widget load. 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: Never let an incoming request set its own approved status. Done when: Only the approved fixture is returned by the public endpoint. Withdrawing it removes it from the endpoint and next widget load. Do not build yet: Do not start embed and export until these checks pass. ### Phase 4 · Embed and export Build: Embed and export for ShowTrust: Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. - Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. - Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. Then check: A pending quote never appears in the embedded HTML source. 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: This supplies collection and display, not independent identity verification or authenticity certification. Done when: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. A pending quote never appears in the embedded HTML source. 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 ShowTrust replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Consent and intake; Moderation and withdrawal; Embed and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for showtrust. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall 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 showtrust. 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 consent-based testimonial collector with approval and an embeddable wall; full ShowTrust feature parity, vendor hosting and support are not included. - a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price: retain the paid product if this capability is essential; it is outside this bounded build. - the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy: retain the paid product if this capability is essential; it is outside this bounded build. - the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand: retain the paid product if this capability is essential; it is outside this bounded build. - did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on: retain the paid product if this capability is essential; it is outside this bounded build. - X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar: 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. Recheck before upgrading; freeze the versions actually tested.
AGENTS.md
# Agent instructions · ShowTrust 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, Pillow. 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. - Do not treat submitting a form as implicit consent to publish a name or photo. - Never let an incoming request set its own approved status. - This supplies collection and display, not independent identity verification or authenticity certification. - Export without an import or restore rehearsal is not verified portability.
BUILD_PLAN.md
# Build plan · ShowTrust Build a consent-based testimonial collector with approval and an embeddable wall. 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 consent-based testimonial collector with approval and an embeddable wall, 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 Pillow 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: testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at); moderation(id,testimonial_id,action,at); wall_settings(id,accent,columns). 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: One approved quote, one pending quote containing HTML and one withdrawn submission. 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` ### 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 · Consent and intake Consent and intake for ShowTrust: Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. ### Steps 1. Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. Files: `features/consent_and_intake.py`, `templates/consent_and_intake.html` 2. Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. Files: `features/consent_and_intake.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: A rating of 6 is rejected and creates no row. Then check: The HTML quote appears as text in the private review page. 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_consent_and_intake.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A rating of 6 is rejected and creates no row. - [ ] The HTML quote appears as text in the private review page. ### Watch out - Do not treat submitting a form as implicit consent to publish a name or photo. ## Phase 3 · Moderation and withdrawal Moderation and withdrawal for ShowTrust: Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. ### Steps 1. Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. Files: `features/moderation_and_withdrawal.py`, `templates/moderation_and_withdrawal.html` 2. Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. Files: `features/moderation_and_withdrawal.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Only the approved fixture is returned by the public endpoint. Then check: Withdrawing it removes it from the endpoint and next widget load. 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_moderation_and_withdrawal.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Only the approved fixture is returned by the public endpoint. - [ ] Withdrawing it removes it from the endpoint and next widget load. ### Watch out - Never let an incoming request set its own approved status. ## Phase 4 · Embed and export Embed and export for ShowTrust: Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. ### Steps 1. Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. Files: `features/embed_and_export.py`, `templates/embed_and_export.html` 2. Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. Files: `features/embed_and_export.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. Then check: A pending quote never appears in the embedded HTML source. 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_embed_and_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Embedding on a separate local test origin displays the approved cards at 375px and 1280px. - [ ] A pending quote never appears in the embedded HTML source. ### Watch out - This supplies collection and display, not independent identity verification or authenticity certification. ## Phase 5 · Portable delivery and clean-start proof Finish the ShowTrust 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: Consent and intake; Moderation and withdrawal; Embed and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for showtrust. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall; full ShowTrust feature parity, vendor hosting and support are not included. - a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price - the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy - the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand - did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on - X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar ## After v1, if you want it - Extend embed and export only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links.
.env.example
# Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/showtrust # 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
PRODUCT.md
# ShowTrust · product brief ## Problem A submission form, an approval queue, and a grid of cards you can embed elsewhere. There is no algorithm here and no network effect · an agent will produce a working version in one sitting, same as it will for the $25 and $29 tools in this category. The catch is the same one Eloqra has: the hosted version is free for a single site, with no cap on testimonials, so you'd be spending a weekend and a hosting bill to replace zero dollars. Worth building if you want the data on your own box or you enjoy the exercise. Not worth building to save money, because there isn't any to save. ## Product outcome An operated version of a consent-based testimonial collector with approval and an embeddable wall, 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 - a small always-on host - somewhere to put uploaded avatars (local disk is fine) ## Explicit non-goals for v1 - This is a consent-based testimonial collector with approval and an embeddable wall; full ShowTrust feature parity, vendor hosting and support are not included. - a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price - the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy - the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand - did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on - X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar ## Success criteria - A rating of 6 is rejected and creates no row. - Only the approved fixture is returned by the public endpoint. - Embedding on a separate local test origin displays the approved cards at 375px and 1280px. - 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 · ShowTrust 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 consent-based testimonial collector with approval and an embeddable wall as a bounded replacement for ShowTrust. 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. - Focused libraries: Pillow. Use these only for the specific file, parsing or provider operations named in the phases; freeze tested versions. ### Data model (create this before Phase 1) - testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at) - moderation(id,testimonial_id,action,at) - wall_settings(id,accent,columns) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: One approved quote, one pending quote containing HTML and one withdrawn submission. ### 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. - ShowTrust acceptance sample: Create synthetic sample data before implementation: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall. 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. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. 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 consent-based testimonial collector with approval and an embeddable wall, 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 Pillow`; `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: testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at); moderation(id,testimonial_id,action,at); wall_settings(id,accent,columns). 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: One approved quote, one pending quote containing HTML and one withdrawn submission. 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. - 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 consent and intake until these checks pass. ### Phase 2 · Consent and intake Build: Consent and intake for ShowTrust: Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. - Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. - Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: A rating of 6 is rejected and creates no row. Then check: The HTML quote appears as text in the private review page. 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: Do not treat submitting a form as implicit consent to publish a name or photo. Done when: A rating of 6 is rejected and creates no row. The HTML quote appears as text in the private review page. Do not build yet: Do not start moderation and withdrawal until these checks pass. ### Phase 3 · Moderation and withdrawal Build: Moderation and withdrawal for ShowTrust: Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. - Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. - Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Only the approved fixture is returned by the public endpoint. Then check: Withdrawing it removes it from the endpoint and next widget load. 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: Never let an incoming request set its own approved status. Done when: Only the approved fixture is returned by the public endpoint. Withdrawing it removes it from the endpoint and next widget load. Do not build yet: Do not start embed and export until these checks pass. ### Phase 4 · Embed and export Build: Embed and export for ShowTrust: Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. - Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. - Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. - Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. Then check: A pending quote never appears in the embedded HTML source. 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: This supplies collection and display, not independent identity verification or authenticity certification. Done when: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. A pending quote never appears in the embedded HTML source. 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 ShowTrust replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Consent and intake; Moderation and withdrawal; Embed and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for showtrust. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall 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 showtrust. 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 consent-based testimonial collector with approval and an embeddable wall; full ShowTrust feature parity, vendor hosting and support are not included. - a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price: retain the paid product if this capability is essential; it is outside this bounded build. - the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy: retain the paid product if this capability is essential; it is outside this bounded build. - the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand: retain the paid product if this capability is essential; it is outside this bounded build. - did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on: retain the paid product if this capability is essential; it is outside this bounded build. - X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar: 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. Recheck before upgrading; freeze the versions actually tested.
ARCHITECTURE.md
# Architecture · ShowTrust ## 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. | | Focused libraries | Pillow | Use these only for the specific file, parsing or provider operations named in the phases; freeze tested versions. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at); moderation(id,testimonial_id,action,at); wall_settings(id,accent,columns) | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Consent and intake | Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. | Keep the acceptance contract: A rating of 6 is rejected and creates no row. Replace only this module after replaying its fixture; preserve ids and existing records. | | Moderation and withdrawal | Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. | Keep the acceptance contract: Only the approved fixture is returned by the public endpoint. Replace only this module after replaying its fixture; preserve ids and existing records. | | Embed and export | Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. | Keep the acceptance contract: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. 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 showtrust. | 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. ## 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 · ShowTrust 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, Pillow. - 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. - Do not treat submitting a form as implicit consent to publish a name or photo. - Never let an incoming request set its own approved status. - This supplies collection and display, not independent identity verification or authenticity certification. - 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 · ShowTrust 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 consent-based testimonial collector with approval and an embeddable wall, 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 Pillow 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: testimonials(id,name,quote,rating,photo_path,consent_at,status,created_at); moderation(id,testimonial_id,action,at); wall_settings(id,accent,columns). 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: One approved quote, one pending quote containing HTML and one withdrawn submission. 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` ### 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 · Consent and intake Consent and intake for ShowTrust: Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. ### Steps 1. Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. Create a public form with bounded name, quote and 1-5 rating, optional photo and explicit publication consent. Files: `features/consent_and_intake.py`, `templates/consent_and_intake.html` 2. Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. Validate image content and dimensions, re-encode it under a generated filename and keep submissions pending by default. Files: `features/consent_and_intake.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: A rating of 6 is rejected and creates no row. Then check: The HTML quote appears as text in the private review page. 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_consent_and_intake.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A rating of 6 is rejected and creates no row. - [ ] The HTML quote appears as text in the private review page. ### Watch out - Do not treat submitting a form as implicit consent to publish a name or photo. ## M3 · Moderation and withdrawal Moderation and withdrawal for ShowTrust: Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. ### Steps 1. Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. Build approve/reject/withdraw controls with an audit trail and a preview of the exact public card. Files: `features/moderation_and_withdrawal.py`, `templates/moderation_and_withdrawal.html` 2. Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. Keep the public query restricted to approved rows with recorded consent; removal must invalidate cached output. Files: `features/moderation_and_withdrawal.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Only the approved fixture is returned by the public endpoint. Then check: Withdrawing it removes it from the endpoint and next widget load. 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_moderation_and_withdrawal.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Only the approved fixture is returned by the public endpoint. - [ ] Withdrawing it removes it from the endpoint and next widget load. ### Watch out - Never let an incoming request set its own approved status. ## M4 · Embed and export Embed and export for ShowTrust: Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. ### Steps 1. Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. Serve a responsive iframe wall with labelled stars, escaped quotes and a fixed theme allowlist. Files: `features/embed_and_export.py`, `templates/embed_and_export.html` 2. Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. Provide a copyable iframe snippet and owner-only CSV/JSON export of consent and moderation records. Files: `features/embed_and_export.py` 3. Exercise the acceptance fixture Use One approved quote, one pending quote containing HTML and one withdrawn submission. Check: Embedding on a separate local test origin displays the approved cards at 375px and 1280px. Then check: A pending quote never appears in the embedded HTML source. 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_embed_and_export.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Embedding on a separate local test origin displays the approved cards at 375px and 1280px. - [ ] A pending quote never appears in the embedded HTML source. ### Watch out - This supplies collection and display, not independent identity verification or authenticity certification. ## M5 · Portable delivery and clean-start proof Finish the ShowTrust 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: Consent and intake; Moderation and withdrawal; Embed and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for showtrust. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 consent-based testimonial collector with approval and an embeddable wall 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 showtrust. 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 · ShowTrust ## 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 showtrust. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One approved quote, one pending quote containing HTML and one withdrawn submission. 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 Consent and intake, Moderation and withdrawal, Embed and export. Alert without logging private payloads. ## Incident checklist Pause outbound jobs and public intake as appropriate, preserve redacted diagnostics, restore an isolated verified backup, rotate affected credentials and reconcile uncertain effects before reopening. 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified backup when needed. 5. Document the root cause, the remediation and the regression test. ## Release gate - [ ] A rating of 6 is rejected and creates no row. - [ ] Only the approved fixture is returned by the public endpoint. - [ ] Embedding on a separate local test origin displays the approved cards at 375px and 1280px. - [ ] 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 ShowTrust 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/showtrust # 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
$ choose a build depth, inspect the files, then open the complete pack in your agent
For one site, they don't · it's free, uncapped, and nothing is feature-gated, so the paid tier only exists to add a second project. What you actually trade away by self-hosting is smaller and more boring than money: the layout and styling controls are a real chunk of fiddly frontend work, and the impression tracking tells you whether the wall is doing anything at all, which a hand-rolled version silently won't. One honest mark against the hosted option · the collection page carries a 'Powered by ShowTrustTo' line on every tier, paid included, and there's no switch to remove it. If that badge on a page you send to customers bothers you, that alone is a legitimate reason to build your own.
xa free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price
xthe install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy
xthe design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand
xdid-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on
xX-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar
share on X ↗"I just replaced ShowTrust ($4.99/mo) with one prompt"
Don't feel like building it? These folks already made it free.
Real TestimonialsAnother WordPress route: forms, moderation, grids and sliders are free; video and the clever automation live upstairs.free↗
ShosayUnlimited text, video and audio proof, imports, walls and 25-plus widgets; the bill is zero, the tiny Powered by pill is not.free↗Strong TestimonialsA WordPress-only form, moderation queue, grid, slider and widget; simple enough once you already own the WordPress problem.free↗all 3 free alternatives to ShowTrust →· no votes, no pay-to-list · just what's real
ShowTrust pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0/workspace | $0/workspace | Unlimited testimonials; 1 project; no visitor/page-view cap; no watermark. |
| pro | $4.99/workspace | $4.17/workspace | Unlimited testimonials and usage; paid project/features bundle. |
free tierUnlimited testimonials; 1 project; no visitor/page-view cap; no watermark.
billingMonthly + annual; annual total is $49.99.
verified 2026-08-12 · source ↗
Vibecode ShowTrust
Yes. A competent AI coding agent (Claude Code, Codex, Cursor) can build a usable personal ShowTrust replacement in one session with the prompt on this page. It runs on your own machine or server with no subscription.
How much does ShowTrust cost?
ShowTrust costs about $4.99/month (Pro, checked 2026-07-31), which is $59.88 per year. That's what you save by replacing it with one prompt.
What do I lose by replacing ShowTrust?
Honestly: a free tier · one site with uncapped testimonials costs nothing hosted, so the DIY build starts out behind on price; the install itself · an agent can provision the account from your email alone, get working credentials in the same response, create the project and paste the snippet into your framework, with the human only clicking a claim link afterwards · your own build is something you have to go and deploy; the design surface you'd otherwise hand-build · multiple layouts, eight card styles, colour palettes, and sliders for width, spacing and radius, all previewable instead of CSS-tweaked by hand; did-it-work data · impression and CTA-click tracking with click-through rate and which domains your wall is actually being viewed on; X-verified testimonials · an OAuth flow that reads X's own verified state, so the quote is provably tied to a real handle and avatar. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to ShowTrust?
Yes: Real Testimonials (Another WordPress route: forms, moderation, grids and sliders are free; video and the clever automation live upstairs.) Shosay (Unlimited text, video and audio proof, imports, walls and 25-plus widgets; the bill is zero, the tiny Powered by pill is not.) Strong Testimonials (A WordPress-only form, moderation queue, grid, slider and widget; simple enough once you already own the WordPress problem.) All 3 curated free alternatives are at vibecodeit.com/showtrust/alternatives. The prompt is for when you want it exactly your way.