Protocols, not destinations.
Trigger → act → pass → keep. The product does its work, then disappears back into the group.
Test: can the group explain the rules without you?BUILDER 001 / FIELD MAP 001 / OPEN
SMALLSOCIALSYSTEMS
The social graph is already full.
Build the missing ritual.
NOT ANOTHER NETWORK ↗
00 / THE POSITION
The interesting product is not the room. It is what the room knows how to do.
Most people already have the people, the chat, and too much content. What is missing is lightweight social structure: who starts, what happens now, how participation passes, how someone can skip, and what the group gets to keep.
TAG is one wedge—a relay. The larger territory is a layer of small, temporary systems that can live inside a group without turning the group into an audience.
01 / SIGNALS AT THE EDGE
The pieces are arriving.
The protocol is still missing.
These are not competitors to copy. They are evidence that people will enter a tiny social object when it fits the relationship and the moment.
MESSAGESApps can play inside the conversation.
Apple supports games, media, collaboration, and custom interfaces without leaving Messages.
Surface proven ↗ DISCORDA channel can become a shared application.Activities place multiplayer games and social tools directly in channels and DMs.
Co-presence proven ↗ TELEGRAMA web app can inherit chat context.Mini Apps support shared use, multiplayer, group orders, and other cooperative systems.
Chat-native web proven ↗ SPOTIFYA message can become a live shared queue.Listening activity and Request to Jam turn a social signal into a synchronized music action.
Media handoff proven ↗ LOCKETA small circle can occupy the home screen.Close-friend photos, reactions without public counts, and recaps make ambient intimacy useful.
Ambient presence proven ↗ PARTIFULAn invitation can become a temporary network.Guest lists, comments, questions, updates, playlists, and albums gather around one occasion.
Event object proven ↗OUR READ → The platforms are proving surfaces one by one. The white space is a portable, group-owned ritual layer that can move between chat, web, place, media, and memory without asking people to rebuild their social graph.
02 / TEN WHITE SPACES
Build behavior,
not inventory.
Each card is a credible four-week wedge. The best one is the one a real group asks to restart.
One live thing everyone can feel.
Who is It? What is open? What expires? A shared state creates tension without a feed.
Test: does unfinished state pull someone back?Alive together, tolerant of absence.
Design between synchronous and asynchronous so late arrival changes the play instead of ruining it.
Test: can a round survive a two-hour gap?The recap is the reward.
A round leaves an inside joke, mini-film, playlist, map, or zine—not a leaderboard.
Test: does the group reshare what it made?Identity as a temporary job.
Host, challenger, witness, archivist, closer. Give people a reason to act differently for one round.
Test: do quieter people gain a clean entrance?One link across incompatible chats.
Messages, WhatsApp, Discord, Telegram, and SMS can point to the same tiny room without importing contacts.
Test: does it work before account creation?Consent is a feature surface.
Skip, pause, soft-exit, delete, export, and group-owned retention should be visible mechanics.
Test: can someone leave without social punishment?Let geography write the prompt.
Kitchens, blocks, campuses, venues, and festivals create constraints no generic prompt library can.
Test: could this round happen only here?Release a behavior like an edition.
Artists, DJs, magazines, teachers, and venues author prompt packs, roles, and recaps people perform together.
Test: is the pack recognizable as someone’s voice?Producer, not synthetic friend.
AI can tune pace, vary prompts, translate, and edit recaps. It should not impersonate friends or silently score relationships.
Test: is the group—not the model—the main character?03 / ECOSYSTEM, NOT APP
A small system has six living layers.
The opportunity grows when creators can author the ritual, groups can own the memory, and many surfaces can carry the same interaction grammar.
- 01People
Friends, families, teams, classmates, neighbors, temporary crews.
- 02Roles
Host, It, witness, DJ, archivist, closer, or a role the group invents.
- 03Ritual
Trigger, turn, time, proof, pass, completion, return.
- 04Surface
Chat extension, room link, widget, lock screen, watch, venue display.
- 05Memory
Recap, playlist, shared album, map, edition, or private archive.
- 06Economy
Creator packs, commissions, licenses, memberships, sponsored rounds—with clear terms.
04 / PRODUCT TANGENTS
The sideways doors are often better.
Family + care
A check-in relay, oral-history prompt, medication witness, or “show me your day” recap where warmth matters more than scale.
Music
One person passes one song and one instruction. The chain becomes a collectively authored listening room.
Creative teams
Critique as a timed pass: notice one thing, make one change, choose the next witness. Less meeting, more visible motion.
Events
Pregame, arrival, scavenger layer, photo mission, afterparty recap. The event page becomes playable before and after the date.
Campus + neighborhood
Location-bound dares and useful micro-missions that produce a local field guide instead of generic engagement points.
Wearables + ambient hardware
A watch tap, widget change, shared light, or venue screen can carry group state without another notification stream.
Civic relay
Pass one small act—photograph a broken curb, water a tree, welcome a neighbor—and keep a public proof without surveillance.
Playable editions
A magazine issue, album release, exhibition, or brand collaboration becomes a bounded social ritual people can perform and keep.
05 / BUILDER 001
Choose one wedge.
Ship one public proof.
The role is exploratory but the finish is concrete. TAG can be the starting material or you can take an adjacent white space.
- WEEK 01One group, one ritual.
Choose the people first. Run a clickable or facilitated proof in seven days.
- WEEK 02Make the handoff work.
Build the smallest room, state, timer, media, role, or recap the ritual actually needs.
- WEEK 03Try three different groups.
Watch for voluntary restarts, role adoption, soft exits, and what gets reshared.
- WEEK 04Publish the system.
Release the prototype, source, field notes, safety boundaries, and a continue / revise / close call.
THE FINISH Working mobile proof · three live groups · field notes · source or forkable kit · public decision
Apply as Builder 001 ↘06 / NON-NEGOTIABLES
Protect the relationship from the product.
- No new follower graph
- No infinite feed
- No behavioral ad profile
- No silent relationship score
- No mandatory wallet
- No growth loop that punishes opting out
07 / RAISE YOUR HAND
Bring a group, a wedge, and a first move.
No pedigree theater. Show something real, name the people you would start with, and make a sharp seven-day call.
Use the 3-minute application ↗
The application door submits privately. The detailed worksheet beside it stays on this device; this page uploads nothing from that worksheet and only opens an email draft.