Restoring a Socket.IO connection did not restore a trustworthy dashboard; the application needed to prove continuity or replace local state.
#realtime
A recently delivered counter update was already old, so T04P learned to preserve when an observation happened and when the system received it.
A live operations screen looked healthy while its data stood still, forcing freshness to become explicit product state.
T04P’s browser connection stayed healthy while one upstream feed stopped, proving that transport and knowledge needed separate state.