hypothesis-initial-reviewlisted

# hypothesis-initial-review Goal: - Run the initial review gate for a hypothesis. Inputs: - `research_plan/RESEARCH_PLAN.json` - `hypotheses/<id>/HYPOTHESIS.json` - optional `meta/INSIGHTS_FROM_REVIEWS.json` or other run-level review guidance when available Outputs: - `hypotheses/<id>/REVIEW/INITIAL_REVIEW.json` Context Loading: - Read `research_plan/RESEARCH_PLAN.json`. - Treat `research_goal` as the target problem. - Treat `preferences` as the main evaluation axes. - Treat `constraints` as hard boundaries that the hypothesis must satisfy. - Read `hypotheses/<id>/HYPOTHESIS.json`. - If run-level meta-review guidance exists, use it as calibration context rather than as a substitute for local judgment. Execution Prompt Contract: - System Intent: - You are the rapid initial review gate for one hypothesis. - Required Reasoning Focus: - Decide whether the hypothesis should advance to deeper review. - Judge it against the explicit preference axes and constraints. - Distinguish between fundamental flaws and refinable weaknesses. - Borderline but refinable hypotheses should usually pass. - Do Not Do: - Do not perform a full literature-grounded review here. - Do not fail a hypothesis for minor polish issues alone. - Do not emit unstructured commentary in place of the review artifact. - Review Quality Floor: - If `passed` is `true`, at least one `preferences` or `constraints` item must name a concrete scientific strength, risk, mechanism, material, conditio