I learned engineering from broken things.
Elyes Rayane Melbouci
AI Engineer / Founder of Lirovo / Montreal
I architect the agentic systems the investment teams run on. A multi-agent extraction pipeline that turns unstructured documents into structured metrics, and an orchestration layer over 30+ institutional research providers where a single agent run picks its own tools, resolves the question, and answers with citations. Versioned agents, eval gates before release, trace telemetry on every run.
Built the warehouse-backed reporting the investment and operations teams work from, and automated the catalog sync, lineage and ownership behind it, so a metric meant the same thing in two different reports.
Two years of escalations, security policy, and the process fixes that stopped the same ticket from coming back a third time. Most of what I know about how production fails, I learned here rather than from a design doc.
AI consulting for Canadian businesses. I find the two or three workflows where automation pays for itself, then build and deploy them on infrastructure the client owns and can audit.
Infrastructure deployment and level-2 support across a regional health network, where an outage reaches clinical staff in minutes and the rollback plan matters more than the change itself.
My first job in tech: SLA-bound ticket work, hands-on troubleshooting, and a lot of practice explaining a complicated failure to someone who just wants their machine back.
Every time an extraction came out wrong and I went looking, the model had done something reasonable with something it should never have been handed. So I spend most of my time on what goes into the window, and very little on the prompt.
A demo tells you the happy path works. It tells you nothing about the next forty documents. I build the eval set first now, even when it feels like a detour, because the alternative is editing prompts and hoping.
A tool returns something useless, the model works around it, the run finishes clean, and nobody gets paged. That whole class of failure is why I trace every tool call going in and coming out, instead of logging only the ones that throw.
Systems
Structured extraction for video
Private beta
A video and a schema in, typed JSON out. Transcription, scene detection, frame dedup, vision, and a temporal knowledge graph, with every value pointing back to the second and the modality it came from. Exposed as an API, an MCP server for agents, and apps.
My part: Founder. Architecture, extraction pipeline, API and SDK, the site.
Four modules, one metric at the end
In production
Turns an unstructured document into a metric an investment team can act on. The parsing lane reads whatever the file actually holds, text and tables but also charts, images, audio and video, and lands it with a trace of every step. A multi-agent extraction lane runs one versioned agent per metric behind an eval gate, writing results into a staging layer. A desktop cockpit lets the owner of a document correct its metadata. A web app is where a human confirms before anything promotes. Telemetry on every agent run, and nothing promotes on its own.
My part: Architecture, data model, the extraction agents and their eval harness, release pipeline across three environments.
Client system. The names, the internals, and the data stay with the client.
Multi-agent system with security-level access and parallelization
Shipped
Fixed income and currencies research, searchable in one place. A named agent object owns routing and search strategy, the backend executes its tools, and a citation composer links every claim back to the report and the page it came from. One agent run resolves a conversation turn. Runs as a container service beside the warehouse, with a desktop client and trace-level observability over every run.
My part: Agent design, retrieval and tool layer, desktop client, deployment.
Client system. The names, the internals, and the data stay with the client.
Contract lifecycle out of the inbox
In production
Contract records with verified status, period selection, and an in-app PDF viewer, plus a sync that pushes contract metadata into the data catalog. Replaced a process running on shared spreadsheets and email threads.
My part: Full-stack build, catalog sync, deployment.
Client system. The names, the internals, and the data stay with the client.
Open Source
A design system with an agent that applies it
Next.js and React 19 with shader-level Three.js scenes, and an agent trained on the design rules so they hold across builds. This site runs on it.
Your coding agent, on a schedule and on a leash
Runs coding agents as cron jobs. Approval gates before a diff lands, notifications when a run needs a human, and a log of what each run touched.
RAG that never leaves your laptop
A Go CLI that indexes a folder and answers questions about it. Embeddings and generation run locally against Ollama. Single binary, no network, no API key.
A searchable memory of your own machine
Screen and audio capture, OCR and transcription, indexed to a local vector store. Searchable by meaning instead of by filename. Uploads nothing.
The first RAG library for Swift
RAG for iOS and macOS. Apple's native NLP for embeddings, a local Ollama endpoint for generation. No Python backend, no network call.
If you’re building something that matters, let’s talk.