The operator search does not say what it can find, and finds less than it promises #64

New Issue

2026-09-21T07:18:19Z

cgalo5758 commented

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

The question

The search on the operator's landing page invites anything: it asks for a person, an organization, or anything with a key. It resolves exact keys for organizations, plan ladders, entitlement sets and products, then people by name or email, then organization names. It touches nothing in billing, and an invoice carries a number rather than a key, so typing an invoice number answers that no person or organization matches it. The placeholder, the no-match sentence and the resolver each describe a different set. What is the set, stated once, so that all three agree?

What depends on the answer

Whether the search is a general finder or a directory of two record classes, and whether a new record class joins it automatically or by someone remembering. The answer also decides the two sentences a person reads, which today contradict each other.

Options known so far

Every record that has a page of its own, found by the identifier its page shows: a name, an email address, a key or a number. That is persons, organizations, products, entitlement sets, plan ladders and invoices today; a class joins the set when it gets a page, and a test keyed on the screen manifest's detail routes holds the search to it. The placeholder then says what to type rather than listing nouns, and the no-match sentence, the one place the list is needed, names the classes from the resolver registry so the two cannot drift. Invoice numbers repeat across billing accounts, which the existing disambiguation list already handles.
Keep the present scope and narrow the invitation to the two classes it really serves.

Decided when

The set is written down, the resolver registry is the single source for both the invitation and the refusal, and a test fails when a record class gains a page without joining the search.

Migrated from status/issues.md at b7a0e15

## The question The search on the operator's landing page invites anything: it asks for a person, an organization, or anything with a key. It resolves exact keys for organizations, plan ladders, entitlement sets and products, then people by name or email, then organization names. It touches nothing in billing, and an invoice carries a number rather than a key, so typing an invoice number answers that no person or organization matches it. The placeholder, the no-match sentence and the resolver each describe a different set. What is the set, stated once, so that all three agree? ## What depends on the answer Whether the search is a general finder or a directory of two record classes, and whether a new record class joins it automatically or by someone remembering. The answer also decides the two sentences a person reads, which today contradict each other. ## Options known so far - Every record that has a page of its own, found by the identifier its page shows: a name, an email address, a key or a number. That is persons, organizations, products, entitlement sets, plan ladders and invoices today; a class joins the set when it gets a page, and a test keyed on the screen manifest's detail routes holds the search to it. The placeholder then says what to type rather than listing nouns, and the no-match sentence, the one place the list is needed, names the classes from the resolver registry so the two cannot drift. Invoice numbers repeat across billing accounts, which the existing disambiguation list already handles. - Keep the present scope and narrow the invitation to the two classes it really serves. ## Decided when The set is written down, the resolver registry is the single source for both the invitation and the refusal, and a test fails when a record class gains a page without joining the search. Migrated from status/issues.md at b7a0e15

cgalo5758 added this to the Public launch milestone 2026-09-21 07:18:19 +00:00

cgalo5758 added the

kind

design

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