TOMORROW SCREEN ACCEPTANCE

Start every screen check from one place.

Review company pages, account and MFA, Blossom documentation and Windows applications separately. HTTP 200, visual rendering, authenticated behavior and native transport are different evidence.

Evidence date2026-08-22No production data or authentication setting is changed
Web screens0local routes
PC app surfaces4Windows
Automatic reachabilityHTTP + HTML
Manual acceptance0this device

Not run yet

WEB SURFACES

Company, account and product screens

Switch all seven locales from each page menu

WINDOWS APPLICATIONS

PC application evidence boundaries

Keep browser delegation separate from native transport

EVIDENCE ORDER

User screen acceptance order

  1. RouteRun the local check; HTTP 200 + HTML proves reachability only.
  2. VisualOpen each screen and confirm layout, content separation and seven-locale switching.
  3. Portal accountComplete real login, TOTP or recovery-code MFA, users and administrator authorization.
  4. Product app accountAuthenticate inside each PC product separately; portal login is not evidence for this gate.
  5. Native transportCheck launch, native window, authenticated workflow, Exit or tray behavior and transport independently. Aurora TLS 443 browser delegation is not Native Transport.