Core mental model
Derived from the published System Guide. Every row cites the claim groups it renders, and every rule on it is quoted from one of them.
T1.1The four main thingsPermalink
The edges are not open doors. Joining a workspace opens none of its projects; reaching a project's tasks needs a separate project membership (FIG-P2-2). Each individual project sits inside exactly one workspace (XD-CONT-1).
T1-1T1-1Account → Workspace → Project → Task.
An account is a person's own identity in ChatWell. A workspace holds a group's projects and the people who take part. A project groups related work inside one workspace. A task is one piece of work inside one project.
Why is this true?
T1-1Fulla fact about the sources, not a reader labelT1-2Every account has a Personal Workspace, created with the account and owned by it — always, whatever else is true of the account.
Every other workspace is created by a person, who becomes its owner; during the current beta, creating one takes permissions an account does not start with (P1.1).
T1-3An account reaches a workspace only as its member, and reaches a project's tasks only as a member of that project.
T1.2Separations that hold everywherePermalink
T1-4Belonging is not seeing.
Being a member of a workspace does not by itself give you access to any of its projects — not even the workspace's main project. Project membership is granted project by project, and a workspace member with no projects at all is a correct state, not a fault (P2.2).
Why is this true?
T1-4Fulla fact about the sources, not a reader labelT1-5Owning is not a role.
Roles are member and admin. Ownership is a separate fact about a workspace.
T1-6State, responsibility and review are separate.
Assigning a task does not change its state, and a task's reviewer is a responsibility on that one task, not a role. The two responsibilities never meet on one task: whoever is responsible for the work is not the one who reviews it.
Why is this true?
T1-6Fulla fact about the sources, not a reader labelT1-7A finished task is not an archived project.
A finished task is frozen and listed among its project's archived tasks, yet stays readable while its project is active. Archiving a project closes its tasks to everyone and freezes the work in it (T2.6).
T1-8Now is not history.
Current state changes; recorded history only grows.
T1-9A person acting is not the system acting.
Some changes happen automatically, as the consequence of another action, and ChatWell records what caused them.
Some of what Gen-5 has decided is not available today. This guide always labels it and says what happens today instead.
T1.3One small castPermalink
The examples use one fictional cast throughout: Anna and Leo, the workspace Northstar Studio, its project Website Redesign, and the task Prepare launch assets. Anna created Northstar Studio, so she owns it. Leo joined it by invitation, as a member.
T1.4What else is in ChatWell todayPermalink
ChatWell is more than workspaces, projects and tasks. Three supporting capabilities also work today. This pilot does not explain them; below are only the established facts.
XD-SUP-1Chat channelsProjects come with chat: creating a project also creates its General Chat.Partly defined
Partly defined. Gen-5's membership model treats chat as business content, not as a passing message stream.
Why is this true?
XD-SUP-1Partly defineda fact about the sources, not a reader labelExact identity
XD-SUP-2Contacts and companiesA workspace keeps contacts and companies, and contacts can be linked to projects.Partly defined
Partly defined. The membership model treats them as customer records that outlive the workspace container.
Why is this true?
XD-SUP-2Partly defineda fact about the sources, not a reader labelExact identity
XD-SUP-3Scheduled eventsEvents can be scheduled in a workspace and linked to a project.Partly defined
Partly defined. The membership model treats them as records of commitments made.
Why is this true?
XD-SUP-3Partly defineda fact about the sources, not a reader labelExact identity
XD-SUP-0Not decided. The wider Gen-5 model for these three capabilities — their lifecycle, who may do what with them, and what their states mean.Not decided
No registered document defines it.
Why is this true?
XD-SUP-0Gapa fact about the sources, not a reader labelExact identity
Where this comes from — Core mental modelPermalink
Where this comes from13 claim groups
| Claim group | Covers | State | Coverage | Sources |
|---|---|---|---|---|
T1-1 | The four main things | Works today | Full | via WS-WHAT-1, PJ-WHAT-1, TK-WHAT-1 |
T1-2 | Personal and created workspaces | Works today | Full | via WS-KIND-1, WS-KIND-2 |
T1-3 | Reach goes through membership | Works today | Full | via WS-MEM-1, PJ-ACC-1 |
T1-4 | Belonging is not seeing | Works today | Full | via PJ-ACC-1, PJ-ACC-2, PJ-ACC-4 |
T1-5 | Owning is not a role | Works today | Full | via WS-OWN-2, WS-ROLE-1 |
T1-6 | State, responsibility, review | Works today | Full | via TK-DIM-1, TK-REV-1, TK-REV-9 |
T1-7 | Finished task vs archived project | Works today | Full | via TK-LC-5, XD-FIN-1 |
T1-8 | Now is not history | Works today | Full | via XD-HIS-1 |
T1-9 | Person versus system | Works today | Full | via XD-SYS-1 |
XD-SUP-1 | Chat channels | Works today | Partly defined | Accepted Gen-5 implementation · Membership model |
XD-SUP-2 | Contacts and companies | Works today | Partly defined | Accepted Gen-5 implementation · Membership model |
XD-SUP-3 | Scheduled events | Works today | Partly defined | Accepted Gen-5 implementation · Membership model |
XD-SUP-0 | Their wider model | Not decided | Gap | Source of Truth Map · Membership model |
Coverage is a fact about the sources, not a reader label. Gap is not one of the five labels.