validate-hypothesis

Hypothesis Validator

Invokes hypothesis-tester agent to validate design assumptions.

Parameters

Extract these parameters from the user's input:

Parameter	Required	Default	Description
FEATURE_ID	Yes	-	Feature identifier whose hypotheses to validate (kebab-case)

Environment values (resolve via shell):

• RP1_ROOT: !rp1 agent-tools rp1-root-dir (extract data.root from JSON response)

Prerequisites

• {{$RP1_ROOT}}/work/features/{FEATURE_ID}/hypotheses.md MUST exist
• Generated by feature-design when high-risk assumptions identified

Execution

Step 1: Invoke Agent

{% dispatch_agent "rp1-dev:hypothesis-tester" %} FEATURE_ID: {FEATURE_ID} RP1_ROOT: {{$RP1_ROOT}} Validate all PENDING hypotheses for this feature. {% enddispatch_agent %}

Agent actions: load hypotheses.md -> parse PENDING -> validate via experiment/analysis/research -> document findings w/ evidence -> update status CONFIRMED|REJECTED -> cleanup temp artifacts -> report summary

Step 2: Handle Rejected Hypotheses

Parse agent output. If JSON block w/ type: "rejected_hypotheses":

{
  "type": "rejected_hypotheses",
  "hypotheses": [...],
  "hypotheses_path": "..."
}

For each rejected:

{% ask_user "{id} REJECTED: {statement}. Evidence: {evidence_summary}. Domain knowledge confirms valid?", options: "Accept rejection", "Override - I confirm valid" %}

If "Override":

1. Edit hypotheses.md:
   • Status: REJECTED -> CONFIRMED_BY_USER
   • Append: **User Override**: User confirmed validity based on domain knowledge.

If "Accept rejection": No change (status remains REJECTED)

Step 3: Report Result

Display validation summary. Note any user overrides.