I design your architecture, and I make its rules verifiable by machine.

A developer carries out a decision; an architect takes the one the others depend on. You need an architect when a structural choice commits the months that follow — which boundaries, which data, which dependencies, and who answers for what. The cost of a badly set architecture is paid later, in rewrites, in incidents and in features that have become impossible to add, often once nobody remembers the original choice. What we discuss is what there is to do and in what order. If you are unsure, the one-hour session gives you enough to decide.

You keep control of your code. For the one-hour session, you are the one who runs a reading program on your own machine. It reads the structure of the project, its dependencies, its configuration files and the history of changes. It does not modify your code, it makes no network calls, and its output appears on your side: you read it before I do. For the three-day audit, read access to your repository makes the work considerably finer; working from an export you prepare remains possible, and a confidentiality agreement signed before the first minute poses me no difficulty. This reluctance is rather a good sign: a director who hesitates to open their code to a stranger has already understood something.

Yes, that is my usual way of working. Architecture is decided in writing: a document that gets read back, a rule a machine verifies, a dated decision with its reasoning. These objects outlive the meeting that produced them. A decision taken out loud, between people who agree at the time, leaves nothing to whoever arrives six months later. I work from Montpellier for clients who are elsewhere, and I travel within France for a framing workshop or a presentation of findings when the meeting warrants it — counted in engagement days, with no disguised surcharge.

Yes. What carries across from one language to another are the separations: which rules your system must guarantee, where they are verified, and what happens when someone crosses them. That reasoning holds in Python, Go, PHP or Ruby, and I have worked on languages other than my own. My strongest expertise is Node.js and TypeScript: that is where I commit without reservation, and on an audit in another ecosystem I distinguish in the report what I read with certainty from what I read with reservation. For a long-running engagement on another technology, the right arrangement is with a counterpart in your team who practises it daily — and I would rather tell you that now.