Claim states and records

the decision is that ownership moves only by an explicit transfer, in two steps: the owner offers ownership to an existing active member, and it moves only if that member accepts. An offer can be declined or cancelled, and expires after 14 days; only one offer can be open at a time. A transfer moves who owns the workspace: nobody's workspace role changes and nobody's access is interrupted. Inside each active project the incoming owner takes up the standing membership that comes with owning the workspace (PJ-ACC-6) — joining it if they were not in it, or moving up to the admin role if they were an ordinary member, without their membership being broken and started again. The outgoing owner keeps every project membership they hold: losing ownership removes none of them. A Personal Workspace is never transferred.

P1.2.

the decision is that only the owner may choose this, after confirming their identity again and confirming explicitly. If other members remain, a 14-day notice period runs, during which the owner can cancel; every member is given notice of the effective date and its effect on their access. Archiving a workspace archives all its projects, closes their unfinished tasks and ends everyone's access at once.

P1.1.

the decision is that a Personal Workspace is archived only together with its account, when the account is deleted — confirming the deletion is the owner's authorization. It cannot be deleted on its own while the account exists, and its ownership never moves.

P1.1.

the decision is that whatever operation restores that access must, in the same step, put the owner back into every active project of the workspace with the admin role — opening a membership where they have none, or raising an ordinary membership to admin without breaking it. Any membership opened begins at the moment of restoration; nothing is written back over the period when the person could not act.

P2.2.

the decision is that archived content can be reached outside the ordinary product only through a separately governed channel: tied to a case, time-limited, least-privilege, attributed and fully audited. It never makes anyone a member again and never changes ownership.

T2.6.

the decision covers only restoration's shape: restoring would make the container active again, and almost nothing else. It would reinstate no former member, no former admin, no assignee, no reviewer and no chat membership; anyone who needs access would have to be added again, as a new membership, and tasks that archiving canceled would not reopen. One exception was decided later, and it is narrow: restoring a project would give the workspace's current owner back the standing membership that comes with owning the workspace (PJ-ACC-6), in the same step, provided they can still reach the workspace — and as a new membership beginning then, never the closed one reopened. Whether restoration will be offered at all is not decided (XD-ARCH-3).

T2.6.

the decision is that an export must be offered before a workspace is archived, and before the account loses the access needed to produce or collect it. For a user-created workspace with other active members, completing the export or explicitly waiving it is part of the closing process. Export never restores ordinary access.

T2.6.

the decision is that the owner may do both. Taking the admin role away is allowed only while governance stays valid — the owner can act, or another active workspace admin remains. A role change neither ends nor restarts anyone's membership.

P1.4.

the decision is that a suspended account keeps its memberships but cannot act in any workspace or project, and that suspension is not departure: it hands no one's work to anyone else.

P1.3.

the decision is that an active workspace admin restores project administration — including appointing project admins — and that where no admin is active, a verified support process outside the product may help restore administration. Nothing ever moves ownership automatically.

the pilot describes no situation in which an owner can no longer act, and its statement about project roles is explicitly scoped to today (PJ-ROLE-1).

the decision is that every such role change is recorded as part of the organization's history, and that an ownership transfer is never recorded as a role change.

P2.2.

the decision is that a project's owner or admins may choose a default reviewer. A new task takes it at creation unless someone names a reviewer, and later changes to the default never change existing tasks.

P3.4.