Files
Jyotisha/docs/research
ClaudeandClaude Opus 5.5 c1fa95c0c1
Independent Staging Quality Gate / validate-frontend (push) Successful in 5m2s
Independent Staging Quality Gate / validate-python (push) Successful in 5m43s
Independent Staging Quality Gate / publish (push) Successful in 2m41s
docs(research): annual real-case calibration audit and plan, with questions for the astrologer
All 25 public figures in references/real_case_calibration were replayed,
held out and opened, or annotated before, so they form the development set;
a new annual holdout needs new people. Records the plan (person-level split,
frozen method, windows generated without event dates, coverage and window-day
metrics, comparable random baselines) and the skill-repo questions for the
astrologer (attribution, template_cases marked external_verified, Tajika rule
review, exact-contact windows, case list).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DbBXoyn7Hj3LCW3BUs5bZ8
2026-11-06 15:23:17 +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