See a request reach its destination.

Descriptive transcript

A disclosure banner remains visible throughout: “Recorded technical demo • synthetic data • test destination.” This continuous browser recording contains no mocked responses or invented receipt. A banner was added above the captured interface; the demonstration was not sped up.

1. 00:00–00:09 — Describe the task. The hosted AICNCT page identifies itself as a demonstration using fictional details. The visitor enters: “I need a fictional conveyor drive VX-48. What is needed for a quotation?” and selects “Find approved information.”
2. 00:09–00:15 — Identify missing details. The interface presents clarification cards and a cited synthetic specification. The source explicitly describes fictional planning variants and does not establish product suitability or a price.
3. 00:15–00:25 — Change a meaningful constraint. The visitor supplies a fictional conveyor application, a quantity of 12 units and a test delivery requirement. They change the technical requirement from 24 V DC to 48 V DC, retaining a 60 rpm target. The name is “Fictional Demo Buyer” and the email is a reserved lab address.
4. 00:25–00:34 — Review before sending. The review card shows the exact request, including 48 V DC and 12 units. It states: “Nothing has been submitted.” The test checks that the receiving system has no record yet. The visitor presses “Confirm and continue.”
5. 00:34–00:43 — See the receiving-system reference. The interface reports delivery with reference lab_request_dbba0fa339c30d3aef5ef792. The signed lab receiver confirms that it stored one synthetic RFQ record with that reference.
6. 00:43–01:09 — Match the owner’s evidence. The actual owner dashboard shows the same receipt and labels the row “Test / demonstration.” The real customer counters remain at zero because this is synthetic activity. The dashboard explains that a request receipt proves delivery, not a booking or service approval.