| name | amaa-hypothesis-verification-ops |
| description | Use when applying multiplicity rule or formatting experiment outputs. Trigger with verification ops request. Loaded by ai-maestro-architect-agent-main-agent |
| context | fork |
| user-invocable | false |
| agent | ai-maestro-architect-agent-main-agent |
Hypothesis Verification Operations
Overview
Operational references for hypothesis verification: the multiplicity rule for testing 3+ approaches, report templates, and quick-reference classifications.
Prerequisites
- Familiarity with the core hypothesis verification workflow
Instructions
- Apply the Multiplicity Rule: generate 3+ candidate approaches
- Use output templates to document experiment results
- Classify findings using status codes from quick reference
- Archive prototypes only when code is essential to explain findings
Checklist
Copy this checklist and track your progress:
Reference Documents
| Document | Content |
|---|
| multiplicity-rule.md | The Multiplicity Process, Example: Implementing a Paper Algorithm, Iterative Selection Workflow |
| output-templates.md | Experiment Directory Structure, Experimentation Report Template, Hypothesis, Candidates Tested, Experimental Setup, Results, Evidence-Based Conclusions |
| quick-reference.md | Status Classifications, Implementation vs Experimental Code, Workflow Integration Points, IRON RULES Summary, Examples |
Examples
Example: Test 3+ Redis configurations in Docker, measure latency, select winner by evidence, document in REPORT.md
Error Handling
| Issue | Fix |
|---|
| Too few candidates | Add approaches until 3+ exist |
| Inconclusive results | Increase sample size or iterations |
Output
| Type | Description |
|---|
| Experimentation Report | experiments/<claim>/REPORT.md with template |
| Prototype Archive | docs_dev/experiments/<claim>/prototypes/ if needed |
Resources
See Reference Documents table above.
