EARLY-ACCESS GUIDE · UPDATED 26 September 2026
Records, changes and exceptions
What a result will mean and how later changes will stay visible.
This guide describes the service scope. Access and the workflow supported for your site are confirmed during onboarding.
Keep the requirements used
The record will retain the source revision, configuration release, component requirements and evidence behind the result. Editing a catalogue later will not rewrite historical checks.
Make exceptions explicit
Operators will not silently substitute an unknown component. Approved alternatives and supervised exceptions will have defined permissions and recorded reasons. An exceptional result will remain distinguishable from verification.
Handle changes as changes
An updated source order will prompt review of existing work. Rework and reopened attempts will retain lineage to earlier records. A new check will not erase what happened previously.
Understand the first-release boundary
The initial service is planned for flat kits, one active station per kit and online acceptance. Recursive bills of materials, bulk RFID, weighing, computer vision, carrier labels and regulatory release are outside that scope.