Position
Augment people. Preserve their authority.
We build technology that extends what people can remember, perceive, decide, and create — without requiring them to surrender their identity, memory, relationships, or digital continuity to the systems they use.
The promise of modern software has been convenience. The cost has been capture. Every chat, document, decision, and preference that passes through a third-party platform becomes part of that platform’s value. The more useful the tool becomes, the harder it is to leave. The more personal the data becomes, the more the user is anchored to the system.
Resonant Constructs is built around a different idea. The user remains the source of authority. The system stays useful to the user, not the other way around. A right of exit is not a marketing claim. It is an architectural guarantee.
A prosthesis is fitted to a person. It does not become one.
The tools here extend what a person can hold. Memory that does not quietly degrade. Attention that can carry more than one thing at once. Retrieval that does not require you to remember in order to remember. Coordination between people who are not in the same room. None of that requires the person to become smaller.
A prosthesis has a shape, and the shape is fitted. It is worn rather than inhabited. Take it away and the person is diminished, not replaced. That is the whole test we intend to be held to: does this leave the person larger than before, or does it quietly move the authorship across?
The failure mode is not that the tool becomes too capable. It is that the tool becomes the author — that what was remembered together is now held apart, and what was decided by a person is now merely inferred on their behalf.
Seven layers the work is organized around.
These are not a literal runtime stack. They are the vocabulary for talking about what the systems we build are for, and the order in which authority descends.
The human is the source of authority.
Technology exists to extend human memory, perception, agency, coordination, and creative capability. We do not frame AI systems as replacements for people or as authorities over them.
Portable continuity of the person across systems.
Identity includes history, memory, preferences, relationships, permissions, knowledge, context, active work, and other user-controlled state. The person should remain portable between applications and services. Providers are destinations the user interacts with, not permanent containers for the user’s identity.
Persistent infrastructure that holds state under user authority.
A Node is any persistent infrastructure capable of holding state and participating in relationships on behalf of a person, household, organization, community, or place. A Node might be a phone, a laptop, a home server, a Raspberry Pi, a hosted instance, neighborhood infrastructure, or future hardware. The durable concept is persistence and authority, not hardware.
Explicit boundaries, not assumed centralized ownership.
Relationships define what one Node, person, service, organization, or community is allowed to know, share, request, or do with another. The user determines what relationships their information participates in — private, shared, public, delegated, or community.
The digital space created when nodes establish meaningful relationships.
ThreadSpace is not a product, app, chat screen, or transport protocol. It is the digital space created when Nodes establish meaningful relationships with one another. It can exist at multiple scales — person to person, household, group, organization, neighborhood, community, global network, or digital spaces associated with actual places.
Codexify is one door. Other doors are welcome.
A browser accesses the web. Codexify can access ThreadSpace. Other software should eventually be able to access ThreadSpace as well. We do not need to own every compatible client for the architecture to work.
Replaceable infrastructure, not a dependency.
ThreadSpace should not conceptually depend on any particular networking system. Wi-Fi, cellular, Reticulum, Meshtastic, Bluetooth, LAN, a cloud relay, or future transports are all candidates. The invariant is that relationships and meaning survive changes in transport.
What we mean by data dignity.
Privacy is not secrecy. Privacy is one symptom of a deeper principle. The stronger concept is data dignity: authority, context, boundaries, consent, portability, and stewardship.
A user with data dignity knows what their information is participating in. They can move it. They can revoke access. They can decide what is shared, with whom, under what conditions, and for how long. Hosting a service is compatible with this principle as long as the user retains a meaningful path to export, migration, ownership, and self-hosted operation.
The mechanisms for holding that line are described in more detail on the boundaries page.
What we are not.
- 01
We are not anti-technology. We are not anti-cloud. Hosted services are part of the architecture.
- 02
We are not asking anyone to disconnect or go dark. The position is user authority over boundaries and participation, not total isolation.
- 03
We are not a hype-driven platform promising to replace physical community with a digital one. The actual place remains primary. ThreadSpace provides a digital layer associated with it.
- 04
We are not claiming the work is further along than it is. Every door on this site carries a status, and the statuses are meant to be read literally.
Pro-agency. Pro-portability. Anti-capture.
The position above is the current public statement of organizational principles. Implementation specifics, runtime claims, and roadmap details live on the research page and are clearly tagged as implemented, prototyped, designed, research, or vision.