How does your team actually keep architecture diagrams from going stale?

Every place I've worked has the same problem a diagram gets made once during a design review, then quietly rots as the system evolves around it.

Curious how more disciplined teams handle this. Scheduled regeneration? Tied to doc review? Or has everyone accepted it's a snapshot, not a source of truth?

Just curious.