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.
WEB SURFACES
Company, account and product screens
WINDOWS APPLICATIONS
PC application evidence boundaries
EVIDENCE ORDER
User screen acceptance order
- RouteRun the local check; HTTP 200 + HTML proves reachability only.
- VisualOpen each screen and confirm layout, content separation and seven-locale switching.
- Portal accountComplete real login, TOTP or recovery-code MFA, users and administrator authorization.
- Product app accountAuthenticate inside each PC product separately; portal login is not evidence for this gate.
- Native transportCheck launch, native window, authenticated workflow, Exit or tray behavior and transport independently. Aurora TLS 443 browser delegation is not Native Transport.
