Nothing defines what a suspended or archived resource pool means #92

New Issue

2026-09-21T07:18:28Z

cgalo5758 commented

2026-09-21 07:18:28 +00:00

The question

A resource pool (the per-organization record of what an organization is allowed) carries a status that can read suspended or archived, with timestamps beside it. Nothing writes either value, and no page offers the move. If a value were set by hand the console would half-honour it: the resolvers that find an organization's default pool filter on pool status, so delivery would stop, while quota consumption reads only the assignment's status and would keep counting. What suspension is supposed to mean, and what it should reach, is written down nowhere.

What depends on the answer

Whether the columns gain writers and an operator control, or are removed as a shape the console does not use; and, if they stay, whether the cascade covers the workspaces assigned to the pool, the sites those workspaces hold, and the counters already spent.

Options known so far

Define the two states and the full cascade, then build the writers and the control.
Drop the columns and express taking a pool out of service some other way.

Until the shared model defines the cascade the console should not add writers, because a half-honoured status is worse than none.

Decided when

The entitlements model states what a suspended and an archived pool mean for delivery, for consumption and for the workspaces assigned to it, and the console either implements that or removes the columns. This is the same question as the workspace one, and the two answers must agree.

Migrated from status/issues.md at b7a0e15

## The question A resource pool (the per-organization record of what an organization is allowed) carries a status that can read `suspended` or `archived`, with timestamps beside it. Nothing writes either value, and no page offers the move. If a value were set by hand the console would half-honour it: the resolvers that find an organization's default pool filter on pool status, so delivery would stop, while quota consumption reads only the assignment's status and would keep counting. What suspension is supposed to mean, and what it should reach, is written down nowhere. ## What depends on the answer Whether the columns gain writers and an operator control, or are removed as a shape the console does not use; and, if they stay, whether the cascade covers the workspaces assigned to the pool, the sites those workspaces hold, and the counters already spent. ## Options known so far - Define the two states and the full cascade, then build the writers and the control. - Drop the columns and express taking a pool out of service some other way. Until the shared model defines the cascade the console should not add writers, because a half-honoured status is worse than none. ## Decided when The entitlements model states what a suspended and an archived pool mean for delivery, for consumption and for the workspaces assigned to it, and the console either implements that or removes the columns. This is the same question as the workspace one, and the two answers must agree. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

design

area/entitlements upstream labels 2026-09-21 07:18:28 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#92