Check records
Kind-typed rounds — lab dip, fit, inspection, test — recorded against whatever they judge. Round two knows about round one, so you read a history rather than a pile of forms.
In the APIChecks, dispositions, certificates and traceability, against any record in the project.
Kind-typed rounds — lab dip, fit, inspection, test — recorded against whatever they judge. Round two knows about round one, so you read a history rather than a pile of forms.
In the APIClose a check with a real decision: approve, use as is, rework or scrap. The disposition is a field with rules, not a comment someone has to interpret.
When the spec moves on after a check passed, the approval is flagged as stale rather than silently continuing to look valid.
Certifications carry an issue date and a semantic expiry, and the grid gives you an expiry facet. What lapses next quarter is a filter, not a calendar reminder.
A sample is the as-built instance of a design: the physical thing that exists, tied to the record it was built from and to the checks run against it.
Model lots that consume lots, then answer the recall question — every shipped lot affected by one bad batch — in a single call.
In the APITrack usage against a limit — hours, cycles, distance — and derive remaining life at read time rather than from a materialised number that drifts.
In the APISpin up a workspace and start building. It only takes a few minutes.