Software is evaluated by whether it ships and whether it crashes. Those are minimum bars. They say nothing about what the software actually does to the people who use it, the people who built it, or the world it runs in. The K Score measures what those bars miss.
The organic label of software engineering.
An organic food certification does not tell you the food tastes good. It tells you that specific standards were met in how it was grown. It is a verifiable claim about process and value, not a marketing assertion. The K Score works the same way. It tells you that software was built to a standard that accounts for everyone it touches.
The score is a number from 0 to 100. It measures how proportional the work is to genuine human flourishing. Not efficiency, not engagement, not growth metrics. The question behind every criterion is the same: does this make things genuinely better for the people involved? That is what gets measured.
The criteria come from a question serious thinkers have tried to answer for two thousand years: what makes something genuinely good, not just apparently good? Three properties consistently emerge across traditions and formulations.
Integritas. Nothing missing. Nothing superfluous.
The thing is complete. Every part serves the whole. A software system fails wholeness when it has features no one uses, promises it does not keep, or sections of the codebase that no one maintains. Wholeness is not the same as finished. It means that what exists is right, and that what should exist does.
Consonantia. Right relation of parts to whole.
The parts are in right relation to each other and to what the product is for. Complexity should match the problem it solves. An interface with twelve options for a two-option decision fails proportion. So does a distributed microservices architecture for an application with three users. Good software is scaled to its task.
Claritas. The thing communicates what it is.
The interface signals its purpose. The code says what it does. The system behaves in ways that match what users expect of it. Clarity is not simplicity. Complex things can be clear. It is the quality of being legible: to users, to other developers, to the organization that maintains it long after the team that built it has moved on.
The Roman architect Vitruvius, writing in the first century BC, described the standard for good building in three words. No structure that fails any one of them can be redeemed by the other two. The same holds for software.
Durability
It holds up. Under load, over time, through changes in requirements and changes in team. Durability is not the same as rigidity. It means the thing was built to last, and that the decisions made during construction reflect that intention.
Usefulness
It does what it is for. Not what someone imagined users would want, but what the people who actually use it need from it. Usefulness is evaluated from the outside, by whether the product serves its purpose in practice, not whether it satisfies requirements in a specification.
Beauty
It delights. The experience is right. This is not ornament applied at the end of the process. It is the quality of something that has been thought through from beginning to end. When something is genuinely beautiful, you can feel that every decision was made deliberately.
A product, system, or codebase evaluated against the K Score standard. Applicable at any stage: before launch to identify what needs work, after launch to document the standard achieved, or ongoing as part of quality maintenance. The output is a score, a full evaluation report, and the right to display the K certification mark.
An individual practitioner evaluated on how they work, not just what they have shipped. This covers engineering ethics, decision-making under pressure, how tradeoffs are handled, and the quality of the systems they have built. A certified engineer has demonstrated that their craft holds to the standard the K Score represents.
Certification produces a K Score from 0 to 100. Above the threshold, you earn the right to display the K certification mark. Below it, you receive a detailed report on what falls short and what closing those gaps requires. It starts with a conversation.
Start the process