Engagement 01
Fixed-scope project
A specification with acceptance criteria, then one delivery against it. A change to the scope is re-scoped in writing rather than absorbed silently.
Everything below is inside the scope registered on 11 August 2026, set verbatim at the foot of this page. The registration covers two further fields — game development, and research and development including competition entry — which are areas of activity rather than packaged services, so they appear on the About page instead. Work outside the registered scope is declined rather than improvised.
01
Development, adaptation and operation of applications, from a single-purpose internal tool to a browser application that has to keep working offline. Existing codebases are taken over as readily as new ones.
Work is done against a written specification with acceptance criteria, so that "done" is a fact rather than an opinion.
You receive
02
Development, training and licensing of models, and the services built on top of them. Two applications are named in the registration and are the ones actually built: machine translation, and automated document capture.
Models are sized for the hardware the operator already has. The prosthesis student model is 2,232,839 parameters and 8.9 MB of ONNX because it has to answer inside 125 ms in a browser; the translation pipeline is sized to one consumer GPU for the same kind of reason.
Evaluation is part of the work, not an afterthought. A model ships with the harness that measured it and the numbers it produced, including the runs where it lost to its own baseline.
You receive
03
Technical consulting, adaptation, maintenance and operation of systems that already exist. This is the least glamorous group and often the most useful one: a pipeline that breaks every second week, a deployment nobody dares to touch, a model whose numbers stopped matching reality.
The first step is always a written assessment with an ordered list of what to fix and in what order.
You receive
04
Creation and editing of graphics, video and audio. In practice this is the material a technical project needs in order to be understood: diagrams, screen recordings of a system running, edited demo footage.
You receive
Three forms of engagement. Which one applies is settled in writing before work starts, together with the scope it covers.
Engagement 01
A specification with acceptance criteria, then one delivery against it. A change to the scope is re-scoped in writing rather than absorbed silently.
Engagement 02
A bounded read of a codebase, a model or an evaluation setup. The output is a written assessment with an ordered list of findings, and it carries no obligation to commission the fixes.
Engagement 03
Continuing responsibility for a system that is already running, including systems written by someone else. Agreed in writing, with a stated scope and a stated way out.
Registered scope of business
Quoted verbatim from the German trade registration. Not translated.
Entwicklung, Anpassung und Betrieb von Individualsoftware und Webanwendungen; Entwicklung, Training und Lizenzierung von KI- und Machine-Learning-Modellen sowie Bereitstellung darauf gestützter Dienste, insbesondere maschinelle Übersetzung und automatisierte Dokumentenerfassung; IT-Dienstleistungen einschließlich technischer Beratung, Anpassung, Wartung und Betrieb; Entwicklung von Computerspielen; Erstellung und Bearbeitung digitaler Medien (Grafik, Video, Audio); Forschung und Entwicklung im Bereich Software und maschinelles Lernen einschließlich der Teilnahme an Forschungs- und Entwicklungswettbewerben.