Files
Jyotisha/docs/research
Jesse 8fb6b65b01 wip: local BUG-139/BUG-140 fixes before syncing origin/main
- pre_work_check.py: prefer repo .venv Python >=3.11, strict JYOTISH_PRE_WORK_PYTHON override, fail closed
- tests/test_pre_work_check.py: regression coverage for venv preference / system 3.9 / strict override
- globals.css: transient :active pressed feedback for entrypoint cards, hover only under (hover: hover)
- consultation-entrypoint.test.ts: sticky-hover regression test
- BUG_HISTORY.md: BUG-139 / BUG-140 records
- pre_work_error_ledger.md: ERR-078 resolved entry
2026-08-10 17:57:06 +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