Working draft · For author review
Why the Covenant
belongs here.
What does a technology make possible for the person who uses it? And what does it quietly take away?

I wrote the Covenant because technical capability does not tell us what to build. A system can become faster, more connected and more useful while leaving its users with less control. The interesting question is what rights survive that improvement.
My research began with minds developing in social environments. How does a young person learn to act, decide and judge risk? Those questions are not the same as questions about technology, but they keep me attentive to the conditions around a person. Agency is exercised somewhere. The surrounding systems matter.
From a commons to a commitment
Open science made that relationship tangible. A result is more useful when someone else can inspect the data, reproduce the method and build on the work. OpSci brought those concerns into infrastructure. The DeSci movement opened up a wider discussion about who funds discovery, who participates and who benefits.
Access alone does not settle the question. A network can call itself open while concentrating decisions in a few hands. A dataset can be available yet practically impossible to use. A new tool can reduce the cost of doing science without changing the institutions that decide which questions receive attention.
Rights belong in the design
The Covenant sets out a different test. Can a person establish their personhood without surrendering their identity? Can they control their keys and protect their private information? Can they participate in a shared system while remaining free to leave it?
These are design questions with institutional consequences. At human.tech, they connect to identity, wallets and the public services built around them. They also require difficult choices. Privacy needs accountability. Security needs recoverability. Public infrastructure needs to serve people who did not choose its implementation.
A document that can be used
I want the Covenant to be read alongside the work, where its principles can be tested against actual decisions. That is why it belongs on this site. It connects the research, the scientific commons and the systems I help build.
The reading copy preserves a specific version. The more useful continuation is in the examples: what a principle changes in a design, where it fails, and what has to be revised. Those are the essays I want to write next.