The Domains page hides two sections behind toggles chosen for convenience, not for a reason #35

New Issue

2026-09-21T07:18:11Z

cgalo5758 commented

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

The question

The effective claim policy and the claim history were put behind collapsed toggles because the page was long, not because either is secondary; the toggles have since been removed and both are plain sections again, which is an interim state rather than a design. The page is the densest in the operator panel: three sections, two tables and the claim, evidence and release flows inline. What on this page is disclosed, on what rule, and how disclosure is shown consistently with the rest of the console?

What depends on the answer

The reading order of the page and whether the same rule governs the other dense surfaces. Two facts belong to the round: the policy section is meant to become a link into the deployment settings once that page exists, rather than a copy of the values; and the live claims table is the one list on the page without the shared list scaffold.

Options known so far

A disclosure rule in the design system, applied here first: what a page shows on arrival, what is one interaction away, and what moves to a page of its own.
Split the page: claims and their evidence on one surface, served domains and history on another.

Decided when

The design system states the disclosure rule, the Domains page follows it, and the claims table carries the same scaffold as every other list.

Migrated from status/issues.md at b7a0e15

## The question The effective claim policy and the claim history were put behind collapsed toggles because the page was long, not because either is secondary; the toggles have since been removed and both are plain sections again, which is an interim state rather than a design. The page is the densest in the operator panel: three sections, two tables and the claim, evidence and release flows inline. What on this page is disclosed, on what rule, and how disclosure is shown consistently with the rest of the console? ## What depends on the answer The reading order of the page and whether the same rule governs the other dense surfaces. Two facts belong to the round: the policy section is meant to become a link into the deployment settings once that page exists, rather than a copy of the values; and the live claims table is the one list on the page without the shared list scaffold. ## Options known so far - A disclosure rule in the design system, applied here first: what a page shows on arrival, what is one interaction away, and what moves to a page of its own. - Split the page: claims and their evidence on one surface, served domains and history on another. ## Decided when The design system states the disclosure rule, the Domains page follows it, and the claims table carries the same scaffold as every other list. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

design

area/domains area/operator-ui labels 2026-09-21 07:18:11 +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#35