Files
ClaudeandClaude Opus 5.5 ecfc010839
Independent Staging Quality Gate / validate-frontend (push) Successful in 5m0s
Independent Staging Quality Gate / validate-python (push) Successful in 6m31s
Independent Staging Quality Gate / publish (push) Successful in 2m53s
research(rect): reseal round8_r2d_rect_granularity_2026_11_11 after R2 option D and #184 (BUG-1835)
Owner-approved one-time reseal (2026-11-09). Same BUG-1809 protocol; new
tag only, older tags untouched. Sensitivity, not accuracy (BUG-1644).
- sealed 20: top-1 0.30->0.35, top-3 0.45->0.50, MAE 6.75->6.75, 6/20 changed
- offset 900: 78 runs changed in 3/20 cases; top-1 0.0100, coverage 0.8833 unchanged
- live v5 231: 30 runs changed (12 cases); best=truth 8->8
- comparability: offset not_reducible 0, 224 runs with consistent exclusion

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