Skip to content

Collaboration⚓︎

This document defines how people work together on a Topic. It focuses on the social rules and how we handle different opinions to build a trustworthy shared memory.

Joining the Conversation⚓︎

Collaboration in DMS is explicit, role-based, and fully attributed.

  • Explicit Access: Users join a Topic by being invited or by requesting access.
  • One Person, One Role: Each user holds exactly one role per Topic (e.g., you are either an Owner or an Advisor, not both).
  • Audit Trail: Every time someone joins, leaves, or changes roles, it is recorded.

Participation Roles⚓︎

How you help depends on your Role:

Role Responsibility
Owner Leads the Topic and makes the final Decision.
Advisor Suggests Choices and adds Reasons (Pros/Cons).
Reviewer Reflects on the Outcome and helps write Lessons.
Observer Follows the Topic but does not add input.

Privacy boundary: Admins are never part of the conversation and cannot see or join Topics. The System may create operational records such as reminders or auto-archive actions, but it is never treated as a human participant.

Handling Disagreement⚓︎

DMS does not force agreement. Disagreement is part of the record.

  • Multiple Choices: It is okay to have many different options on the table.
  • Conflicting Reasons: One person might see a "Pro" while another sees a "Con." Both are saved.
  • Honest Reviews: A Reviewer is allowed to say a Decision was wrong without the system hiding that opinion.

The system never hides disagreement. It preserves the messy reality of thinking so people can learn from it later.

Decision Conflicts⚓︎

If a Topic has more than one Owner and they cannot agree on a Choice:

  1. Record Everything: Each suggested Decision is saved separately.
  2. Flag the Topic: The Topic is marked as Disputed.
  3. Manual Resolution: The conflict must be solved by the people, not the software.

Owners can resolve the conflict in one of three ways:

  • Agree on one path
  • Withdraw one of the competing decisions
  • Close the Topic as Unresolved if no agreement is possible

History & Trust⚓︎

To keep the memory honest, we follow these rules:

  • No Silent Edits: Every change creates a new version. You can always see what changed and who changed it.
  • Full Attribution: Every Choice, Reason, and Lesson is signed by the person who wrote it.
  • Shared History: Everyone invited to a Topic can see how that Topic evolved.

Trust is built through transparency. By knowing exactly who thought what and when, the team can move forward with confidence.

Collaboration defines how people work together inside a Topic. For identity, authorization, and privacy policy, see: