MAJR Daily Brief: August 4th, 2026

MAJR
Return GoblinDossierDial for curious people.
majr.app ↗ for AI builders.
not at the desk right now · last worked aug 21
← today
← aug 1aug 5 →

wrapped aug 4, 2026 · 10:05pm America/Los_Angeles

shipped

  • Dossier — in Dossier, the two decisions that determine whether someone is charged and whether their dossier is stored have direct tests, instead of being reachable only through a live request.
  • Dossier — the path where a payment turns into credit in Dossier is split out and covered by tests.
  • Dossier — Dossier's data-access rules are checked by the database itself and re-checked on every change, so a later change cannot quietly weaken them.
  • MAJR agent services — MAJR agent services can tell one caller from another, rather than reading every request as coming from the same place.
  • Dossier — the guard that stops a single analysis being paid for twice, and the merge of local and cloud dossiers, moved into code the tests can reach.
  • Dossier — the shape of an analysis reply is pinned by a test, so a change on the backend cannot quietly break how the Dossier app reads it.

the back half of the day went into the places where Dossier touches money and stored data.

in flight

Return Goblin · built and in review.

Return Goblin is getting a weekly summary email, with its own record of which week has already been sent, so a recurring email cannot go quiet after one send and look fine doing it.

→ settle the review before it runs against a real week.

MAJR · written and in review.

the pages on gomajr.com that list what shipped and what was written are getting real links, so they can be followed by something that is not a mouse, and a short opening line stops standing in for a page's description.

→ get it reviewed and out.

system status & ops

the sign-in thread from earlier is still open; everything else quiet in monitoring.

  • MAJR — the sign-in code step has still not been traced
  • Dossier — quiet, nothing new in monitoring
  • MAJR agent services — quiet, and the service came back up healthy after the change
  • Return Goblin — quiet, nothing new in monitoring

a couple of small fixes have been sitting finished and unmerged for a while; those go out next.

wrapped aug 4, 2026 · 5:20pm America/Los_Angeles

shipped

  • Dossier — Dossier's model-output parser and request validator have direct tests, including one that holds the parse-failure path to recording a category rather than the text it could not read.
  • MAJR — automated dependency-update checks cover the iOS app's own package dependencies, and a coverage claim that overstated what they reached was corrected rather than left in place.
  • Dossier — the Dossier signup form records which site a signup came from instead of a coarse label, and a field that had been going nowhere is gone.

let's get right into the details.

investigating

MAJR · reliability

sign-in on the MAJR app is failing at the code step

the step that checks a sign-in code is returning a server error to the app rather than completing. it is not new and it is not constant, which is what has let it slip out of view more than once. an earlier note here reported it as stopped, and this week says otherwise. Next: trace the failing step to a cause instead of reading another quiet stretch as a fix.

in flight

MAJR · the standard is written down and applies to anything written from here on; the text already in the products has not been reworked.

support text, help copy, error messages and onboarding across the products move to a controlled writing standard: short sentences, one instruction at a time, and the same word for the same thing every time instead of reaching for a synonym.

→ work back through the copy customers already read.

exploring

  • how rate limits should work across MAJR agent services. leaning toward limits written in one place but enforced inside each service, so that answering a request never waits on a call to anything central and a service can still answer when that central piece is unreachable. still being written up.
  • how to track an email that is meant to arrive every week. the safeguard that stops any single message going out twice is built around a one-time send, so a weekly digest run through it would go quiet after one send with nothing appearing broken. leaning toward giving the recurring email its own record, keyed to the person and the week.

system status & ops

one open thread on MAJR sign-in; everything else quiet in monitoring.

  • MAJR — the sign-in code step is returning a server error and has not been traced yet
  • MAJR agent services — quiet, and the deploy path ran clean on the first attempt
  • Dossier — quiet, nothing new in monitoring
  • Return Goblin — quiet, nothing new in monitoring

most of this landed in one sitting after a couple of quiet days.