Files
Jyotisha/docs/research
ClaudeandClaude Opus 5.5 676b7d47cd fix: parity3 product-side defects and upstream lag (Vimsopaka, Narayana ages, asc precision, labels, Sade Sati)
Three-way parity audit 2026-11-07 (U ea2a9d65 / F frozen / P f70ae94e):
- Vimsopaka: look vargas up by "D{n}_" prefix (D60 key was misspelt, every
  D60 fell to Neutral) and score only the sign-owner relation (upstream
  ab5b8709, BPHS 7.21-27). All 16 varga scores now equal U on 3 charts.
- Narayana: age = total_seconds / (86400 x 365.25) keeping the birth time
  (upstream ab5b8709); Rath rows carry start_date / end_date from the
  unrounded ages; consult layer, report facts, API and calendar read them.
- Ascendant degree_raw / lon unrounded (engine and chart API).
- position_mode label: legacy is the apparent frame since BUG-1275; the
  profile and module labels now say "apparent" (legacy still accepted).
- Functional profile label v2 -> v3_166q4 (the table actually used).
- full-reading Sade Sati uses the dated transit Saturn (upstream e628118d):
  Jobs 2026-11-07 peak, owner / Obama not active, as U.
Consult evidence card golden recaptured.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DbBXoyn7Hj3LCW3BUs5bZ8
2026-11-07 19:01:10 +08:00
..

Research Workspace

This directory stores research notes, audits, benchmark packets, and active adjudicator iteration records for the Jyotish project.

Layout

  • active/
    • reserved for current working research fronts that directly support the next implementation cycle
  • archive/
    • historical round notes, sidecar work orders, and local draft research that should not clutter normal implementation work
  • top-level docs/research/*.md
    • current canonical research notes that are still referenced by active engineering work

What Stays Top-Level

Keep a research file at the top level only if at least one of the following is true:

  • it is referenced by an active implementation spec
  • it is referenced by tests, workflow docs, or benchmark dashboards
  • it captures a currently active adjudicator audit or closure board

What Moves To Archive

Move a research file into archive/ when:

  • it is a completed round log or sidecar work order
  • it is a local exploration draft with no active code dependency
  • it is superseded by a newer audit, dashboard, or implementation note

Current Working Rule

When adding new research notes:

  1. put active, decision-driving notes at the top level
  2. move noisy round-by-round drafts into archive/
  3. avoid storing transient terminal captures or scratch outputs here