Hi Neko Health,
Curated elements and projects for your consideration
Longevity Focused Metabolism Obsidian Vault
My interest in Neko Health is not speculative. For several years, I have been building a private Obsidian research vault of 1,000+ linked notes around metabolism, preventive health, longevity, biomarkers, mitochondrial function, interventions and human performance.
This has meant staying close to papers, mechanisms, expert debates and emerging academic directions, not as casual reading, but as a working map of the field. I use it the same way I use production notes or project boards: to track what matters, where the dependencies are, what keeps repeating, and where the system starts to break or reorganise.
That is the connection to Neko. I’m used to looking at health as a coordinated system, not a pile of separate facts. Neko is doing that in the real world: connecting diagnostics, preventive medicine, physical space, technology, operations and trust into one experience people can actually use.
LIVE Fashion Shows
These productions were shaped by exceptional teams across creative direction, production, technical delivery, and post. I am glad to have been a part of such herculean efforts, as the experience around this level of work gave me an incomparable appreciation for high-performing creative systems designed to operate under pressure: precision, timing, trust, taste, and coordination all at once.
Taste being the world class outlier here, but operations is what allows it to exist unbriddled in the first place.
AI & System Design
This is a systems-design showcase for Mighty Andy, an AI bid-readiness pipeline I built around controlled context, staged reasoning, quality gates, and client-safe report generation. Rather than relying on one large prompt, the architecture separates file custody, tender analysis, evidence matching, judgment, and rendering into inspectable components.
Scroll inside the frame to explore the pipeline ⬇️
Creative Team Enablement Under Extreme Constraints
Game jams are hard to explain to anyone who has never done one. They sound playful from the outside: a theme, a deadline, a game at the end. In practice, they are compressed creative emergencies. Nobody is paid, everyone is tired, tools break, scope mutates, morale fluctuates, and the whole thing has to become coherent before the deadline wins.
This is why they are so relevant to operations. The work is not simply to “lead.” It is to make the team function: find the right people, clarify ownership, protect momentum, resolve bottlenecks, keep morale alive, and give talented contributors enough structure to do their best work.
"Up to 40 strangers recruited at a time"
"Top 2% out of 11,000+ teams competing"
Over several years, I have built and coordinated game-jam teams from scratch, sometimes reaching nearly 40 contributors, an extreme size in that context. At that scale, the challenge stops being simply “make a game.” It becomes talent identification, cohesion, creative direction, production architecture, crisis control and delivery under pressure. (This year I am on track to lead a 65 people team)
The visible output is the game. The real feat is turning strangers into a functioning creative system fast enough to ship something excellent.
