What the fourth number on the operator's landing page should be #49

New Issue

2026-09-21T07:18:15Z

cgalo5758 commented

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

The question

The landing page's headline row is reserved for the numbers an operator reads every day and holds three. A fourth was weighed and deferred: the candidates were payments whose collection has failed, which is one more filter on the query already behind the recurring-revenue caption and links to a facet the subscriptions list already has, and grants ending within the week, which is one new count. The preference at the time was to wait until an issue tracker existed and make the fourth number its open count. A tracker now exists, and it is a separate service. So: which number, and may the row hold a count the console does not compute?

What depends on the answer

The headline row's contract, which says the row carries daily readings and nothing else, and whether the console acquires a reason to read another service on its landing page.

Options known so far

Payments past due, linking to the subscriptions list's existing facet.
Grants ending within seven days, linking to the grants list.
Open tickets from the tracker, which means the console reads a service it does not own and fails softly when that service is down.
Leave the row at three, and say in the navigation spec that three is the answer.

Decided when

The operator navigation spec names the fourth daily reading and where its number comes from, or records that the row stays at three.

Migrated from status/issues.md at b7a0e15

## The question The landing page's headline row is reserved for the numbers an operator reads every day and holds three. A fourth was weighed and deferred: the candidates were payments whose collection has failed, which is one more filter on the query already behind the recurring-revenue caption and links to a facet the subscriptions list already has, and grants ending within the week, which is one new count. The preference at the time was to wait until an issue tracker existed and make the fourth number its open count. A tracker now exists, and it is a separate service. So: which number, and may the row hold a count the console does not compute? ## What depends on the answer The headline row's contract, which says the row carries daily readings and nothing else, and whether the console acquires a reason to read another service on its landing page. ## Options known so far - Payments past due, linking to the subscriptions list's existing facet. - Grants ending within seven days, linking to the grants list. - Open tickets from the tracker, which means the console reads a service it does not own and fails softly when that service is down. - Leave the row at three, and say in the navigation spec that three is the answer. ## Decided when The operator navigation spec names the fourth daily reading and where its number comes from, or records that the row stays at three. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

design

area/entitlements area/billing area/operator-ui labels 2026-09-21 07:18:15 +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#49