/ Method
Shipped fast, built to last, sovereign.
The specification drives, the AI executes, the human decides — and your data stays in Europe.
01 — Spec-driven
The spec before the code.
Every change starts from a written, validated, archived specification. The spec is the durable asset — it outlives both tools and models.
The spec also outlives its author: because every change is specified and documented, the product is resumable by any team — no black box, no lock-in.
02 — Harnessed AI
AI accelerates. Humans decide.
It doesn’t only accelerate: it broadens the range one person can cover end to end — design, code, ops, architecture. One maître d’œuvre delivers what used to require a team, with judgement and business understanding the constant that guarantees quality.
Why — where it accelerates
- →Prototyping and exploration in a few hours.
- →Boilerplate generated from the spec.
- →Docs and tests kept up to date.
How — where the human decides
- ·Architecture, security, data model.
- ·Supervised code review before production.
- ·AI terms: no retention, no training.
03 — Sovereignty · GDPR
“An AI outside Europe?” Sovereignty remains intact.
Production data stays in Europe and is never used to train the AI. For code, the best models are American today (Anthropic, OpenAI, Google) — but it isn’t locked in: since the spec is the durable asset, I’ll switch to a European model frictionlessly the day it reaches that level.
- User data hosted in the EU — never sent to the AI.
- The AI sees code and specs, not data (build ≠ run).
- AI model not locked in — the spec lasts; I switch to an EU model once it’s good enough.
- Code on gitlab.com or EU self-hosted — outside GDPR.
04 — The proof, live
This page was born from the method.
Same cycle as your features: propose, apply, archive.
Click on a step
- ## Method page- Hero: result promise- Address the sovereignty objection- Live demo of the cycle
A spec states the what and the why, before a single line.
- ✓ promise hero✓ sovereignty section✓ demo island✓ FR / EN tests
The code realizes the spec, task by task, under human review.
- method-page → specs/changes/archive/2026-…
The validated spec joins the source of truth. A memory, not just code.
Meta, but true: this cycle produced the page you’re reading.
Shall we talk?
Does this way of working speak to you? The next step fits in a single conversation.