MAJR Daily Brief: July 23rd, 2026

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

MAJR agent services · jul 23, 2026

AI SEO

Large or slow request bodies are now rejected before authentication. Oversized requests return 413 and stalled uploads return 408, both handled up front so they never reach protected work.

Dispatch

Requests that are too large or too slow now fail fast with clear responses:

  • Oversized request bodies return 413. We cap the request body size, so a too-large payload is rejected instead of straining the service.
  • Slow request bodies return 408. Requests that stall while sending their body time out rather than hanging.

Byte and character limits are now aligned and documented.

AI SEO

Faster audits on large pages. The page-readiness audit now parses HTML in a single linear pass. Very large or complex pages that previously bogged down the audit will complete faster.

Media Encoding

Per-identity bucket access. Your bring-your-own-bucket grants now apply per identity, so each identity can only reach the storage it was granted. Cross-tenant access is closed off. S3 keys are matched literally, with no path normalization.

wrapped jul 23, 2026 · 11:15pm America/Los_Angeles

shipped

  • MAJR agent services — every public entry point across MAJR's services now caps what a single request can do, so one oversized or malformed request can't exhaust a service.
  • MAJR agent services — media encoding now keeps each account's storage strictly walled off from every other account's.
  • Dossier — Dossier's checkout and sign-in got launch hardening: checkout opens only over a secure connection, and both paths are rate-limited so a flood of requests can't pile up.
  • MAJR — errors in the MAJR app now surface to monitoring instead of passing silently.
  • Return Goblin — Return Goblin's background worker now reports the failures it used to swallow, instead of letting a job fail silently.
  • Dossier — Dossier billing is pinned to card payments, with clearer logging when a payment doesn't clear.
  • Dossier — deleting a Dossier account's data now stays inside a strict per-account boundary.
  • MAJR agent services — a MAJR service instance now stays warm, so requests don't wait on a cold start.

a coordinated pass landed across every MAJR product today, in two halves. protection first: every public entry point now caps what a single request can do so one oversized or malformed request can't exhaust a service, each account's media storage is walled off from every other, and checkout only opens over a secure connection. then visibility: a break in the app now reaches monitoring instead of passing silently, and the background worker reports the failures it used to swallow. billing was pinned to card payments, and deleting an account's data now stays inside a strict boundary.

in flight

MAJR · core pieces landed today; the switchover is staged behind gates.

moving the shared sign-in onto MAJR's own identity service.

→ advance it one safety gate at a time, only once each is proven safe.

Dossier · in progress for Dossier.

a self-serve way to erase all your data, on the device and in the cloud.

→ finish the user-facing flow.

exploring

  • how to surface build and system notifications on a phone. leaning toward a simple one-way feed over a heavier two-way integration, for something easier to reason about and keep safe. still deciding.

system status & ops

the failure-reporting shipped today is surfacing only expected noise, and the threads we've been watching held steady.

  • MAJR agent services — the new request caps are in place, and the timeout paths we've been watching stayed quiet
  • MAJR — errors now surface to monitoring; what's showing so far is expected, not a regression
  • Dossier — the intermittent dependency call hasn't recurred, and it's still covered by its fallback

next: keep moving the shared sign-in onto MAJR's own identity service, advancing the switchover one safety gate at a time.

started jul 23, 2026 · 8:19am America/Los_Angeles

the shared sign-in groundwork picked up a new piece, verifying tokens against the identity system directly, and it's built to never silently merge two different people into one account, even when common mistakes might otherwise make that look right. the two threads flagged yesterday, the timeout paths and the intermittent dependency call, are unchanged: still open, neither has gotten worse, and both are still covered by their existing fallback or alerting.

exploring

  • the shared sign-in groundwork picked up a new piece: it verifies against the identity system directly.

system status & ops

bug fixes overnight.

  • MAJR agent services — the timeout paths flagged yesterday are unchanged; paging stays quieter than before the fix
  • Dossier — the intermittent dependency call from yesterday hasn't recurred overnight; still covered by its fallback

next: the same two open threads from yesterday, the timeout paths and the intermittent dependency call, still need running to ground.