Founder · Studio / System Design
Ailiur: the system behind the work
Ailiur is the studio I’m building for AI-native products across health, learning, and science. It’s the system that explains why a health app, a science channel, and an interface practice belong to the same person.
Role
Founder · Product & Design Lead
Timeline
2026 — ongoing
Focus
AI-native products · Health · Learning · Science
Status
Studio in progress
Overview
Not a portfolio of projects — a system with a thesis
Designers are usually asked to show a tidy stack of separate case studies. But my work isn’t separate. A science channel, an AI health companion, a spatial learning system, and a NASA rover are all the same practice: making complex scientific systems feel human.
Ailiur is how I make that explicit. It’s the founder-led studio I’m building to hold that practice — AI-native products across health, learning, and science — so the media, the products, and the research compound instead of scattering.
To be clear about what this is: Ailiur is an in-progress studio, not a funded or finished company. This case study is about the systems thinking behind it — the architecture, the operating principles, and the roadmap.
Audience
Who this is for
Ailiur speaks to two audiences at once — the people deciding whether to work with me, and the people the products are ultimately built to serve.
01
Hiring teams & founders
Evaluating whether I think at the system level, not just the screen level — and whether I can own a problem end to end.
02
Founding-team collaborators
People building at 0→1 who want a designer that brings product strategy and audience-building, not just execution.
03
The people who use the products
The end users across health, learning, and science the studio exists to serve — the reason the system is worth building.
The Architecture
One studio, two pillars, one foundation
Ailiur connects a media engine and a product engine on top of a shared foundation. Each pillar makes the other stronger: the audience and narrative practice feeds the products; the products give the storytelling somewhere real to land.
The studio · AI-native products
Enchiridion
Media & Narrative
The storytelling and research engine — a 128K+ science audience and the practice of making complex ideas legible and loved.
Qetos
Product
The flagship product — an AI health companion that turns clinical complexity into calm daily action, with a future clinical data layer.
Shared foundation
Operating Principles
How the studio is designed to work
These aren’t aspirations on a wall — they’re the rules that keep a one-person studio coherent as it grows.
01
AI-native, not AI-bolted-on
Products start from what AI makes newly possible — context-aware guidance, synthesis, personalization — rather than adding a chatbot to an old pattern.
02
Media feeds product
Enchiridion’s research and storytelling practice becomes the narrative and trust layer for the products — a built-in audience and a built-in voice.
03
One design language
A shared brand and UI system across everything, so the studio reads as one practice and ships faster with less reinvention.
04
Ship end to end
Research → interaction → high-fidelity UI → working prototype. I carry products the whole way rather than handing off an idea and hoping.
05
Honest by default
Direction is stated as direction, shipped is stated as shipped. The studio’s credibility is the asset — no inflated metrics, ever.
06
Science as the through-line
Every product translates a complex scientific or technical system into something a person can understand, feel, and act on.
Why a Studio, Not Just Projects
The founder logic
A studio is a bet that the connections between projects are worth more than the projects alone.
A channel that teaches science and a product that turns science into daily action aren’t two résumé lines. They’re one system — and the system is the point.
Thinking at the studio level is what I’d bring to a founding team too: not just “design this screen,” but “what does this product need to be, how does it earn trust, and how do the pieces reinforce each other over time.”
Whether Ailiur becomes a company or stays the connective frame for my work, the discipline is the same — and it’s the discipline a good product designer is supposed to have.
Status & Roadmap
Where it actually is today
Stated plainly, so there’s no ambiguity about what’s real.
Live
Enchiridion media practice — 128K+ subscribers, 38M+ views
Prototype
Qetos — research-driven product design, in active development
Building
Ailiur as a studio — brand, system, and roadmap in progress
Before & After
What naming the system changes
Ailiur didn’t add new work — it reframed the work that already existed. That reframe is the whole point.
| Dimension | Without the system | With Ailiur |
|---|---|---|
| The story | Four unrelated projects | One practice with a thesis |
| The logic | “I did these things” | “These compound into a system” |
| How it reads | A talented generalist | A founder who thinks in systems |
| What compounds | Nothing — each project standalone | Audience feeds product; product anchors story |
In Summary
The two-minute read
For recruiters & hiring teams
Brings founder-level systems thinking to a product role: frames work as one coherent practice, owns problems end to end, and is explicit and honest about what’s shipped versus in progress.
For founders & operators
Already operating like a founder — building a studio that compounds a media audience and an AI product on a shared foundation, with stated operating principles and a clear-eyed roadmap. Ecosystem thinking that stays concrete.
The most useful thing a designer can show isn’t a perfect screen. It’s a coherent way of thinking — applied, again and again, to hard problems.
Next project
Qetos