ILLUSTRATIVE REMOTE AI HARDWARE LAB ACCEPTANCE RECORD BLANK SAMPLE TEMPLATE — NO REAL CUSTOMER TEST OR CERTIFICATION Project reference: [ID] Client legal entity: [Name] Workstation city and operator: [Actual city and assigned person] PC or Mac / asset serial number: [Device, ID] Client-owned or sold equipment: [Ownership per agreement] Development board and hardware revision: [Board, ID] IDE / SDK / firmware source revision: [Versions] Authorized remote engineer: [Approved account, not passwords] Session date, time and timezone: [Date/time] Power and environmental constraints: [Limits] Test objectives and acceptance criteria: [Written before testing] TEST LOG # Description / steps | Observation / evidence | Pass/Fail/Blocked 1 Identity verified and remote login completed | [Record] | [Status] 2 Toolchain loads / project builds | [Commit, hash] | [Status] 3 Approved firmware is flashed | [Device output] | [Status] 4 Serial/debug log matches expected behavior | [Log ID] | [Status] 5 Camera/photo shows the actual prototype reaction | [Evidence ID] | [Status] 6 Local operator performs any agreed reset/change safely | [Record] | [Status] 7 Issues, exclusions and next actions captured | [Issue list] | [Status] Client decision: [Approve milestone / Request change / Needs physical inspection] Responsibility for retest or next shipment: [Agreed] Evidence secure location and retention: [Project system] Client sign-off: [Name/date] Operator sign-off: [Name/date] BOUNDARY: Functional tests and video do not replace accredited lab tests, product certifications, independent safety inspections or import compliance. Only actual project results may be presented as customer case studies with permission.