Philosophy ── Where Should a Voice Live?
Where is the voice a person left behind? Inside a smartphone? On some cloud server somewhere? In a Google data center, or Apple's storage? Most people don't even know the name of the place.
In designing proof of existence, I have carried this question throughout. As long as a voice is "deposited with someone else's server," it cannot truly be said to survive. When the service ends, it disappears. When the company changes direction, it disappears. When an account is suspended, it disappears.
A voice should live in the land where the person lived.
This is not sentiment — it is a principle of design. The voice of someone who lived in Urayasu should remain in Urayasu. Accessible to the people living on that land a hundred years from now. Not dependent on the survival of a cloud company, not bound to the lifespan of any particular device.
Concept ── Paper Is the Node
TokiQR has already given one answer to this question.
A voice is physically inscribed inside the URL string of a QR code. Encoded with Codec2 audio compression, converted to Base64URL, printed as a URL parameter. No server is needed for playback. As long as the paper exists, the voice will sound thirty or fifty years from now.
But the context surrounding a voice — who issued it, when, to whom it belongs, which community's record it forms — still lives in fragile places: localStorage, cloud databases. Lose the device and it disappears. End the service and it disappears.
What QR has solved for voice needs to be extended to the whole surrounding context. The answer is a computer that the community holds.
Architecture ── The Spider's Web
There is one Raspberry Pi on my desk. This is TokiStorage's infrastructure today. When GitHub Pages suddenly returned 404, I moved the deployment pipeline to this small computer and began serving static sites through Cloudflare. GitHub became only a place to store code and receive webhooks.
In that moment, a question arose: if this Pi were not one but ten thousand, what would change?
Centralized systems are star-shaped. Every node faces the center — the cloud. A spider's web is different. Each node connects directly to its neighbors. There is no center. When one thread breaks, the web holds.
Implementing this requires almost no new technical invention. It is an assembly of existing parts.
Neighbor Discovery Is Autonomous
When a Pi starts up, it calls a /geo endpoint on a Cloudflare Worker. The Worker automatically returns the postal code and latitude/longitude from the request's IP address. The Pi registers itself in the database with that location, then measures round-trip time to existing nodes in the same municipality and designates the closest three to five as its neighbors.
No human action is required. Plug the Pi into power, and it joins the mesh.
Data Belongs to the Region
Urayasu's Pi holds Urayasu's data. Three neighboring nodes hold replicas. Everything stays within the municipality. Cross-border communication is rare. This naturally conforms to the EU's GDPR restrictions on cross-border data transfer. Data locality is legally correct design, not just technically sound.
GitHub Becomes a Window
Only code hosting and webhook reception remain on GitHub. But static site delivery, data management, deployment execution, notification delivery, and neighbor synchronization — all of this runs on Pis and Cloudflare. Even if GitHub goes down, the sites keep running and the voices keep playing.
Resources ── What Does It Actually Take?
One Raspberry Pi 5: approximately ¥25,000. Cloudflare Tunnel: zero. Electricity: a few hundred yen per month. The community hall: already there.
Japan has approximately 296,000 neighborhood associations. Twenty percent of them is roughly 60,000 nodes. The hardware cost at that scale is significant in aggregate, but per community hall it is the cost of replacing one printer — a one-time outlay, after which maintenance costs are essentially just electricity.
The software can be designed to install with a single command:
- Connect the Pi to the community hall's router
- Run the installation script
- Location is detected automatically; the Pi joins the mesh
- From that point, it operates autonomously
No technical knowledge is required. What is required is someone to install it, and the will to see its value.
Toward Realization ── Starting from Urayasu
When ten nodes are running, the structure is proven.
Ten community halls in Urayasu. Each Pi autonomously discovers its neighbors, synchronizes data, and monitors the health of the others. If one stops, the rest compensate. The data exists physically on this land.
The moment those ten nodes run, the question of scale disappears. If the architecture is correct, the same principles operate at a hundred nodes or ten thousand. A hundred nodes connects Chiba Prefecture. Ten thousand connects the Kanto region. Sixty thousand makes twenty percent of Japan's local communities into infrastructure that holds its own memory.
A voice inscribed on paper lasts longest.
Next most durable: a computer that belongs to a place.
This is a story about infrastructure, and at the same time the embodiment of a philosophy of proof of existence. Where a voice lives is a question of design. We are now in a position to choose that design.
The computer in the community hall holds the voice of someone who lived on that land. It will still be there in a hundred years. Whether we call that "infrastructure" or "monument" is not what matters most.