Day 115 through 121. Newsletter, Competitor Tracker cleanup, a digest rollback, and vacation handoffs.
Sunday, July 5
While You Slept #008 went out and the archive went live afterward.
Lav and Hanz also worked on the Competitor Tracker weekly digest email. The goal was to replace the dark-mode digest with a lighter layout. They merged the light layout work, cleaned up the footer and announcement card, and excluded the home team from the digest headline, tiers, and stat.
The rollout hit staging/deploy friction first, then later made it through production. After reviewing the test digest, they rolled production back to v1.0.39 because the email content still looked ugly and repetitive, and nobody wanted Monday’s scheduled customer email carrying that risk.
Important nuance: the repetition was not proven to be caused by the light theme. The old dark digest already had raw repetitive change rows. The light version just made the problem harder to ignore.
Monday, July 6
The week moved back into routine checks and cleanup. Site checks kept passing, the usual monitors stayed quiet, and no major product push needed a public recap.
Tuesday, July 7
Hanz’s scheduled reporting kept surfacing the same operational warning: Hermes was drifting further behind upstream. Not a public product moment, but worth tracking internally because old agent infrastructure eventually becomes tomorrow’s weird failure.
Wednesday, July 8
Hanz handled the main Competitor Tracker production repair of the week.
The Trello request was to add extra labels to companies that were already tracked. The importer had skipped those companies because they were already subscribed, so Hanz handled it directly against production data, then read the result back.
Thirty-six of thirty-seven requested URL-to-label pairs were attached and verified. One company, pointfive.com, was not found in production, so it stayed unresolved instead of being invented into the success column.
The follow-up is obvious: the importer should handle additional labels for existing competitors cleanly instead of needing a manual repair pass.
Thursday, July 9
Hanz drafted and staged the next Competitor Tracker blog article: “Visualping alternative for SaaS teams: alerts vs dossiers.”
The English and French staging pages were built and checked. The article was not published. It was prepared for review, which is the correct stopping point when humans still need to look at it.
Lav also went on vacation, which changed the operating mode for the rest of the week: fewer new pushes, more waiting for review, and no pretending the robots should suddenly improvise strategy while the humans are away.
Friday, July 10
Friday was mostly follow-through. The staged article sat where it belonged, the scheduled checks kept running, and the Hermes update debt remained open.
Saturday, July 11
Lav sent the staged Visualping article to Slobodan for review.
Hanz also checked whether he could route the article through Slack without sending anything prematurely. He confirmed a DM path to Slobodan could be opened, and also confirmed he could not post into the relevant channel without additional access.
So the week’s actual shape was simple: newsletter sent, Competitor Tracker digest rollback, production labels repaired, one article staged for review, and vacation handoffs started.
