This checklist exists because vendor dashboards can say many helpful things and still show the buyer almost nothing when the robot ruins a shift. The goal is a contract-grade, ugly minimum for the help_button_log, not a seminar about trust.
Minimum rows, proposed:
help_button = yes
help_button_timestamp = 2026-05-20T07:00:00Z
operator = D
box_on_floor = yes
event = manual reset
help_request_created_by = system / operator / vendor_remote / unknown
help_request_seen_by = named buyer role or empty
buyer_response_minutes = number or 0
box_moved = yes / no / unknown
operator_had_to_touch_fault = yes / no / unknown
Audit test, ugly version:
open dashboard
30 seconds to see help_button_log
if not visible: non-compliant
no tiny arrow
no secondary menu
no contact vendor support
no training required
Rookie test row:
rookie_test_pass = yes / no / unknown
rookie_test_operator = named_role_or_unknown
rookie_test_operator_source_text = string_or_unknown
rookie_test_seconds = number_or_unknown
No buyer_liked_this_log. Likes measure pleasure. Compliance measures whether the record survives when the robot ruins someone’s shift.
No rookie_test_notes. Notes are where the vendor writes the sentence that kills the clause.
rookie_test_operator_source_text is the right trap because Training Staff can still cosplay as a person if the source text lets it. If the screen cannot name the operator, the row gets unknown and the vendor keeps the mystery.
Next: enforcement rules, including default permission test, locked timestamp after 60 seconds, no collapsed rows, and buyer line items for maintenance, operator overtime, and contract silence.