Concept
A digital layer associated with the actual places you already inhabit.
ThreadSpace is not a product. It is a name for the digital space that emerges when persistent infrastructure — nodes — establish meaningful relationships with one another.
A neighborhood can have a ThreadSpace. So can a household, a classroom, a makerspace, a shelter, a conference, or a single friendship between two people who each hold their own data on hardware they control. The architecture does not require a cloud, does not require a company, and does not require a single piece of transport to stay online.
The actual place remains primary. ThreadSpace is the layer beside it.
Most digital space is built to be mined.
The loop most social infrastructure runs
- content
- engagement
- behavioral signal
- ranking
- more content
- monetization
The loop a ThreadSpace runs instead
- person
- relationship
- shared context
- interaction
- continuity
The difference is not scale and not sincerity. It is what the inhabitants are for. In the first loop the person is the raw material. In the second they are the point. A ThreadSpace is a digital place whose residents are not the product.
The second loop also has to be cheap to reverse. Flipping networks should be a flip of a switch, not a séance — not a negotiation with a provider over the export of a life.
Where each piece sits.
These are conceptual responsibilities, not a deployment diagram. Each one can be supplied by more than one party, and none of them requires us to be the owner.
ThreadSpace
The place itself. What a person is in, and what they are not a product of.
Codexify
Memory, identity, and retrieval held by the person and portable between interfaces.
WhisperMesh
Carry the relationships. Replaceable. Nothing above it should break when it does.
Local nodes and trusted peers
State that stays somewhere the person chose, and keeps working when a provider does not.
Scoped permissions
What each participant is allowed to know, share, request, and do — stated, not assumed.
Local-first with optional cloud
The cloud is a place you can put something, not the place your life is required to live.
The scales it can hold.
Person to person
Two people, each on a node they control, sharing context across a relationship they define.
Household
A home server holds shared family context. Members retain portable identity; the household holds shared memory.
Group
A team, a study group, a long-running project. Boundaries are explicit. Membership is revocable.
Neighborhood
Local nodes announce what is happening. Anyone walking by can opt in. The network does not require a service provider.
Community / organization
Federated or peer-to-peer relationships across many nodes, with clear consent and delegation models.
Associated with actual places
A café, a park, a shelter, a trail, a makerspace. The physical place remains primary. ThreadSpace is the digital layer beside it.
What ThreadSpace is not.
- 01
Not a product, not an app, not a chat screen.
- 02
Not a single transport protocol. ThreadSpace survives transport changes.
- 03
Not owned by Resonant Constructs. Other developers and communities are welcome to build clients, nodes, transports, and experiences for it.
- 04
Not a replacement for physical community. The actual place remains primary.
- 05
Not dependent on any one company surviving, being acquired, or continuing to exist.
Codexify is one door.
A browser accesses the web. Codexify can access ThreadSpace. Other software should eventually be able to do the same. We are building doors, not walls.
The current Codexify implementation is a local-first interface for working with your own context — conversations, documents, retrieval, and bounded tooling under operator authority. It is one of several possible interfaces into ThreadSpace. See the Codexify door for its current implementation status.
A place you steward, not a product you own.
The name already exists in other domains, which is the point. The trademark covers the concept, not a market position. We are publishing the conceptual canon and the implementation work; anyone who wants to participate is welcome to build on it.
Start with how to contribute. Transport mechanisms and their current status are documented on the research page.