Files
Jyotisha/docs/research
Jesse_ChenandClaude Opus 5.5 7cb332bce6 feat(narayana): Sanjay Rath profile replayed against the book tables; not wired (BUG-1215)
Round-4 ruling Q4. scripts/narayana_rath.py builds the Rath sequence from the
rule ledger and book rows ported verbatim from upstream yinduzhanxing c7117f92
(sanjay_rath_narayana_book_ledger JSON + md, chara_narayana_book_golden_cases):
Table 10 order (Saturn -> Table 11, Ketu -> reversed), years by
jaimini_odd_footed_dignity_v2 with jaimini_dual_lord_source_v1, ADs twelve
equal parts from the MD sign (Table 13 / 11 / 14), start sign by the existing
select_narayana_seed_sign, ties reported as parameter_sensitive with both
sequences.

Given the book's start sign, Tables 15 / 17 / 18 match 36/36 MD signs and
years. The start sign does not: Table 17 picks Virgo (book Pisces), Table 18
ties (book Cancer). Task red line 2: the profile stays out of every
user-visible surface and out of scoring; T5 trial not run. A test pins that no
script imports it.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N4f2nya58RoRu4yEmJgRGE
2026-10-03 16:36:31 +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