Foundations
Verification
Verification proves integrity: that an artifact is authentic, unchanged, and attributable to a specific keypair. Verification is not a quality claim — it is cryptographic evidence.
What verification means in ETHORITY
“This published snapshot matches its signature under the declared public key.”
No endorsement. No implied safety. Only integrity and publication state.
Who it serves
Auditors
Establish that a specific trust artifact existed at a specific time and has not been modified since publication.
Example: a compliance report references the snapshot hash and signature for audit traceability.
Engineers & autonomous agents
Use verification as a precondition to automation. Accept only verified artifacts into pipelines.
Example: a CI job refuses to ingest an unsigned registry snapshot.
Operational boundary
Verification validates integrity. Lifecycle state and governance interpretation remain separate layers.
Do it yourself
You can independently verify an ETHORITY snapshot by downloading the JSON artifact, its signature, and the corresponding public key.