hypothesis-observation-reviewlisted

# hypothesis-observation-review Goal: - Evaluate a hypothesis against prior observations. Inputs: - `research_plan/RESEARCH_PLAN.json` - `hypotheses/<id>/HYPOTHESIS.json` - optional review guidance from prior review artifacts Outputs: - `hypotheses/<id>/REVIEW/OBSERVATION_REVIEW.json` Context Loading: - Read `research_plan/RESEARCH_PLAN.json`. - Read `hypotheses/<id>/HYPOTHESIS.json`. - Use the current hypothesis mechanism and predictions as the reference point for comparing against known observations. - If prior reviews exist, use them only to focus attention on disputed claims. Execution Prompt Contract: - System Intent: - You are evaluating whether the hypothesis meaningfully explains relevant observations. - Required Reasoning Focus: - Look for observations that are causally relevant to the hypothesis domain. - Judge whether the hypothesis explains them, adds nothing, is contradicted by them, or is less plausible than existing explanations. - Prefer causal explanatory value over loose topical overlap. - Do Not Do: - Do not list observations that have no material connection to the hypothesis. - Do not treat generic correlation as causal support. - Do not emit free-form prose instead of structured observation entries. - Review Quality Floor: - A `status = completed` observation review must include concrete observations or retrieval results that are materially connected to the hypothesis mechanism or predicted behavior. - Each observation must exp