deleguix REF · DLX/THE-MACHINE LAST UPDATED · 2026-07-16
Production systems · France

The Machine

One human, running a company of agents that markets, sells, writes, reviews and operates.

Deleguix is a French services company: tradespeople delegate the admin that eats their evenings. This file is about the engineering underneath it, an agent company with written doctrines, coded gates and adversarial review, plus what else came out of the same workshop. Every headline metric is read from live system state.

01 / 07 The business

A real company, not a demo.

The pitch fits in one line: you do your trade, we handle the rest. The plumber's unanswered phone, the quote nobody follows up, the invoice nobody chases. Subscription offers per trade, a booking page, and a lead capture that reaches the operator within the minute.

The founder does the client work. The machine does the marketing, the vetting and the follow-through, which is what the rest of this file describes.

30pages on the live site
150social visuals banked, art-directed and reviewed
25workflows in production
9packaged service templates
02 / 07 The brain

Twenty-two employees. None of them human.

The staff are named agents with written briefs, doctrines and vetoes: an orchestrator that routes work, analysts, writers, an art director, a French grammarian with veto power, adversarial reviewers, a conformity validator that scores every deliverable out of ten, and a doctor whose patients are the other agents.

Every request moves through the same spine, whatever the job is: a cold email, a poster, a web page, a hiring brief.

Request

One line from the operator, often from a phone.

Orchestrate

Intent decoded, routed to the right specialists, sequential or parallel.

Produce

Specialist cells do the work. Each reads its brief first; the core doctrines are versioned documents, amended after every incident.
GATE · CODE

Gate

Deterministic checks where they exist. Code flags, never decides alone.

Review

Adversarial pass, briefed to refuse. Creators never validate their own work.

Validate

Scored out of 10 against fixed criteria. Below 8 does not ship.
the founder sees only what survived all of it doctrines are versioned documents, amended after every incident

The company also remembers. A persistent memory graph (entity and project nodes, plus a state file updated in the same session as every event) is read before any non-trivial action, so lessons survive across sessions instead of being relearned. And it self-repairs: the doctor agent audits the staff for drift, broken briefs and duplicated roles, and archives before every treatment.

Two rules hold the whole thing together. Writers never see raw data: they get a verified diagnosis. And reviewers never create: the one time they crossed that line, a second agent caught the pattern they had introduced and the fix was rolled back.

+ 14 more across strategy, research, copy, studio and recruiting.

BATCH-48 · REVIEW LOG · what refusal looks like in practice

V1
REJECTED

Same call-to-action shape on 12 of 14 emails.

V2
REJECTED

"The mould moved." Fix relocated the pattern instead of removing it: 7 of 14 now share the pivot.

V3
REJECTED

Two emails never name the company. The reader finishes without knowing who "we" is.

V4
PASS

Shipped. Final fix was insertion and deletion, not creation: inside the doctrine.

03 / 07 Acquisition · the cold machine

Seven stages. Each one exists to refuse something.

Pick

30 prospects from a 21k reservoir. Chains, branch offices, third-party platforms and implausible names are dropped before anyone reads them.

Analyse

An agent visits the prospect's actual website. Output: one verified anchor fact. Never a draft.

Write

Sees only the diagnosis, never raw data. One email, one observation.
GATE · CODE

Gate

Versioned law. 92 banned patterns, clone detection, checks on the rendered email. One hit: batch exits red.

Review

Adversarial agents prompted to refuse. Most batches bounce at least once.

Bank

Append-only. The loader aborts if send history would shrink.

Send

5 weekday slots, human-like jitter, suppression list, kill switch.
45 to 57% of a raw batch dies at analysis the gate is deterministic, not a model an illegal batch cannot reach the sender

The hard problem is not duplicates, it is structure: a batch can pass every duplicate check while being the same email fourteen times with the nouns swapped. Three structural detectors compare every batch against the bank and against itself (the phrase that reached 119 occurrences in the bank was born at 2). All three are advisory: the code flags, a reviewer decides, and the documentation states the boundary plainly: semantic moulds remain invisible to code. No pretending otherwise.

04 / 07 Zero fabricated facts

Code cannot see a lie. So something else has to.

Language models fill a data vacuum with plausible detail. At scale, that is the failure mode that burns a domain and a reputation. It was caught early, treated as an incident, and engineered out.

INCIDENT-001 · FABRICATED DETAIL AT SCALE 2026-06-27 · RESOLVED
Summary

First scaled batch: 7 of 20 emails invented facts. A Michelin mention. A "since 1925". A Bugatti. None existed in the source data.

Detection

Adversarial review. The coded gate was green: code checks patterns, not truth.

Root cause

Writers received thin data and filled the gaps with plausible texture, as language models do when nobody stops them.

Remediation

Guardrail written into four layers: writing doctrine, both agent briefs, generation prompts. One number is allowed into an email: the prospect's public review count. Everything else must be a logical consequence of their trade.

Verified

Every audited sample since: zero fabricated facts.

Addendum

The subtle leak came later: the brief itself once handed the writer an unsourced fact. The writer refused it and escalated. Standing rule since: the diagnosis is the contract, and the writer is the last line of defense, even against instructions.

05 / 07 Ops discipline

The part a security engineer checks first.

06 / 07 Same workshop

Other builds, same hands.

healwithquetzal.com

LIVE

A trauma-informed coaching practice, shipped end to end: bilingual site with a WebGL sky that responds to the cursor, a built-in nervous-system regulation panel (guided breathing, grounding exercises), booking on Cal.com, payments live on Stripe, structured clinical intake. Built for the coach in the family.

Sugod Bisaya

PLAYABLE

A Duolingo-style app for learning Cebuano: lessons, quizzes, lives, streaks, XP, and 298 recorded words and phrases with audio. "Sugod" means "begin". Built to learn the family's language, one streak at a time.

The video factory

STAGED

16 themed channels mapped and ~95 short-video scripts written by a writers' room of agents, with a greenlight committee that scores every pitch out of 100 and kills the weak ones. The n8n generation pipeline is proven end to end. Paused on generation budget, deliberately: infrastructure first, spend later.

07 / 07 Live state · 2026-07-16

Real numbers, not projections.

21,224
reservoir
1,498
queued
1,265
banked
748
sent · 3 touches
60
emails per day · unattended · deliverability-capped
22agents on staff
25workflows live
4products shipped or staged

Operated by 1 human. That is the point.