What the role actually covered
Technical direction and community leadership, working with maintainers and the Technical Advisory Council to set the roadmap, drive execution and grow the ecosystem around it.
Hands-on engineering on one side, long-term architectural ownership, contributor mentorship and open source governance on the other.
The intelligence platform
- Problem
- Maintainers had no single view of project health. Signals were scattered across roadmaps, issue trackers, pull requests, discussions, community channels and other ecosystems, and contributors join and leave constantly.
- Approach
- Led the architecture and development of a distributed platform of 14 interconnected services: scalable ingestion pipelines, AI-powered signal processing, multi-agent orchestration, search and retrieval, and analytics that correlate all of it.
- Result
- A real-time picture of project health, contributor activity, user demand and competitive landscape — connecting engineering progress to what the community actually expects.
Caracal — policy-driven authority delegation
- Problem
- Autonomous AI systems and other non-human actors need to collaborate without anyone losing track of who authorised what.
- Approach
- Policy-as-Code with graph-based delegation models, authorisation evaluated before execution, real-time revocation, secure credential management and immutable audit trails.
- Result
- Agents able to work together across distributed environments with verifiable authorisation and complete auditability.
Running it in production
Deployments, infrastructure maintenance, scaling distributed services and release management — including reliability for organisations in regulated industries, banking and financial services in particular.
Which mostly means holding feature velocity and production stability in tension without letting either win outright.
A project that depends on one person isn't infrastructure. It's a liability.
Leading people, not just code
Architectural discussions, technical reviews, roadmap planning, project governance and community growth — coordinating across engineering, the open source community and organisational stakeholders.
I stayed one of the most active contributors throughout. The coordination was in addition to the code, not instead of it.
Representing the foundation
Open Source Summit Korea, Japan, India and North America, plus OpenSearchCon Europe, China and Korea — presenting the technical work and meeting founders, CTOs, maintainers and executives from across the ecosystem.
I went to talk about the project and spent most of it listening. The hallway track changed the roadmap more than any talk did.