Two plan pages disagree about which end of the list the lowest tier goes #103

New Issue

2026-09-21T07:18:31Z

cgalo5758 commented

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

The question

The page that manages a ladder's tiers lists the lowest rank at the top and counts downwards. The cross-ladder grid puts the lowest rank at the bottom, so the ladder reads upwards, mirroring the member catalog where the larger plan sits higher. Each was chosen deliberately and they contradict each other, so an operator reading both in one sitting has to re-orient. Which direction wins, and does the member catalog's mirroring survive it?

What depends on the answer

The two operator surfaces, the member catalog's ordering if the mirror is the thing that gives way, and any later surface that lists ranks.

Options known so far

Lowest rank first everywhere, on the argument that a list is read from the top and rank zero is the beginning.
Lowest rank last everywhere, keeping the member catalog's mirror and making the management page read upwards.
Keep both and write down why a configuration list and an overview read in opposite directions, which is what happens today without anyone having decided it.

Decided when

The plan model states the direction ranks are listed in, and both operator surfaces and the member catalog match it.

Migrated from status/issues.md at b7a0e15

## The question The page that manages a ladder's tiers lists the lowest rank at the top and counts downwards. The cross-ladder grid puts the lowest rank at the bottom, so the ladder reads upwards, mirroring the member catalog where the larger plan sits higher. Each was chosen deliberately and they contradict each other, so an operator reading both in one sitting has to re-orient. Which direction wins, and does the member catalog's mirroring survive it? ## What depends on the answer The two operator surfaces, the member catalog's ordering if the mirror is the thing that gives way, and any later surface that lists ranks. ## Options known so far - Lowest rank first everywhere, on the argument that a list is read from the top and rank zero is the beginning. - Lowest rank last everywhere, keeping the member catalog's mirror and making the management page read upwards. - Keep both and write down why a configuration list and an overview read in opposite directions, which is what happens today without anyone having decided it. ## Decided when The plan model states the direction ranks are listed in, and both operator surfaces and the member catalog match it. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

design

area/catalog area/operator-ui labels 2026-09-21 07:18:31 +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#103