Zulip-style discussions for projects

A discussion stays where the decision is made.

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.

Base recordField value, link, row status, and specification stay in the record context.
Diagram pointCoordinates, label, room, and connection do not get lost outside the sheet.
ResolvedThere is a result for everyone: which option was accepted and what is correct.

Grew from Zulip

Topics and streams, next to the project object

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.

Source model Zulip
SHD version Discussions

From Zulip to project context

A topic must lead back to the work

Zulip organizes conversations well. SHD connects a topic to the project object, its access rules, and the next action.

In chat

The topic drifts away

A month later no one knows which outlet was meant. 'OK' records nothing, and a new person rebuilds the context.

By the object

The decision remains

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

The conversation is tied to a place

When the object is known, open the topic from it. A free topic is for places with no record or point yet.

01

Base record

Field value, link, row status, and specification stay in the record context.

02

Diagram point

Coordinates, label, room, and connection do not get lost outside the sheet.

03

PDF canvas

The topic appears on the sheet even when there is no separate point yet.

04

Specification text

The wording and scope are discussed beside the original requirement.

05

Task

Execution details and verification stay with the task, not in a parallel conversation.

06

Finance and documents

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

Close it and leave the result

A status helps the list, but the decision must be written in words and available to everyone in the topic.

01

Resolved

There is a result for everyone: which option was accepted and what is correct.

02

Pin the result

In a long topic, the decision moves to the top instead of hiding in the feed.

03

Archive

The topic leaves the working list while its history remains available.

04

Hide

It removes the topic only for you. The team can still see and discuss it.

05

Unsubscribe

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

A work list, not a feed of noise

Mentions, new messages, and reminders gather in one place. A star stores personal decisions and notifies nobody.

Work inbox · 3 new
  • New thread by the outletReply in place and record the result
  • Project mentionAn engineer's answer is needed before the check
  • ReminderReturn to the question after delivery
  • Passport fragmentSave the wording in the object notes

☆ personal · remind later · Mention only the person who is needed

Access and task boundary

A conversation does not widen access

A discussion has the same boundaries as its object. When an owner and deadline are needed, pass the decision to a task.

  • Object access — Start with the boundaryA general topic page does not open a private base or diagram.
  • Need a deadline and owner — Then make a taskA comment does not replace an assignment. The topic keeps a link to the decision.

Before a discussion

The boundaries in brief

A discussion keeps context and decisions, but does not replace an object, task, or access rule.

Is this just a project chat?

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.

Why cannot a colleague see the topic?

They do not have access to the object. Access comes before a mention.

Can I write a free topic?

Yes, when there is no object. If there is a record or point, write there instead.

Does a hidden topic close for everyone?

No. Hide removes it only for you. Everyone needs a result and resolved status.

Does deleting a discussion delete the record?

No. The object remains. If the object is deleted, its topic goes with it.

How is this different from regular Zulip?

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

Keep decisions where the team does the work.

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.

Code from the image
Code from the image