# About AiOverload is built by Johannes Girard, a senior platform engineer working remotely from Normandy, with a preference for inspectable systems over inflated claims. Source: https://aioverload.io/about/ {{< section id="person" eyebrow="THE MAINTAINER" title="A platform problem, built by a platform engineer." >}} I’m **Johannes Girard**, a French senior platform engineer working fully remote from Normandy. AiOverload is my independent project, built in my free time and developed in the open from the public release onward. The starting observation was simple: agent capability was accelerating faster than the operational discipline around it. I wanted the same things I expect from other consequential systems — reviewed configuration, explicit authority, deterministic state, and evidence that survives the session. Find me on [GitHub](https://github.com/JohGirard) and [LinkedIn](https://www.linkedin.com/in/johannes-girard/), or [email me directly](mailto:johannes.girard@gmail.com). {{< /section >}} {{< section id="method" eyebrow="THE METHOD" title="AI pair-programmers. Hermetic checks. Human accountability." class="section--tint" >}} AI tools help write and review the code; they do not become the project’s authority. The work is held by schemas, end-to-end tests, a live NATS stack, dependency and vulnerability checks, and a threat model that records real failures. The site follows the same discipline. Engine facts are generated from a source commit. Limitations sit beside claims. Build-log entries name the merge stamp instead of announcing vague progress. {{< /section >}} {{< section id="ambition" eyebrow="THE AMBITION" title="Small enough to inspect. Serious enough to trust with a pause." >}} AiOverload is new and has one maintainer. There are no customer logos, adoption numbers, or reliability benchmarks to borrow credibility from. The project has to earn inspection through its implementation and its record. The ambition is not to make agents look magical. It is to make their authority legible: what they were asked to do, what they were allowed to touch, when a human intervened, and how the run ended. {{< /section >}} {{< next "/log/" "Read the project’s trail" "Short merge notes, source stamps, and the changes that actually landed." >}}