Promote Raman dasha boundary oracle seed

docs/research/ACTIVE_FRONTS.md

@@ -38,6 +38,7 @@ This file is the small index for the current engineering fronts that still drive
 - `/Users/wuyongnaren/Documents/印度占星/docs/research/oracle_closure_master_dashboard_latest.md`
 - `/Users/wuyongnaren/Documents/印度占星/docs/research/public_benchmark_dashboard_latest.md`
 - `/Users/wuyongnaren/Documents/印度占星/docs/research/shadbala_absolute_oracle_comparison_audit_2026_06_28.md`
+- `/Users/wuyongnaren/Documents/印度占星/docs/research/raman_dasha_boundary_series_oracle_seed_2026_06_28.md`
 - `/Users/wuyongnaren/Documents/印度占星/scripts/shadbala_oracle_comparison.py`
 - `/Users/wuyongnaren/Documents/印度占星/references/oracle/`
 - Before changing oracle-dependent adjudicator or benchmark claims, run:

docs/research/raman_dasha_boundary_series_oracle_seed_2026_06_28.md

@@ -0,0 +1,43 @@
+# Raman Dasha Boundary Series Oracle Seed - 2026-06-28
+
+## Scope
+
+This pass converts the untracked `test_dasha_raman_truth.py` placeholder idea into a formal external-oracle seed.
+
+## Source Value Recovered
+
+The useful fragment was not the mocked `xfail` test. The valuable part was the B.V. Raman Vimshottari Mahadasha boundary series:
+
+- Mars: `1912-08-08`
+- Rahu: `1918-09-21`
+- Jupiter: `1936-09-21`
+- Saturn: `1952-09-21`
+- Mercury: `1971-09-21`
+- Ketu: `1988-09-21`
+
+## Promoted Asset
+
+Added a new template row:
+
+- `template_bv_raman_vimshottari_boundary_series`
+- file: `/Users/wuyongnaren/Documents/印度占星/references/oracle/dasha_shadbala_oracle_cases.json`
+
+The oracle queue now recognizes:
+
+- `target.vimshottari_mahadasa_boundaries`
+- target module: `dasha`
+
+## Boundary
+
+- Status remains `template_only`.
+- It is not production calibration evidence.
+- It does not prove local Raman ayanamsa or Vimshottari year-length alignment.
+- It must not replace an external source artifact or screenshot.
+
+## Why Not Keep The Old Test
+
+The untracked `tests/test_dasha_raman_truth.py` used mocked calculation and ended with `pytest.xfail`. Keeping that test would create a false sense of executable coverage. The oracle seed is more honest: it preserves the reference value while keeping calibration blocked until metadata and external capture are complete.
+
+## Regression Coverage
+
+- `/Users/wuyongnaren/Documents/印度占星/tests/test_oracle_collection_queue.py`

docs/research/worktree_fragment_triage_2026_06_28.md

@@ -53,7 +53,8 @@ Only promote this report later if a stable human-facing archive is needed.
 
 - `/Users/wuyongnaren/Documents/印度占星/tests/test_dasha_raman_truth.py`
   - Current state: `pytest.xfail` placeholder with mocked computation.
-  - Better path: convert B.V. Raman Dasha boundaries into an external oracle packet or executable comparison after local Raman ayanamsa support is explicit.
+  - Disposition: useful boundary values were promoted into `/Users/wuyongnaren/Documents/印度占星/references/oracle/dasha_shadbala_oracle_cases.json` as `template_bv_raman_vimshottari_boundary_series`.
+  - Follow-up: collect source artifact metadata before promoting beyond `template_only`.
 - `/Users/wuyongnaren/Documents/印度占星/tests/test_yoga_benchmark_cases.py`
   - Current state: smoke-style test ending in `assert True`.
   - Better path: replace with concrete yoga names and expected detections before promotion.
@@ -73,4 +74,3 @@ Only promote this report later if a stable human-facing archive is needed.
 - `/Users/wuyongnaren/Documents/印度占星/references/oracle/artifacts/pyjhora_oracle_artifact_manifest.json`
 
 Current diff only changes `generated_at`. Do not commit timestamp-only churn unless the artifact inventory materially changes.
-