Olivier Debeuf De Rijcker

Chief AI Engineer

I build agent systems.

I work with stakeholders to turn ambiguous business problems into useful products and stay involved through architecture, code, evaluation, and production acceptance.

01 / Practice

I find useful business problems with stakeholders, shape the product, build it, and stay involved through acceptance.

Useful model output depends on context, tool boundaries, state, evidence, and clear interfaces.

The implementation covers retrieval, ranking, agent workflows, evaluation, observability, privacy, and production verification.

02 / Systems

I take product work through production verification.

That includes product framing, architecture, code, evaluation, and commercial constraints.

Role
Chief AI Engineer
Mode
Builder + seller
Span
Product to runtime
03 / Record

Selected evidence

Product launchPublic / linked

Seld

Launched Seld, a local-first, open-source AI chief of staff that keeps open work, decisions, evidence references, and next actions in plain files so agent sessions can be replaced without losing the outcome. I built the product architecture, deterministic continuity layer, public site, and evidence-led release process.

Product + engineering / Open source / Local-first / Agent continuity

Open seld.ai
Open sourcePublic / linked

codex-multiprovider

Released codex-multiprovider 0.1.0 alpha, which lets Codex use Kimi K3 and experimental Claude routes through an external CLI bridge. It includes fail-closed routing, a gated continuity preview for provider exhaustion, Fable review, and private ChatGPT Pro handoffs without changing the signed app.

Python / Codex CLI / Provider routing / Local continuity

Open repository
Open sourcePublic / linked

Databricks MCP Server

Built and open-sourced an MCP server that lets coding agents inspect and operate Databricks environments across notebooks, SQL, and Unity Catalog.

Python / MCP / Databricks / Agent tooling

Open repository
Upstream reviewPublic / linked

Claude Code 2.1.0 regression

Diagnosed a Claude Code 2.1.0 release crash, traced it to semver parsing of a dated changelog header, and submitted a minimal repair. Anthropic confirmed the fix and closed the report.

Failure analysis / Root cause / Upstream review

Open reviewed PR #16683

04 / Method

  1. 01

    Failure analysis

    I start with the point where the model, data, product, and operator disagree.

  2. 02

    Context design

    I treat state, tools, evidence, and permissions as part of the system.

  3. 03

    Testable claims

    I version prompts and schemas, then tie confidence to evidence.

  4. 04

    Runtime verification

    I check deployed behaviour after the branch passes its tests.

  5. 05

    Human control

    People retain the final decision on architecture, risk, acceptance, and consequential actions.

05 / Contact

Technical conversations, open-source work, and media.

Build
Next.js / TypeScript / static export
Type
Onest / IBM Plex Mono
Background
Engineering / company building / commercial operations