Chapter 5 / 17
The engagement
The engagement runs five weeks and is structured as chapters, not calendar weeks. A chapter closes when its criteria are met — not when Friday arrives.
Chapter 1 — Ground Truth In Progress
Everything is set up and in place. The AI computer is running in the server room and reachable remotely. All four domains are managed on Cloudflare. The GitHub organisation exists with the first repositories published. Credentials are documented and distributed to all four seats. Rani’s laptop has completed three paired working sessions. This changelog site is live.
Chapter 2 — Data Liberation Blocked — Florian's dump
Sodiwin data arrives automatically every night. The pipeline processes it and loads the database before 03:00. Paul confirms the numbers match what he sees in Sodiwin. Automated alerts fire if Florian’s files change format without notice.
Chapter 3 — Email Freedom Blocked — Framework Desktop + ISP ticket
All 33 mailboxes have moved from Strato to the on-prem mail server. Every domain has full email authentication. The archive is indexing every message. Strato is cancelled.
Chapter 4 — AI Layer Online Blocked — depends on Chapters 2 and 3
AI tools can reach Sodimo data end-to-end. Rani’s pre-call brief returns real data on a real customer. At least one AI skill runs daily from at least three seats.
Chapter 5 — Transformation Measured Planned
Morning briefs go out at 07:00 automatically every day. The board report skill generates the Fattal monthly report from live data, approved and sent by Paul. Collection letter drafts queue for Paul’s approval. The dual-axis dashboard shows real numbers.
Chapter 6 — Handover Planned
Per-role guides are printed and delivered in French. Every operational procedure is documented — certificate renewal, adding a mailbox, bare-metal restore. Credentials have transferred to Paul with emergency access for Jack.
Chapter 7 — Compound Layer Continuous
Starts day 1, never closes. Daily notes, weekly Friday Reports, the public case study.
“Deployed” has a strict meaning used throughout this manual.
A workflow is deployed when the person who used to do it manually no longer does it, and the replacement has run for five consecutive business days without Thomas touching it. A workflow built Monday and broken Tuesday is back to “in progress” until the next clean streak. A merge does not move the number. A deploy does not move the number.
Regressions ship as new releases.
If the mail server goes live April 22 and breaks April 23, the release feed reads:
2026-04-22-postfix-live → 2026-04-23-postfix-deliverability-issue → 2026-04-24-postfix-restored
The past is never edited. The honest record is the point.