Advanced techniques

Birth-Time Spread (which sub lords and verdicts move within the stated uncertainty)

get_birth_time_spread

[KP] Rebuilds the chart across the birth-time uncertainty the user states and reports exactly which cusp sub lords change, at which minute, and which promise verdicts change between which values. Use it BEFORE stating any verdict whenever the user knows their birth time only roughly ('about 7:20', 'to the nearest five minutes'): measured over 48 charts ('scripts/bp022-birth-time-spread.ts'), at plus or minus 5 minutes 72.9% of promise verdicts change inside the window and 51.3% cross DENIED. Every instant at which a cusp or planet changes sign, star, sub or house, or a node gains or loses a conjunction or aspect, is solved to the second, and the same gate analyze_natal_promise runs is re-run between those instants (never on a grid). Returns per cusp the stated lords, every change with its minute and 'subLordHoldsOver' (the stretch of birth times over which the stated sub lord holds); per planet its house and lord changes; 'nodeContactChanges'; and per event 'timeStability' ('stable' or 'changes'), 'verdictsInWindow', 'crossesDenied', 'statedVerdictHoldsOver', 'firstChangeMinutes' (the nearest minute, signed, at which the verdict becomes something else), 'intervals' with the deciding CSL, and 'changes' each naming its 'causes'. READ 'summary.eventsStable' FIRST: those verdicts rest on nothing the uncertainty moves and can be stated outright. A verdict marked 'changes' is not settled until the time is rectified (rectify_birth_time, rectify_by_event_ruling_planets): give the reading on each side of the minute that separates them, or rectify first. The source is Astro Secrets canon p.180 (a later author, not KSK): 'in case birth time given is wrong, it has to be rectified. Otherwise cuspal sublords and planet sublords will vary'. The window is the user's own figure: never invent one, and ask when it is unknown. Nothing is scored, ranked or weighed and no minute is picked. **'cusps' and 'events' are paged together**: page N carries the Nth page of each, cut to its own row weight, and a list that ends sooner is empty on the pages after its last (the page note says which); 'planets', 'nodeContactChanges' and 'summary' repeat whole on every page.

Parameters

Example call

Send the request as a standard MCP tools/call:

POST https://mcp.lumin.guru/mcp
Authorization: Bearer mcp_yourkey...
Accept: application/json, text/event-stream
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_birth_time_spread",
    "arguments": {
      "birth_datetime": "1992-08-14T04:32:00",
      "latitude": 6.927,
      "longitude": 79.861,
      "utc_offset_minutes": 330,
      "ayanamsa": "kp",
      "birth_time_uncertainty_minutes": 0
    }
  }
}