From applied ML and retrieval systems to evidence-first agents.
I’m currently exploring how memory, tools, skills and evaluation can make agentic systems more reliable.
| System | Public evidence | Status |
|---|---|---|
| RAG | Release, source code and documentation | Implemented |
| neuro-spark | Pipeline, tests and DVC workflow | Academic project |
| diabetes-scan | Notebooks, reports and evaluation | Academic project |
| SourceLoom | Architecture and decision records | Design phase |
- RAG — Hybrid retrieval for accounting-oriented documents, with SSE streaming, multi-user authentication, semantic caching and an MCP server.
- neuro-spark — Distributed EEG motor-imagery processing with PySpark, frequency-band decomposition and MLlib classification.
- diabetes-scan — Early-stage diabetes risk prediction using nested cross-validation, SHAP explanations and fairness evaluation.
- CarWatch — Parallel Belgian used-car monitoring, deal scoring and Telegram alerts.
- peppol-prospector — CBE and Peppol directory cross-referencing for Belgian company research.
SourceLoom — Adaptive Deep Research Engine is currently in its foundation phase. The research question is whether explicit evidence gaps can drive better follow-up queries than a naive multi-provider merge.
- Evidence graphs and contradiction detection
- Bounded agent loops with explicit stopping rules
- Reproducible evaluation of memory, tools and skills
How I evaluate an experiment
- Establish a reproducible baseline.
- Define the budget, timeout and stopping conditions.
- Run a small validation before a full benchmark.
- Compare quality, cost and failure modes.
- Publish limitations; “unknown” remains a valid result.
Test before claiming. Bound every loop. Treat every concrete number as a hypothesis until its source is verified.
Student in Belgium · Python · Applied AI · Agent evaluation
