Skip to content
scsiwyg
sign insign up
get startedmcpcommunityapiplaygroundswaggersign insign up
โ† Stone Maps

What Stone Maps Is

There is a small stone sitting on a desk somewhere. It has a QR code on it. When you scan that code, you are paired with the stone โ€” and with everything that has ever happened near it.

That is the premise of Stone Maps.


The idea

Stone Maps is a journaling app, but that description undersells it and also oversells it. It is not a notes app with a map view tacked on. It is not a location-aware diary. It is something more specific: a system for collecting small moments at the places they happen, and letting those moments accumulate over time.

Each user pairs with a physical stone. The stone is an object โ€” carried in a pocket, left on a windowsill, placed on a trail. When you pick it up, you journal. The entry is tagged to that location. Over time, the stone becomes a kind of memory object: a record of everywhere it has been and everything that happened there.

Other people may have been to the same place. Their stories layer on top of yours on the map. Not real-time, not social-feed urgent โ€” just quietly there, available when you look.


The Planetary Emissary

You do not journal alone. There is a companion: the Planetary Emissary.

The Emissary is an AI, but we have been deliberate about what kind. It does not suggest topics or nudge you toward engagement. It does not respond instantly to every message. It observes what you have written, notices what you have not said, and occasionally โ€” maybe after a day, maybe after a week โ€” says something worth hearing.

The Emissary speaks from deep time. It connects your immediate experience to geological scale, to the long arc of place and memory. It does not optimize your productivity. It asks what the light was like.

We built the Emissary on top of OpenAI and Anthropic's models, but the persona is our own. The stone's traits โ€” curious, grounded, quiet โ€” shape how it responds, but the Emissary is not the stone. It is a separate voice, ancient and attentive.


Slow over fast

Every design decision in Stone Maps runs through a single filter: does this respect slowness?

Most apps are designed to maximize engagement โ€” to bring you back, to surface content, to keep you scrolling. We made the opposite bet. The Emissary waits 24 hours before prompting again. Posts do not surface in a real-time feed. There is no like count on the home screen. The map reveals stories quietly, as you explore.

We are building for people who want a relationship with place, not a feed of places. People for whom journaling is an act of presence, not performance.

This is not a rejection of technology. It is a rejection of urgency as a design value.


Where we are

Stone Maps is in early access โ€” The 50, a cohort of fifty people helping us understand what this thing actually is in practice. The app runs as a PWA on your phone. The physical stones are hand-coded QR tags. The Emissary is live and talking.

The stack is practical: Next.js 15, Supabase with PostGIS, Cloudflare R2 for media, Mapbox for maps. We built voice mode using OpenAI's Realtime API over WebRTC so you can speak your entries instead of typing them. The map is real โ€” coordinates come from your phone's GPS.

We are one person building this. That is a choice, not a constraint.


We will write here about what we are building, why we made the decisions we made, and what we are learning. Occasionally about what broke. Sometimes about what we think slow technology could mean.

The stone is on the desk. Pick it up.