Naming rules that survive a site move
Site codes feel permanent until facilities moves a floor or consolidates two campuses. Application events that still emit the old label make session continuity look like a mass logout. Connectivity teams then chase ghosts on circuits that never carried those users.
We favour a thin taxonomy: a stable site identifier that outlives marketing names, a path identifier for the journey under study, and a change marker that can be joined to both application and connectivity timelines. Anything beyond that tends to rot faster than it helps.
Write the rename rule before the move, not after. Include who owns the application property, who owns the circuit inventory label, and how long dual-write is allowed. Dual-write without an end date is how two truths become permanent.
Session Continuity Mapping packages these rules into a catalogue your release and change-day checklists can reuse. The goal is boring charts that stay comparable when Hung Hom offices reshuffle—not a prettier dashboard.