Manual · Chapter 2 of 3

Communal Computer

Shared memory for this place. Kept alive by whoever shows up.

The neighborhood instance lives at atlas.garden — a chronicle dressed as a garden, a map you tend. The name is the vibe: not a ledger, not a bulletin board, not a platform. A secret society in a box, open to anyone who walks up.

You scan a QR code on a sign in the park. The page shows what is happening at this place — events coming up, paint on the map, a few open needs. Reading is open to anyone. To post, two neighbors stand together: one shows a rotating QR, the other scans, both phones submit GPS. Close enough, the tap completes — new neighbor verified, a pixel drops on the map where you stood.

Every post is a range: a stretch of time with optional place, sprite, and category. An evening potluck. "Bench is broken until Tuesday." A brushstroke on the map. They pile up into the chronicle of one place; a scrubber slides forward into scheduled events and backward through what has happened. Needs and offers ride the same shape — open, claimed, done. No money, ever — not even links to payment processors. No like counts, no view counts, no reactions. Their absence is the point.

The whole system runs on a phone-sized device in a sealed box on a pole. A stationary bike charges its battery; an hour of pedaling buys a day of uptime. If no one pedals, the box goes dark until someone does. One binary, one database file, one operator. No SaaS, no analytics, no logins, no grid tie. The decades-long aspiration is for the community to literally own the land the map represents; the bike is that goal in miniature — the neighborhood already owns the energy that powers its shared memory.