Critical systems architecture
- Critical data platform architecture
- Strongly auditable systems
- Complex flow modelling
- Distributed architectures, monitoring and flow control
Consulting & architecture
I design critical information systems where you can prove what happened: which data, which process, when, by whom. I extend that same demand for proof to systems that rely on AI — integrity and auditability in the architecture from the first line, never a mere end-of-project report.
Banking, insurance, public finance: environments where wrong or missing data has a real cost — regulatory, financial, operational. That is where I have worked for 20 years.
My approach is constant: make the system auditable by design. We do not bolt traceability on afterwards, we model it with the flows. Control is not a step, it is a property.
That demand doesn't stop at databases. As AI enters production pipelines, the question becomes: can you prove, trace and govern what an AI-assisted system decides and produces? It is the natural extension of my craft — and the heart of my R&D.
Areas of work
How we work together
Time-and-materials mission (long-term), fixed-price architecture scoping, or one-off expertise (audit, second opinion, technical arbitration).
Target architecture dossier, flow and traceability model, control mechanisms, migration plan and scripts, steering indicators.
From a few days (scoping/audit) to several months (transformation, migration). Paris area or full remote. Billed via PHYDYA (SARL).
Cases — problem → intervention → result
Anonymised missions. Named references on request.
A legacy business application (the whole shipping chain: orders, invoicing, logistics, traceability) on ageing Oracle — ~342 tables, technical debt and licensing, strong traceability and integrity-control requirements.
A 3-phase migration architecture (Ora2Pg → staging → TypeORM transformations → target schema), end-to-end hash validation and referential-integrity constraint checks, multi-environment industrialisation (Ansible, dev → prod).
A tooled, reproducible and verifiable migration — integrity proven table by table, with no loss or drift.
Migrating finance data from a legacy ERP to Workday, with an integrator, across many domains (parties, banking, fixed assets, invoices, warranties, claims…) and several runs — strict reconciliation required, "zero difference per stream".
Data Migration role: scoping the perimeter object by object, migration strategy (pivots, runs, tenants), canonical business rules, accounting reconciliation, tracking and decision mechanisms (supported by AI-assisted steering with deterministic controls).
A structured, governed migration, perimeters agreed object by object, on track for a controlled go-live.
Steering and modernising the group's Data & BI activities — ageing ETL chains, heterogeneous decision indicators.
Directing a service centre (20 people, a €12M portfolio over 4 years), ETL modernisation, indicator standardisation, technical governance, value-driven steering and KPIs.
Industrialised, standardised Data/BI activities, value-driven steering.
New ground
AI is entering production pipelines: the same demand for proof applies. I design auditable AI architectures — governed agents, quality gates, decision traceability, formal verification of invariants — so that what an AI-assisted system decides and produces stays verifiable end to end.
See my /gov frameworkMethod
I start by understanding the business stakes and real constraints — not by picking a technology. The target architecture follows the need for proof, not fashion.
Traceability, lineage and control mechanisms are modelled with the flows. Every process leaves a verifiable trace. Nothing is added "at the end".
Tooled pipelines, standardised indicators, coordinated teams. I deliver a system your teams can run and evolve without me.
Technical environments
Migration, compliance, control mechanism, architecture scoping: tell me the context.