An agathogen is the structural inverse of a pathogen — agathos + -gen, a thing whose spreading produces good. A pathogen propagates because propagating serves the pathogen. An agathogen propagates because propagating serves the host.
Most technology is built as the first and marketed as the second. Building the second on purpose is an engineering problem, a legal-structure problem, and a moral problem — in ascending order of difficulty.
Good intentions are not a mechanism.
Anything that only produces good while its makers feel like it is not an agathogen. It is a mood. The difference is whether the good survives the people who promised it — which makes this three problems, not one, and they do not get easier in the order you meet them.
Make it verifiable.
Sealed, signed, content-addressable work that re-verifies on every install and every invocation. A digest mismatch does not warn. It gates.
Make it unrepossessable.
Steward-owned and purpose-trust structured, so the architecture cannot be taken back. No cap table. No acquisition path. No shareholder to betray the mission to.
Make it declared.
Purpose, refused behaviours and voice written down in version control and injected on every call. Behaviour is declared, not hoped for — and someone has to decide what it should be.
Not for power. Not for profit.
But for the good of all.
An agathogen learns and it understands, and then it has to act — with wisdom, compassion and integrity, or the word means nothing. These five are the ones the work is measured against.
One idea. Several doors.
Agathogen is the idea stated plainly. The tools, the architecture and the mission each have their own address, and each one stands on its own.
