To fettle something is to put it into good condition. For us, that starts with understanding the job — and continues through the choices, explanations and details around it.
A clear explanation is more useful than false reassurance. A tool should make uncertainty visible and distinguish what it tried from what it can confirm.
That honesty belongs in how we describe our work, too: clear about what it does, where its limits are and what still needs attention.
Useful defaults should not quietly become permission. People should understand what a tool will do and have a meaningful say in what happens next.
Choices deserve clear consequences, room to reconsider and respect for the preferences you have already expressed.
Care is a readable result, a preference that is respected, a next step that makes sense. It is also knowing when a tool cannot help and saying so.
Fettle is independent. We build with care for the people who will use our tools and the work of maintaining them.
We favour understandable tools and documented behaviour. Longevity is a responsibility to work towards, not a lifetime-support promise.