Single-select dropdown
Searchable or native one-value selection with deterministic ordering, clear state and stable option keys.
Shared componentFuture Spec 16 →Current-state summary
Single-select dropdown appears across the current product but is not yet governed as one fully documented reusable component. Native selects are widespread, but option ordering is inconsistent, clear behavior varies and the same taxonomy can differ between builders and grids.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Canonical interaction | Use a native select for short stable lists and an accessible searchable combobox for long or remote lists. Alphabetize by display label unless semantic order is documented, such as lifecycle or severity. Store stable option key, not display label; define placeholder, clearability, disabled reasons and unknown retired-value behavior. | Required reusable contract |
| Data contract | Store stable option ID/key and registry version; labels, order, colour and active state are presentation metadata. | Required shared storage and API behavior |
| Accessibility | Combobox announces label, expanded state, active option, result count, selection and disabled reason; full keyboard operation is required. | Required before component is approved for reuse |
| Reuse inventory | Pipeline Stage, Task Type/State/Priority, countries and regions, owners, Provider Categories, statuses, builder configuration | Known current and future consumers |
| Current inconsistencies | Task Builder Type order is not alphabetical. Urgent exists in builder but not directory filters. Select an option placeholders and clear behavior vary. | Observed or identified correction work |
User journeys
Current flows
Use Single-select dropdown
- Render from the shared component registry
- Load canonical value and configuration
- Accept keyboard, pointer or assistive-technology input
- Validate and normalize
- Persist canonical value with provenance
- Render the same meaning in profiles, grids, filters, exports and integrations
State model
Current and expected states
Value can be entered or selected with a visible label.
Must provide a visible focus indicator without layout shift.
Must distinguish unavailable input from view-only canonical value.
Requirement is communicated in label, schema and validation—not colour alone.
Inline message explains the problem and preserves the user’s input where safe.
Async work prevents duplicate commands and remains announced.
Null, empty string, zero and empty collection retain distinct meanings.
Product rules
Non-negotiable boundaries
- Build once and reuse the same component, schema and formatter in every Workspace experience.
- Display formatting is separate from canonical storage.
- Every value has a stable field key, type, validation, privacy classification and version.
- Client validation improves usability; server validation remains authoritative.
- Equivalent values render consistently in forms, grids, profiles, filters, exports, notifications and documents.
- Use a native select for short stable lists and an accessible searchable combobox for long or remote lists.
- Alphabetize by display label unless semantic order is documented, such as lifecycle or severity.
- Store stable option key, not display label; define placeholder, clearability, disabled reasons and unknown retired-value behavior.
Known current limitations · 3 mapped
What is missing, broken or unverified
Future Spec 16 owns closure →- Task Builder Type order is not alphabetical.
- Urgent exists in builder but not directory filters.
- Select an option placeholders and clear behavior vary.
Future alignment
Required evolution
- 01Promote this pattern into the approved component library.
- 02Replace local copies incrementally and retain migration adapters only where required.
- 03Add automated interaction, validation, accessibility and serialization tests.
- 04Track reuse across: Pipeline Stage, Task Type/State/Priority, countries and regions, owners, Provider Categories, statuses, builder configuration.
Current baseline
Acceptance record
- The component has one public API and canonical data contract.
- All required states are documented and tested.
- Formatting and validation are consistent across every consumer.
- Keyboard and screen-reader testing passes.
- Existing inconsistent copies have an owner and migration plan.
Reverse-spec completeness
Documentation coverage
The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.
Purpose and user outcome
DocumentedRoles and access
DocumentedRoutes and entry points
DocumentedPage and component anatomy
DocumentedFields and displayed data
DocumentedPrimary actions
DocumentedForms and validation
DocumentedStates and transitions
DocumentedEmpty, loading and error states
DocumentedResponsive behavior
PartialAccessibility behavior
PartialActivity and audit events
PartialData sources and persistence
DocumentedNotifications and automation
PartialKnown defects and limitations
DocumentedReusable component dependencies
DocumentedFuture-spec conflicts
PartialVisual and repository evidence
DeferredAcceptance of current baseline
Documented