Method

How the work is made

Agents build, review and ship. I write the brief and decide when it is finished.

About

I am a product and delivery leader based in Vaud, with more than eight years spent building products, platforms and teams, from a healthcare start-up to a global digital-health platform. I hold an MSc in Robotics from EPFL. My day work is taking AI products from first prototype to scale in regulated settings, and setting up the operating models that make delivery predictable.

This site is the other half: products I build myself, for people I know. A trip organizer for a group of friends, a weekly meal planner for a household of two, a travel companion for a couple, a quiz app for medical students, a quarterly check-in for couples. Each one is finished rather than broad: states, motion, copy and accessibility are all done before a screen ships.

I build this way because I want to find out how far one product owner can go with a well-run team of agents, and to keep the answer honest.

Method

The loop is the same in every project. It is written down in each repository and read by the agents every session.

  1. Brief. I steer as product owner, in short messages, often from a phone. Work is cut into waves, one per milestone, each opened with a one-page brief.
  2. Issue. Every unit of work is a GitHub issue, handled one at a time.
  3. Implementer. An orchestrator session briefs one implementer agent per issue. The agent works on a branch, commits at every step and opens a pull request only when the local gate is green.
  4. Review. A separate read-only reviewer reads the pull request while another agent watches CI. Fixes go to a fresh agent, because long-running agents carried too much context and made review rounds expensive.
  5. Gate. Lint, types, unit tests, a database suite and a build must pass before merge.
  6. Deploy. Merging to main triggers the deploy. The orchestrator polls the health endpoint until the new build hash appears and reports ok.

What stays human: what to build, what to call finished, anything involving money, credentials, deployment or irreversible changes. Agents ask me for those. Each wave closes with a check of the real screens on a phone. A status file and build log carry the memory between sessions.

Infrastructure

Everything runs on hardware I own: a Synology NAS hosting Coolify, which builds Docker images from each repository and deploys on every merge to main. Each product has its own subdomain under borden.ch. Some are private apps for a household or a group, and so are not linked here. This site itself is a static build served by nginx in a container, deployed the same way.

House rules

“It never writes feature code itself; it briefs, reviews, merges and keeps the record.”
mauritius/CLAUDE.md · Build process, on the orchestrator
“It never waits on CI and never merges.”
mauritius/CLAUDE.md · Build process, on the implementer agent
“Every shipped surface is finished: states, motion, copy, accessibility. Breadth never beats finish.”
mauritius/CLAUDE.md · Who and what
“never wait in a loop on CI, a deploy or a health endpoint; done is ‘PR open’.”
mauritius/CLAUDE.md · Subagents

Six products, in numbers

Product First commit Commits Co-authored by Claude Code agents Share
Fig. 1 Popote 20 Sep 2026 1,729 1,498 87%
Fig. 2 Anatomie UNIL 6 Dec 2015 340 101 30%
Fig. 3 Couple Check-In 5 Oct 2025 991 297 30%
Fig. 4 10Lapse 5 Oct 2017 771 675 88%
Fig. 5 Dodo 7 Oct 2026 745 693 93%
Fig. 6 Après-Ski 9 Feb 2026 337 188 56%
All six 4,913 3,452 70%

Read 24 Oct 2026