Treat the Browser Surface as Part of the Product

A product is encountered in browser tabs, bookmarks, launchers, headers, and shared links before a user reads the main page. Those surfaces deserve the same source-of-truth discipline as the primary interface.

Keep the asset inventory explicit: name the source file, emitted path, consuming surface, and verification step. This prevents a visually correct page from shipping with a stale tab icon or an inconsistent footer mark.

The practical lesson is to include identity surfaces in the acceptance criteria for a UI change. Small omissions are still product defects when they repeat across every session.