wrapped 10:40pm America/Los_Angeles · jul 6, 2026
today went into the shared-services backbone that sits under the products. the release-notes service finished its move to per-tenant access: each product now reaches it with its own key and its own separately-metered usage, and the shared token it used to run on is retired. the voice that service writes in is now enforced centrally, so release notes read the same across every product. Return Goblin, meanwhile, grew past Amazon: its return-policy engine now handles more than one retailer, each with its own return windows by category. and its search-and-discovery logic is being moved off a bundled copy onto that same shared service, so there's one version to keep correct instead of a copy per product.
in the works
Return Goblin's search-and-discovery logic is being moved off a bundled copy and onto the shared service the other products already use, so there's a single version to maintain rather than one per product.
→ finish the switch, run it against the tests, and retire the old bundled copy
shipped
- Return Goblin — Return Goblin's return-deadline tracking has the groundwork for tracking returns from stores beyond Amazon.
- majr · shared services — the release-notes service finished moving to per-tenant access. each product that uses it now has its own key and its own separately-metered usage, and the single shared token it used to run on has been retired, so products are kept cleanly apart instead of sharing one way in.
- majr · shared services — that same service now enforces its writing voice at the point it generates text. every product's release notes inherit the shared house voice from the service itself, so they read consistently no matter which product asked, and the voice can't drift caller by caller.
thinking about
- as products move onto the shared services, a real trade-off shows up: keep a local fallback copy so a product still works if the shared service blips, or drop it for a single source of truth that's simpler to keep correct. for Return Goblin's discovery move the call was the single source, covered by quick retries and a small cached last-good result for brief hiccups instead of a full second copy.
systems
steady evening. nothing new lit up on the server side today, and the couple of older, low-volume client-side blips are unchanged and quiet.
- systems & telemetry — no new server-side errors surfaced today; a couple of older low-volume client blips, unchanged
- Return Goblin reminders — the halt-on-fault safeguard remains armed
- shared services — per-tenant release-notes access live after today's rollout
finishing Return Goblin's move onto the shared discovery service, and retiring the bundled copy it's replacing.