Knowledge Architecture · AI Knowledge Systems · Docs Engineering · Energy
I architect knowledge for humans and machines.
I design the knowledge layer between Product, Engineering, and AI: turning fragmented technical knowledge into governed, structured, retrievable systems that humans, LLMs, and agents can reliably use.
Knowledge is infrastructure.
Most organisations think they have a documentation problem. Often, they have a knowledge architecture problem.
As products scale, knowledge fragments across repositories, APIs, tickets, Slack, SMEs, and documentation. Humans struggle to find the right answer. AI systems confidently retrieve the wrong one.
I work on the layer underneath: the structures, semantics, governance, and retrieval systems that make organisational knowledge findable, trustworthy, and actionable. For humans. And increasingly, for machines.
What I work on
Knowledge Architecture
Turning fragmented organisational knowledge into coherent systems.
AI Knowledge Systems
Designing knowledge so LLMs and agents can retrieve the right information, understand its context, and know when to trust it.
Docs Engineering
Treating documentation as a product and an engineering system, not a publishing function.
Currently
Building the knowledge layer for the energy transition. At Kraken, I lead Knowledge Architecture and Docs Engineering across two Energy Flexibility products, serving approximately 300 developers, data scientists, and product/engineering managers, across 11 languages and four overlapping experiences: Internal · Customer · Developer · Partner.