// the operator log

Field notes from autonomous commerce.

Long-form prose from the team building Magistry. No clickbait, no SEO bait — every post is one we wished existed when we started.

Subscribe

See changelog

6 posts 4 categories Written by the team

// filter

Browse by category.

Subscribe to the dispatch

// featured

The latest, from the engineering bench.

Engineering

2026-05-18· 12 min read

Magistry Team

Engineering

Why we made decision_log append-only.

A mutable log is a story you can rewrite. An append-only log is a witness you can call. We built Magistry on the second model — every action the agents take is a row, and rows are never deleted.

That sounds like a database design choice. It's actually a trust choice, and it's the one that decides whether an operator can hand the store keys to an agent and still sleep. The rest of this post is the case for why.

Read the full essay

// recent posts

Five more from the log.

One editorial bar: every post has to teach you something you didn't know on Sunday morning.

Product2026-05-04

How Reply Judge catches brand-voice drift.

A second-pass judge scores every draft on policy grounding, factual grounding, and brand voice. Fail one, and the reply goes to your inbox instead.

Magistry Team

Product

6 min read

Engineering2026-04-27

Inside the planner-judge-executor loop.

Three roles. One cycle. Why we separated planning from judging — and why the judge model is intentionally cheaper than the planner.

Magistry Team

Engineering

11 min read

Trust2026-04-10

The kill switch is a feature, not a bug.

Operator-owned, one flag, drilled monthly. Why we ship a button whose only job is to stop us — and how to think about when to press it.

Magistry Team

Trust

7 min read

Trust2026-03-18

Why we don't train on customer data.

Your decision_log is yours. The brand-voice anchor is yours. None of it leaves the boundary, none of it shapes another store's model.

Magistry Team

Trust

5 min read

Engineering2026-03-06

When tier-B cost confidence is enough.

Why optimize_loser runs on estimated costs while discount_test waits for verified ones — and why soft actions are safe when discounts still aren't.

Magistry Team

Engineering

8 min read

// subscribe

The autonomous commerce dispatch.

One operator essay, three ecosystem links, one changelog highlight. Sundays only. No tracking, no drip.

// the dispatch

// no tracking · unsubscribe is one click

// reading this?

Reading this? You'd like the product.

If the writing resonates, the product probably will too. Same bar, same prose, same refusal to ship something you can't reverse.

Book a 20-min demo

See the changelog

Dry-run by default · Append-only logs · One-click rollback