Vibecode Retool
track this build5 phases, 15 steps, beginner friendly0%KINDA · weekend project
The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Retool, build one internal CRUD tool over a trusted database with role-aware actions. The hard boundary is connectors, component library, permissions, workflows, and hosted runtime, plus connectors, runtime reliability, and governance.
the project pack5 files · written for this build, step by step
You are building a lean indie version of Retool. 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 ===== # Retool · indie build Build one private inventory administration tool with audited actions. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Retool acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions. 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 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: - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - This is one private inventory administration tool with audited actions; full Retool feature parity, vendor hosting and support are not included. - connectors, component library, permissions, workflows, and hosted runtime - hundreds of connectors - pixel-perfect app design - mobile app-store builds - enterprise permissions and scale If one of those is essential to you, that is the reason to keep paying for Retool, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · Retool 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 one private inventory administration tool with audited actions as a bounded replacement for Retool. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - products(id,sku,name,stock,revision) - adjustments(id,product_id,delta,reason,actor,at) - users(id,email,password_hash,role) - sessions(id,user_id,expires_at) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Two products with stock 5 and 0; owner, operator and viewer identities. ### 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. - Retool acceptance sample: Create synthetic sample data before implementation: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions. 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 one private inventory administration tool with audited actions, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: products(id,sku,name,stock,revision); adjustments(id,product_id,delta,reason,actor,at); users(id,email,password_hash,role); sessions(id,user_id,expires_at). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Two products with stock 5 and 0; owner, operator and viewer identities. 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 inventory contract until these checks pass. ### Phase 2 · Inventory contract Build: Inventory contract for Retool: Create a fixed product schema and seeded data; expose paginated search and detail views. - Create a fixed product schema and seeded data; expose paginated search and detail views. - Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: An adjustment of -6 against stock 5 is rejected. Then check: Two adjustments against the same revision conflict instead of losing an update. 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: The useful replacement is this internal tool, not a generic low-code platform. Done when: An adjustment of -6 against stock 5 is rejected. Two adjustments against the same revision conflict instead of losing an update. Do not build yet: Do not start authorized actions until these checks pass. ### Phase 3 · Authorized actions Build: Authorized actions for Retool: Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. - Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. - Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: A viewer posting directly to adjustment receives 403 and creates no audit entry. Then check: An operator adjustment changes stock and creates exactly one audit record. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: A hidden button is not an authorization boundary. Done when: A viewer posting directly to adjustment receives 403 and creates no audit entry. An operator adjustment changes stock and creates exactly one audit record. Do not build yet: Do not start auditable exchange until these checks pass. ### Phase 4 · Auditable exchange Build: Auditable exchange for Retool: Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. - Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. - Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: One invalid SKU aborts the import and names the row. Then check: Every exported stock correction can be traced to an actor and reason. 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 accept user SQL, arbitrary database credentials or unbounded file uploads. Done when: One invalid SKU aborts the import and names the row. Every exported stock correction can be traced to an actor and reason. 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 Retool replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Inventory contract; Authorized actions; Auditable exchange. 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 retool. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions 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 retool. 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) - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - This is one private inventory administration tool with audited actions; full Retool feature parity, vendor hosting and support are not included. - connectors, component library, permissions, workflows, and hosted runtime: retain the paid product if this capability is essential; it is outside this bounded build. - hundreds of connectors: retain the paid product if this capability is essential; it is outside this bounded build. - pixel-perfect app design: retain the paid product if this capability is essential; it is outside this bounded build. - mobile app-store builds: retain the paid product if this capability is essential; it is outside this bounded build. - enterprise permissions and scale: 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 · Retool indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - Never accept user SQL, arbitrary database credentials or unbounded file uploads. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · Retool Build one private inventory administration tool with audited actions. 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 one private inventory administration tool with audited actions, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: products(id,sku,name,stock,revision); adjustments(id,product_id,delta,reason,actor,at); users(id,email,password_hash,role); sessions(id,user_id,expires_at). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Two products with stock 5 and 0; owner, operator and viewer identities. 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 · Inventory contract Inventory contract for Retool: Create a fixed product schema and seeded data; expose paginated search and detail views. ### Steps 1. Create a fixed product schema and seeded data; expose paginated search and detail views. Create a fixed product schema and seeded data; expose paginated search and detail views. Files: `features/inventory_contract.py`, `templates/inventory_contract.html` 2. Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. Files: `features/inventory_contract.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: An adjustment of -6 against stock 5 is rejected. Then check: Two adjustments against the same revision conflict instead of losing an update. 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_inventory_contract.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] An adjustment of -6 against stock 5 is rejected. - [ ] Two adjustments against the same revision conflict instead of losing an update. ### Watch out - The useful replacement is this internal tool, not a generic low-code platform. ## Phase 3 · Authorized actions Authorized actions for Retool: Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. ### Steps 1. Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. Files: `features/authorized_actions.py`, `templates/authorized_actions.html` 2. Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. Files: `features/authorized_actions.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: A viewer posting directly to adjustment receives 403 and creates no audit entry. Then check: An operator adjustment changes stock and creates exactly one audit record. 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_authorized_actions.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A viewer posting directly to adjustment receives 403 and creates no audit entry. - [ ] An operator adjustment changes stock and creates exactly one audit record. ### Watch out - A hidden button is not an authorization boundary. ## Phase 4 · Auditable exchange Auditable exchange for Retool: Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. ### Steps 1. Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. Files: `features/auditable_exchange.py`, `templates/auditable_exchange.html` 2. Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. Files: `features/auditable_exchange.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: One invalid SKU aborts the import and names the row. Then check: Every exported stock correction can be traced to an actor and reason. 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_auditable_exchange.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] One invalid SKU aborts the import and names the row. - [ ] Every exported stock correction can be traced to an actor and reason. ### Watch out - Never accept user SQL, arbitrary database credentials or unbounded file uploads. ## Phase 5 · Portable delivery and clean-start proof Finish the Retool 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: Inventory contract; Authorized actions; Auditable exchange. 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 retool. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two products with stock 5 and 0; owner, operator and viewer identities. 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 - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - This is one private inventory administration tool with audited actions; full Retool feature parity, vendor hosting and support are not included. - connectors, component library, permissions, workflows, and hosted runtime - hundreds of connectors - pixel-perfect app design - mobile app-store builds - enterprise permissions and scale ## After v1, if you want it - Extend auditable exchange 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/retool # 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 Retool. 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 ===== # Retool · indie build Build one private inventory administration tool with audited actions. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Retool acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions. 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 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: - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - This is one private inventory administration tool with audited actions; full Retool feature parity, vendor hosting and support are not included. - connectors, component library, permissions, workflows, and hosted runtime - hundreds of connectors - pixel-perfect app design - mobile app-store builds - enterprise permissions and scale If one of those is essential to you, that is the reason to keep paying for Retool, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · Retool 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 one private inventory administration tool with audited actions as a bounded replacement for Retool. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - products(id,sku,name,stock,revision) - adjustments(id,product_id,delta,reason,actor,at) - users(id,email,password_hash,role) - sessions(id,user_id,expires_at) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Two products with stock 5 and 0; owner, operator and viewer identities. ### 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. - Retool acceptance sample: Create synthetic sample data before implementation: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions. 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 one private inventory administration tool with audited actions, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: products(id,sku,name,stock,revision); adjustments(id,product_id,delta,reason,actor,at); users(id,email,password_hash,role); sessions(id,user_id,expires_at). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Two products with stock 5 and 0; owner, operator and viewer identities. 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 inventory contract until these checks pass. ### Phase 2 · Inventory contract Build: Inventory contract for Retool: Create a fixed product schema and seeded data; expose paginated search and detail views. - Create a fixed product schema and seeded data; expose paginated search and detail views. - Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: An adjustment of -6 against stock 5 is rejected. Then check: Two adjustments against the same revision conflict instead of losing an update. 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: The useful replacement is this internal tool, not a generic low-code platform. Done when: An adjustment of -6 against stock 5 is rejected. Two adjustments against the same revision conflict instead of losing an update. Do not build yet: Do not start authorized actions until these checks pass. ### Phase 3 · Authorized actions Build: Authorized actions for Retool: Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. - Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. - Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: A viewer posting directly to adjustment receives 403 and creates no audit entry. Then check: An operator adjustment changes stock and creates exactly one audit record. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: A hidden button is not an authorization boundary. Done when: A viewer posting directly to adjustment receives 403 and creates no audit entry. An operator adjustment changes stock and creates exactly one audit record. Do not build yet: Do not start auditable exchange until these checks pass. ### Phase 4 · Auditable exchange Build: Auditable exchange for Retool: Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. - Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. - Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: One invalid SKU aborts the import and names the row. Then check: Every exported stock correction can be traced to an actor and reason. 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 accept user SQL, arbitrary database credentials or unbounded file uploads. Done when: One invalid SKU aborts the import and names the row. Every exported stock correction can be traced to an actor and reason. 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 Retool replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Inventory contract; Authorized actions; Auditable exchange. 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 retool. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions 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 retool. 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) - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - This is one private inventory administration tool with audited actions; full Retool feature parity, vendor hosting and support are not included. - connectors, component library, permissions, workflows, and hosted runtime: retain the paid product if this capability is essential; it is outside this bounded build. - hundreds of connectors: retain the paid product if this capability is essential; it is outside this bounded build. - pixel-perfect app design: retain the paid product if this capability is essential; it is outside this bounded build. - mobile app-store builds: retain the paid product if this capability is essential; it is outside this bounded build. - enterprise permissions and scale: 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 · Retool indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - Never accept user SQL, arbitrary database credentials or unbounded file uploads. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · Retool Build one private inventory administration tool with audited actions. 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 one private inventory administration tool with audited actions, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: products(id,sku,name,stock,revision); adjustments(id,product_id,delta,reason,actor,at); users(id,email,password_hash,role); sessions(id,user_id,expires_at). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Two products with stock 5 and 0; owner, operator and viewer identities. 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 · Inventory contract Inventory contract for Retool: Create a fixed product schema and seeded data; expose paginated search and detail views. ### Steps 1. Create a fixed product schema and seeded data; expose paginated search and detail views. Create a fixed product schema and seeded data; expose paginated search and detail views. Files: `features/inventory_contract.py`, `templates/inventory_contract.html` 2. Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. Files: `features/inventory_contract.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: An adjustment of -6 against stock 5 is rejected. Then check: Two adjustments against the same revision conflict instead of losing an update. 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_inventory_contract.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] An adjustment of -6 against stock 5 is rejected. - [ ] Two adjustments against the same revision conflict instead of losing an update. ### Watch out - The useful replacement is this internal tool, not a generic low-code platform. ## Phase 3 · Authorized actions Authorized actions for Retool: Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. ### Steps 1. Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. Files: `features/authorized_actions.py`, `templates/authorized_actions.html` 2. Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. Files: `features/authorized_actions.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: A viewer posting directly to adjustment receives 403 and creates no audit entry. Then check: An operator adjustment changes stock and creates exactly one audit record. 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_authorized_actions.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A viewer posting directly to adjustment receives 403 and creates no audit entry. - [ ] An operator adjustment changes stock and creates exactly one audit record. ### Watch out - A hidden button is not an authorization boundary. ## Phase 4 · Auditable exchange Auditable exchange for Retool: Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. ### Steps 1. Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. Files: `features/auditable_exchange.py`, `templates/auditable_exchange.html` 2. Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. Files: `features/auditable_exchange.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: One invalid SKU aborts the import and names the row. Then check: Every exported stock correction can be traced to an actor and reason. 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_auditable_exchange.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] One invalid SKU aborts the import and names the row. - [ ] Every exported stock correction can be traced to an actor and reason. ### Watch out - Never accept user SQL, arbitrary database credentials or unbounded file uploads. ## Phase 5 · Portable delivery and clean-start proof Finish the Retool 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: Inventory contract; Authorized actions; Auditable exchange. 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 retool. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two products with stock 5 and 0; owner, operator and viewer identities. 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 - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - This is one private inventory administration tool with audited actions; full Retool feature parity, vendor hosting and support are not included. - connectors, component library, permissions, workflows, and hosted runtime - hundreds of connectors - pixel-perfect app design - mobile app-store builds - enterprise permissions and scale ## After v1, if you want it - Extend auditable exchange 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/retool # 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 Retool. 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 ===== # Retool · product brief ## Problem The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Retool, build one internal CRUD tool over a trusted database with role-aware actions. The hard boundary is connectors, component library, permissions, workflows, and hosted runtime, plus connectors, runtime reliability, and governance. ## Product outcome An operated version of one private inventory administration tool with audited actions, 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 - Docker - PostgreSQL - self-hosted deploy target - API credentials for one selected integration ## Explicit non-goals for v1 - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - This is one private inventory administration tool with audited actions; full Retool feature parity, vendor hosting and support are not included. - connectors, component library, permissions, workflows, and hosted runtime - hundreds of connectors - pixel-perfect app design - mobile app-store builds - enterprise permissions and scale ## Success criteria - An adjustment of -6 against stock 5 is rejected. - A viewer posting directly to adjustment receives 403 and creates no audit entry. - One invalid SKU aborts the import and names the row. - 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 · Retool 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 one private inventory administration tool with audited actions as a bounded replacement for Retool. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - products(id,sku,name,stock,revision) - adjustments(id,product_id,delta,reason,actor,at) - users(id,email,password_hash,role) - sessions(id,user_id,expires_at) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Two products with stock 5 and 0; owner, operator and viewer identities. ### 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. - Retool acceptance sample: Create synthetic sample data before implementation: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions. 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 one private inventory administration tool with audited actions, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: products(id,sku,name,stock,revision); adjustments(id,product_id,delta,reason,actor,at); users(id,email,password_hash,role); sessions(id,user_id,expires_at). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Two products with stock 5 and 0; owner, operator and viewer identities. 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 inventory contract until these checks pass. ### Phase 2 · Inventory contract Build: Inventory contract for Retool: Create a fixed product schema and seeded data; expose paginated search and detail views. - Create a fixed product schema and seeded data; expose paginated search and detail views. - Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: An adjustment of -6 against stock 5 is rejected. Then check: Two adjustments against the same revision conflict instead of losing an update. 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: The useful replacement is this internal tool, not a generic low-code platform. Done when: An adjustment of -6 against stock 5 is rejected. Two adjustments against the same revision conflict instead of losing an update. Do not build yet: Do not start authorized actions until these checks pass. ### Phase 3 · Authorized actions Build: Authorized actions for Retool: Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. - Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. - Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: A viewer posting directly to adjustment receives 403 and creates no audit entry. Then check: An operator adjustment changes stock and creates exactly one audit record. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: A hidden button is not an authorization boundary. Done when: A viewer posting directly to adjustment receives 403 and creates no audit entry. An operator adjustment changes stock and creates exactly one audit record. Do not build yet: Do not start auditable exchange until these checks pass. ### Phase 4 · Auditable exchange Build: Auditable exchange for Retool: Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. - Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. - Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: One invalid SKU aborts the import and names the row. Then check: Every exported stock correction can be traced to an actor and reason. 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 accept user SQL, arbitrary database credentials or unbounded file uploads. Done when: One invalid SKU aborts the import and names the row. Every exported stock correction can be traced to an actor and reason. 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 Retool replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Inventory contract; Authorized actions; Auditable exchange. 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 retool. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions 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 retool. 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) - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - This is one private inventory administration tool with audited actions; full Retool feature parity, vendor hosting and support are not included. - connectors, component library, permissions, workflows, and hosted runtime: retain the paid product if this capability is essential; it is outside this bounded build. - hundreds of connectors: retain the paid product if this capability is essential; it is outside this bounded build. - pixel-perfect app design: retain the paid product if this capability is essential; it is outside this bounded build. - mobile app-store builds: retain the paid product if this capability is essential; it is outside this bounded build. - enterprise permissions and scale: 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 · Retool ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | products(id,sku,name,stock,revision); adjustments(id,product_id,delta,reason,actor,at); users(id,email,password_hash,role); sessions(id,user_id,expires_at) | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Inventory contract | Create a fixed product schema and seeded data; expose paginated search and detail views. | Keep the acceptance contract: An adjustment of -6 against stock 5 is rejected. Replace only this module after replaying its fixture; preserve ids and existing records. | | Authorized actions | Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. | Keep the acceptance contract: A viewer posting directly to adjustment receives 403 and creates no audit entry. Replace only this module after replaying its fixture; preserve ids and existing records. | | Auditable exchange | Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. | Keep the acceptance contract: One invalid SKU aborts the import and names the row. 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 retool. | 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 · Retool product build - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. - Implement milestone by milestone from `MILESTONES.md`; keep each change reviewable and leave the application runnable at every commit. - Treat authentication, payments, encryption, imports, webhooks and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a check pass. - Put every external service behind an interface with a deterministic fake for tests. - Add migrations and rollback or recovery notes for every persistent data change. - Log useful operational context without credentials, tokens, passwords or personal data. - Update documentation and run every check before completing a milestone. ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - Never accept user SQL, arbitrary database credentials or unbounded file uploads. - 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 · Retool 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 one private inventory administration tool with audited actions, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: products(id,sku,name,stock,revision); adjustments(id,product_id,delta,reason,actor,at); users(id,email,password_hash,role); sessions(id,user_id,expires_at). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Two products with stock 5 and 0; owner, operator and viewer identities. 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 · Inventory contract Inventory contract for Retool: Create a fixed product schema and seeded data; expose paginated search and detail views. ### Steps 1. Create a fixed product schema and seeded data; expose paginated search and detail views. Create a fixed product schema and seeded data; expose paginated search and detail views. Files: `features/inventory_contract.py`, `templates/inventory_contract.html` 2. Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. Files: `features/inventory_contract.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: An adjustment of -6 against stock 5 is rejected. Then check: Two adjustments against the same revision conflict instead of losing an update. 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_inventory_contract.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] An adjustment of -6 against stock 5 is rejected. - [ ] Two adjustments against the same revision conflict instead of losing an update. ### Watch out - The useful replacement is this internal tool, not a generic low-code platform. ## M3 · Authorized actions Authorized actions for Retool: Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. ### Steps 1. Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. Files: `features/authorized_actions.py`, `templates/authorized_actions.html` 2. Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. Files: `features/authorized_actions.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: A viewer posting directly to adjustment receives 403 and creates no audit entry. Then check: An operator adjustment changes stock and creates exactly one audit record. 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_authorized_actions.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A viewer posting directly to adjustment receives 403 and creates no audit entry. - [ ] An operator adjustment changes stock and creates exactly one audit record. ### Watch out - A hidden button is not an authorization boundary. ## M4 · Auditable exchange Auditable exchange for Retool: Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. ### Steps 1. Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. Files: `features/auditable_exchange.py`, `templates/auditable_exchange.html` 2. Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. Files: `features/auditable_exchange.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: One invalid SKU aborts the import and names the row. Then check: Every exported stock correction can be traced to an actor and reason. 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_auditable_exchange.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] One invalid SKU aborts the import and names the row. - [ ] Every exported stock correction can be traced to an actor and reason. ### Watch out - Never accept user SQL, arbitrary database credentials or unbounded file uploads. ## M5 · Portable delivery and clean-start proof Finish the Retool 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: Inventory contract; Authorized actions; Auditable exchange. 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 retool. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions 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 retool. 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 · Retool ## 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 retool. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two products with stock 5 and 0; owner, operator and viewer identities. 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 Inventory contract, Authorized actions, Auditable exchange. 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 - [ ] An adjustment of -6 against stock 5 is rejected. - [ ] A viewer posting directly to adjustment receives 403 and creates no audit entry. - [ ] One invalid SKU aborts the import and names the row. - [ ] 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 Retool 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/retool # 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
# Retool · indie build Build one private inventory administration tool with audited actions. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Retool acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions. 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 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: - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - This is one private inventory administration tool with audited actions; full Retool feature parity, vendor hosting and support are not included. - connectors, component library, permissions, workflows, and hosted runtime - hundreds of connectors - pixel-perfect app design - mobile app-store builds - enterprise permissions and scale If one of those is essential to you, that is the reason to keep paying for Retool, and the README should say so rather than pretend.
BRIEF.md
# Build brief · Retool 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 one private inventory administration tool with audited actions as a bounded replacement for Retool. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - products(id,sku,name,stock,revision) - adjustments(id,product_id,delta,reason,actor,at) - users(id,email,password_hash,role) - sessions(id,user_id,expires_at) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Two products with stock 5 and 0; owner, operator and viewer identities. ### 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. - Retool acceptance sample: Create synthetic sample data before implementation: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions. 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 one private inventory administration tool with audited actions, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: products(id,sku,name,stock,revision); adjustments(id,product_id,delta,reason,actor,at); users(id,email,password_hash,role); sessions(id,user_id,expires_at). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Two products with stock 5 and 0; owner, operator and viewer identities. 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 inventory contract until these checks pass. ### Phase 2 · Inventory contract Build: Inventory contract for Retool: Create a fixed product schema and seeded data; expose paginated search and detail views. - Create a fixed product schema and seeded data; expose paginated search and detail views. - Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: An adjustment of -6 against stock 5 is rejected. Then check: Two adjustments against the same revision conflict instead of losing an update. 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: The useful replacement is this internal tool, not a generic low-code platform. Done when: An adjustment of -6 against stock 5 is rejected. Two adjustments against the same revision conflict instead of losing an update. Do not build yet: Do not start authorized actions until these checks pass. ### Phase 3 · Authorized actions Build: Authorized actions for Retool: Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. - Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. - Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: A viewer posting directly to adjustment receives 403 and creates no audit entry. Then check: An operator adjustment changes stock and creates exactly one audit record. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: A hidden button is not an authorization boundary. Done when: A viewer posting directly to adjustment receives 403 and creates no audit entry. An operator adjustment changes stock and creates exactly one audit record. Do not build yet: Do not start auditable exchange until these checks pass. ### Phase 4 · Auditable exchange Build: Auditable exchange for Retool: Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. - Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. - Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: One invalid SKU aborts the import and names the row. Then check: Every exported stock correction can be traced to an actor and reason. 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 accept user SQL, arbitrary database credentials or unbounded file uploads. Done when: One invalid SKU aborts the import and names the row. Every exported stock correction can be traced to an actor and reason. 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 Retool replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Inventory contract; Authorized actions; Auditable exchange. 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 retool. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions 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 retool. 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) - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - This is one private inventory administration tool with audited actions; full Retool feature parity, vendor hosting and support are not included. - connectors, component library, permissions, workflows, and hosted runtime: retain the paid product if this capability is essential; it is outside this bounded build. - hundreds of connectors: retain the paid product if this capability is essential; it is outside this bounded build. - pixel-perfect app design: retain the paid product if this capability is essential; it is outside this bounded build. - mobile app-store builds: retain the paid product if this capability is essential; it is outside this bounded build. - enterprise permissions and scale: 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 · Retool indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - Never accept user SQL, arbitrary database credentials or unbounded file uploads. - Export without an import or restore rehearsal is not verified portability.
BUILD_PLAN.md
# Build plan · Retool Build one private inventory administration tool with audited actions. 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 one private inventory administration tool with audited actions, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: products(id,sku,name,stock,revision); adjustments(id,product_id,delta,reason,actor,at); users(id,email,password_hash,role); sessions(id,user_id,expires_at). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Two products with stock 5 and 0; owner, operator and viewer identities. 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 · Inventory contract Inventory contract for Retool: Create a fixed product schema and seeded data; expose paginated search and detail views. ### Steps 1. Create a fixed product schema and seeded data; expose paginated search and detail views. Create a fixed product schema and seeded data; expose paginated search and detail views. Files: `features/inventory_contract.py`, `templates/inventory_contract.html` 2. Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. Files: `features/inventory_contract.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: An adjustment of -6 against stock 5 is rejected. Then check: Two adjustments against the same revision conflict instead of losing an update. 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_inventory_contract.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] An adjustment of -6 against stock 5 is rejected. - [ ] Two adjustments against the same revision conflict instead of losing an update. ### Watch out - The useful replacement is this internal tool, not a generic low-code platform. ## Phase 3 · Authorized actions Authorized actions for Retool: Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. ### Steps 1. Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. Files: `features/authorized_actions.py`, `templates/authorized_actions.html` 2. Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. Files: `features/authorized_actions.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: A viewer posting directly to adjustment receives 403 and creates no audit entry. Then check: An operator adjustment changes stock and creates exactly one audit record. 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_authorized_actions.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A viewer posting directly to adjustment receives 403 and creates no audit entry. - [ ] An operator adjustment changes stock and creates exactly one audit record. ### Watch out - A hidden button is not an authorization boundary. ## Phase 4 · Auditable exchange Auditable exchange for Retool: Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. ### Steps 1. Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. Files: `features/auditable_exchange.py`, `templates/auditable_exchange.html` 2. Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. Files: `features/auditable_exchange.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: One invalid SKU aborts the import and names the row. Then check: Every exported stock correction can be traced to an actor and reason. 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_auditable_exchange.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] One invalid SKU aborts the import and names the row. - [ ] Every exported stock correction can be traced to an actor and reason. ### Watch out - Never accept user SQL, arbitrary database credentials or unbounded file uploads. ## Phase 5 · Portable delivery and clean-start proof Finish the Retool 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: Inventory contract; Authorized actions; Auditable exchange. 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 retool. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two products with stock 5 and 0; owner, operator and viewer identities. 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 - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - This is one private inventory administration tool with audited actions; full Retool feature parity, vendor hosting and support are not included. - connectors, component library, permissions, workflows, and hosted runtime - hundreds of connectors - pixel-perfect app design - mobile app-store builds - enterprise permissions and scale ## After v1, if you want it - Extend auditable exchange 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/retool # 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
# Retool · product brief ## Problem The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Retool, build one internal CRUD tool over a trusted database with role-aware actions. The hard boundary is connectors, component library, permissions, workflows, and hosted runtime, plus connectors, runtime reliability, and governance. ## Product outcome An operated version of one private inventory administration tool with audited actions, 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 - Docker - PostgreSQL - self-hosted deploy target - API credentials for one selected integration ## Explicit non-goals for v1 - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - This is one private inventory administration tool with audited actions; full Retool feature parity, vendor hosting and support are not included. - connectors, component library, permissions, workflows, and hosted runtime - hundreds of connectors - pixel-perfect app design - mobile app-store builds - enterprise permissions and scale ## Success criteria - An adjustment of -6 against stock 5 is rejected. - A viewer posting directly to adjustment receives 403 and creates no audit entry. - One invalid SKU aborts the import and names the row. - 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 · Retool 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 one private inventory administration tool with audited actions as a bounded replacement for Retool. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - products(id,sku,name,stock,revision) - adjustments(id,product_id,delta,reason,actor,at) - users(id,email,password_hash,role) - sessions(id,user_id,expires_at) - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: Two products with stock 5 and 0; owner, operator and viewer identities. ### 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. - Retool acceptance sample: Create synthetic sample data before implementation: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions. 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 one private inventory administration tool with audited actions, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: products(id,sku,name,stock,revision); adjustments(id,product_id,delta,reason,actor,at); users(id,email,password_hash,role); sessions(id,user_id,expires_at). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Two products with stock 5 and 0; owner, operator and viewer identities. 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 inventory contract until these checks pass. ### Phase 2 · Inventory contract Build: Inventory contract for Retool: Create a fixed product schema and seeded data; expose paginated search and detail views. - Create a fixed product schema and seeded data; expose paginated search and detail views. - Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: An adjustment of -6 against stock 5 is rejected. Then check: Two adjustments against the same revision conflict instead of losing an update. 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: The useful replacement is this internal tool, not a generic low-code platform. Done when: An adjustment of -6 against stock 5 is rejected. Two adjustments against the same revision conflict instead of losing an update. Do not build yet: Do not start authorized actions until these checks pass. ### Phase 3 · Authorized actions Build: Authorized actions for Retool: Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. - Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. - Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: A viewer posting directly to adjustment receives 403 and creates no audit entry. Then check: An operator adjustment changes stock and creates exactly one audit record. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: A hidden button is not an authorization boundary. Done when: A viewer posting directly to adjustment receives 403 and creates no audit entry. An operator adjustment changes stock and creates exactly one audit record. Do not build yet: Do not start auditable exchange until these checks pass. ### Phase 4 · Auditable exchange Build: Auditable exchange for Retool: Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. - Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. - Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. - Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: One invalid SKU aborts the import and names the row. Then check: Every exported stock correction can be traced to an actor and reason. 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 accept user SQL, arbitrary database credentials or unbounded file uploads. Done when: One invalid SKU aborts the import and names the row. Every exported stock correction can be traced to an actor and reason. 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 Retool replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Inventory contract; Authorized actions; Auditable exchange. 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 retool. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions 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 retool. 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) - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - This is one private inventory administration tool with audited actions; full Retool feature parity, vendor hosting and support are not included. - connectors, component library, permissions, workflows, and hosted runtime: retain the paid product if this capability is essential; it is outside this bounded build. - hundreds of connectors: retain the paid product if this capability is essential; it is outside this bounded build. - pixel-perfect app design: retain the paid product if this capability is essential; it is outside this bounded build. - mobile app-store builds: retain the paid product if this capability is essential; it is outside this bounded build. - enterprise permissions and scale: 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 · Retool ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | products(id,sku,name,stock,revision); adjustments(id,product_id,delta,reason,actor,at); users(id,email,password_hash,role); sessions(id,user_id,expires_at) | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Inventory contract | Create a fixed product schema and seeded data; expose paginated search and detail views. | Keep the acceptance contract: An adjustment of -6 against stock 5 is rejected. Replace only this module after replaying its fixture; preserve ids and existing records. | | Authorized actions | Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. | Keep the acceptance contract: A viewer posting directly to adjustment receives 403 and creates no audit entry. Replace only this module after replaying its fixture; preserve ids and existing records. | | Auditable exchange | Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. | Keep the acceptance contract: One invalid SKU aborts the import and names the row. 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 retool. | 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 · Retool product build - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. - Implement milestone by milestone from `MILESTONES.md`; keep each change reviewable and leave the application runnable at every commit. - Treat authentication, payments, encryption, imports, webhooks and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a check pass. - Put every external service behind an interface with a deterministic fake for tests. - Add migrations and rollback or recovery notes for every persistent data change. - Log useful operational context without credentials, tokens, passwords or personal data. - Update documentation and run every check before completing a milestone. ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - The useful replacement is this internal tool, not a generic low-code platform. - A hidden button is not an authorization boundary. - Never accept user SQL, arbitrary database credentials or unbounded file uploads. - 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 · Retool 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 one private inventory administration tool with audited actions, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: products(id,sku,name,stock,revision); adjustments(id,product_id,delta,reason,actor,at); users(id,email,password_hash,role); sessions(id,user_id,expires_at). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Two products with stock 5 and 0; owner, operator and viewer identities. 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 · Inventory contract Inventory contract for Retool: Create a fixed product schema and seeded data; expose paginated search and detail views. ### Steps 1. Create a fixed product schema and seeded data; expose paginated search and detail views. Create a fixed product schema and seeded data; expose paginated search and detail views. Files: `features/inventory_contract.py`, `templates/inventory_contract.html` 2. Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. Implement adjustment as an explicit operation with a reason and expected revision, not a raw SQL textbox. Files: `features/inventory_contract.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: An adjustment of -6 against stock 5 is rejected. Then check: Two adjustments against the same revision conflict instead of losing an update. 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_inventory_contract.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] An adjustment of -6 against stock 5 is rejected. - [ ] Two adjustments against the same revision conflict instead of losing an update. ### Watch out - The useful replacement is this internal tool, not a generic low-code platform. ## M3 · Authorized actions Authorized actions for Retool: Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. ### Steps 1. Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. Implement owner/operator/viewer roles with password-hashed login and expiring server sessions for shared mode. Files: `features/authorized_actions.py`, `templates/authorized_actions.html` 2. Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. Authorize adjustment endpoints server-side and append actor, before/after stock and reason atomically. Files: `features/authorized_actions.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: A viewer posting directly to adjustment receives 403 and creates no audit entry. Then check: An operator adjustment changes stock and creates exactly one audit record. 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_authorized_actions.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A viewer posting directly to adjustment receives 403 and creates no audit entry. - [ ] An operator adjustment changes stock and creates exactly one audit record. ### Watch out - A hidden button is not an authorization boundary. ## M4 · Auditable exchange Auditable exchange for Retool: Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. ### Steps 1. Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. Add CSV product import with dry-run validation and export current stock plus a separate adjustment ledger. Files: `features/auditable_exchange.py`, `templates/auditable_exchange.html` 2. Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. Require owner confirmation for bulk changes and retain batch ids to trace imported corrections. Files: `features/auditable_exchange.py` 3. Exercise the acceptance fixture Use Two products with stock 5 and 0; owner, operator and viewer identities. Check: One invalid SKU aborts the import and names the row. Then check: Every exported stock correction can be traced to an actor and reason. 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_auditable_exchange.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] One invalid SKU aborts the import and names the row. - [ ] Every exported stock correction can be traced to an actor and reason. ### Watch out - Never accept user SQL, arbitrary database credentials or unbounded file uploads. ## M5 · Portable delivery and clean-start proof Finish the Retool 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: Inventory contract; Authorized actions; Auditable exchange. 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 retool. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two products with stock 5 and 0; owner, operator and viewer identities. 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 one private inventory administration tool with audited actions 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 retool. 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 · Retool ## 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 retool. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two products with stock 5 and 0; owner, operator and viewer identities. 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 Inventory contract, Authorized actions, Auditable exchange. 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 - [ ] An adjustment of -6 against stock 5 is rejected. - [ ] A viewer posting directly to adjustment receives 403 and creates no audit entry. - [ ] One invalid SKU aborts the import and names the row. - [ ] 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 Retool 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/retool # 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
People still pay for Retool because the builder is only useful when its runtime, connectors, permissions, and deployments remain boring for years. The recurring cost buys schema migration, auth, permissions, connector drift, queues, deployments, backups, and auditability, not just the visible interface.
xconnectors, component library, permissions, workflows, and hosted runtime
xhundreds of connectors
xpixel-perfect app design
xmobile app-store builds
xenterprise permissions and scale
share on X ↗"I just replaced Retool ($15/mo) with one prompt"
Don't feel like building it? These folks already made it free.
BudibaseInternal apps, forms, automations, and portals in one box; much closer to Knack than its developer branding suggests.open source↗
Appsmith FreeFive people can build and run database-backed internal apps in the hosted product without paying.free↗
Directus Self-HostedA polished data studio with tables, forms, dashboards, flows, and APIs; free only below its organization-size ceiling.free↗all 5 free alternatives to Retool →· no votes, no pay-to-list · just what's real
Retool pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0/user | $0/user | Up to 5 users; 500 workflow runs/month; 5 GB storage; 20 agent hours; 250 AI credits |
| team, builder | — | $10/user | Builder seat; 5,000 workflow runs/month per organization; 1,000 pooled AI credits after introductory bonus |
| team, internal user | — | $5/user | Internal end-user seat; shares the organization's workflow and AI allowances |
| business, builder | — | $50/user | Builder seat; 5,000 workflow runs/month; 3,000 pooled AI credits; advanced permissions and environments |
| business, internal user | — | $15/user | Internal end-user seat; business controls |
| enterprise | custom | — | Custom builder/internal/external users, support, security and deployment terms |
free tier5 total users; 500 workflow runs/month; 5 GB storage; 20 agent hours; 250 AI credits
billingmonthly + annual; published self-serve figures are role-based per user
hidden costsBuilder and internal-user seats have different rates; extra workflow capacity costs $75 per 5,000 runs, AI credits are pooled and reset without rollover, Agents are metered separately, and external-user pricing changes after the included band
verified 2026-08-14 · source ↗
Vibecode Retool
Kinda. The core of Retool is buildable in a weekend with the prompt on this page, but there are real gaps: connectors, component library, permissions, workflows, and hosted runtime, hundreds of connectors. Read the honest list above before committing.
How much does Retool cost?
Retool costs about $15/month (Team, checked 2026-07-31), which is $180 per year.
What do I lose by replacing Retool?
Honestly: connectors, component library, permissions, workflows, and hosted runtime; hundreds of connectors; pixel-perfect app design; mobile app-store builds; enterprise permissions and scale. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Retool?
Yes: Budibase (Internal apps, forms, automations, and portals in one box; much closer to Knack than its developer branding suggests.) Appsmith Free (Five people can build and run database-backed internal apps in the hosted product without paying.) Directus Self-Hosted (A polished data studio with tables, forms, dashboards, flows, and APIs; free only below its organization-size ceiling.) All 5 curated free alternatives are at vibecodeit.com/retool/alternatives. The prompt is for when you want it exactly your way.