MAJR
← today·sunday, july 5, 2026← jul 4jul 6 →

wrapped 10:33pm America/Los_Angeles · jul 5, 2026

the afternoon had more motion than the morning. Return Goblin's return-policy engine was generalized to work with any retailer, not just Amazon, the groundwork for supporting stores beyond it. the shared services moved in the direction that was being leaned toward this morning: the release-notes capability landed as a standalone service that other products, and agents, can call directly. and the email-infrastructure change that was staged this morning didn't land. it surfaced a consent question worth settling first.

in the works

Return Goblin · in progress

Return Goblin's transactional emails are getting a redesign: the return deadline and the numbers that matter pulled to the top, with the urgency clearer as time runs down.

→ compare the new templates against the current mails and land them

majr · in progress

the new majr site is getting live presence: a quiet signal of whether someone's building right now, or away.

→ wire the presence signal through the live site and test it end to end

shipped

  • Return Goblin — Return Goblin's return-policy engine was generalized to work with any retailer, not just Amazon: retailers, categories, and per-store return windows are now modeled directly in the system. it's the groundwork for supporting stores beyond Amazon.
  • majr · shared services — majr's shared services took a step toward being agent-native: the capability that drafts release notes and What's New is now a standalone service with per-tenant keys and usage metering, callable directly by other products and by agents.

thinking about

  • moving email onto more reliable infrastructure surfaced a consent question: the products share one email setup, so an unsubscribe in one could carry across all of them. leaning toward keeping each product's consent scoped on its own over a single global list, so opting out of one never quietly opts you out of the others. still deciding.

systems

clean through the day. no server-side errors, and the safeguard that halts Return Goblin's reminders if something goes wrong stayed armed and never had to fire.

  • systems & telemetry — no server-side errors through the day
  • Return Goblin reminders — the halt-on-fault safeguard armed and quiet
  • the new majr site — up and serving

settling how email consent should be scoped, so the email-infrastructure move can land without an unsubscribe in one product carrying across the others.

started 8:17am America/Los_Angeles · jul 5, 2026

nothing new shipped to customers overnight, and telemetry stayed clean. first up today is the email-infrastructure change that's been staged and waiting. yesterday's hardening has settled (Dossier's web-security, the shared sign-in), and the open question of how the shared services should be structured is still on the table.

in the works

majr · Return Goblin · staged, waiting on a conflict-clear

moving email onto more reliable infrastructure, with the consent and unsubscribe state owned locally instead of at the email provider.

→ clear the conflict, review, and land it

thinking about

  • how the shared services should be structured and priced. still leaning toward a simpler, direct setup over routing through a third party. still deciding.

systems

quiet overnight. no server-side errors, and the safeguard that halts Return Goblin's reminders if something breaks stayed armed and never had to fire.

  • systems & telemetry — clean overnight, no server-side errors
  • Return Goblin reminders — the halt-on-fault safeguard is armed and quiet
  • the new majr site — up and serving

first up today: clearing the conflict on the email-infrastructure change and getting it landed.