Cross-module signal clicks

Every click on a related-ecosystem-signals card emits a `cross_module_signal_click` event. The data answers the strategic question: which cross-module links actually move users, and from which surfaces? This is the empirical feedback loop for the editorial-curation discipline.

Event shape

cross_module_signal_click

Single canonical event name for all 7 signal types. The properties distinguish the variants.

Required properties

• source_module — The page the user clicked FROM. One of the 7 module values.
• source_entity_id — ID of the source entity (e.g. the article being read, the founder profile being viewed).
• target_module — The module of the clicked signal. The user is being routed INTO this module.
• target_entity_id — ID of the destination entity.
• relation_type — One of: linked_founder, linked_startup, related_opportunity, mentioned_in, preparation_resource, follow_up_signal, born_from_event, speaker_at, etc.
• source — `manual` if the link is in the editorial manifest; `auto` if auto-suggested by the resolver.
• score — Relation strength 0-100. Helps measure auto-suggester quality.
• position — 1-indexed position in the signals block. Helps measure visual hierarchy effectiveness.