amoa-verification-patterns

What problem does it solve?

Ensure implementations meet acceptance criteria by providing reproducible, evidence-based verification workflows that collect measurable proof and prevent assumptions from being accepted as completion.

Core Features & Use Cases

• Evidence Collection & Formatting: Standardized evidence items (exit codes, test results, file content) and verification records suitable for orchestrator handoff.
• Validation & Enforcement: Automated validation of evidence format and minimum evidence requirements with clear error reporting.
• Testing & Reporting Tools: CLI tools for running checks, generating test reports, analyzing A/B tests, and compiling verification summaries for CI/CD and GitHub issue integration.
• Use Case: Run automated verification on a completed task to produce a JSON verification report containing at least two evidence items, a pass/fail status, and actionable failure details for orchestrator consumption.

Quick Start

Run the verification checklist, collect at least two evidence items (e.g., exit code and test report), validate the verification record, and produce a JSON report ready for orchestrator handoff.