Number input
Locale-aware integer and decimal entry with units, bounds, precision and comma formatting.
Shared componentFuture Spec 16 →Current-state summary
Number input appears across the current product but is not yet governed as one fully documented reusable component. Square footage, design hours, team size and due offsets use different plain inputs and display suffixes.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Canonical interaction | Define integer or decimal, minimum, maximum, step, precision and unit in the field schema. Accept locale separators but normalize to a numeric value. Keep blank, zero and not applicable distinct; display thousands separators and unit consistently. | Required reusable contract |
| Data contract | Store numeric value in an appropriate integer/decimal type plus stable unit code; never store commas or unit text in the numeric column. | Required shared storage and API behavior |
| Accessibility | Provide input mode, explicit unit text and usable increment controls; do not rely on browser spinner alone. | Required before component is approved for reuse |
| Reuse inventory | square footage, quantities, design hours, team and crew size, capacity, lead times, task offsets | Known current and future consumers |
| Current inconsistencies | Comma formatting is inconsistent. Unit may be embedded in labels or display strings. Precision and negative-value behavior are undocumented. | Observed or identified correction work |
User journeys
Current flows
Use Number input
- 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.
- Define integer or decimal, minimum, maximum, step, precision and unit in the field schema.
- Accept locale separators but normalize to a numeric value.
- Keep blank, zero and not applicable distinct; display thousands separators and unit consistently.
Known current limitations · 3 mapped
What is missing, broken or unverified
Future Spec 16 owns closure →- Comma formatting is inconsistent.
- Unit may be embedded in labels or display strings.
- Precision and negative-value behavior are undocumented.
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: square footage, quantities, design hours, team and crew size, capacity, lead times, task offsets.
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