A Commons in Practice

Samaritan exists to make people more capable, then release enough control for the practice to become theirs.

This is not a membership promise or a platform waiting to gather users. It is a place to leave methods, tools, and field notes where another person can pick them up without first needing Casey as an interpreter.

Keep authority close

The people affected by a decision should remain able to understand it, refuse it, change it, and stop it. Data stays as local as the work permits. Software assists named people; it does not quietly become their governor.

Authority also needs an exit. A neighbor network should survive a dead server. A food exchange should survive a failed model. Keep the paper list, the phone call, the person who knows the route, and the right to walk away.

Test it somewhere

A method becomes useful when it meets a place: different soil, hardware, weather, law, money, skill, and trust. Name those conditions. Record the part that failed. Do not turn a proposal into proof by writing it confidently.

Small work is enough. One crop note corrected for local weather, one safer deployment pattern, or one consented contact tree is more valuable than a universal system nobody can govern.

Let it travel

Read it, save it, print it, adapt it, or teach it. Return a correction, a local version, or a failure report when you can. Code and other reusable artifacts keep the license named by their owning project; free access does not erase that boundary.

Lineage should remain visible without becoming central control. Samaritan began with Casey Tunturi's work, but a healthy commons can continue when he is not in the room. His history belongs at caseytunturi.com. Souveraine's design record belongs at souveraineai.com. What belongs here is the part another person can carry home.

Start where you live.