If you haven’t read the Manifesto first
Start with the Manifesto for the plain-language version of why ARA exists. This page is the longer companion: the same ideas, traced back to where they come from.
Look at the system before you change it. The cheapest design choice is the one informed by what is already happening.
In ARA
Vitality scores on Gardens show which projects are thriving and which need attention. Solar and Shade availability marks who has bandwidth before anyone hands them a Seed. The Mycelium graph lets stewards see a sanctuary all at once.
When something useful is abundant, save some of it. The work to capture it once is much smaller than the work of doing without it later.
In ARA
The Library holds the knowledge a community accumulates: agreements, proposals, founding documents, the way decisions were made and why. The Ledger captures contributions so sweat equity does not vanish into memory. Scrolls keep version history so the reasoning behind a change stays attached to it.
A system that does not feed the people inside it does not last. Effort needs to come back in some form that participants can see.
In ARA
The Exchange turns surplus into something neighbours can use: the bumper crop of zucchini, the spare hour, the skill someone learned this winter. The Ledger lets contributions show up where they can be acknowledged.
Build the correction loop into the design. Outside enforcement is brittle; internal feedback is durable.
In ARA
Rhythms rotate chores automatically so the system does the nagging instead of a person. Proposals run on consent and abstain and block, with a clear paper trail. Sanctuaries that go over their plan capacity get a soft warning before anything is enforced.
Prefer the things that grow back. Treat the things that do not as the rare and serious materials they are.
In ARA
The Shed makes one good drill the village drill instead of every household owning their own. Federated resources flow across connected sanctuaries through Mycelium, so a press, a mill, or a kiln can serve more than one place.
What looks like waste is usually a resource in the wrong location. Find where it belongs.
In ARA
Knowledge does not leave when a member does: the Library and the Ledger keep what they wrote, decided, or built. Tools no longer used in one sanctuary surface in the federated Shed. Old proposals stay searchable so a question from five years ago is not asked again from scratch.
Get the shape of the whole right before you fuss with any one part. Patterns repeat at every scale.
In ARA
Gardens move through four phases: Inception, Planting, Growth, Harvest. Sections inside Gardens carry the same rhythm at a smaller scale. The whole sanctuary uses the same language for time, work, and belonging, top to bottom.
Connections between elements often do more work than the elements themselves. A cow next to a pond is a different thing than a cow alone in a field.
In ARA
Mycelium federation lets sanctuaries share the things that travel well: tools, market listings, federation-level proposals, ecosystem-wide invitations. Boundaries stay where they should be (private content remains private) while the things that benefit from being shared can flow.
Small systems are easier to maintain and easier to understand. Slow change holds. Fast change rarely takes root.
In ARA
There is no engagement loop, no streak counter, no notification arms race. The Seedling tier is free for groups of five so a community can start without a budget meeting. Plan limits scale gently with size rather than punishing growth.
A field that grows one thing fails when that thing fails. A field that grows many things bends through the same shock.
In ARA
Sanctuaries are not forced into a single shape. Roles, sections, garden phases, and rhythms are configurable per place. Plans range from a free Seedling to multi-sanctuary Ecosystem, so a kibbutz, a co-housing block, and a land trust can each find their fit.
The interesting things often happen at the boundary: where two systems meet, where someone is half-in and half-out, where the rules of one place rub up against the rules of another.
In ARA
My Patch is the edge between personal work and shared work, where private Seeds become public commitments. Public Scrolls live at the boundary between members and the world. Federation edges are exactly that: edges, where two sanctuaries share what they choose to share.
Change is the one constant the design must plan for. Resilience is the ability to take a hit and keep being itself.
In ARA
Inactive sanctuaries enter a soft dormancy with a long grace period before anything is removed. Members can pause, leave, or return without breaking the record. Proposals can be escalated to federation level when a single sanctuary needs the wider circle. Account deletion anonymises authorship rather than erasing the work itself.
These are not metaphors.
They are the design moves the app actually makes, named in the older language so the inheritance is obvious. If they describe the kind of place you are building, ARA might be the right shape for it.