Agor journal
Notes on building agents
worth depending on.
Product principles, field patterns, and the operating choices behind the Agor agent workspace.
The job is the unit
The fastest way to make an agent vague is to give it a department. Give it one measurable job instead.
Ship simulations, not hope
A fluent demo is not a release gate. A hundred difficult, repeatable conversations are closer.
Every agent needs a supervisor
The agent handles the conversation. A separate layer watches the promises it makes while doing so.
The loop after handoff
A human resolution should make the next conversation easier, not disappear into a ticket history.