Meet Notes
Where things stand
Compute is settled for now: Reid rents cloud machines to test, and Joe decides what to buy once those numbers are in. Reid is running the Ector County OCR and will send Joe a write-up today. Claude moves the meeting app onto Reid's cloud server and fixes the problems Reid's walk-through found.
Suggested Claude's overnight update: Reid ran his first real call on the new meeting page on Oct 26, and it showed the page is not yet easy for someone who did not build it: six problems, like a typed question vanishing and stray talk being counted as a yes. Joe and Reid also agreed that the meeting notes, Reid's intake app and the inventory view become one app, each part kept separate behind one front door. What matters next is getting the meeting app running on Reid's cloud server so anyone can use it, then fixing the walk-through problems.
Not confirmed yet. Claude checks it with you at the next call.
Status board
Projects · 3
Meet Notes app
Is it a yes to keeping everything said, even unused ideas? And if yes: full transcript, parked idea records, or both?
Suggested Get the cloud server's address and access from Reid, run the meeting app there, then fix the six walk-through problems · Reid (server access) and Reid's write-up on the plan for the code homes
Experiment 1: four ways to build the co-worker
What are the four ways (arms)? The records in the series folder never name them, and the tool for each arm is still unconfirmed (todo T3).
Suggested In one real call: name the arms and the one thing that changes between them, answer the eight run details (now including one rented machine or one per arm), confirm or reject Excel as the answer sheet, and fix the words of the written task; then Claude writes the setup down · Joe and Reid, next working call
Send one document at a time through deal intake
When does the single-document build resume, and is a small new entry point OK to build (to-do T8)?
Suggested Joe says when the one-document build resumes and whether the small hand-one-file entry point is OK; then the group confirms Excel as the answer source on a real call · Joe (to-do T8) and a spoken yes on Excel as source
Suggested All 3 are Claude's suggestions, not discussed yet. Each waits on the next call.
Topics · 19
AI server hardware
Reid sets up the rented cloud test; Joe picks the two setups and the rent-or-own point
Reading old county records: OCR plus a vision model
Reid runs the OCR on the Ector County records and compares with Title Lab
Testing the new meeting page
Controls tried; reload test passed
What one AI agent run looks like, technically
Answer the eight run questions
The interface any AI plugs into
Decide one shared interface or per-agent tools
The experiment system and its arms
Write the setup down once the arms are named
How runs are scored: the eval criteria
Joe names the memo; Claude puts it on the page
One app for meetings, intake and our data, running in the cloud
Confirm the site work list order at tomorrow's sync
Getting every deal's record to 100%
Seed with what we have; close the gaps later
Deal intake comes first: a complete inventory record for every closed deal
Seed the inventory with the 48 deals already run through intake
County data plan
Name an owner to pick how to search the thumb drive's county records
A shareable map of what we own
Add-on to the framework, after intake
What happens after intake: the steps that close every loop
Wait until intake works, then test the steps after it
Where all of this is going
Possible vision, not confirmed
Reid's check: how often plain code matches documents to deals
Baseline set for check stubs: 81%
The answers we test against
27 documents proposed across 8 types, waiting for Reid. A few leases and the 2 tax documents need hand checks.
Measuring success
Two measures: how good each step is, and whether it runs end to end with little supervision. The key number: how often it was wrong and didn't ask. Still to write: what counts as a pass.
Phase 1 and Phase 2 questions
Phase 1 is settled enough. Phase 2 is answered for taking documents in and filling the inventory; the later steps wait for experiment 1.
Revenue and tax data
Reid loaded the historical revenue and tax data into our database. It still needs linking to deals and leases.
Decided · 4
Scanner and storage
Decided: the Fujitsu scanners with their free software, saving into one SharePoint folder. Open: can the free software split a stack into separate documents?
Everything is a record
Decided. A draft of what a document record holds is written; Reid reviews it and answers its 3 questions.
Safety rules
Decided: a person approves every outside email, every approval shows its proof (page, quote, why), and nothing leaves the building during tests.
Which transfer work to automate first
Decided: take documents in, fill the inventory, find the operator contact, notify the operator, read replies, and file the paperwork, with a needs-a-person list. No comparison with how it is done today.
The others wait on the next call.
Not filed yet 26
From Oct 26 · Joe, Reid
To-do
Send Joe a write-up after the call: what we discussed, what is done, what is left, and the plan for the repositories
To-do
Put the records into the sandbox database and define the actions from the transfer automation plan, using plain code first and an AI setup only where code falls short
Decision
The intake in the Command Center is the old first version and is retired; the one we build on is in the deal data project
To-do
Meet again tomorrow: wearables, and getting the environment set up so we can start processing records (tidy-up a week later)
To-do
Get Joe's answers to Reid's questions to Reid; they were given to Claude but never reached him
To-do
Finish the answer sheet for the intake app tests, so the setups on the Cletus rig are scored for accuracy, not only for agreeing with each other
From Oct 22 · Joe, Reid
To-do
Move the scanner work to next week so the title index gets attention first
Decision
Use the Excel inventory as the source for the title index
From Oct 22 · Joe, Reid
To-do
Move the scanner work to next week so the title index gets attention first
Decision
Use the Excel inventory as the source for the title index
From Oct 21 · Joe
Decision
This meeting (2026-10-21-qkv-fney-xag) is 30 minutes long.
File: Update: Reid, Oct 19 (night)
File: Update: Reid, Oct 19 (evening)
File: Update: Reid, Oct 19 (morning)
From Oct 16 · Joe, Reid, Keegan
File: Memo B: how we pick a winner for Cletus
File: Memo A: which AI-with-its-own-desk versions to test
File: Google Meet notes for the whole call (Gemini)
From Oct 15
File: AI server purchase: updated recommendation (Dell)
File: Research: four ways to build the co-worker
File: Compute cost and breakeven calculator
File: Inference Server Design Lab
File: Experiment 1: the proposed documents
From Oct 14
File: What a document record holds (draft for Reid)
File: Meet Notes UI/UX proposal
From Oct 13
File: Experiment 1 handoff (draft)
File: Transfer Automation, in plain English
Claude asks where these go at the next call.
Meetings
Mon, Oct 26, 2026
Reid's first call on the new site.
Thu, Oct 22, 2026
Fourth practice call on the new page, run by Claude end to end with a spoken script and two signed-in profiles.
Thu, Oct 22, 2026
Third practice call on the new page, run by Claude with a spoken script and a second signed-in profile.
Earlier meetings · 13
Thu, Oct 22, 2026
Second practice call on the new page, Joe and Reid, 15 minutes.
Wed, Oct 21, 2026
Tue, Oct 20, 2026
A short, twice-interrupted call.
Tue, Oct 20, 2026
The experiment system and its arms, What one AI agent run looks like, technically, How runs are scored: the eval criteria, The interface any AI plugs into
Mon, Oct 19, 2026
Mon, Oct 19, 2026, 11:09
Joe and Reid lined up Reid's work.
Mon, Oct 19, 2026
Mon, Oct 19, 2026
Deal intake comes first: a closed deal becomes a complete inventory record, and every later step trusts it.
Fri, Oct 16, 2026
First call chaired by Claude.
Thu, Oct 15, 2026
Wed, Oct 14, 2026
Tue, Oct 13, 2026
Fri, Oct 9, 2026
No vision yet. Claude will ask for one at the start of the call.