Cross-module relationships

Cross-module management is the admin surface for maintaining the platform’s entity graph — the web of relatedXxxIds + mentionedXxxIds that connects founders, startups, events, opportunities, files, editorial, and coverage. It is the maintenance layer, not a creation layer: every link is born in a per-module admin surface; this layer audits, repairs, and visualises.

Admin surfaces

• /founder-account/admin/graph — integrity dashboard. Counters: total entities by type, broken-link count, orphaned records (e.g. CoverageArticle whose parentEventId no longer resolves).
• /founder-account/admin/graph/integrity-sweep — run the integrity sweep on demand. Output: CSV of every broken (source-id, target-id, target-module) tuple + severity.
• /founder-account/admin/graph/repair — bulk repair tool. Pick a broken-link CSV, the tool re-resolves each row, suggests fixes (re-link to a renamed entity, or strip the broken ID), admin approves batch-wise.
• /founder-account/admin/graph/visualize — force-directed graph of entity connections for one starting entity. Useful for explaining "why is this article surfacing on this startup’s page" type questions.

The integrity sweep contract

• Runs automatically on every release as part of the build pipeline. Output is the release gate — zero broken pairs allowed.
• Runs on-demand via the admin surface when a release is hot-fixed or when an admin suspects drift.
• Output severity: blocker = orphaned core record (e.g. published coverage with missing parent event); critical = broken bidirectional pair (founder ↔ startup half-link); major = stale mention in optional array.