The topic drifts away
A month later no one knows which outlet was meant. 'OK' records nothing, and a new person rebuilds the context.
Zulip-style discussions for projects
A question about a record, diagram, task, or document opens in its own topic. Participants see context, outcome, and history instead of searching through chats.
Grew from Zulip
We took Zulip's topic and stream model and tied it to the work: records, diagrams, tasks, and documents keep the discussion, access, and outcome together.
From Zulip to project context
Zulip organizes conversations well. SHD connects a topic to the project object, its access rules, and the next action.
A month later no one knows which outlet was meant. 'OK' records nothing, and a new person rebuilds the context.
The place, history, answer author, and accepted option are visible. The link opens from the record and the tree.
Check the point by the desk: the diagram says study, but the table says dressing room. Which one is correct?
Where a topic lives
When the object is known, open the topic from it. A free topic is for places with no record or point yet.
Field value, link, row status, and specification stay in the record context.
Coordinates, label, room, and connection do not get lost outside the sheet.
The topic appears on the sheet even when there is no separate point yet.
The wording and scope are discussed beside the original requirement.
Execution details and verification stay with the task, not in a parallel conversation.
Amount, delivery, version, and next contact are visible where the object lives.
A topic without an object is the exception. When the place is known, start there.
How a question closes
A status helps the list, but the decision must be written in words and available to everyone in the topic.
There is a result for everyone: which option was accepted and what is correct.
In a long topic, the decision moves to the top instead of hiding in the feed.
The topic leaves the working list while its history remains available.
It removes the topic only for you. The team can still see and discuss it.
It removes the topic from your inbox without closing it for the team.
A question cannot be closed without a result message. Archive does not replace a decision.
Inbox
Mentions, new messages, and reminders gather in one place. A star stores personal decisions and notifies nobody.
☆ personal · remind later · Mention only the person who is needed
A discussion has the same boundaries as its object. When an owner and deadline are needed, pass the decision to a task.
Before a discussion
A discussion keeps context and decisions, but does not replace an object, task, or access rule.
No. A topic is tied to the place of work: a record, point, task, or document. A free topic is for work that has no object yet.
They do not have access to the object. Access comes before a mention.
Yes, when there is no object. If there is a record or point, write there instead.
No. Hide removes it only for you. Everyone needs a result and resolved status.
No. The object remains. If the object is deleted, its topic goes with it.
Topics and streams remain, but a working topic can link to a record, diagram, task, or document. Access follows the object, and the outcome stays in its history.
Decision context
We will find where your team needs threads: logs, diagrams, tasks, and documents.
We will start with the places where questions, versions, and accepted options disappear today.