At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Supported CAD file | Match extension and MIME type | Accepted format identity | Unsupported pairs are rejected |
| CAD bytes | Calculate SHA-256 | Immutable file revision | No native CAD semantic parsing |
| Upload metadata | Record source and retention | Governed artifact provenance | Metadata fields are bounded |
| Declared relationship | Normalize it as a candidate link | Review-only trace evidence | Candidate links do not count as governed evidence |
How it works
- Open Upload controlled evidence.
- Select a supported CAD file.
- Add approved retention settings.
- Add declared links only when their targets are known.
- Select Upload evidence.
- Review the metadata-only status and candidate-link count.
Example
A STEP file is uploaded for a controlled design record. The app records its SHA-256 value, byte length, format, provenance, retention, and one declared candidate link to a requirement. Engineering review still occurs in the CAD and quality systems.
What this does not mean
Compliance Glossary does not open native CAD models, inspect geometry, compare assemblies, validate tolerances, or infer design meaning. CAD links remain candidates until governed elsewhere.
Related questions
Next step
Use CAD upload only when metadata-level evidence meets the control need.
View on Atlassian Marketplace