Panchangam Reference

Same-Rasi Chandra conjunction primitive ​

interpretation.same-rasi-conjunction

A complete canonical chart is classified for Chandra sharing a Rasi with Kuja or Shani, then sampled states are combined with fail-closed window precedence.

Assurance ​

LevelCurrent statement
Documented and traceableYes — the canonical record includes the process and a worked example.
Regression or reproduction checkedLinked to 3 repository test file(s).
Independently source-supportedAvailable only for the explicitly named provenance claims or comparison cells.

Computation method ​

Method type: decision-table

Admit only a complete canonical nine-graha Rasi map, fail when Chandra shares a Rasi with Kuja or Shani, pass when both are different, and otherwise return unknown; across a window, fail outranks unknown, which outranks pass.

Process ​

  1. Validate that all nine canonical Grahas occur exactly once with canonical names and Rasis; otherwise return unknown.
  2. Compare Chandra's Rasi independently with Kuja's and Shani's Rasis.
  3. Return fail when either equality holds and pass only when both comparisons are unequal.
  4. Across sampled states, return the first fail; otherwise the first unknown; otherwise return unknown for empty samples, budget exhaustion, or incomplete transition coverage; return pass only after complete all-pass coverage.
  5. Map a known fail to rejection only in the Borrowing Drik post-screen; keep non-Drik engines unknown and preserve the separate baseline-completeness boundary.

Formulae ​

Distributive same-Rasi conjunction ​

text
C = (R(Chandra) = R(Kuja)) OR (R(Chandra) = R(Shani))
  • R(g): canonical Rasi occupied by Graha g
  • C: event-bounded same-Rasi conjunction fact

Worked example ​

Chandra and Kuja in Mesha, Shani in Kumbha ​

Inputs

  • Chandra Rasi: Mesha
  • Kuja Rasi: Mesha
  • Shani Rasi: Kumbha
  • complete canonical chart: yes

Calculation

  1. R(Chandra) equals R(Kuja).
  2. The disjunction is true even though R(Chandra) differs from R(Shani).

Result

  • Primitive outcome: fail
  • Borrowing Drik post-screen effect: reject

Method notes ​

  • Window aggregation preserves fail over unknown so an already-observed prohibited state is not hidden by incomplete later coverage.

Contract ​

Owning layer: interpretation
Claim kind: project-heuristic
Time basis: An exact chart snapshot or a sampled half-open candidate window; the Borrowing Drik post-screen consumes the sampled outcome.

Inputs ​

  • complete canonical nine-graha Rasi facts
  • sampled primitive outcomes
  • Rasi-transition coverage state
  • chart-request budget state

Outputs ​

  • pass, fail, or unknown outcome with evidence
  • sampled-window outcome

References and evidence ​

Evidence classes: textual, project_heuristic
Verification states: verified, heuristic

The cited source statement, selected same-Rasi computation convention and event-level reject effect are separately registered. The primitive is implemented with a TypeScript parity mirror and consumed only by the Borrowing Drik post-screen.

muhurta.borrowing_money ​

Evidence class: textual
Verification state: verified
Locator: B. V. Raman, Chapter X, 'Borrowing Money,' inspected in the 2020 Chistabo derivative at internal printed p. 45 (physical PDF p. 49)
Last reviewed: 2026-09-12
Scope: Supports hard exclusion of Krittika, Moola, Punarvasu, Dhanishtha and the explicit primary borrower's Janma Nakshatra. The Drik website post-screen automates the same-Rasi Chandra-Kuja/Shani reject predicate under separately registered project conventions and does not blend that result into Surya Siddhanta or Vakya. The quick domestic/personal and business relationship phrases remain purpose-specific manual checks because the complete registered work supplies no operational formula. The passage supplies no event-specific weekday or Tithi list, but explicitly inherits general Tithi, Vara, Nakshatra and Tarabala purity; reusable baseline coverage remains incomplete under issue 284. This is debtor-side election guidance only; repayment capacity, borrowing cost, collateral, lender terms and professional advice take precedence.

Sources ​

election_chart.same_rasi_distributive_conjunction_policy_v1 ​

Evidence class: project_heuristic
Verification state: heuristic
Locator: same-rasi-distributive-conjunction-v1; source wording remains independently registered as muhurta.borrowing_money
Last reviewed: 2026-09-12
Scope: Represents the borrowing passage's Chandra conjunction with Mangala and Shani as the distributive formula R(Chandra)=R(Kuja) OR R(Chandra)=R(Shani), with same sidereal Rasi as the only association test and no numerical degree orb. The Python owner and TypeScript mirror implement the reusable three-valued primitive with shared fixture parity. This is an event-bounded selected mode, not a universal conjunction default; issue 271 wires it only into the Borrowing Drik post-screen.

Sources ​

  • No external source is registered for this claim.

election_chart.borrowing_same_rasi_conjunction_reject_policy_v1 ​

Evidence class: project_heuristic
Verification state: heuristic
Locator: borrowing-money.same-rasi-conjunction-reject-v1; source wording and same-Rasi computation remain separately registered
Last reviewed: 2026-09-12
Scope: Maps a known same-Rasi Chandra-Kuja or Chandra-Shani conjunction failure to the reject effect in the Borrowing Drik post-screen. Fail outranks unknown and pass across the sampled window; incomplete transition coverage fails closed to unknown. Surya Siddhanta and Vakya do not consume the Drik chart rule.

Sources ​

  • No external source is registered for this claim.

The complete machine-readable source registry is available in provenance.json. A regression fixture or same-code reproduction is not independent verification.

Reproduce and review ​

Run the linked tests, then the complete offline contract:

bash
python tools/verify_project.py

Public surfaces ​

  • python-library

Limitations ​

  • Conjunction means same Rasi only; it does not imply a degree orb or a global conjunction default.
  • Missing, malformed, duplicate, or conflicting chart facts resolve to unknown.
  • A sampled window passes only when every sample passes and transition coverage completes within the request budget.
  • The Borrowing event-specific assessor maps a fail to rejection, but its overall completion remains provisional while the reusable baseline under issue 284 is incomplete.

Implementation ​

This route is generated from computations.json. Edit the registry and canonical reference prose in the same pull request as a behavior change.