Cross-Module Integration
Manual vs auto-suggested
Manual vs auto-suggested — documentation pending.
Complete
Manual editorial links and auto-suggested links coexist in the same table. The resolver merges them on every page render — manual first by featured/score, auto fills remaining slots up to the per-module cap. Editors can hide any auto-suggestion they reject without affecting the source data.
Difference at a glance
MANUAL (T2)
- Curated by an editor via the manifest or admin UI.
- Authored bilingual reason text (160 chars max).
- Score defaults to 90. Featured manual links rank first.
- Survives auto-suggester runs — the nightly pipeline does not overwrite manual rows.
- Editor adds editorial_reason → renders as italic body of the Why eyebrow.
AUTO-SUGGESTED (T3)
- Generated by the resolver pipeline based on taxonomy scoring.
- Reason is filled by a localized template (e.g. "Founder in matching sector + country").
- Score 30-70 based on country + sector + stage matches.
- Editor can hide via `is_hidden = true` if the auto-suggestion is wrong.
- Re-runs nightly — fresh entity changes propagate without editor intervention.
The auto-suggester scoring pipeline
For each source entity, the suggester scans every candidate target across all 7 module types. Per match: +30 country, +25 sector, +15 stage, +20 opportunity-is-open. Threshold by target type: ≥30 (file), ≥30 (startup/founder/opportunity), ≥25 (event/coverage/editorial). Candidates above threshold land in the table with `is_auto_suggested = true`.