hypothesis-track

Hypothesis tracking involves appending evidence to open product hypotheses to validate or refute predictions. It analyzes observations in a structured manner and automatically proposes decisions when evidence crosses defined thresholds.

Use the /hypothesis-track command followed by the hypothesis ID to append evidence and propose decisions. This logs new observations into the chronicle system and automatically suggests validation or refutation based on threshold analysis.

Threshold analysis automatically recognizes when appended evidence crosses predefined limits for an open hypothesis. Once crossed, it triggers an automated decision proposal suggesting either refutation or validation of the original prediction.

Yes, a chronicle system is required for evidence and decision tracking. The hypothesis tracking process depends on interaction with this chronicle system to log observations and manage the resulting decision proposals effectively.

Use automated decision proposals after a feature ships and new evidence is collected. The system proposes a decision based on whether the prediction was met or a falsifier was triggered, ensuring structured evidence management for product strategy.

The primary limitation is the dependency on a chronicle system for tracking evidence and decisions. Without this external system interaction, the scripts cannot independently manage threshold analysis or generate automated decision proposals.