research-hypothesis-reflectionlisted

# Research Hypothesis Reflection Reflect on structured research state without rewriting the input case or hiding adverse results. Contract identity: - `skill_id`: `research-hypothesis-reflection` - `skill_version`: `1.2.0` - ReflectionMemo schema: `1.1` ([references/reflection-memo-v1.1.schema.json](references/reflection-memo-v1.1.schema.json)) - Frozen predecessor: memo schema `1.0` from Skill `1.0.0`/`1.1.0` ([references/reflection-memo-v1.0.schema.json](references/reflection-memo-v1.0.schema.json)); documents written under it keep validating unchanged. ## Run Use Python 3 and the standard library: ```bash python3 scripts/reflect.py \ --case /path/to/research-case.json \ --output-dir /path/to/reflections \ --write-updated-case ``` The command creates `CASE--reflection-vNNN.json` and, when requested, `CASE--case-after-reflection-vNNN.json`. It selects the next unused revision and refuses to overwrite either the input or an existing output. ## Workflow 1. Validate the required ResearchCase v1 structure. 2. Link feedback and experiments through hypothesis, evidence, and experiment IDs. 3. Detect support/challenge conflicts, negative/null/invalid outcomes, missing or unusable evidence, non-independent positive support, and repeated no-information outcomes. 4. Select an action with deterministic priority: conflict → `human_review`; invalid method → `rollback`; exhausted evidence → `stop_unresolved`; negative/dependent/stalled evidence → `reroute`; otherwise → `con