Toast, banner and inline alert
Transient confirmation, persistent page-level notice and contextual warning/error patterns.
Shared componentFuture Spec 16 →Current-state summary
Toast, banner and inline alert appears across the current product but is not yet governed as one fully documented reusable component. Future workflows require delivery failures, access sessions, integration health and save confirmations, but a complete live hierarchy of transient versus persistent messages is not documented.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Canonical interaction | Toast confirms low-risk completed actions and never carries required decisions. Banner communicates persistent page/Workspace conditions until resolved or acknowledged. Inline alert belongs beside affected content; errors include action and correlation/reference where support is needed. | Required reusable contract |
| Data contract | Messages use stable event/error codes, severity, scope, dismissibility, expiry and action descriptors; sensitive content is permission-safe. | Required shared storage and API behavior |
| Accessibility | Use status for confirmations and alert for urgent failures; provide pause/dismiss controls and enough time to read without stealing focus. | Required before component is approved for reuse |
| Reuse inventory | saves, imports, provisioning, administrative access, integration health, payments, delivery exceptions, security | Known current and future consumers |
| Current inconsistencies | No central severity/duration rules are evidenced. Notification centre and toast responsibilities may overlap. Failure recovery actions are inconsistent. | Observed or identified correction work |
User journeys
Current flows
Use Toast, banner and inline alert
- 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.
- Toast confirms low-risk completed actions and never carries required decisions.
- Banner communicates persistent page/Workspace conditions until resolved or acknowledged.
- Inline alert belongs beside affected content; errors include action and correlation/reference where support is needed.
Known current limitations · 3 mapped
What is missing, broken or unverified
Future Spec 16 owns closure →- No central severity/duration rules are evidenced.
- Notification centre and toast responsibilities may overlap.
- Failure recovery actions are inconsistent.
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: saves, imports, provisioning, administrative access, integration health, payments, delivery exceptions, security.
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