Cross-module navigation

Cross-module navigation is the entity graph in action. Every detail page surfaces signals from OTHER modules: a founder profile shows their startup + open opportunities for them; an opportunity shows preparation files + the event it was born from. This is the platform’s strategic moat.

How it works in one line

The shared component

`<app-related-ecosystem-signals [block]="signalsBlock()" />` is the one component that renders every cross-module signal block on every surface. It is a router — it switches on `signal.module` and renders the canonical card from each source module. Visual consistency is automatic.

The 7 supported modules

• Opportunity → <app-opportunity-card>
• Founder → <app-founder-card>
• Founder File → <app-founder-file-card>
• Calendar event → <app-event-card variant="compact">
• Startup Showcase → <app-startup-card>
• Editorial article → <app-editorial-card>
• Events Coverage → <app-coverage-card>

Why above each card

Every signal carries a one-line `reason` rendered ABOVE the canonical card as a small eyebrow. The eyebrow has a purple module-label chip + an orange arrow + italic body text. Manual editorial reasons take priority; auto-generated reasons fall back to a template ("Founder active in {sector} across {country}", "Open program matching this stage", etc).