Build Glide

The build, in order

1. 1

   Local foundation and data contract

   hideshow

   Create the runnable local foundation for one mobile-friendly client-and-job portal rather than a no-code builder, including the real schema and acceptance fixture.

   1. 1.1Create 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.pyrequirements.txt.env.example.gitignore

      terminalcopy

      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. 1.2Implement storage and seed the named fixture

      For database-backed state create schema.sql and db.py using this model: clients(id,name,email,notes); jobs(id,client_id,title,status,due_date,revision); import_batches(id,checksum,at); audit(id,entity_id,event,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: A CSV with two clients, three jobs, a quoted comma and one invalid client reference. Re-running init must not erase data.

      Files schema.sqldb.pymanage.pyfixtures/README.md

      terminalcopy

      python manage.py init
      python manage.py seed

   3. 1.3Protect 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.pytemplates/base.htmltest/test_foundation.py

   done when · tick each as it passes

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

   next phase
2. 2

   Import the actual dataset

   hideshow

   Import the actual dataset for Glide: Create a fixed client/job schema and a CSV mapping screen; preserve source ids in a mapping table.

   1. 2.1Create a fixed client/job schema and a CSV mapping screen; preserve source ids in a mapping table.

      Create a fixed client/job schema and a CSV mapping screen; preserve source ids in a mapping table.

      Files features/import_the_actual_dataset.pytemplates/import_the_actual_dataset.html

   2. 2.2Preview row errors and commit one import transaction after confirmation; hash batches to flag accidental repeat imports.

      Preview row errors and commit one import transaction after confirmation; hash batches to flag accidental repeat imports.

      Files features/import_the_actual_dataset.py

   3. 2.3Exercise the acceptance fixture

      Use A CSV with two clients, three jobs, a quoted comma and one invalid client reference. Check: The invalid client reference reports a row number and prevents the batch commit. Then check: A quoted comma in a client name survives import and export. 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_import_the_actual_dataset.py

      terminalcopy

      python -m unittest discover -s test

   done when · tick each as it passes

   • The invalid client reference reports a row number and prevents the batch commit.
   • A quoted comma in a client name survives import and export.

   watch out

   • Build the portal the user needs, not a drag-and-drop app designer.

   next phase
3. 3

   Phone workflow

   hideshow

   Phone workflow for Glide: Create searchable client list, client detail and job forms with large labelled controls and explicit status choices.

   1. 3.1Create searchable client list, client detail and job forms with large labelled controls and explicit status choices.

      Create searchable client list, client detail and job forms with large labelled controls and explicit status choices.

      Files features/phone_workflow.pytemplates/phone_workflow.html

   2. 3.2Use optimistic revisions on edits and preserve form input after a validation or conflict response.

      Use optimistic revisions on edits and preserve form input after a validation or conflict response.

      Files features/phone_workflow.py

   3. 3.3Exercise the acceptance fixture

      Use A CSV with two clients, three jobs, a quoted comma and one invalid client reference. Check: At 375px width a user can add a job without horizontal scrolling. Then check: Two tabs editing one job cannot silently overwrite each other. 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_phone_workflow.py

      terminalcopy

      python -m unittest discover -s test

   done when · tick each as it passes

   • At 375px width a user can add a job without horizontal scrolling.
   • Two tabs editing one job cannot silently overwrite each other.

   watch out

   • A secret embedded in a URL leaks through history and referrers; do not use it for access control.

   next phase
4. 4

   Crew access and export

   hideshow

   Crew access and export for Glide: In product mode add owner/member/viewer accounts and check role and job ownership on every mutation; indie remains loopback-only.

   1. 4.1In product mode add owner/member/viewer accounts and check role and job ownership on every mutation; indie remains loopback-only.

      In product mode add owner/member/viewer accounts and check role and job ownership on every mutation; indie remains loopback-only.

      Files features/crew_access_and_export.pytemplates/crew_access_and_export.html

   2. 4.2Export clients and jobs together with a schema version and document how to change fields in code.

      Export clients and jobs together with a schema version and document how to change fields in code.

      Files features/crew_access_and_export.py

   3. 4.3Exercise the acceptance fixture

      Use A CSV with two clients, three jobs, a quoted comma and one invalid client reference. Check: A viewer receives 403 when directly posting a job edit. Then check: A fresh database imports the exported bundle with identical client/job links. 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_crew_access_and_export.py

      terminalcopy

      python -m unittest discover -s test

   done when · tick each as it passes

   • A viewer receives 403 when directly posting a job edit.
   • A fresh database imports the exported bundle with identical client/job links.

   watch out

   • Shared editing requires server authorization even when the UI hides the edit button.

   next phase
5. 5

   Portable delivery and clean-start proof

   hideshow

   Finish the Glide replacement with a documented first-run path and a recoverable export.

   1. 5.1Write the user-facing runbook

      Document prerequisites, every configuration variable, data locations and the three domain workflows: Import the actual dataset; Phone workflow; Crew access and export. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them.

      Files README.md.env.example

   2. 5.2Create 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 glide. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A CSV with two clients, three jobs, a quoted comma and one invalid client reference. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy.

      Files OPERATIONS.mdscripts/backup.py

   3. 5.3Reproduce 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.mdverification.md

      terminalcopy

      python -m pip install -r requirements.txt
      python -m unittest discover -s test

   done when · tick each as it passes

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