sync: auto-sync from DESKTOP-0O8A1RL at 2026-05-13 10:53:57

Author: Mike Swanson
Machine: DESKTOP-0O8A1RL
Timestamp: 2026-05-13 10:53:57
This commit is contained in:
2026-05-13 10:53:57 -07:00
parent c74e5bccbb
commit 70ba676176
3 changed files with 398 additions and 1 deletions

View File

@@ -198,3 +198,45 @@ irm 'https://rmm.azcomputerguru.com/install/LIGHT-PEAK-6399/windows' | iex
- **GND-SERVER ITGlue:** https://azcomputerguru.itglue.com/8731407/configurations/78496804
- **GuruRMM INSTALL_DIR:** `C:\Program Files\GuruRMM`
- **LIGHT-PEAK site key:** `LIGHT-PEAK-6399`
---
## Update: 10:52 MT — Grabb & Durando pre-meeting intel
### Session Summary
Post-compaction continuation focused entirely on the Grabb & Durando AI demand letter project. Mike reported three pieces of pre-meeting intelligence gathered directly from Robert Grabb. Incorporated the intel into the meeting prep document and discussed expectation management strategy.
Robert's primary concern about the AI API is training data and document leakage — rooted in his experience with the ChatGPT web UI, where full documents are uploaded. He does not yet understand the distinction between the web UI and the API. Under Anthropic's standard API terms, inputs are not retained or used for training. The remaining open compliance question is whether G&D needs a Business Associate Agreement (BAA) with Anthropic given that case files contain PHI (medical records). The meeting prep question was updated from a vague "what's your position" framing to a specific pivot: explain API vs. web UI, then ask about the BAA.
Robert confirmed he does not want files duplicated or uploaded to a second location — the app must read directly from the existing F: drive SMB share (`F:\Shares\Company Data\CLIENTS\`). This was already the preferred architecture; it is now a stated client requirement.
The most significant intel: asked "what does this app do for you in a year?", Robert answered "I see this replacing nearly all of my legal assistants entirely." He has also tested AI on pleadings and was impressed with output quality. He does not express concern about inaccuracy. This indicates Robert is thinking platform-scale practice automation, not a demand letter efficiency tool. Phase 1-3 as scoped delivers demand letters only. Mike will manage this expectation gap by exuding caution throughout the build process and explicitly telling Robert that staff offloading cannot happen until considerably later in development. The Phase 1 fact sheet artifact (structured extraction before any letter is written) will itself demonstrate why human review is required, training the client on the workflow rather than requiring Mike to argue about it.
GND-meeting-prep.txt was updated: added a pre-meeting intel section at the top, marked questions #5 and #7 as answered with follow-up notes, updated the commit checklist with the BAA question and an explicit scope conversation item.
### Key Decisions
- API vs. web UI explanation is the core deliverable on question #5. Resolve Robert's concern by explaining the mechanism, then pivot to the BAA as the actual open compliance question.
- F: drive direct SMB access confirmed as a stated client requirement, not just an architectural preference.
- Explicit scope conversation must happen at the meeting. Robert's "replace legal assistants" vision and the Phase 1-3 demand letter scope are not the same project. Mike will surface the gap and frame a Phase 4+ roadmap without committing to it.
- Expectation management via demonstrated caution rather than explicit scope negotiation. Build pace and review cycle rigor enforce the timeline naturally; the Phase 1 fact sheet teaches the client why human review is necessary through experience rather than argument.
### Configuration Changes
- `clients/grabb-durando/ai-demand-review/GND-meeting-prep.txt` — Updated: added INTEL FROM PRE-MEETING CONVERSATIONS section, marked questions #5 and #7 as answered, updated checklist with BAA question and scope conversation item.
### Pending / Incomplete Tasks
- **Grabb & Durando scoping meeting:** Mike gathering more intel. Key open items: style trigger rule (short-form vs. full-narrative), 3-5 additional closed test cases beyond SWAILIEH and ORTEGA, BAA question, explicit scope confirmation.
- **LIGHT-PEAK agent install:** CI rebuild triggered by ba4e86a push — re-run install once build completes if not already done.
- **GND-SERVER Adobe Acrobat:** Unconfirmed — ask Jeff at meeting or verify via ScreenConnect.
- **GND-SERVER storage:** 834 GB free (21%) — flag to Robert at meeting.
- **Confidentiality/BAA sign-off:** Required before evaluation run on 161-case archive. Follows from API/BAA conversation at the meeting.
- **Howard hook setup:** Verify on Howard-Home and ACG-TECH03L (carried over).
### Reference Information
- **Meeting prep doc:** `clients/grabb-durando/ai-demand-review/GND-meeting-prep.txt`
- **PI case folder:** `F:\Shares\Company Data\CLIENTS\` (161 cases, 90.5 GB, near-standardized naming)
- **Anthropic API data policy:** Inputs not retained or used for training under standard API terms. BAA available for HIPAA covered entities on request.