Reverse spec drafted

Email input

Validated, normalized email field with identity, invitation and contact-safe behavior.

Observed routeShared componentFuture Spec 16 →

Current maturityReusable pattern identified; canonical component contract required

Evidence confidencePartially verified

Last reviewedAugust 4, 2026

Visual evidenceDeferred during UI updates

Current-state summary

Email input appears across the current product but is not yet governed as one fully documented reusable component. Email fields appear across authentication, invitations, Clients, Applications and Workspace Profiles, but canonicalization, verification and duplicate-identity behavior are not visible as one control.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

Element	Current behavior	Verification
Canonical interaction	Use input type email and autocomplete=email where appropriate. Normalize surrounding whitespace and domain case without making unsafe assumptions about local-part equivalence. Separate syntax validity, verification status, deliverability and identity uniqueness.	Required reusable contract
Data contract	Store original display email and normalized comparison form, verification timestamp, source and purpose; avoid using email as an immutable foreign key.	Required shared storage and API behavior
Accessibility	Expose clear format errors without account enumeration; support paste, password managers and mobile email keyboard.	Required before component is approved for reuse
Reuse inventory	Sign in and recovery, Teammate invitations, Client contacts, Provider Applications, Workspace Profile, communications	Known current and future consumers
Current inconsistencies	Verification state is inconsistently surfaced. Duplicate User/contact handling is undocumented. Primary versus secondary email semantics are not standardized.	Observed or identified correction work

User journeys

Current flows

Use Email 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

Default

Value can be entered or selected with a visible label.

Focused

Must provide a visible focus indicator without layout shift.

Disabled or read-only

Must distinguish unavailable input from view-only canonical value.

Required or optional

Requirement is communicated in label, schema and validation—not colour alone.

Invalid or warning

Inline message explains the problem and preserves the user’s input where safe.

Loading or saving

Async work prevents duplicate commands and remains announced.

Empty or cleared

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 input type email and autocomplete=email where appropriate.
Normalize surrounding whitespace and domain case without making unsafe assumptions about local-part equivalence.
Separate syntax validity, verification status, deliverability and identity uniqueness.

Dependencies

Spec 16 Design System and Reusable ComponentsShared field registryDesign tokensDynamic formsPermissionsLocalization and accessibility testing

Known current limitations · 3 mapped

What is missing, broken or unverified

Future Spec 16 owns closure →

Verification state is inconsistently surfaced.
Duplicate User/contact handling is undocumented.
Primary versus secondary email semantics 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: Sign in and recovery, Teammate invitations, Client contacts, Provider Applications, Workspace Profile, communications.

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

Documented

Roles and access

Documented

Routes and entry points

Documented

Page and component anatomy

Documented

Fields and displayed data

Documented

Primary actions

Documented

Forms and validation

Documented

States and transitions

Documented

Empty, loading and error states

Documented

Responsive behavior

Partial

Accessibility behavior

Partial

Activity and audit events

Partial

Data sources and persistence

Documented

Notifications and automation

Partial

Known defects and limitations

Documented

Reusable component dependencies

Documented

Future-spec conflicts

Partial

Visual and repository evidence

Deferred

Acceptance of current baseline

Documented