Step 1: state the question, hypotheses and test
state_hypothesesDefine the test, data columns, H₀/H₁, α and alternative before seeing results to keep hypothesis tests pre-registered and avoid data-driven bias.
Instructions
Step 1 of a hypothesis test. Fix the test, the data selection and H₀/H₁ BEFORE looking at results. test_arguments are the same fields the test takes (e.g. t_test: {type, file, column, group_column, group1, group2, equal_variances, mu0}; anova: {file, column, group_column}; ab_test: {metric, file, variant_column, outcome_column, control, success_value, expected_split, segment_column}; chi_square: {type, file, row_column, col_column}; correlation: {file, x_column, y_column, method}). Only use columns the user asked about. The user confirms every column/group choice, the direction and α. Calling it again later revises the plan and restarts steps 2–6.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| h0 | No | Null hypothesis in plain words (a sensible default is proposed if omitted). | |
| h1 | No | ||
| test | Yes | ||
| alpha | No | ||
| confidence | No | ||
| alternative | No | Decide from the question, never from the data. | two-sided |
| test_arguments | Yes | Fields for the chosen test (file, columns, groups, type, method, ...). Not alpha/alternative. | |
| confirmation_token | No | Only after the user has confirmed the proposed choices: the confirmation_token from the previous response. |