Platforms you rent
Gardens you tend

Tools that help you move your data off of platforms and leverage it to build what you need for your local context.

Horizon 1 · today · Running

Cultivate your data

In the age of AI, anyone can build any tool. But to do this, we need to be able to leverage AI and harness it on our own data. Cultivating your data means moving your data off of platforms and building your own tools, ideally with your own local AI.

View on map

Events

Horizon 2 · Protect community intelligence

Help your network connect with their ICP

Learn to define your ideal customer profile.

Read more

Program · Slides

The matchmaking pitch

Everyone shares one thing. Everyone leaves with their own card.

See the slides
  • Intelligence Packet An AI workflow system anyone can adopt to make their local systems more legible. Get started
  • Node graph A map of your stuff, drawn as a web of connected dots. Your AI fills it from one of your apps and you get a single file you can open and share. View on GitHub
  • Video tools Fourteen tools that run on your own computer. A video in, a page out, and a prompt for each thing you want cut. Open the tools
  • Pinboard MCP Members’ bookmarks, tagged by a shared convention, become a commons you can query in Claude. No central database. View on GitHub
  • ChatGPT Data Transformer Turns your ChatGPT export into an MCP server, so Claude can search your past conversations. Try it live

Horizon 2 · near

Protect community intelligence

Building

A tool you build on your own can only see what you put into it. Working with other people means connecting your data to theirs, and almost every way of doing that puts a platform in the middle holding both copies. Cultivating community legibility means information passes peer to peer and into the community data commons at in-person events. Two people record the same connection from their own side, each keeping their own half, so both have the history and neither had to hand it over.

View on map

vault A holds its own half vault B holds its own half one membership · two records
A membership is one connection recorded on both sides. Either side ends it by deleting its own half. The commons pools principles without names while each vault keeps the receipt. No platform saw the exchange.
  • Bloom Capture Template A single HTML file. Scan cards, build contacts, sort them, export a zip. Runs in the browser on your phone with nothing installed. Coming soon
  • The card Template A one-page profile rendered from your own vault, with your principles and an issue date inside the QR. Print two. Coming soon
  • Two-vault attribution Template The smallest dual ledger. Two people, two vaults, each recording what they worked on, in what role, on what date, on what principle. The pattern the rest of this horizon grows from. Get started
  • Relational Space Template See your friends’ and collaborators’ real-time activity without a platform in between. The file holds no data: it renders from whatever local data you point it at, and keeps nothing when you close it. See how it works

Horizon 3 · far

Enable emergent governance

Designed

Once your community keeps its own record, you still cannot see the groups outside it doing related work. A land trust needs a muralist and knows none. Every way of finding them today puts a directory in the middle. Emergent governance means two communities comparing what they stand for and what they have been doing, recognizing the match themselves, and acting on it. No directory, and nobody deciding for them.

View on map

individual A community A two logs confirm each other match on a principle and a timestamp
Two records compared on principles and dated activity. No document shared, no index between. What forms after that can only be conditioned and watched for.