A network of adaptable social places
Aitta Network connects independently controlled places called Aittas. In an Aitta, a message, idea, or conversation can grow into a shared space where people talk, decide, and use trusted apps together.
Invited to an Aitta? Join with ChatGPT and take part without creating an Aitta of your own.
One place in the network
It is not only a profile, feed, app, or conversation. An Aitta contains the identity it represents, the people who may take part, what they share, the apps they trust, and the spaces that grow around their work.
It can connect with other Aittas while remaining authoritative for what it controls.
An Aitta contains
A nested space can have its own purpose, people, activity, and apps—but it remains a space, not another top-level Aitta.
How it grows
Most online tools make a group move somewhere else as soon as it needs to do more. Aitta keeps the context, people, and useful tool together as the work takes shape.
A project update, idea, question, or invitation gives people one clear thing to gather around.
The conversation stays with the thing that started it instead of disappearing into a general feed.
When the need becomes clearer, the relevant people can continue together with understandable access.
A trusted app can help the group ask, decide, organize, or take the next action—right in context.
The social context and the useful tool can evolve together, without becoming a disconnected collection of apps.
Any shared item can take part in its current space while becoming the beginning of another—always with clear context and access.Useful before it is large
Aitta is not designed around an empty global feed. It begins with small groups, real relationships, something meaningful to share, and a foreseeable next interaction.
For organizers
Start an Aitta for a project, community, company, club, creator group, publication, or working group you already bring together. Share one real item, invite the people who care, and let the next useful space grow from what they do.
For participants
Open a real invitation or public item, understand its purpose, then sign in with ChatGPT to follow, join, respond, or take part. You never need to create an Aitta to belong.
Grows with boundaries
Independent control, explicit access, and trusted software let people do more together without turning every connection into an open door.
Every Aitta retains its own identity, people, appearance, data, and boundaries while still being able to connect with others.
A reply, follow, or parent relationship never opens another space automatically. People can understand where they are and what they can do.
Apps are installed and trusted deliberately. Aitta shares typed data and events—not executable software from a remote sender.
What we are building first
The first version is designed to help a small existing group from its first meaningful shared item—not to fill an empty global feed.
Give it a purpose, identity, address, appearance, people, and clear boundaries.
Follow an invitation or public link, understand the purpose, then follow, join, respond, or take part.
Return to relevant public activity from the Aittas you explicitly choose to follow.
Keep the people, context, access, conversation, and useful interaction connected.
Use message requests, acceptance, unread state, blocking, reporting, and clear retention.
Shape it together and carry it through to a reviewed, trusted release.
Built from the conversation
Describe what the group needs where the need appeared. If trusted capabilities already available in the Aitta can provide it, ChatGPT can configure them. If the need requires new software, it becomes an App Idea that people clarify, discuss, test, and shape together.
Configure trusted capabilities
ChatGPT can create an app definition or instance from bounded, installed capabilities such as fields, choices, actions, permissions, validation, calculations, and layouts. No new executable code is introduced.
Create a new implementation
Aitta's agents can help draft the contract, implementation, tests, security checks, compatibility review, and release notes. A human-approved, versioned release is still required before any Aitta can choose to trust and install it.
Natural-language creation can configure what an Aitta already trusts. It cannot publish arbitrary live code or bypass review.
How the network works
The network lets Aittas and their members work together without turning them into one centrally owned place. Identity, relationships, data, software trust, access, and state authority each have an explicit role.
The software platform and product family used to build and run the network.
One independently controlled top-level place, with its own authority, lifecycle, data, and trusted apps.
The relationships and exchanges connecting Aittas and signed-in members—not a central feed or shared content store.
The trusted service for identity, discovery, relationships, authorization evidence, and coordination.
Messages, replies, questions, decisions, actions, and app state use versioned, typed events. Types are namespaced—for example, social.aitta.message—so compatible apps recognize the same meaning.
Every event may be a child in one app space and the root of another. A message can open a discussion; a question inside it can open a restricted working space; that space can contain another app.
The parent describes structure. The event type describes meaning. Neither grants access.
Follow, Join, Read, Write, and Watch are different relationships and permissions. A related child may still be invisible or unavailable when someone lacks access.
A network event may carry its type and version, global identity, parent, actor, authoritative Aitta, typed data, state transitions, policies, and hashes or signatures. It never carries executable JavaScript, arbitrary HTML, remote scripts, or automatically installed packages.
Each Aitta interprets an app through a trusted, versioned implementation already installed there. Unsupported types fall back to a bounded generic view showing the trusted type, source, authority, safe static data, and why interaction is unavailable. The sender's implementation is never fetched and executed.
The same logical app space may appear in several Aittas, but its state is not one ownerless pool. Every app contract says which state belongs to the root, a child event, a participant, the local Aitta, a cache, or a synchronization rule—and what happens during conflict or revocation.
An originating Aitta may control a question's canonical wording and closing state. A participant controls the response they create. Each Aitta controls local drafts, viewed status, and notifications.
Members without Aittas
A member can follow an Aitta, join an allowed space, respond, message, and use apps without owning an Aitta. Joining never creates one silently.
Sign in with ChatGPT provides only the identity information shown during sign-in. It does not give Aitta access to ChatGPT conversations, memory, files, tokens, or billing data.
For builders
Founding organizers
We want organizers who already bring people together and can identify a recurring need that ordinary messages alone do not solve. You do not need a mass audience. You need a real purpose, people you can invite, and a reason to return.
The launch unit