Chapter 1 / 17

Welcome

This site is the living manual for how Sodimo works in 2026 — the people, the processes, the data, and the infrastructure. It also doubles as the release feed for every piece of software and configuration Thomas ships during the five-week engagement (Apr 14 – May 16, 2026). One URL, one evolving document.

The audience is internal. Rani runs most of the day. Paul signs the invoices and owns the data. Jack signs contracts and unblocks the ISP. Michel reads the Friday board memo from his phone in Dubai. Future team members read it to understand how the pieces fit together without having to reconstruct the decisions from scratch. The site is gated behind Cloudflare Access — only sodimo.eu email addresses and Thomas’s thomas@leger.run get in.

Two ways to read this manual. The first is top-to-bottom, once, to build the mental map: who, what, where, why. The second is as a reference — when you want to know why the mail goes through an on-prem box instead of Gmail, or why the quote tool talks to a black-box ERP over SFTP instead of a clean API, you come straight to the relevant chapter.

A convention runs through every page. If something is decided and shipped, it is stated as fact. If something is still open, it says so specifically, with the owner and the blocker named. Example: as of Apr 20, the TARIF code dictionary is pending from Paul — see chapter 16. No hand-waving.

The changelog itself is append-only. When a piece of infrastructure breaks, the event ships as a new release (2026-04-23-postfix-deliverability-issue), not as an edit to an earlier one. The history is the honest record. The gauge on the home page — two numbers, one defensive, one offensive — only moves when a workflow has run five consecutive business days without Thomas touching it. “Deployed” has a strict meaning here: the human who used to do it no longer does it, and the replacement has held for a business week.

The engagement is structured as chapters, not calendar weeks. Chapters close on criteria, not the calendar. The chapters are listed in Part 1.

Everything here is written in English. The internal operation is bilingual — French is the working language with the team — but this manual is English because a second audience reads over the shoulder: future Sodimo engineers, the Fattal group post-acquisition, and external operators who may one day adopt the same playbook.