Index
Claim index
Every claim group in the guide, once, with the chapter it is stated in, its state, its authority coverage and its sources. This is a transpose of the six Where this comes from tables; it adds nothing to them.
Coverage is a fact about the sources, not a reader label. Gap is not one of the five labels: where a claim works today, a Gap coverage means only that the accepted implementation is what shows it.
| Claim group | Where | Covers | State | Coverage | Sources |
|---|---|---|---|---|---|
T0-1 | T0 · At a glance | Workspaces, projects, tasks, accounts | Full | via T1-1 | |
T0-2 | T0 · At a glance | People belong to workspaces | Full | via WS-MEM-1, WS-KIND-1 | |
T0-3 | T0 · At a glance | Joining a workspace adds no projects | Full | via PJ-ACC-1, PJ-ACC-4 | |
T0-4 | T0 · At a glance | Ownership is not a role | Full | via WS-OWN-1, WS-OWN-2 | |
T0-5 | T0 · At a glance | Three questions per task | Full | via TK-DIM-1, TK-REV-9 | |
T0-6 | T0 · At a glance | History is not rewritten | Full | via TK-HIS-2, WS-MEM-3, XD-ARCH-2 | |
T0-7 | T0 · At a glance | Supporting capabilities exist | Partly defined | via XD-SUP-1, XD-SUP-2, XD-SUP-3 | |
T1-1 | T1 · T1.1 | The four main things | Full | via WS-WHAT-1, PJ-WHAT-1, TK-WHAT-1 | |
T1-2 | T1 · T1.1 | Personal and created workspaces | Full | via WS-KIND-1, WS-KIND-2 | |
T1-3 | T1 · T1.1 | Reach goes through membership | Full | via WS-MEM-1, PJ-ACC-1 | |
T1-4 | T1 · T1.2 | Belonging is not seeing | Full | via PJ-ACC-1, PJ-ACC-2, PJ-ACC-4 | |
T1-5 | T1 · T1.2 | Owning is not a role | Full | via WS-OWN-2, WS-ROLE-1 | |
T1-6 | T1 · T1.2 | State, responsibility, review | Full | via TK-DIM-1, TK-REV-1, TK-REV-9 | |
T1-7 | T1 · T1.2 | Finished task vs archived project | Full | via TK-LC-5, XD-FIN-1 | |
T1-8 | T1 · T1.2 | Now is not history | Full | via XD-HIS-1 | |
T1-9 | T1 · T1.2 | Person versus system | Full | via XD-SYS-1 | |
XD-SUP-1 | T1 · T1.4 | Chat channels | Partly defined | Accepted Gen-5 implementation · Membership model | |
XD-SUP-2 | T1 · T1.4 | Contacts and companies | Partly defined | Accepted Gen-5 implementation · Membership model | |
XD-SUP-3 | T1 · T1.4 | Scheduled events | Partly defined | Accepted Gen-5 implementation · Membership model | |
XD-SUP-0 | T1 · T1.4 | Their wider model | Not decided | Gap | Source of Truth Map · Membership model |
XD-CONT-1 | T2 · T2.1 | Strict containment | Full | Workspace & project lifecycle model · Membership model · Accepted Gen-5 implementation | |
XD-ACC-1 | T2 · T2.2 | Conditions for task work | Full | Membership model · Gen-5 task implementation specification · Accepted Gen-5 implementation | |
XD-ACC-2 | T2 · T2.2 | For tasks, roles are not access | Full | Workspace & project lifecycle model · Gen-5 task implementation specification · Project access policy decision · Accepted Gen-5 implementation | |
XD-GOV-1 | T2 · T2.3 | Authority ladder | Full | via WS-ROLE-2, WS-OWN-4, PJ-ACC-6 | |
XD-DER-1 | T2 · T2.3 | Stored versus derived | Full | via WS-OWN-4, TK-LC-5, TK-REV-1, WS-ROLE-1 | |
XD-HIS-1 | T2 · T2.4 | Now versus history | Full | via TK-HIS-2, WS-MEM-2 | |
XD-SYS-1 | T2 · T2.5 | System-side cancellation | Full | Gen-5 lifecycle decisions · Task lifecycle & assignment model · Gen-5 task implementation specification · Accepted Gen-5 implementation | |
XD-FIN-1 | T2 · T2.6 | Finished task vs archived project | Full | Task lifecycle & assignment model · Task operation contract · Accepted Gen-5 implementation | |
XD-ARCH-1 | T2 · T2.6 | Access after archiving | Full | Workspace & project lifecycle model · Gen-5 lifecycle decisions · Source of Truth Map · Task lifecycle & assignment model · Gen-5 task implementation specification · Accepted Gen-5 implementation | |
XD-ARCH-2 | T2 · T2.6 | Content is kept | Full | Workspace & project lifecycle model · Gen-5 lifecycle decisions · Accepted Gen-5 implementation | |
XD-ARCH-3 | T2 · T2.6 | Whether restoration is offered | Not decided | Full | Workspace & project lifecycle model · Accepted Gen-5 implementation |
WS-WHAT-1 | P1 · P1.1 | What a workspace is | Full | Workspace & project lifecycle model · Membership model · Accepted Gen-5 implementation | |
WS-KIND-1 | P1 · P1.1 | Personal Workspace, unconditional | Full | Beta workspace creation decision · Default template contract · Workspace templates runbook · Accepted runtime evidence (R1–R4) · Gen-5 lifecycle decisions · Workspace & project lifecycle model · Accepted Gen-5 implementation | |
WS-KIND-5 | P1 · P1.1 | "Free" is positioning, not a setting | Full | Beta workspace creation decision · Default template contract · Accepted Gen-5 implementation | |
WS-KIND-4 | P1 · P1.1 | Others in a Personal Workspace | Partly defined | Project access policy decision · Membership model · Accepted Gen-5 implementation · Workspace & project lifecycle model | |
WS-KIND-2 | P1 · P1.1 | User-created workspace | Full | Gen-5 lifecycle decisions · Accepted Gen-5 implementation | |
WS-KIND-3 | P1 · P1.1 | A further workspace takes two permissions | Full | Beta workspace creation decision · Workspace templates runbook · Accepted Gen-5 implementation · Accepted runtime evidence (R1–R4) | |
WS-KIND-6 | P1 · P1.1 | Operator-conferred, no product screen | Full | Beta workspace creation decision · Workspace templates runbook · Accepted Gen-5 implementation · Accepted runtime evidence (R1–R4) | |
WS-KIND-7 | P1 · P1.1 | Template availability today | Full | Workspace templates runbook · Beta workspace creation decision · Accepted Gen-5 implementation · Accepted runtime evidence (R1–R4) | |
WS-START-1 | P1 · P1.1 | Starting structure | Partly defined | Membership model · Default template contract · Accepted Gen-5 implementation | |
WS-LIM-1 | P1 · P1.1 | How many workspaces | Not decided | Gap | Decision Index · Beta workspace creation decision |
WS-LIFE-1 | P1 · P1.1 | No deletion; archival ends the lifecycle | Full | Workspace & project lifecycle model · Gen-5 lifecycle decisions · Accepted Gen-5 implementation | |
WS-OWN-1 | P1 · P1.2 | Exactly one owner | Full | Workspace & project lifecycle model · Accepted Gen-5 implementation | |
WS-OWN-2 | P1 · P1.2 | Ownership is not a role | Full | Workspace & project lifecycle model · Accepted Gen-5 implementation | |
WS-OWN-3 | P1 · P1.2 | Owner is also an admin member | Partly defined | Workspace & project lifecycle model · Accepted Gen-5 implementation | |
WS-OWN-4 | P1 · P1.2 | Derived project ownership | Full | Workspace & project lifecycle model · Accepted Gen-5 implementation | |
WS-OWN-7 | P1 · P1.2 | Owner is an admin member of every active project | Full | via PJ-ACC-6 | |
WS-OWN-5 | P1 · P1.2 | Ownership never simply ends | Full | Workspace & project lifecycle model · Accepted Gen-5 implementation | |
WS-OWN-6 | P1 · P1.2 | Owner cannot leave or be removed | Partly defined | Accepted Gen-5 implementation | |
WS-MEM-1 | P1 · P1.3 | How membership starts | Full | Membership model · Accepted Gen-5 implementation | |
WS-MEM-2 | P1 · P1.3 | Membership periods | Full | Membership model · Accepted Gen-5 implementation | |
WS-MEM-3 | P1 · P1.3 | Who belonged when is kept | Full | Membership model · Identity invariants · Accepted Gen-5 implementation | |
WS-MEM-4 | P1 · P1.3 | Membership is not enough to act | Full | Membership model · Accepted Gen-5 implementation | |
WS-MEM-5 | P1 · P1.3 | Leaving ends project memberships | Full | Membership model · Accepted Gen-5 implementation | |
WS-MEM-6 | P1 · P1.3 | Removing members | Partly defined | Accepted Gen-5 implementation · Membership model · Task lifecycle & assignment model · Task operation contract | |
WS-MEM-7 | P1 · P1.3 | One replacement per project, never its assignee | Full | Task reviewer authority decision · Task lifecycle & assignment model · Task operation contract · Accepted Gen-5 implementation · Accepted runtime evidence (R1–R4) | |
WS-ROLE-1 | P1 · P1.4 | Two stored roles | Full | Workspace & project lifecycle model · Accepted Gen-5 implementation | |
WS-ROLE-2 | P1 · P1.4 | Authority ladder | Full | Workspace & project lifecycle model · Source of Truth Map | |
WS-ROLE-3 | P1 · P1.4 | Authority is not access | Full | Workspace & project lifecycle model · Accepted Gen-5 implementation | |
WS-ROLE-4 | P1 · P1.4 | Role chosen at invitation | Partly defined | Accepted Gen-5 implementation · Membership model · Workspace & project lifecycle model | |
WS-ROLE-5 | P1 · P1.4 | Roles are per place | Full | Workspace & project lifecycle model · Accepted Gen-5 implementation | |
WS-ROLE-6 | P1 · P1.4 | What the role change does not affect | Partly defined | via WS-ROLE-4, PJ-ROLE-1 | |
WS-MX-1 | P1 · P1.4 | Workspace actions by level | Partly defined | Accepted Gen-5 implementation · Workspace & project lifecycle model | |
PJ-WHAT-1 | P2 · P2.1 | What a project is | Full | Workspace & project lifecycle model · Accepted Gen-5 implementation | |
PJ-MAIN-1 | P2 · P2.1 | The main project | Partly defined | Membership model · Accepted Gen-5 implementation | |
PJ-CRE-1 | P2 · P2.1 | Who creates projects | Partly defined | Project access policy decision · Membership model · Accepted Gen-5 implementation · Accepted runtime evidence (R1–R4) | |
PJ-EDIT-1 | P2 · P2.1 | Changing a project's name, details and type | Gap | Accepted Gen-5 implementation | |
PJ-ACC-1 | P2 · P2.2 | Project access needs membership | Full | Membership model · Accepted Gen-5 implementation | |
PJ-ACC-2 | P2 · P2.2 | Also for admins and the owner | Full | Workspace & project lifecycle model · Project access policy decision · Gen-5 task implementation specification · Accepted Gen-5 implementation | |
PJ-ACC-4 | P2 · P2.2 | Joining adds no project | Full | Project access policy decision · Membership model · Accepted Gen-5 implementation · Accepted runtime evidence (R1–R4) | |
PJ-ACC-7 | P2 · P2.2 | Zero projects is correct | Full | Project access policy decision · Membership model · Accepted Gen-5 implementation · Accepted runtime evidence (R1–R4) | |
PJ-ACC-8 | P2 · P2.2 | Earlier memberships are kept | Full | Project access policy decision · Membership model · Accepted Gen-5 implementation | |
PJ-ACC-3 | P2 · P2.2 | Adding and removing people | Partly defined | Membership model · Workspace & project lifecycle model · Task reviewer authority decision · Task operation contract · Accepted Gen-5 implementation | |
PJ-ACC-6 | P2 · P2.2 | The owner's standing project membership | Full | Project access policy decision · Membership model · Workspace & project lifecycle model · Accepted Gen-5 implementation · Accepted runtime evidence (R1–R4) | |
PJ-ACC-9 | P2 · P2.2 | Active projects only | Full | Project access policy decision · Membership model · Accepted Gen-5 implementation | |
PJ-ACC-10 | P2 · P2.2 | Conditioned on the owner's own access | Full | Project access policy decision · Membership model · Workspace & project lifecycle model · Accepted Gen-5 implementation | |
PJ-ACC-11 | P2 · P2.2 | The owner cannot leave, be removed or be demoted | Full | Project access policy decision · Task lifecycle & assignment model · Accepted Gen-5 implementation · Accepted runtime evidence (R1–R4) | |
PJ-ACC-5 | P2 · P2.2 | Owner reach outside tasks | Gap | Accepted Gen-5 implementation · Gen-5 task implementation specification · Project access policy decision · Workspace & project lifecycle model | |
PJ-ROLE-1 | P2 · P2.2 | Changing project roles | Partly defined | Workspace & project lifecycle model · Project access policy decision · Accepted Gen-5 implementation | |
PJ-ROLE-2 | P2 · P2.2 | Role change keeps membership | Full | Membership model · Accepted Gen-5 implementation | |
PJ-ARCH-1 | P2 · P2.3 | Who archives; one-way today | Partly defined | Workspace & project lifecycle model · Accepted Gen-5 implementation | |
PJ-ARCH-2 | P2 · P2.3 | Archive closes unfinished work | Full | Gen-5 lifecycle decisions · Gen-5 task implementation specification · Accepted Gen-5 implementation | |
PJ-ARCH-3 | P2 · P2.3 | Nothing reassigned | Full | Workspace & project lifecycle model · Task lifecycle & assignment model · Project access policy decision · Accepted Gen-5 implementation | |
PJ-ARCH-4 | P2 · P2.3 | Tasks closed to everyone | Full | Task lifecycle & assignment model · Gen-5 task implementation specification · Accepted Gen-5 implementation | |
PJ-ARCH-5 | P2 · P2.3 | Owner exceptions outside tasks | Gap | Accepted Gen-5 implementation · Workspace & project lifecycle model · Source of Truth Map | |
TK-WHAT-1 | P3 · P3.1 | What a task is | Full | Gen-5 task implementation specification · Task lifecycle & assignment model · Accepted Gen-5 implementation | |
TK-DIM-1 | P3 · P3.1 | Three independent questions | Full | Task lifecycle & assignment model · Task operation contract · Accepted Gen-5 implementation | |
TK-DIM-2 | P3 · P3.1 | No assignment state | Full | Task lifecycle & assignment model · Accepted Gen-5 implementation | |
TK-CRE-1 | P3 · P3.1 | Creating a task | Full | Task operation contract · Gen-5 task implementation specification · Accepted Gen-5 implementation · Task reviewer authority decision · Accepted runtime evidence (R1–R4) | |
TK-LC-1 | P3 · P3.2 | Six states | Full | Task lifecycle & assignment model · Accepted Gen-5 implementation | |
TK-LC-2 | P3 · P3.2 | What the states mean | Full | Task lifecycle & assignment model | |
TK-LC-3 | P3 · P3.2 | How a task moves | Full | Task lifecycle & assignment model · Accepted Gen-5 implementation · Accepted runtime evidence (Gate-25) · Accepted runtime evidence (R1–R4) | |
TK-LC-4 | P3 · P3.2 | Who moves it before review | Full | Task lifecycle & assignment model · Gen-5 task implementation specification · Accepted Gen-5 implementation | |
TK-LC-5 | P3 · P3.2 | Finished tasks are frozen | Full | Task lifecycle & assignment model · Task operation contract · Accepted Gen-5 implementation | |
TK-DEL-1 | P3 · P3.2 | No task deletion | Partly defined | Accepted Gen-5 implementation · Gen-5 task implementation specification | |
TK-DEL-2 | P3 · P3.2 | Whether deletion will exist | Not decided | Partly defined | Gen-5 task implementation specification · Workspace & project lifecycle model |
TK-CONT-1 | P3 · P3.2 | Continuing a finished task | Not decided | Gap | Gen-5 task implementation specification · Task lifecycle & assignment model |
TK-ASG-1 | P3 · P3.3 | The assignee | Full | Task lifecycle & assignment model · Accepted Gen-5 implementation | |
TK-ASG-2 | P3 · P3.3 | Who may assign | Full | Task lifecycle & assignment model · Task operation contract · Accepted Gen-5 implementation | |
TK-ASG-3 | P3 · P3.3 | Assignee needs access | Full | Task operation contract · Task reviewer authority decision · Accepted runtime evidence (R1–R4) · Accepted Gen-5 implementation | |
TK-ASG-4 | P3 · P3.3 | Assignment and state are independent | Full | Task lifecycle & assignment model · Accepted Gen-5 implementation | |
TK-REV-1 | P3 · P3.4 | Reviewer is per task | Full | Task lifecycle & assignment model · Workspace & project lifecycle model · Accepted Gen-5 implementation | |
TK-REV-2 | P3 · P3.4 | Reviewer access; a record, not a grant | Full | Task lifecycle & assignment model · Task reviewer authority decision · Task operation contract · Accepted Gen-5 implementation | |
TK-REV-3 | P3 · P3.4 | Entering review | Full | Task lifecycle & assignment model · Task reviewer authority decision · Accepted runtime evidence (R1–R4) · Task operation contract · Accepted Gen-5 implementation | |
TK-REV-7 | P3 · P3.4 | Reviewer selection takes its own authority | Full | Task reviewer authority decision · Task lifecycle & assignment model · Task operation contract · Gen-5 task implementation specification · Accepted Gen-5 implementation · Accepted runtime evidence (R1–R4) | |
TK-REV-8 | P3 · P3.4 | Positions add up | Full | Task reviewer authority decision · Task lifecycle & assignment model · Gen-5 task implementation specification · Accepted Gen-5 implementation · Accepted runtime evidence (R1–R4) | |
TK-REV-9 | P3 · P3.4 | Assignee is never the reviewer | Full | Task reviewer authority decision · Task lifecycle & assignment model · Task operation contract · Gen-5 task implementation specification · Accepted Gen-5 implementation · Accepted runtime evidence (R1–R4) | |
TK-REV-10 | P3 · P3.4 | A creator may review their own task | Full | Accepted Gen-5 implementation · Task reviewer authority decision · Task lifecycle & assignment model | |
TK-REV-11 | P3 · P3.4 | No reviewer, no handoff | Full | Task reviewer authority decision · Task lifecycle & assignment model · Gen-5 task implementation specification · Task operation contract · Accepted Gen-5 implementation · Accepted runtime evidence (R1–R4) | |
TK-REV-4 | P3 · P3.4 | Close-out from review | Full | Task lifecycle & assignment model · Gen-5 task implementation specification · Accepted Gen-5 implementation | |
TK-REV-5 | P3 · P3.4 | Changing the reviewer | Full | Task lifecycle & assignment model · Task reviewer authority decision · Task operation contract · Accepted runtime evidence (R1–R4) · Accepted Gen-5 implementation | |
TK-REV-6 | P3 · P3.4 | My tasks | Full | Task operation contract · Gen-5 task implementation specification · Accepted Gen-5 implementation | |
TK-MX-1 | P3 · P3.4 | Who may act on a task | Full | Gen-5 task implementation specification · Task reviewer authority decision · Accepted runtime evidence (R1–R4) · Task lifecycle & assignment model · Accepted Gen-5 implementation | |
TK-HIS-1 | P3 · P3.5 | One ordered history | Full | Task lifecycle & assignment model · Accepted Gen-5 implementation | |
TK-HIS-2 | P3 · P3.5 | History only grows | Full | Task lifecycle & assignment model · Task operation contract · Accepted Gen-5 implementation | |
TK-HIS-3 | P3 · P3.5 | Who acted, for whom | Full | Task lifecycle & assignment model · Membership model · Gen-5 task implementation specification · Accepted Gen-5 implementation | |
TK-HIS-4 | P3 · P3.5 | Assignee and reviewer entries | Full | Task lifecycle & assignment model · Accepted Gen-5 implementation | |
TK-HIS-5 | P3 · P3.5 | Comments in the history | Full | Task lifecycle & assignment model · Task operation contract · Accepted Gen-5 implementation | |
TK-HIS-6 | P3 · P3.5 | Editing comments | Not decided | Gap | Gen-5 task implementation specification · Accepted Gen-5 implementation |
TK-HIS-7 | P3 · P3.5 | Unread counts | Not decided | Full | Task lifecycle & assignment model · Gen-5 task implementation specification · Accepted Gen-5 implementation |