Remix at Neighborhood Scale

Most civic technology is built for cities, countries, or the whole world. Almost all of it can be *used* smaller.

Ushahidi was built for crisis mapping across Kenya — and it can map the third places of one neighborhood. FixMyStreet was built for reporting potholes to councils across the UK — and its pattern (see something, report it, watch it get fixed in public) works for a block's broken streetlights or a park's maintenance backlog. Participatory budgeting was born across Porto Alegre — and it works on a single ward's discretionary fund, or a block association's $500.

Three kinds of remixable material:

1. Open-source platforms — software you can run for your own place (Ushahidi, Decidim, LocalWiki, Loomio). The license is the permission slip; the neighborhood use case is yours to invent.
2. Patterns — designs proven somewhere and rebuildable anywhere, even in an afternoon with an AI builder: adopt-a-hydrant's 'civic objects with volunteer stewards', FixMyStreet's public issue ledger, a timebank's hour-for-hour exchange.
3. Stories — what neighbors in other places actually did, which is where the judgment lives: what they built, what they skipped, why it worked.

Two disciplines keep the remix honest. First, the technology is the smallest part — the map is the 10%, the door-knocking is the 90%; every tool on this shelf assumes organizing around it (that's the other shelf). Second, learn from the graveyard: civic tech has a rich history of dead projects, and the Civic Tech Field Guide keeps the cemetery well-labeled. The pattern behind most headstones: tech that substituted for relationships instead of strengthening them, or maintenance nobody committed to. Remix accordingly.

Details

• disciplines: the tech is the 10% — organizing is the 90%, learn from the graveyard
• remix kinds: open-source platforms, patterns, stories
• practice kind: framework