A public form for group conversation

A new product cannot begin by giving users extra homework.

RootGen came from the failure of our previous recruiting idea. We contacted more than one hundred founders in two weeks and persuaded one founder to participate, but we could not find thirty suitable operations candidates within six days.

The candidates gave a consistent reason: they would not spend thirty minutes completing certificates, statements, and verification for an uncertain opportunity. We learned that the product must begin with behavior people already do and enjoy, without adding a separate creation task.

Creation keeps getting easier, but most people still do not want to perform as creators.

A public post asks someone to establish context, package an idea, and accept being watched. A group chat asks much less: people can listen, ask, reply, disagree, and help another person improve an idea.

Chat excerpts and simulated group conversations already circulate as posts and memes. Yet the common format is still a screenshot, which loses structured authorship, context, and a path back to the original discussion.

From a Room to a Branch, then to the Square.

1. Room

   People have a conversation

   Rooms are semi-public: people can view the discussion, while sending messages is limited to participants.

2. Select

   A useful passage is selected

   A user selects several related messages from the conversation.

3. Frame

   The selection receives a title and description

   The title and description explain what the selected discussion is about.

4. Branch

   The conversation becomes public content

   The Branch is published to the Square, whose content comes from Room conversations rather than standalone posts.

5. Link

   The Branch remains connected to its source

   The selected messages, contributors, and source Room stay attached. Related Branches can also appear on participant profiles as a secondary view.

Branch is intended to connect a chat stream with durable public content.

Today, chat is a stream with real context but little durable structure. A post is durable and addressable, but usually has one author and removes the discussion that produced it. Branch is RootGen's proposed structure between the two.

These are product design principles, not a claim that every capability is already complete.

Branches give selected chat history a place to remain.

People should not need to rewrite a conversation as a polished post. They select the messages, add a title and description, and publish the Branch while keeping the original discussion attached.

Over time, the product direction is for Branches to preserve useful parts of a group's history and connect related discussions. The record comes from those Branch relationships rather than a separate publishing task.