You are the brain, the tool reasons
The programme does not teach a tool. It sets up a way of working: the assistant prepares, the person decides, and every success becomes a method you replay.
What the assistant does, and what it does not
- Reading and drafting
- The assistant reads mail, messages and files. It sends nothing: the person reviews and sends.
- No automatic sending
- No payment, no write into a business database, until the rule is changed in writing.
- The real state before "done"
- The assistant checks the real state before it says a task is done.
- Every correction counts
- A draft corrected by hand feeds the next one: the assistant writes in the person's voice.
A kit, not a course
- Numbered pieces
- Each step has its piece: mirror prompt, case card, agent card, charter, roadmap, follow-up block.
- Opened step by step
- The pieces open as the day goes, behind the day code given in the room.
- In French and English
- Each piece exists in both languages, with the same reference and the same structure.
- One default tool, transposable
- The default tooling is Cursor. Each piece transposes to another assistant, except the installation, which is specific to the tool.
Governance, in writing
- The usage charter
- Written by the group at the third stage, signed by leadership.
- One annex per assistant
- At level 2, each assistant that runs has its page: the data it touches, its rights, who validates what goes out, how it is stopped.
- The run log
- The proof that an assistant runs, week after week, without anyone watching it.
See the programme stage by stage
3 or 4 days on site, 2 days of remote follow-up, then the Associate and Advanced levels.