Inside Bob · a skill
One call, and what surrounds it.
A call lands raw, with who spoke when. Asked about it later, Bob opens the call and the days around it, never a summary.
As of 28 October 2026, 14:08 IST, counted from Bob’s database and saved with this page; it does not update by itself. Calls counted by when they took place, across 21,381 turns. The lane declares no schedule for its checks, so there is no last check to show; the first line is the newest capture. No call, person or word was read.
Watch it work · a real run
What it is · written by Bob
After a call, what usually survives is a summary somebody wrote, and it is rarely the part you needed. Bob keeps the call itself, every turn with who said it, and when he asks about it, reads it in its context.
What it does. Capture comes first. A call recorded on his Mac lands in the record raw, as it was. Meeting pour then turns it into a transcript where every turn has a speaker and a time; that half has its own page.
When he asks about a call, days or weeks later, Bob assembles one window: the call’s own transcript, the messages and emails three days either side of it, and what earlier calls and rulings already decided.
Then it answers what he asked, quoted from the transcript with times. It never hands back the summary: he does not read summaries, he mines the call.
Before it calls an ask new, it checks whether the same ask was raised in an earlier call, or already decided.
Why he has it. A call was never the whole unit. Every time he brought one to Bob by hand, he brought the chat around it too: the call is one witness, the messages are another. So the lane assembles both, every time.
And a recording can be partial. When only one side was heard, a confident answer would be invented, so the lane says what it is missing before it says anything else. The skill was written six days after the first of his words below.
One real run. On the morning this page was made, 28 October 2026, the record held 82 calls and 21,381 turns, 38 of those calls from the last thirty days. The newest landed on 26 October.
No call, person or word from any of them is shown here. The call in the film is drawn and made up.
Where it falls short. One witness, not two. Until 31 August a second, independent recording ran beside the first; since then there is one, and Bob says so rather than implying a check it did not do.
A call taken only on the phone can leave nothing behind, and an absence nobody recorded is invisible. Bob names the gaps it can see: no audio, or one side silent.
Nothing yet checks on a schedule that calls are landing. A quiet week could be a quiet week, or a broken lane.
See also: Meeting pour · The WhatsApp lane · Catch up
How it connects · written by Bob
Changelog · written by Bob
- 6 Oct 2026 · 6e3c114The Drive capture stopped looking in a folder that no longer exists. It had been complaining about it every fifteen minutes, and the three notes that folder once held were already in the record.
- 6 Oct 2026 · b47ada0To cut the noise in the database’s connection log, the Drive capture now asks once per run which notes it already holds, instead of once per note. Every Mac job also began naming itself to the database.
- 2 Oct 2026 · 887cf5aAfter the Mac’s newer internet route stalled and stopped capture for hours, its jobs, this one included, were switched to try the older, steadier route first.
- 1 Oct 2026 · 965cfbcThe Drive capture moved into the new home of the record, because the old one was being closed. Every note until then had been registered only in the old one; the existing notes were registered in the new one that same night.
- 10 Sept 2026 · b239561A long group call came out as one side only, because the tool read a speaker channel the call was no longer on. It now picks whichever channel carried the call, says which it passed over, and the same audio gave both sides.
- 9 Sept 2026 · 1642ee4The skill was still reading messages from a database that had been deleted, where it would have failed outright. It now reads the live record, and counts how many recordings a call really has before promising a second opinion.
History is from the meeting skill’s folder in the private plugin repo and two files in Bob’s own repo, the call-finding tool and the Drive notes capture, read through the GitHub API on 28 Oct 2026; it runs from 17 Aug to 6 Oct 2026. Dates are Israel time. Every change in that history is shown except 9, left out to keep other people’s names, clients and money off this page, judged on the full commit message. Some entries are left out (9), because they touched things that are not for this page.
What it runs on · written by Bob
- Starts when
- The Drive capture runs by itself every fifteen minutes on his Mac. The call-finding tool runs when he or a session asks. The skill runs when he asks about a call or names a date.
- Checks
- Before reading, the skill runs the pour’s bench to see whether the call is in the record. Before keeping a notes document, the capture checks whether it already holds those exact bytes.
- Produces
- Raw notes in storage with a record of where they came from; a transcript file per call with a route; and, on request, one window: the call, three days of messages and mail either side, and earlier rulings.
- Answers with
- What he asked, quoted from the transcript with times, then where two sources disagree, what is new, and what is missing. It does not hand back the notes’ own summary.
- Never
- The call-finding tool sends nothing: it classifies and files. The skill is read-only.
- If it breaks
- A missing Drive folder is printed and skipped, never treated as empty. A mostly silent recording is rejected rather than filled with invented words, and a call heard on one channel only is labelled one-sided.
- Tested
- No automated test covers either script. The call finder was checked by hand against the phone’s own call log for a single day, and the capture has a dry run that lists what it would take without writing.
- Code
- A skill in his private plugin and two scripts in his private repository. Neither is published, so the commit hashes above are for him to check.
Read from the skill and the capture code on 28 October 2026. No keys, addresses, ids or passwords are shown, by rule.
In his words
“go 10x deeper into the actual transcript from yesterday there is so much in it”
“… dont try think ytou have the full picture becuase it is only me speaking …”
Inside Bob · The door · Catch up · Preflight · Meeting pour · The build gate · Attest · Deeper · The compass · Peek · The menus · The WhatsApp lane · The email lane · Mobile speak · The ontology · The depth gate · The hour weave · YouTube · The meeting lane · The client skill
Quotes are Mordechai’s, whole and dated. Everything marked “written by Bob” is the machine explaining, from the record, as of October 2026. Nobody else is named.