Prove before claiming
A green build is not proof. Required artefact: test, device, dated capture, or the live protocol above.
See the protocolFrom design to systems
I design, I build, I prove.
Art director and builder in Paris. Medical sites, own media product (Guidechirurgie), systems with replayable proofs, open source. Every claim has a proof, a limit, or an embargo.
Reading shortcuts, or run the protocol.
The jellyfish is a Studio Azur piece. Click in the water: it reacts. Nappe (plankton + hand) is the sequel. Open Azur N3 · swim
Review protocol · live
Your browser queries GitHub, npm and PyPI. A gate replays a refusal. What stays closed is named: embargo, client data, device demo.
01–04 read live. 05 = network ping. Failure = KO, never a fake chip.
Not verified here: measurement method (INPI embargo) · client data · real-device demo on request.
Public repositories: release gates, quantization, vault tooling, generative work. Every README separates what is proven from what is not. Repo count is read live.
Deterministic gates for agent runs: npx -y -p agent-proof-kit agent-proof verify replays the proof locally, no API key, no network. Published on npm. Version on the live chip.
Bounded AI code edits via fill-in-the-middle: only the region between two anchors is rewritten, the rest of the file stays byte-identical.
8-bit quantization of a 4-billion-parameter TTS: hand-written WGSL GPU kernels, Metal and Vulkan. Public upstream PR. Status on the live chip.
The product site of the skin-reading app (acuence.app): public host reachable from the browser. Full DNS/TLS ownership and infrastructure: outside the live protocol, available on request.
The ACUENCE trademark, filed on 24 June 2026 with the INPI (classes 9, 42, 44), published in BOPI 2026-29 on 17 July 2026. Official status: application published. The associated patent application stays confidential during review.
Real output, recorded on 9 July 2026 against the repo's public fixtures. Replayable: npx -y -p agent-proof-kit agent-proof verify. The third call shows the refusal: the gate fails closed.
Systems
Six files. For each: the status, what can be proven, what stays closed.
iOS · pre-launch · IP filed
An iOS skin-reading app. The heart of the product is not the score: it is reading reliability. The app prefers to abstain rather than assert when the signal is insufficient, and that behaviour is tested.
Tests counted on the repository on 9 July 2026.
Web · product & clients
Own product first (Guidechirurgie: editorial media, SEO, AdSense/Ezoic/affiliate), then client sites: medical, real estate, services. Design, SEO, hosting.

Health media · Own productProduct · monetised
Editorial media built end-to-end: architecture, content, international SEO, monetisation (AdSense, Ezoic, affiliate). Proof a site can rank and fund itself without a services catalogue.
Visit siteBefore AI
Five years of art direction. Identities, campaigns, installations. The eye trained there refuses a fuzzy claim in a product.
Background
Trained in graphic design (EPSAA, École Estienne). Years of art direction, then building AI products and infrastructure under real conditions.
Today: Guidechirurgie (health media built end-to-end, SEO + AdSense/Ezoic/affiliate), medical client sites in production, a real-estate legal SaaS, a skin-reading iOS app in pre-launch (ACUENCE trademark, patent under examination), and open-source tools on npm and PyPI.
Method: prove before claiming; name embargo and non-public work; retire what does not prove its value.
Discipline
Not a manifesto: rules already visible in the protocol, the files, and the applied boundaries.
A green build is not proof. Required artefact: test, device, dated capture, or the live protocol above.
See the protocolOn Acuence, every PubMed citation is script-verified. A blocking gate runs before any ship.
Acuence fileINPI embargo, no medical dosages, no client data in public, no risky agent action without confirmation.
Read the closing lineWarren, a trading agent, was paper-evaluated then retired. What does not prove its value leaves production.
Hermes fileQuestions
A few method points, without a pitch.
Health structures (sites and SEO), product teams that require design direction and proof, technical reviews of an AI system or a production site.
Your browser queries GitHub, npm and PyPI. A KO chip is never invented. INPI embargo, client data and device demos stay off-page, and that is stated.
Yes: architecture, content, production, follow-up. Institutional tone, no dosages or clinical promises on delivered sites. References are in the Sites section.
An email to contact@acuence.app with the context and the level of rigour expected. What cannot be public is shown on a call or in person.
Paris and Île-de-France. Remote work depending on the engagement.
Contact
Real-device demo, infrastructure architecture, full protocols: whatever cannot be published here is shown on a call or in person.
contact@acuence.appGraphic design and systems. One standard: prove before claiming.