Posts

VDP Development Update — September 27, 2026

VDP Development Update — September 27, 2026 Strategy Workbench Expanded, Issue Packet Export Added, and Backup Verified VDP_End_of_Day_Summary_2026-09-27.txt VDP Development Update — September 27, 2026 Strategy Workbench Expanded, Issue Packet Export Added, and Backup Verified Today’s Voter Decision Project work focused on two goals: making the local VDP development environment more reliable and advancing the Strategy Workbench so it can produce a structured VDP Issue Packet. Backup System The scheduled backup from C:\VDP2026 to BASEMENTONE was investigated after repeated failures. The problem was traced to SMB authentication rather than network reachability. Credentials were corrected, the backup was run successfully, and a source/backup file comparison produced matching SHA-256 hashes. The actual Windows Scheduled Task was then tested without relying on an existing SMB session and returned LastTaskResult = 0. The backup repair and verification are now complete. Strategy Workbench...

VDP Development Update — September 26, 2026

  VDP Development Update — September 26, 2026 Today’s work focused on improving the reliability of the VDP Strategy Workbench and preparing a cross-machine Playwright testing setup. Completed and Accomplished 1. Improved Dashboard Button11 logic - Updated the Strategy Workbench launch logic so Button11 can detect whether the Workbench is already running before attempting to start another Flask instance. - Replaced the earlier simple port check with an HTTP-level Strategy Workbench check. - Removed the need for the old IsPortOpenAsync helper. - Added logic to open the Workbench in the browser when it is already available. - Added validation for the Python executable and run.py before attempting startup. 2. Identified and corrected Python environment issues - Discovered that the existing Strategy Workbench .venv under the LEFTBRAIN shared folder referenced an obsolete Python 3.11 installation. - Confirmed LEFTBRAIN currently has Python 3.14, 3.12, and 3.9 installed. - Determined ...

Work today

Finished organizing seven ChatGPT conversations into the correct Project and renamed them with consistent prefixes such as [REMOTE], [SYSTEM], [VIRTUAL], and [MEDIA]. This was necessary to make past technical work easier to find and manage. Debugged and stabilized the Playwright ChatGPT Project Mover. We corrected the VLC chat title, fixed a timing problem with the Project “Show more” list, and confirmed that all seven chats now show MOVED and RENAMED. This was necessary so the automation can be reused reliably instead of moving and renaming chats manually. Created known-good backups of the working CSV and Python mover script. This provides a safe recovery point before making future changes. Created a Word user guide documenting how to run, verify, troubleshoot, and recover the Project Mover. This was necessary so the process can be repeated later without reconstructing the steps from memory. Freed space on the C: drive, including clearing the Python pip cache and moving Playwright...

Built WINDOWS RECOVERY REPAIR TOOLKIT

Image
https://www.facebook.com/reel/1375009104798998 These local files were selected for this Social Publish job but are not embedded by the current Blogger path: Windows_Recovery_Toolkit.jpg

VDP Web Development History — 2026-09-18 14:47

CURRENT_VERSION_SUMMARY.pdf Open CURRENT_VERSION_SUMMARY.pdf in Google Drive Published automatically from AF Tools Social Publish.

VDP Daily Dialog — 2026-08-30_1530

VDP Daily Dialog — 2026-08-30_1530 This entry records a NotebookLM-generated VDP Audio/Video Overview. The overview is AI-generated and may contain interpretation errors. Today’s work moved the project forward in a few concrete ways: • Narrowed the current VDP experiment toward testing one civic issue through a transparent, auditable citizen-to-representative process • Began documenting the project's WHY, PROBLEM, HYPOTHESIS, BOUNDARY, CURRENT EXPERIMENT, and NEXT ACTION • Began building a daily publication process so project progress can be documented publicly rather than disappearing into private notes and experiments • A continuing design concern is ensuring that AI helps citizens communicate and reason without becoming a new political gatekeeper • Continued inventorying the local VDP infrastructure, including BASEMENTONE file-server access, storage, and remote administration • Created 3 scheduled automation tasks. One is a generalized backup to the BASMENTONE server. Another ...

Can I have AI create me a website to be used by voters?

 As an experiment, I ask a "What if" Specifically, is it possible to create a "Bracket" as might be used during March Madness - but with a reimagining     I nstead of basketball teams competing Voters compete.      Instead of playing a physical game... 2 voters/households anonymously submit insights to an AI specific to the household. Each AI summarizes the insights and submits to a clearing house to be matched Each registered household insights are to be matched with a voter/household with political positions that are diametrically opposed The resulting paired insight from the AI clearing house are submitted to voter for approvals Both households must approve  If no approval AI will repeat summarize process AI will repeat summarization and resubmit to voter/household for approval Repeat for X number of times.   When summarized insights are approved A new voter/household that is determined to be in opposition is identified. A new sequence wit...