The problem. A receiving clerk has gloves on and an unplanned pallet in front of her. Recording it means stopping, walking to a terminal and typing. GlovesOn lets her do it by talking. The workflow. She names the material and the quantity. GlovesOn looks up the description, unit and bin itself, reads the receipt back (quantity, unit, material description, bin) and posts it only after an explicit "yes". A wrong receipt is corrected with a reversal document; both documents stay. The same receipt twice is refused by a duplicate guard in the gateway. Built on AssemblyAI. The Voice Agent API carries speech, conversation and voice. Tool calls return to the browser and pass through a scoped capability to our gateway, which speaks SAP's released OData APIs with the CSRF handshake a real S/4HANA requires. The write tool does not exist until a draft has been read back. Honest limits. Reads have been verified against SAP's S/4HANA Cloud sandbox; writes go to a mock S/4HANA that follows SAP's contract, and nothing has been posted to a real SAP system. The posting is made by a service user, not the individual worker. Calls, emails and notes are demo records. Noise robustness is not benchmarked. Every claim, the file it lives in and the test that holds it: docs/JUDGE-GUIDE.md in the repository.
Category tags: