Architecture · Evidence package
Evidence packages a reviewer can verify
Regulators need evidence, not data dumps. Licensees must protect commercial and export-controlled information. The software is designed to export a scoped evidence package with a fingerprint for every record, so a reviewer can confirm that nothing has changed since it was issued.
In design, with licensees. It supports official submission routes and does not replace them.
- Owner / licensee
- EPC contractor
- Vendors
- Subcontractors
01
What the regulator sees
- Requirements and the evidence that meets them
- Inspection, test and hold-point results
- Nonconformances and how they were closed
- Document revisions in force
What stays private
- Prices, contracts and commercial terms
- Supplier relationships outside the licensing scope
- Proprietary design data not needed for the decision
- Export-controlled technology, unless authorised
02
Why hashes instead of copies
A hash is a short fingerprint of a record. Change one character and the fingerprint changes. It shows that a record has not changed since it was shared; it does not by itself prove that the record is correct, authorised or accepted. Those remain matters for the licensee's QA system and the regulator's review.
03 / Licence-holder layer
How does it work in practice?
How the layers are linked, checked and kept consistent is part of the licensed software and is explained to licence holders. Tell us about your project and we will walk you through it.
Ask us how it works04
Have a licence file, a supplier or a work package you are worried about?
Send a short description. We reply within two working days and sign your NDA before any document changes hands.