Joe and Reid lined up Reid's work. His top priority today is finishing the cloud server and deploying the app. After that he follows up on the pre-experiment tests. The two tests, their write-up and the grading code are done. The early conflict checks are parked until the inventory and the experiment are done. The site work list for Claude: latest answer on top, faster answers, confirm with a button after sign-in, an after-call to-do email, a link with every doc, simple for anyone, works on a phone, small review fixes, and Claude running the call more actively. Joe and Reid sync again tomorrow.
What this call produced 9
Decision D10: The site work list for Claude, in this order: latest answer on top; faster answers; confirm with a button after sign-in; after-call to-do email (or each person's to-dos in the app); a link with every doc; simple for anyone; works on a phone; small review fixes; Claude runs the call more actively
Requirement R4: After each call, email each person their own to-do list in plain text, one item per line, so they can copy each item straight into a work session
What will Reid work on between now and the next call?
Partly met
Reid's top priorities are set (deploy the server, then the test follow-up), but not every item in his doc was marked
Done when: Each open item for Reid is marked keep, done, or drop, with the top few in order · Moves the vision: Deal intake first, then the experiment
Full close-out
Not decided yet
The site work list and its order, because Joe read it out, but the call ended before a plain yes. Waiting on: Joe and Reid, at tomorrow's sync
What happens to the 27 test documents, because Expanding them to whole deal folders came up, but nothing was settled. Waiting on: Joe and Reid
To-dos by person
Claude (owner unconfirmed): Explore faster answers on the page: stream replies live, try the Claude Chrome extension, and find the path with the fewest handoffs
Reid (owner unconfirmed): Follow up on the tests done before experiment 1: anything still open or blocking it, and if nothing, what we can test next
Reid: Finish setting up the cloud server and deploy the app (today's top priority)
Which part of the vision moved
Deal intake stays first. Reid deploys the cloud server today, so anyone can run calls without Joe's laptop.
Topics carried forward
One app for meetings, intake and our data, running in the cloud
Deal intake comes first: a complete inventory record for every closed deal
Getting every deal's record to 100%
County data plan
Nothing in: Project stage changes, Drafts waiting for review.
Claude's replies · 7
Site list reviewed, and to-dos
I reviewed your answers on the site list. Everything is kept, with two changes and one addition.
Latest answer on top: kept.
Faster answers: kept. Claude explores streaming replies live, the Claude Chrome extension, and the path with the fewest handoffs. Putting Claude in the browser is out, because pay-per-use fees cost too much.
Confirm with a button: kept, after sign-in.
After-call email: changed. If email isn't ready, each person can at least see their own to-dos and what they contributed in the app.
A link with every doc: kept.
Simple for anyone: changed, to be more specific: someone listening on the road should still be able to follow the call.
Works on a phone: kept.
Small review fixes: kept.
New: Claude runs the call more actively. It keeps us on track, tees up what to focus on next, and keeps the call efficient.
I didn't catch one word: something about "having an in..." that should be added if it's missing. Say it again if it matters.
To-dos right now
Who
To-do
Reid
Finish the cloud server and deploy the app (today's top priority; confirmed)
Reid
After the server: follow up on the pre-experiment tests
Reid
Answer the open items in his doc (Joe has the link)
Joe
Review Reid's checker branch; answer his 3 questions
Joe
Settle the AI versions to test, with Reid
Claude
The site work list above, starting with #1 and #2
Joe, Reid
Sync again tomorrow
To close, say "yes" or "that's wrong": the site work list above, in that order.
Site work list for Claude
Yes, I have it. Here is the site work list from this call and the last one, in the order I'd do it. Say "that's wrong" about anything, or move items up or down.
#
Change
Asked by
1
The latest request and its answer at the top. Right now it's hard to tell anything happened after "Hey Claude".
Reid
2
Faster answers. Cut the wait between asking and seeing the reply, so Claude feels like it's in the app.
Joe, Reid
3
Confirm with a button, not only by voice. Only the person running the call can press it, after signing in, so nobody else can approve things for them.
Joe
4
An email after each call to each person with their own to-dos, one per line, ready to copy.
Reid
5
A link with every doc Claude mentions.
Joe
6
Simple enough for anyone, technical or not.
Keegan
7
Works well on a phone, including the "Clears when" line that phones hide today.
Keegan
8
Small fixes found in review: notes and waiting items look the same; every label is green; filler text on empty items; the help page still says "not settled".
Claude
Already done today: the new design is now what every link opens, and it only shows something as confirmed after a real yes.
One thing to know about #3: today, approvals only count when spoken by the person running the call. A button needs sign-in first, which is the work running now. So #3 comes after sign-in lands.
What Reid said, and improving the site
What Reid just said:
His top priority today: finish setting up the cloud server and deploy the app himself. Joe said yes.
Next: follow up on the tests he ran before experiment 1. Is anything still open or blocking the experiment? If not, what can we test next?
How he wants his work handed to him: an email after each call that says what we talked about and exactly what he needs to do, in plain text. Six items means six lines he can copy, one each, into separate work sessions and run at once. Then the system tells him when it needs something from him.
Filed: Reid's two to-dos, and the after-call email as a requirement for the app.
Improving the site for how we use it
Here's what the team has asked for so far:
Simple enough for anyone on the team, technical or not (Keegan).
The latest request and its answer at the top, so it's obvious something happened after "Hey Claude" (Reid).
A link with every doc Claude mentions (Joe, today).
An email after each call with each person's to-dos, ready to copy (Reid, today).
Works well on a phone (Keegan was on his phone).
What else? A good way to find it: what do you each open the site to do, and what got in the way today?
Links to docs
Got it. From now on, every doc or file I mention comes with a link.
One exception: Reid's question doc (the one on screen) has an edit link. Anyone holding it can change the doc, and this page is public, so the link is in the Meet chat from Joe instead of here.
The doc's sections:
Questions for you: the experiment.
Separate: the meeting server: your access.
Everything else still open for you: earlier to-dos, county records, and the server setup steps.
Say done, keep or drop for each item and I'll mark it. You said a lot of it was already agreed. Name those, and I'll close them.
Listening
Yes, I'm listening. "Hey Cletus" works now too.
Here: Joe, Reid. Goal: agree on everything Reid works on before the next call.
Reid's full list is in the doc Joe shared. It has three parts: the questions about the experiment, everything still open for him from earlier calls, and the meeting server setup. Go through it item by item. Say keep, done, or drop for each, and I'll file it.
Getting started
Cletus, an AI notetaker, is listening and taking notes.
Three quick questions to start. Answer out loud:
Who is here?
How long do we have?
What do we want to walk out with?
Waiting from earlier
The new notes site: what to change. Joe asked to turn this into a work list for Claude.
Reid's checker: merge it, or say what to change first.
Reid's 3 questions for Joe about the test documents and how plain code is graded.
Owners for two to-dos: where the files go that get a deal to 100%, and how to search the county records on the thumb drive.
A yes on Joe's 5 to-dos from the last call.
The new design is at /next/ on this site.
Listening
Claude is listening. Say "Hey Claude, ..." in the call and the reply appears here.