The Transit Engine
How the opportunity feed computes who to contact — which clients, which events, and over what window.
This page documents how the opportunity feed decides what to surface.
Which clients
Only clients marked active are scanned. Clients you're no longer working with don't clutter the feed (though long-silent active clients surface separately as dormant).
Which events, over what window
ChartVault looks at a window from roughly 30 days in the past to 180 days ahead, and surfaces age- and return-based events computed from each client's chart, including:
- Returns — Saturn, Jupiter and the annual Solar Return.
- Hard transits — major outer-planet transits to the natal chart (squares, oppositions and the like) at the classical ages they recur.
- Progressed-Moon and nodal milestones.
Each event is dated to when it becomes exact, and duplicate exact-dates from a planet drifting back and forth are collapsed into one row.
How it's ranked
Events are scored by value × urgency — the client's lifetime value against how soon the event is exact — and sorted so the most worthwhile outreach is at the top. See the five signals for the full list of what feeds in.
Computed, then actionable
The feed isn't a static list — it recomputes against the real sky, and each row carries the pipeline actions (contacted, snooze, dismiss) so it stays a clean to-do list.