Use cases
Scheduling and electional
Events and venues, calendars and productivity, and local and regional services all lean on the same electional core: rank_candidate_dates is the right call for a real scheduling conversation, because the user names the 2 to 10 dates they can actually do, which is far cheaper than an open search.
Events, weddings and venues
| Product | Tool chain | Constraint |
|---|---|---|
| Venue dates re-ranked by auspiciousness | get_election_catalog, rank_candidate_dates, find_wedding_muhurta | Label the joint mode as a Lumin extension |
| Multi-day ceremony run sheet | find_auspicious_time, get_choghadiya_today, get_hora_today | None |
| Corporate event and launch scheduling | find_business_launch_time, find_meeting_time, get_mundane_ingress | The mundane layer is a content lens |
| Contract-signing slot in a deal room | find_contract_signing_time, get_muhurta_advanced | Not legal advice |
| Naming ceremony and family rites | get_election_catalog, find_election_window, get_panchang | None |
rank_candidate_dates is the right call for a real scheduling conversation: the user names the 2 to 10 dates they can actually do, which is far cheaper than an open search.
Calendars, productivity and scheduling
| Product | Tool chain | Constraint |
|---|---|---|
| Calendar plugin that suggests when to do things | get_election_catalog, find_meeting_time, find_contract_signing_time, rank_candidate_dates | None |
| Focus and deep-work hour planner | get_hora_today, get_choghadiya_today, get_moon_transit, get_sublord_changes | None, and zero PII |
| Do-not-start band for a project tool | get_chidra_dasha, get_retrograde_advanced, get_transit_crossings | Advisory |
| Team meeting scheduler across charts | find_meeting_time, find_joint_election_window | Voluntary. Label the joint mode |
Local and regional services
| Product | Tool chain | Constraint |
|---|---|---|
| Panchang widget for a news site or temple portal | get_panchang, get_choghadiya_today, get_hora_today | None. Zero PII, three calls |
| Priest and ritual-services marketplace | get_election_catalog, find_election_window, get_panchang, get_mantra_recommendation | None |
| Regional almanac and festival app | get_ephemeris, get_panchang, get_seasonal_outlook, get_mundane_ingress | Content lens |
The detail every implementation misses
The day runs sunrise to sunrise, so the UTC offset is mandatory on the panchang family. Getting that wrong makes every call a day early east of Greenwich.
No score, no ranked top ten, by design
Every tool chain on this page draws on the electional family. An exhaustive sweep of the corpus found no numeric or ordinal ranking of moments anywhere; the strongest language used is "seems to be the best" and "next in priority". The tools return one moment, or up to three on a genuine tie, each with a stated reason. Do not build a score on top of them, and do not present the output as a ranked list.
Where to next
- muhurta-scheduler is the worked example: a date picker over the event catalog.
- today-panel is the worked example for the panchang widget row, zero PII, five calls.
- Responsible use for the full electional constraint.