Four things, named broadly

Software that holds a task rather than a state. It reads, decides, acts, and reports — and it keeps doing so at three in the morning without being asked twice.

Most automation is a rule that someone has to keep rewriting. An agent is something else: a worker given an objective, a set of tools, and the judgment to choose between them. It handles the case you did not anticipate by reasoning about it, not by failing.

We build these the way you would hire — narrow remit, clear boundaries, an audit trail for everything it touched. A worker that cannot explain itself is not finished.

The interesting question is never whether a machine can do the task. It is which tasks stop being yours once it can.

Internal machinery built to the shape of an operation instead of the other way round. Inventory, movement, records, permissions — the unglamorous structure a business actually runs on.

Off-the-shelf tools ask an operation to bend until it fits. That bend is where the cost hides: the spreadsheet kept alongside the software, the step everyone knows to skip, the export nobody trusts.

We map the operation first and model it second. What comes out is a system whose vocabulary matches the one already used out loud — so the people who live in it eight hours a day do not have to translate.

Built to be handed over. Documented, typed, and dull in the places where dull is the point.

Sites, storefronts, and interfaces treated as a design problem first and an engineering problem second. Typography, motion, and restraint — then the code that makes them fast.

A surface is the most scrutinised object a company owns. It gets three seconds and a verdict, and no amount of correctness underneath survives a bad one.

So we start with the composition — the measure, the scale, the pacing between one idea and the next — and only then decide what has to be true technically for it to hold. Nothing is templated. Nothing arrives from a page builder.

Fast is part of the aesthetic. A beautiful thing that takes four seconds to appear is not beautiful yet.

Teaching — rooms, stages, and cohorts. Not what these tools are, but where they create leverage in one specific context, and what to do about it on Monday.

Literacy is not knowing the names of the models. It is being able to look at your own week and see which four hours of it were never yours to spend.

Sessions are built around real workflows brought into the room, not a generic overview deck. People leave with something they use the next day.

It has been done for children and for boards, in lecture halls and on conference stages. The material changes completely; the test does not.