Why certificate amendments should preserve immutable history
Why electrical certificate corrections are clearer when a new current version is created without rewriting the record that was originally issued.
Issued records should not behave like drafts
Before issue, editing a draft is expected. After issue, silently changing the same record makes it difficult to prove what information existed at the time the document was supplied.
A stronger model treats the issued version as a historical event and creates a new version when a legitimate correction or amendment is required.
A useful amendment trail answers four questions
Someone reviewing an amended certificate should be able to see what the current version is and understand the path that led to it.
- Which version is current?
- Who recorded the amendment?
- When was the new version issued?
- Why was the record changed?
Hash linkage can strengthen integrity checks
A cryptographic fingerprint can be calculated from a stored snapshot. If each later version also records the previous version's fingerprint, the sequence can be checked for unexpected changes or broken links.
That integrity check does not replace professional judgement and it does not determine whether a certificate remains valid for current use. Lifecycle state and cryptographic integrity are separate concepts.
Void records still need history
Voiding a certificate should make the current-use status unmistakable, but the preserved historical record can still be valuable for audit and traceability. Deleting the evidence would remove the very history needed to explain what happened.
Public verification should reveal only what is needed
A public verifier can confirm reference, lifecycle state, version and integrity without exposing client addresses, inspection results or other private workspace data. Verification features should be deliberately data-minimised.