8 — 14 AUGUST 2026

What didDavid do?

ShopBack · IntentHQ · Nature’s Fusions

0MERGED
0OPEN
0CUSTOMERS

SCROLL ↓

01 — THE SHAPE OF THE WEEK

Half code.Half calls.

26 merged · 21 meetings · 19 hours on video

0SAT
2SUN
8MON
7TUE
2WED
4THU
3FRI

Thursday: 3 meetings at once · 25 commits

ACT I — SHOPBACK · THE SLACK BOT

It held upon the demo.

Their workspace · it performed

Everyone saw someone else’s connection as their own

Bot connection renders as the user’s ownFIXED · #3187
Identity bridge moved onto the identities tableFIXED · #3183
Install-override check, answering, dashboard reachFIXED · ENG-3759
ACT I — SHOPBACK · THE SIGNAL

89% of itwas a robot.

Their Jira corpus

89% — ONE BOT PROJECT11% — EVERYTHING ELSE
8NO PREF
290 DAYS
130 DAYS
01 DAY

Same corpus. Only the recency preference changed.

ACT II — INTENTHQ · STILL OPEN

Shipped Friday.Still not right.

Fixes didn’t hold on today’s call

Meeting notes — speaker turnsINTACT
Summary, actions, decisions, topicsWAS MISSING
EU connections, lifetime syncsZERO
EU CONNECT US REGION EU REGION 0 SYNCS

Region is permanent · no migration exists

ACT III — NATURE’S FUSIONS · THE BOOKS

Built it twice.

2,473 lines · then 2,193 more

5 credential shapes · byte-identical replies

ACT III — NATURE’S FUSIONS · THE FILES

134 folders.Four visible.

“Giving us only the wrong folders”

VISIBLE — 4 INVISIBLE — 130

And it never looked like a failure

0% — BACKFILL 0 DOCUMENTS INDEXED
02 — NEGATIVE RESULTS

Two of themwere failures.

Written up · left open · labelled

PR #3171

Teach retrieval who “me” means. It works — I just oversold the measurement, and corrected it in public rather than quietly editing.

DO NOT MERGE
PR #3170

Stop the answer model second-guessing itself. It traded polite “I don’t know”s for confident wrong answers. Strictly worse.

DO NOT MERGE
03 — RECONCILED

Then the paperwork.

8 had no ticket · 4 were lying

0MERGED
0OPEN
0TICKETS CREATED
0STATUSES FIXED