Signal maps that keep product and ops aligned

We start with verbs and nouns only. Adjectives like significant or material vary by reader. Instead, we pair each signal with a measurement location, even if instrumentation arrives later.

We then add escalation paths that do not depend on a single executive. Escalation trees rot when one leader travels. We require a deputy on every node.

We also insist on version numbers for maps. Small version bumps make it obvious which launch used which map, preventing retroactive arguments.

Limitation: signal maps do not replace monitoring stacks. They document intent and ownership so monitoring work stays coherent.