Files
Jyotisha/docs/research
ClaudeandClaude Opus 5.5 b6a6833ace fix(chart): stop /chart locking out with 「刚才打开得太勤」 after normal navigation (BUG-1530, BUG-1531)
- Reuse the loaded chart view and its layers from the module cache for
  5 minutes (same as the server engine cache): returning to /chart, the
  chat natal panel and the sidebar hover read make no request. Dropped on
  fingerprint change, invalidate, person/account switch and sign-out.
- Birth-sky data is remembered the same way (account + person + fingerprint).
- Layer reads get their own limiter bucket (chartViewLayer 60/min); base view
  stays 20/min, birth-sky 20/min. Throttled replies carry retryAfterSeconds
  and Retry-After.
- Throttled base view keeps the workspace skeleton, shows the line once with
  重试, and retries after the window; throttled layers retry after the window;
  throttled birth-sky keeps the entry pending and retries.
- Layer reads no longer run the heavy ascendant precheck; a late D1 refresh
  keeps ashtakavarga and points (BUG-1531).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DbBXoyeZrYn6ryNcSe5Y2Y
2026-11-03 18:04:41 +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