all public dashboard stuff changed to static dashboard stuff

README.md

@@ -31,7 +31,6 @@ Start with the [final report](docs/final_report.md). Supporting deliverables:
 - [Private-to-public architecture](docs/architecture.mmd)
 - [10-minute presentation outline](docs/presentation_outline.md)
 - [Dashboard demo script](docs/demo_script.md)
-- [Optional public-hosting notes](docs/bolt_deployment.md)
 
 The [data inventory](docs/data_inventory.md) and archived
 [project options](docs/project_options.md) provide source-discovery history;
@@ -63,7 +62,7 @@ python3 -m venv .venv
 
 The local `.env` contains PostgreSQL connection values and the project-specific
 `VIN_HASH_KEY`; it is excluded from Git. Never put those values in source code,
-screenshots, browser JavaScript, presentation materials, or a Bolt project.
+screenshots, browser JavaScript, or presentation materials.
 
 ## Safe database access in VS Code
 
@@ -165,11 +164,11 @@ authenticate the network transport, so use a trusted demo network.
 
 ## Public hosting is not required
 
-The current presentation plan is the same-network live demo above. Nothing
-needs to be uploaded or published, and the server exposes only the dashboard's
-explicit static-file allowlist. The older
-[public-hosting checklist](docs/bolt_deployment.md) is retained only in case the
-delivery requirements change later.
+The presentation plan is the same-network live demo above. Nothing needs to be
+uploaded or published, and the server exposes only the dashboard's explicit
+static-file allowlist. If public hosting is ever reconsidered, publish only a
+separately reviewed copy of the `dashboard/` directory—never the private source
+repository.
 
 ## Author
 

dashboard/README.md

@@ -92,7 +92,7 @@ records must never enter this directory.
 
 ## Public hosting is not required
 
-The current delivery path is the same-network live demo. No Bolt project,
-public URL, dependency install, or build step is needed. If public hosting is
+The delivery path is the same-network live demo. No public URL, dependency
+install, or build step is needed. If public hosting is
 ever reconsidered, publish only a separately reviewed copy of this dashboard
 directory—never the private source repository.

docs/data_inventory.md

@@ -112,7 +112,7 @@ possible, but must never appear in public outputs.
 - Extreme repeat counts exist and require invalid/shared-identifier filtering.
 
 Use a salted one-way internal token if a stable identifier is needed during
-feature engineering. Never send VINs or plates to the browser or Bolt.
+feature engineering. Never send VINs or plates to the browser.
 
 ## Operational and sensitive relations
 

docs/final_report.md

@@ -222,4 +222,3 @@ ranking, production model, diagnosis, or individual decision tool.
 - [Private-to-public architecture](architecture.mmd)
 - [10-minute presentation outline](presentation_outline.md)
 - [Dashboard demo script](demo_script.md)
-- [Optional public-hosting notes](bolt_deployment.md)

docs/project_options.md

@@ -162,7 +162,7 @@ Use option 1 as the main story and option 6 as its data-engineering foundation:
 3. Compare a transparent logistic baseline with a tree model.
 4. Validate on a later time period and separately by county/source.
 5. Export only aggregate scorecards, curves, and de-identified model outputs.
-6. Build the public Bolt dashboard over those safe outputs.
+6. Build the static dashboard over those safe outputs.
 
 This gives the project a coherent end-to-end narrative across data engineering,
 analytics, machine learning, responsible validation, and product design.