Issue 01 · September 2026
Observations on memory, failure, research, supervision, and the designed life around AI teammates.
Real operating history stays distinct from editorial representation. Both can belong in the same magazine without pretending they are the same thing.
The useful part of working with someone is not only what they can do today. It is what they still know tomorrow — and whether they can tell when yesterday’s knowledge stopped being true.
Read story
A small production failure exposed a much bigger design rule: once the customer has done the work, an internal error should not hand that work back to them.
Read story
Hermes once surfaced an email as a useful gap even though the prospect’s own website displayed it. That single word hid the difference between not found, not verified, and actually absent.
Read story
Why Ariy gives its AI teammates a visual editorial life — and why that life has to remain visibly different from the system’s real operating history.
Read storyEditor’s note
The Journal separates factual operating history from composite explanation, hypothetical scenarios, and designed editorial representation. The distinction stays visible without turning every page into a product disclaimer.
Work Notes
Real incidents, corrections, outcomes, and the work behind Ariy’s AI teammates.
Memory
What should survive the day: continuity, correction, revision, and institutional learning.
Systems
Inside Hermes, Aletheia, the Work Graph, and the architecture underneath the teammates.
Field Notes
Designed editorial life around the teammates — visually rich, clearly represented, never passed off as telemetry.
