Agents do not need more intelligence, they need narrower mandates
Agents stall when their authority is undefined. Narrow mandates make scope, ownership, audit and reversal clear.
ReadInsights
Notes from the work itself.
Practical notes on AI-first engineering, software architecture, security and delivery, written for the people who have to decide what gets built and who pays for it when it goes wrong.
Building for a site with no signal
Construction software fails when it assumes a signal. On site, the device must record work locally, sync later and keep evidence intact.
ReadSchool bandwidth is a design constraint, not an excuse
Education software fails when it is designed on fast office fibre but used by whole classes on shared school connections and older devices.
ReadNine ways an LLM fails once it reaches production
Production LLM failures usually come from the system around the model: truncation, retries, schema drift, monitoring gaps and weak evaluation.
ReadNobody promised you a result
General AI assistants shift responsibility to buyers when outputs are wrong, so production use needs a defined result and remedy.
ReadYour peak hour is a specification, not a hope
Peak capacity has to be agreed, tested to failure, and designed around before the campaign, because the busiest minute breaks systems.
ReadReconciliation is the only feature that matters on your worst day
Payment systems earn trust when they can prove the ledger matches the outside world, especially when retries, timing gaps and partial batches hit.
ReadWhat a defined job looks like when an AI does it
A defined AI job needs a written input, output, evaluation, confidence rule and remedy before anyone pays.
ReadClinicians route around slow software, and that is a safety problem
Slow clinical software pushes staff into workarounds, breaking live records, timestamps and audit trails when safety questions arise.
ReadThe chat window was never the product
AI buyers need finished work with a price, deadline, quality measure and recourse, rather than open-ended chat access.
ReadNext step
Reading because you have a project in mind?
A senior engineer reads every enquiry and replies within one business day with an honest assessment, including when we think you shouldn’t build it. No sales call, no deck.
