Human authority
Models can inform, organize, and assist. They do not inherit the moral authority or accountability of the people using them.
About Akritas Systems
Technology should serve the human person.
Akritas exists to help organizations use powerful technology without surrendering judgment, responsibility, dignity, or ownership.
01 / The measure
Humanity is not a defect to automate away
A system is only useful if it leaves people better able to do good work.
Efficiency matters. So do accuracy, speed, and cost. But none of them is a sufficient measure of progress on its own.
We also ask what the system does to the people around it. Does it support their judgment? Does it respect the knowledge earned through practice? Does it make responsibility clearer? Does it preserve a real path to question, correct, or stop what the technology is doing?
Those questions are part of the engineering—not decoration added after deployment.
Working convictions
What we try to preserve.
These principles shape discovery, system boundaries, implementation, and the ongoing stewardship that follows a launch.
Dignity before efficiency
People are never merely inputs, costs, obstacles, or sources of data to be optimized away.
Discernment before deployment
We avoid both uncritical enthusiasm and reflexive fear. We examine the real workflow, the consequences, and the limits first.
Work worth doing
Automation should reduce needless burden and help people bring more judgment, craft, attention, and care to their work.
Power with boundaries
Access, data, authority, cost, and failure behavior should be constrained deliberately—not discovered through harm.
Shared responsibility
Good systems are built with the people who know the work. Technology should strengthen participation, not impose uniformity from above.
02 / An influence
Magnifica Humanitas
The person stays at the center of the choice.
Magnifica Humanitas gave fuller language to a conviction that shaped the beginning of Akritas’s AI journey: technical power does not grant the right to govern the people it affects.
The document is explicitly Catholic. Akritas serves people and organizations of many beliefs, and no customer is asked to adopt its theology. We do, however, openly carry forward its insistence that human intelligence, conscience, and freedom must guide technology and set its limits.
For us, that means building systems that assist without pretending to be persons, using automation without abandoning responsibility, and judging progress by what it allows people and communities to become—not simply by what a machine can do.
Read the encyclical at the Holy See03 / In practice
Philosophy must change the build
The principles become operating decisions.
- Before the build
- Understand the people, the work, the trusted information, and the consequences of getting it wrong.
- Inside the system
- Use approved sources, explicit permissions, visible uncertainty, human decision points, and the least authority necessary.
- At deployment
- Stage the change, evaluate real cases, protect credentials, limit exposure, and preserve a known-good rollback.
- After launch
- Monitor behavior, cost, exceptions, and human impact; revise the system when the work or its responsibilities change.
The standard we return to
Build the capability.
Preserve the person.
If that is the kind of technology practice you want beside your organization, begin with one workflow worth improving.
Discuss a workflow