
Proof Green, Money in the Wrong Account
SC-68's streaming worker passed its proof run, the R2 rotation closed, both glasses videos play — and three jobs' payments showed where money leaks.
Share this episode
Every share includes a caption, call to action, and hashtags — just pick your platform.
🎙️ Proof Green, Money in the Wrong Account SC-68's streaming worker passed its proof run, the R2 rotation closed, both glasses videos play — and three jobs' pay... Press play and listen 👇
https://momsoilchange.com/podcast/proof-green-money-in-the-wrong-account-2026-11-20
#MobileOilChange #momsoilchange #servicewriter #AutoIndustry #SmallBusiness #PhillyBusiness
LinkedIn doesn't accept pre-filled text — we copy the caption for you automatically.
Full Transcript
Tyreese: Day two of the Build Log, and today proved something I keep saying around here. No evidence, no green. The big streaming worker passed its proof run, both glasses videos play in the library, and the money from today's three jobs showed me where my own systems still leak. Wins first, then the honest part.
Tyreese: The headline is ScreenCut. The bounded streaming proxy worker, ticket SC sixty-eight, went fully green on its proof run. We fed it five hundred eighty-eight megabytes, bigger than the old memory cap, and it came back with a five hundred eleven megabyte proxy. Peak worker memory was one hundred eighty-seven megabytes. The old worker choked past five hundred megabytes because it held the whole file in memory. This one streams to disk, encodes CRF eighteen, preset slow, full resolution, never downscaled, and streams the upload back out in parts. The probe came back H two six four, Y U V four two zero P, AAC audio, fast start, dimensions held. Originals hash identical before and after, nothing touched the clean original. The same asset processed twice registered exactly one proxy variant, no duplicates. An injected failure aborted the multipart upload cleanly, nothing left behind, no false ready record. That's ChatGPT's whole checklist, every box ticked with measurements, not opinions.
Tyreese: Same night, the credential rotation closed. The old R two secret was unrecoverable, so we minted a fresh token, installed the new pair in Vercel production, redeployed, and verified playback signing with the new key plus a full production upload end to end. Then we revoked the old token, and a check confirmed it is gone, token not found. And the two HEVC glasses videos that started this phase converted to H two six four proxies. I pressed play in the library myself. Both play. That's SC sixty-nine and SC seventy, proven, not promised. The pull request, number two thirty-eight, is open with ChatGPT for review now.
Tyreese: We also finished the plumbing between Job Capture and ScreenCut. Migration thirty-seven is live in the production database, the integration tokens table is in place, and a media write token named Job Capture production was minted and proven live by opening a real upload slot with that token alone. It expires February eighteenth, twenty twenty-seven. Once those three settings land in the Job Capture environment, the connector should stop reporting not connected.
Tyreese: Then there's Rashid, one of our editors, who gave us a real usability test this morning. It stung in the useful way. He said the editor opens blank, he can only find ninety-one of six hundred plus videos, he can't find clean originals, he doesn't know his assignment, and he can't find or download the clips he needs. We measured the library. Four hundred sixty-six videos, every single one status ready. Six hundred thirty-four assets total. Three hundred forty-three proxies exist, but only two of the one hundred twenty-four direct uploads have one, the SC sixty-eight backlog. Clean originals exist for four hundred sixty-four of four hundred sixty-six videos, so Rashid's problem is discoverability, not missing media. His ninety-one processed matches no count anywhere in the backend. The interface shows a number that means nothing. That's an information architecture failure, not a features failure. Fix navigation, library states, and editor reliability before any new AI feature. No WhatsApp fallback until the path works.
Tyreese: Now the money, because the shop ran three jobs today and the payments taught me something. Aaron Bado, European spec oil change, closed at two hundred twenty-one dollars, paid by Stripe this morning. The morning board said two hundred seventy-one, and for a while a double charge looked possible. It wasn't. Aaron booked through the website, oil change plus wiper blades, two hundred seventy-one total, and the wiper add-on silently never attached. No wiper line on the appointment, no email, nothing in the tech app. I ran the oil change only, he paid two hundred twenty-one. We swept all of November in Stripe, no two hundred seventy-one dollar charge anywhere. The ghost was a broken booking record, not a real hold. But the defect is real, in the engine we're retiring, and the replacement has to carry add-ons into ServiceWriter or this repeats.
Tyreese: Bianca Dean, full synthetic, one hundred twenty-three dollars, paid cash, closed out. Bookkeeping wrinkle, the payment is recorded as type other instead of cash. Labels matter when you're reconciling. And Michelle Campellone, Mobil one, one hundred sixty-three dollars. I told the team she paid by Stripe. It wasn't in ServiceWriter at all. Invoice twelve twenty-seven still shows zero paid, balance one hundred sixty-three. Then I found it in a screenshot on my own phone. The charge is real, net one hundred fifty-eight dollars and fifty-five cents after a four dollar and forty-five cent fee. But it landed in the wrong Stripe account, the Book Your Oil Change account, because I was poking around in the Stripe app and forgot which account I was in. That's software money, not shop money, and it never touched ServiceWriter. Two money worlds, keep them separate, and the shop account is the only one a job ever touches.
Tyreese: What's blocked, honestly. The streaming worker pull request waits on ChatGPT's review, and the rule stands, a hermetic test proves the worker in a controlled environment, it does not replace a production test on real glasses footage. The glasses live preview still waits on my field verdict from build four, step three. The official Stripe connector is down on an OAuth refresh, so reads go through the rotated keys path for now. Facebook's connector has a stale write lock that killed two unattended posts today, those drafts wait for an attended retry. None of it stops the work, and none of it is fixed.
Tyreese: What's next. ChatGPT reviews pull request two thirty-eight, we address findings, merge, deploy, and test on real glasses footage in production. The SC sixty-eight backlog, roughly one hundred twenty-two direct uploads without proxies, starts clearing once that worker ships. Evidence for SC sixty-nine and seventy goes to the phase one gate. On the shop side, I record Michelle's payment against invoice twelve twenty-seven, and add-on carryover goes into the booking replacement spec so a wiper blade never vanishes again.
Tyreese: Same as day one. Proof over promises. The worker proved itself with numbers. The library proved Rashid right with numbers. And the money proved the leak isn't always in the code, sometimes it's the operator tapping the wrong account. Tomorrow, same time, same rule. If it isn't proven, it isn't green.
New episodes every weekday. Subscribe via RSS to get them in your podcatcher.
Book Your Oil Change