Applied Horizons
Beyond the immediate horizon.
We work on problems that do not yet have a playbook.
Bring us the problem. Not the category.
- Some problems are called technical until they become legal.
- Some are called security problems until they become operational.
- Some are called medical until they become questions of data, autonomy, liability, or trust.
The label usually depends on who noticed first.
We care about what the problem becomes next.
The first effect is rarely the last.
- 1st order
A new technology solves a problem.
- 2nd order
Then it changes the environment around the problem.
- 3rd order
People depend on it. Competitors adapt to it. New vulnerabilities appear. Rules written for the old world stop fitting the new one.
- Later
Eventually the secondary effects matter more than the original capability.
- In practice
Most organisations study those questions separately. Engineering looks at performance. Security looks at exposure. Counsel looks at liability. Policy looks at governance.
Applied Horizons looks at the whole chain before the chain becomes obvious.
What happens after it works?
New technology is usually judged by whether it works.
We start there.
Then we ask what happens because it works.
Most analysis stops when the technology works. Ours starts there.
- Capability
What became possible?
- Application
Where does it actually get used?
- Dependency
What begins to rely on it?
- Exposure
What becomes vulnerable?
- Response
Who adapts?
- Governance
What now requires rules, proof, or accountability?
- Consequence
What changed that will not easily change back?
Areas of exploration.
The subject changes. The method does not.
- 01
Artificial Intelligence
Intelligence is becoming infrastructure. Emerging architectures, agentic systems, model security, evaluation, and the operational consequences of software that increasingly decides. - 02
Cyber & Resilience
New capability creates new exposure. Adversarial behaviour, systemic dependency, emerging attack surface, and the difference between a system that resists failure and one that survives it. - 03
Quantum Technologies
Some technologies change the assumptions beneath the system. Computing, communication, sensing, and timing — four capabilities maturing at different rates, each altering something a great deal of infrastructure quietly assumes. - 04
Autonomous Systems
When software begins to act. Perception, decision, and action in increasingly independent systems — and the question of who remains accountable for the outcome. - 05
Governance & Assurance
Capability alone does not establish trust. Oversight, standards, evaluation, controls, and the mechanisms by which a system earns the confidence already placed in it. - 06
Law, Policy & Institutions
Technology moves. Institutions respond. The evolving rules, obligations, and institutional structures that form around a technology once it becomes consequential. - 07
Health & Human Systems
Where technical capability becomes human consequence. Clinical systems, medical devices, health data, human performance, and the interfaces where a person and a machine share a decision.
When the obvious calls have been made.
Any one of these is reason enough.
-
Nobody is sure which discipline owns it.
-
Every expert you have asked understands one piece of it.
-
The obvious answer feels inadequate, and you cannot yet say why.
-
The usual approach rests on assumptions that may no longer hold.
-
Something is clearly happening, and nobody can yet say what.
-
There is no accepted way to work out what happens next.
The horizon is rarely the end of the problem.
If the problem does not fit the category it arrived in, that is usually the interesting part.