Ideas explain code.
Code tests ideas.
I study how AI changes what people can do, what companies are worth and how work should be organised — and build the systems that test the thinking.
What changes when intelligence becomes more available — and how should people and companies reorganise to benefit?
The work follows that question from philosophy to code — and back. Experiments expose weak theory; better theory changes what gets built.
Four layers. One arch.
Value is carried across the span — from why it matters to what provably works. Not a pyramid: nothing here is a base you finish first. Every layer is load-bearing, and the load only crosses when the arch is closed.
The object of design is not an AI application.
It is how the business works as a whole.
Marketing, sales, operations, service, HR and finance are not six AI use-case lists. They are six views of one promise. Change the promise, and every view changes.
It runs in both directions
An inquiry can start anywhere — a research finding, a commercial assumption, an agent behaving badly. The job is to find the level that explains it.
The symptom → the mechanism
The books are part of the machinery
Not content marketing beside the technical work. An ebook explains the argument, a doctrine states the rule, a playbook makes it a procedure, a wiki serves it during work — and code tests it.
| Part of the practice | Representative titles | What it contributes |
|---|---|---|
| Human thinking & consequences | The Reshape · The AI Learning Flywheel · HR Governance Seat | Problem framing, augmentation, learning, the human terms of adoption |
| Economics & strategic choice | The Terminal Value Doctrine · The Re-Roll · The Cognition Dimension Ladder | Value migration, commercial redesign, defensible search |
| Knowledge & organisational understanding | Executable Worldview · The Wiki Is the Kernel · The Wiki Playbook | Source-connected institutional knowledge that informs live work |
| Authority & persistent work | Two Leashes · The Business Runtime | Bounded action, continuing responsibility, explicit completion |
| Engineering practice | The Generative Pendulum · Designing Loops, Not Prompts | Agentic / deterministic boundaries, feedback, verification, reuse |
Thirteen titles shown. The library holds 263, on two wikis — the ideas and the builds, inspectable side by side.
enterprise delivery — insurance, banking, energy, Defence
an 11-person consulting firm — these economics are lived, not theorised
postgrad lecturer — MGSM 2001, CSU / IT Masters 2018–20
doctrines, playbooks and field guides — a published, queryable body of work
IP and dev — the ideas and the builds, cross-linked and source-grounded
production AI systems in live businesses — governed, audited, measured
The Review is this practice, applied to your company in four weeks.
We arrive with a thesis about your market and the machinery to test it. Your numbers decide whether it survives. Forty-five minutes to start.