Start Where You Live

This is a draft practice, not evidence that a Samaritan chapter, food network, or software service already operates. Take what fits your place, correct what does not, and keep the people affected in charge.

Begin with one useful circle

Do not start by recruiting a movement or installing a platform. Start with a few people who already live near one another and one task they would genuinely like to make easier.

1. Ask before recording. Get clear consent before writing down a name, address, need, schedule, or contact method.
2. Map offers and needs. Who has a ladder, freezer space, a vehicle, garden experience, an hour for deliveries, or food that would otherwise be wasted? Who would welcome help?
3. Choose one repeatable act. A monthly pantry check, seed exchange, harvest pickup, shared preservation day, or phone tree is enough.
4. Name the stewards. At least two people should understand the routine, hold the current list, and know how to stop it.
5. Keep a paper path. Print the minimum contact and procedure sheet needed to continue when power, internet, or software fails. Store it securely and destroy stale copies.
6. Review after one cycle. Ask what helped, what exposed too much, who was missed, and whether the practice should continue at all.

Food is a relationship, not an inventory problem

A local food exchange can begin with crops already growing, meals already being cooked, and preservation skills already present. Record less personal information, not more.

• Let people state what they are offering and what they would welcome; do not infer need from income, disability, family status, or rumor.
• Record allergens, storage limits, safe-handling requirements, and pickup windows with the item.
• Follow the food-safety and distribution rules where you live. A local guide should link its health authority and be reviewed by someone with relevant experience.
• Use crop calendars and garden notes as planning aids, not promises of yield.
• Make refusal easy. Nobody owes a reason for declining food, a visit, a delivery, or inclusion in a database.

Crop calendars, soil guidance, preservation methods, and food-safety rules must be written for a named place and checked against its health and agricultural authorities. Samaritan does not yet publish a reviewed garden library.

If software would help

A small, isolated agent-assisted cell could later help match offers to requests, remind stewards about harvest windows, or propose delivery routes. It should remain a tool inside the human practice.

Minimum boundaries:

• one named community and one narrow purpose;
• local storage under the community's control;
• explicit consent and a short retention period for personal data;
• sources attached to recommendations;
• no model deciding who deserves food or which need outranks another;
• a named human confirming every allocation or delivery;
• an audit trail people can read without the model;
• an immediate off switch and a tested paper, phone, or in-person fallback;
• no requirement that another community join the same server or copy the same rules.

Isolation is not only a security boundary. It protects local judgment. Groups can exchange guides and improvements without pooling every person's needs into one authority.

Send back evidence, not allegiance

Useful returns include a corrected step, a safer storage rule, a translated sheet, a field report from different soil, or a clear account of why the practice failed. You do not need to become a member or wait for permission to improve your own copy.

Use Contributing for the kinds of material that can come back. Use Connect when another person would help.