ENGINEERING JUDGMENT FOR CODING AGENTS
You speak to your coding agent as usual. Preston gives it what the code cannot say on its own: the decisions already made, the standards in force, the dangerous paths, and the reasons behind them.
A REAL EXCHANGE
Preston is not another chat window. It is the judgment layer your agent calls while it plans, writes, and reviews. What follows is one exchange, word for word.
There has to be idempotency and safe-retries wherever money is being moved
establish({ rule: "there has to be idempotency and safe-retries wherever money is being moved" })
I read this as a standard Preston already knows how to hold: “Money movement must be safe under retry”. If you confirm, it becomes your team’s standard — I’ll hold your code to it and raise it in reviews.
confirm: offer:4ea680b4eedee170 · the proposal stays open for 14 days
A LATER SESSION
Your agent already has the files. Preston gives it the layer above them — here, an agent about to hand-roll a retry loop learns this framework already owns retry.
consult({ intent: "make the queue consumer retry failed messages", repo: "phyxius" })
CONVENTIONS TO IMITATE
Operation handlers are pure functions of validated input and tools; validation, timeout, retry, circuit breaking, concurrency, and journaling are owned by the framework, not the handler.
likely files · packages/adapters/queue/src/types.ts · packages/components/connector/src/define.ts
THE SAME MEMORY, AFTER THE EDIT
It is the same team judgment applied at a different moment: the standard that guided implementation becomes the reason a later change is accepted, questioned, or blocked. This finding rests on the money rule from the top of the page — a principle, a correctness floor, the one kind that can block; the conventions your agent just inherited are noted and never block. Say yes to Preston’s proposal, and this is the review that yes produces.
See how Preston decides what not to post →57 + if (isTimeout(err)) {
58 + return transfers.send(amount);The timeout path re-sends the transfer with no idempotency key — if the first send landed, money moves twice.
payments/idempotency.tstransfer-worker.ts:58START WITH ONE REPOSITORY
The room is what Preston currently holds about a repository. This is a real one — the sentence Preston wrote after reading phyxius, as it stands today.
CURRENT READ · PHYXIUS
I’m seeing how stability choices are baked in as required, typed values on handlers, with ‘none’ as a real option and being silent means the compiler stops you.