data and metadata inventory stuff

docs/data_inventory.md

@@ -1,7 +1,32 @@
 # Countydata inventory
 
-Inventory date: 2026-07-15. All inspection was performed with read-only
-transactions and aggregate queries; no identifiers were exported.
+Inventory date: 2026-07-15; live schema revalidated 2026-07-21. All inspection
+was performed with read-only transactions, metadata queries, aggregate queries,
+and bounded JSON field-path sampling; no identifier values were exported.
+
+## Live access and full-schema boundary
+
+The July 21 validation connected successfully from this VS Code workspace using
+TLS 1.3 and a session forced into read-only mode. It found 24 visible non-system
+relations in `countydata`. The repeatable metadata-only inventory is
+`scripts/inventory_metadata.py`, exposed as the VS Code task **Countydata:
+inventory metadata safely**.
+
+The analytical `data` schema contains 10 normalized tables. Four
+`fdw_countydata` relations and the `fdw_data.dmv_tax_record*` relations are
+source mirrors rather than additional populations. The remaining operational
+relations contain API-key names and secrets, application usernames/emails and
+password hashes, invitations, sessions, IP addresses, event logs, upload
+contents, and ingest state. Their field names were inventoried, but their row
+values were not read because they are unrelated to the project and sensitive.
+
+A bounded raw-JSON field-path sample found vehicle attributes plus VIN and
+plate identifiers, station/certificate/calibration fields, technician-license
+numbers, odometer, engine/fuel/GVWR/transmission fields, DTC/PID arrays,
+readiness monitors, MIL state, and visual inspection results. No owner-name
+field was observed in that sample. This does not prove that every historical
+source file has the same shape, so raw JSON remains private and out of the
+public application.
 
 ## Accessible databases