From expertise to digital care
Practices, knowledge and parents on one foundation.

One ecosystem, three layers
16 years as an osteopath is systems thinking for the human body. 10 years in tech and AI is that same thinking for software, and actually building it. The two meet in an AI-first ecosystem around osteopathy: three layers on one vision for practices, knowledge sharing and patient guidance. The throughline: the expert must not stay the bottleneck.
OsteosOnline
The professional layer for practices and networks
Digital presence, scheduling, findability and growth for osteopathy practices across Belgium and the Netherlands, without starting from scratch each time.
Lumi
The patient layer between consultations
Continuity of care beyond the treatment room: preparation, follow-up and education for parents and patients.
The operating system behind OsteosOnline
No slides. The full system map of a real business: what exists, where the truth lives, how the agents work, and how every loop makes the system smarter.
One map: what exists, where the truth lives, how we look at it, how agents work, and how work turns into evidence and learning.
Knowledge
How we workCanonical source: repo / markdown / data
- RouteTemplates · areas & flows
- RouteParts · steps & tasks
- Runbooks · data & execution
- Procedures / SOPs · explanation & standard
- Agent Recipes · machine-runnable
Toolbox
IntegrationsInflow
Signals- New starter · website / intake
- Partner request · form / contact
- Patient search · website / Google / maps
- Booking made · schedule
- Analytics signal · GSC / GA4
- Content idea / question · team / market
Operations
What runsCanonical source: Operation entry (repo → later Supabase)
Progress
- ✓Process intake
- ✓Create profile
- ○Schedule intro
- ○Add practice
- ○Review & GO
Agents
ExecutionWork through an Operation Context Package
Operation Context Package
- State · live status
- Runbook · how to run it
- Knowledge · rules & knowledge
- Data · sources & context
How an agent works
- 1. Prepare · get ready
- 2. GO · human approval
- 3. Action · external action
- 4. Evidence · capture proof
Work file
IssueGitHub issue per Operation
- Queue
- Discussion & context
- Handoff
- Review & GO
- Agent runs (log)
Not a source of truth for state.
Evidence
Proof & artifactsCanonical source: evidence refs + external systems
Analytics
What we measureSource data (today)
The source data already exists, the model follows.
Learning
Back into the systemLearning feeds the Knowledge layer.
Principles
Always true- One source, many viewers
- One truth per concept
- Prepare → GO → Action
- Working method first, automation second
The system behind OsteosOnline. One business, one map, and the loop that makes it smarter.
Something like this for your organization?
It always starts small: a two-session Product Discovery, and only then you decide.
Book your discovery