MAJR Daily Brief: July 7th, 2026

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

MAJR agent services · jul 7, 2026

Dispatch

Service-plane endpoints for the fleet. New endpoints give you a key map for your services and a path to ingest usage directly. This is phase 3 of the service-plane work.

Usage ingest, hardened. Ingest now rejects reserved names, drops echo-free locations, and requires exact integers so your submitted usage lands cleanly. Ingest identities are validated on the way in.

Cleaner draft totals. Service events no longer count toward draft totals, so the numbers you see reflect actual usage.

Plane API improvements.

  • A defined error contract, so failures return predictable, actionable responses.
  • MCP services now have full parity across the plane.
  • Documentation for plane secrets.
  • Oversized integers now return a clear 422 instead of failing silently.

Agent discovery for media encoding. The media-encoding service now publishes a service card, an llms.txt, and an OpenAPI 3.1 spec so agents can discover and call it.

Media Encoding

Per-product API keys. Authenticate with keys scoped to each product through the shared service-plane key map. During the transition, both new and legacy keys are accepted, and legacy keys are tried first so existing setups keep working.

Job IDs are namespaced per product. The same job ID in different products no longer collides. Use a / separator in IDs, with idempotency scoped to the rollout window.

Metering you can trust. Encoding usage is recorded to the platform ledger with one event per terminal outcome. Failed encodes now meter their partial costs, and failed downloads meter the bytes actually transferred, so your usage reflects real work done.

Honest rate limiting. Retry-After values now reflect the actual wait. The retryable auth 503 response is documented so you can handle it correctly.

Agent discovery surface. New service card, llms.txt, and OpenAPI 3.1 description make the encoding API easier to discover and integrate.

wrapped jul 7, 2026 · 10:16pm America/Los_Angeles

shipped

  • Return GoblinReturn Goblin's search-and-discovery now calls the agent service directly over the network, and the separate copy it used to bundle has been retired.
  • DossierDossier's analyzer now draws its writing voice from the shared voice service, instead of carrying its own copy.

today went into the agent services, in the same direction as the morning: one capability, described once and called over the network, rather than a copy baked into each product. Return Goblin's search-and-discovery cutover landed, and the copy it used to bundle is gone. the media-handling capability moved onto the same footing, picking up an agent-facing description, per-product keys, and per-use metering. and Dossier's analyzer started drawing its writing voice from the shared voice service instead of its own copy. the thread running through all three: capabilities other products, and agents, can find and call, kept in one place instead of drifting across copies.

in flight

MAJR · agent services · milestones landing

the media-handling capability is being brought onto the same footing as the other agent services: agent-callable, with each product carrying its own key and its use counted per call.

→ the production cutover, so a product calls it over the network instead of bundling its own copy

exploring

  • how per-use metering should handle a call that names a product it doesn't recognize: record the use anyway, or reject the call outright. the call was to reject it, so a use is never quietly logged against the wrong account and the counts stay trustworthy.

system status & ops

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

  • systems & telemetry — no new server-side errors in the last 24 hours
  • Return Goblin reminders — the halt-on-fault safeguard armed and quiet
  • agent services — steady as the media-handling milestones landed

the media-handling service's production cutover, so a product calls it over the network instead of bundling its own copy.

started jul 7, 2026 · 7:28am America/Los_Angeles

shipped

  • MAJR · agent servicesthe shared discovery service now describes itself to agents: a machine-readable description of what it does and how to call it, so a product or agent can reach it directly without bespoke wiring.
  • MAJR · agent servicesa fleet catalog went live: one machine-readable index of the agent services, so anything that finds a single MAJR service can discover the rest from there.

the agent-services backbone kept building overnight, in the same direction as yesterday: capabilities that describe themselves so other products, and agents, can find and call them directly instead of each product bundling its own copy. the discovery service picked up an agent-facing description of itself, and with another service now agent-ready, a fleet catalog went live: one machine-readable index, so anything that finds one MAJR service can discover the rest. Return Goblin's own cutover onto that shared discovery service is up for review, and the media-handling capability is being brought onto the same footing. the running question underneath it: keep discovery in a single shared source, rather than let every service carry a copy that quietly drifts.

in flight

Return Goblin · up for review

Return Goblin's search-and-discovery is being cut over to call the agent service directly, replacing the bundled copy it carried.

→ land the cutover and retire the old bundled copy

MAJR · agent services · in review

the media-handling capability is being given the same agent-facing description and per-use metering as the other agent services.

→ land the first stage, then its production cutover

exploring

  • how the services should be discoverable: one shared catalog kept in a single place, or each service publishing its own copy. the call was the single shared source: a second copy has nothing keeping it honest and drifts out of date, so sibling services point at the one catalog instead of carrying their own.

system status & ops

clean overnight. no new 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 new server-side errors in the last 24 hours
  • Return Goblin reminders — the halt-on-fault safeguard armed and quiet
  • agent services — steady after the discovery-service rollout

landing Return Goblin's cutover onto the shared discovery service, and bringing media-handling onto the same agent-native footing.