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 DO
Capabilities
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.
WHAT I'VE DONE
Work
Verified professional outcomes, including a 50% support-ticket reduction and €250,000+ in information-development savings, plus the current professional context I can share, without reproducing any employer's internal architecture.
WHAT I'M BUILDING
Knowledge Lab
Independent, inspectable artifacts, built on public or synthetic data, status labelled honestly.
WHAT I'M FINDING
Research Lab
Evidence-led research into how the knowledge layer is showing up in hiring, tooling and organisational design: sourced, classified, and open to correction.
DOMAIN / ENERGY TRANSITION
What happens when physical infrastructure doesn't share a knowledge model?
Britain has one electricity grid. The organisations coordinating it don't necessarily have one representation of that grid.
I built an interactive Knowledge Graph exploring the grid connection queue as a Knowledge Architecture problem: mapping where semantics fragment, where systems require translation, and what that reconciliation can cost.
WHO I AM
About
Engineer by training. Knowledge Architect by practice. 20+ years across Telecom, Semiconductors, SaaS/AI and Energy, all versions of the same problem: how do you make complex technical knowledge understandable, maintainable, and useful for humans, and increasingly, for machines.