Money, rate and percentage input
Currency, hourly rate, project value, budget and percentage entry with precise storage and consistent formatting.
Shared componentFuture Spec 16 →Current-state summary
Money, rate and percentage input appears across the current product but is not yet governed as one fully documented reusable component. Estimated values and Project Snapshot amounts display dollars and commas, but currency selection, minor-unit precision, rate basis and percentage semantics are not one shared contract.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Canonical interaction | Money always includes ISO currency and stores exact minor units or fixed decimal—not floating point. Rates declare their basis such as per hour, item, day or fixed. Percent fields declare whether 15 means 15% and store a consistent decimal representation; format on blur without moving the cursor unexpectedly. | Required reusable contract |
| Data contract | Store amount_minor plus ISO currency, or fixed decimal where required; percentages use a documented normalized decimal and rates include basis/unit. | Required shared storage and API behavior |
| Accessibility | Currency/unit prefix and suffix must be programmatically associated; errors state allowed range and precision. | Required before component is approved for reuse |
| Reuse inventory | Project values, Budget Categories, Items, shopping lists, Proposals, Purchase Orders, Invoices, commissions and taxes | Known current and future consumers |
| Current inconsistencies | Currency is often implied as dollars. Rate basis is rendered inconsistently. Blank/zero and tax-inclusive/exclusive behavior are not standardized. | Observed or identified correction work |
User journeys
Current flows
Use Money, rate and percentage 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.
- Money always includes ISO currency and stores exact minor units or fixed decimal—not floating point.
- Rates declare their basis such as per hour, item, day or fixed.
- Percent fields declare whether 15 means 15% and store a consistent decimal representation; format on blur without moving the cursor unexpectedly.
Known current limitations · 3 mapped
What is missing, broken or unverified
Future Spec 16 owns closure →- Currency is often implied as dollars.
- Rate basis is rendered inconsistently.
- Blank/zero and tax-inclusive/exclusive behavior are not standardized.
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: Project values, Budget Categories, Items, shopping lists, Proposals, Purchase Orders, Invoices, commissions and taxes.
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