Running an Exchange 17 of 17 in this collection

The Village Exchange Agreement

Running an Exchange · 4 min read · original

NeighborNet only works if the culture is aligned. This agreement is the shared boundary that prevents:

scope creep
martyrdom
guilt-based yeses
silent resentment
chaos in the feed
uncontained conflict leaking into operations

The short version

We agree that:

consent and capacity are real
small requests win
offers include boundaries
no scope creep
close the loop
privacy protects safety
stewards protect clarity and capacity
conflicts go in the right container

Why it matters

A village can survive imperfect tools. It cannot survive unclear expectations and invisible labor. This agreement keeps the system human and sustainable.

This agreement exists for one reason:

So the village can support each other without burnout, guilt, rescuing, or quiet resentment. A simple set of norms so help stays clean, kind, and sustainable It is not a contract. It is a shared culture boundary.

1) Our purpose

We use VillageTRACK360 ("VT360") to make exchange:

clear
timeboxed
consent-based
easy to participate in
sustainable over time

We want a village where care is normal, not heroic.

2) Consent and capacity are real

Everyone has different:

energy levels
nervous system capacity
time availability
emotional bandwidth

So we agree:

No one owes anyone help.
No is allowed.
Yes has limits.
Capacity changes week to week.

Declining a request is not rejection. It is honesty.

3) Requests must be small enough to succeed

We agree to make requests matchable by including:

what we need
time window
location
scope size (small, medium, large)
emotional load (low, medium, high)
what “done” looks like

If a request is too vague, it will be marked NeedsInfo until clarified. This protects everyone’s time and nervous system.

4) Offers must include boundaries

We agree to offer in a way that protects ourselves by stating:

what we can do
how long we can do it
when we are available
what we cannot do

Open-ended offers create hidden expectations. Timeboxed offers create trust.

5) No scope creep

We agree not to expand a request mid-session. If more help is needed:

complete the original request
create a new request for the rest

This prevents helpers from feeling trapped and prevents resentment.

6) Clean communication beats perfect communication

We agree to keep communication simple and direct:

confirm time and place
communicate changes early
cancel respectfully if needed
close the loop when complete

Ghosting is harmful. Silence creates confusion.

7) VT360 is not a container for relational conflict

We agree not to use requests as a backdoor to process emotional or relational tension. If something is emotionally charged, we name it clearly and route it to the right container:

a listening request in a care domain
a mediation or repair process
a tension record if needed

This protects the exchange system from becoming a drama pipeline.

8) Privacy is part of safety

We agree that:

Pulse checks are private
contribution and balance data are private
stewards do not share private patterns publicly

If a steward checks in with you about capacity or imbalance, it is support, not punishment.

9) Steward role and authority

Stewards are not bosses. They are responsible for:

request clarity
clean matching
protecting capacity
closing requests cleanly when needed
keeping minimal system memory

Stewards may pause a domain or reduce scope if the village is overloading. That is not control. That is system protection.

10) Completion is part of care

We agree to close the loop. When help is completed:

requester acknowledges completion
helper confirms completion
the system is marked complete

This prevents invisible labor and keeps the village memory accurate.

11) When we miss the mark

We are human. We will mess up. We agree that when something goes sideways:

we name it early
we repair simply
we adjust the system so it is less likely to repeat

Shame is not a strategy. Clarity is.

12) The spirit of the agreement

The goal is not perfection. The goal is a village where:

people can ask without shame
people can offer without resentment
help stays practical and consent-based
capacity is respected
care is shared, not concentrated

Simple pledge (optional to include at the bottom)

“I agree to participate in village exchange with clarity, consent, and respect for capacity. I will keep requests matchable, offers bounded, and communication clean. I will support repair when needed and protect privacy.”