harness-accept

An HTML acceptance demo renders acceptance criteria verification status and a ship, wait, or reject recommendation into a single self-contained file. It joins stored criteria by user_request_hash to produce a shareable, auditable decision document for stakeholders.

Threshold-based acceptance evaluation checks stored criteria from a Plan Brief, marks each as verified or unverified, and computes a final ship, wait, or reject recommendation. It provides evidence for non-engineers deciding whether to release a delivered task.

Yes, the acceptance review outputs a portable single-file HTML report requiring no dependencies. It summarises each criterion's verification status and the final decision, making it directly shareable with non-engineer stakeholders for audit purposes.

Acceptance criteria are read back from personal-preference.v1 storage and joined by user_request_hash. This retrieval feeds the HTML rendering so the demo accurately reflects the criteria originally defined in the Plan Brief.

A self-contained HTML acceptance demo provides an auditable decision document by displaying criteria verification status alongside a threshold-based ship, wait, or reject recommendation. It consolidates evidence into one portable file for release reviews.

Automated HTML acceptance reports are designed for non-engineer stakeholders reviewing pre-release tasks. They are not suited if acceptance criteria have not been stored in a Plan Brief beforehand, since the report depends on retrieving that data by user_request_hash.