Quality
Software rarely breaks with a bang. It breaks quietly: a button moves, an email stops arriving. We write down what your software has to do, and check it on every change.
funnel.erstgespraech.buchenExampleMust hold
The behaviour catalogue
Every behaviour of your software gets a short entry in plain language: who uses it, what must hold, how important it is.
Every test points to the behaviour it checks. If an important behaviour has no test, you see it straight away.
On every change the tests run automatically. Where no test is enough, an AI agent checks in a real browser, and a person checks anything that changes data.
On every change
The same route for every change, whether it comes from an AI agent or a person. If one station fails, nothing moves on.
From an AI agent or a person, always as a traceable proposal.
Biome and TypeScript catch typos and wrong data.
Vitest checks calculations and rules in seconds.
No behaviour disappears from the catalogue unnoticed.
Playwright clicks through the important paths, like a customer.
Code and dependencies are checked for known vulnerabilities.
A person looks at the result and approves it.
With monitoring and a way back, in case something does go wrong.
Every night: full test runs, plus load time and quality with Lighthouse.
Every week: findability, with a local AI model.
Dynamic, not rigid
Classic tests check what someone wrote down months ago. The catalogue describes what should hold and leaves open how it is checked: by a test, an AI agent or a person.
During a rebuild every behaviour is confirmed again. The wave shows at any moment what is checked, open or blocked.
checkedopenblocked
Where no test exists yet, an agent checks the behaviour in a real browser. Only a person checks what changes data.
Every important path has a maximum number of steps. If a rebuild makes it longer, the check fails, even when everything else is green.
A local AI model gets nothing but a one-sentence goal and finds the way itself. How often it has to guess shows where the interface is unclear.
For engineers
mechanics/funnel/erstgespraech-buchen.md
--- title: Book an intro call with a time slot kind: user-facing priority: p0 claims: route: ["/buchen"] verify: e2e ---
e2e/buchen.spec.ts
// @mechanic hansenexus.funnel.erstgespraech-buchen
The catalogue lives as Markdown in the repository. Tests point to their behaviour in a comment, the check runs as a required step in the pipeline, and agents query the catalogue over MCP.
mechanics on GitHubTwo ways
In every package
Every application we build or run for you gets its catalogue, its tests and its pipeline.
As a fixed-price project
Even if we did not build it: we describe what your software has to do, build tests and a pipeline, and hand everything over to your team.
We look at it together in the intro call. 30 minutes, free of charge, by video or phone.