pub struct VerifyReport {
pub proof_id: Option<String>,
pub cryptographic_validity: Validity,
pub evidence_validity: Validity,
pub policy_decision: PolicyDecision,
pub lifecycle_checked: bool,
pub lifecycle: Vec<LifecycleRecord>,
pub status_objects: Vec<String>,
pub checks: Vec<CheckRecord>,
}Expand description
Full verification output.
Fields§
§proof_id: Option<String>Recomputed proof id, or None when the envelope never parsed.
cryptographic_validity: Validity“Is the cryptographic material internally valid?”
evidence_validity: Validity“Is the evidence consistent, connected, and timely?” — timeliness and
revocation are stages TIME/REVOCATION (Phase 6): Expired/Revoked/
Unknown flip this to Invalid; Superseded keeps it Valid with a
historical note.
policy_decision: PolicyDecision“Does the evidence satisfy the requested policy?” The pipeline never
evaluates policy itself; it reports Indeterminate and the caller runs
proof-policy::evaluate_policy on the verified state.
lifecycle_checked: boolTrue once stages TIME+REVOCATION ran (Phase 6). Early exits (parse/ schema/canonical failures) leave it false.
lifecycle: Vec<LifecycleRecord>Per-attestation lifecycle status, one entry per signature-verified statement attestation.
status_objects: Vec<String>Ids of signature-verified embedded status attestations (revoke/ supersede claims), in proof order. Caller-supplied status objects are not proof members and never appear here. Consumers (e.g. policy state projection) must never treat a status attestation as a statement.
checks: Vec<CheckRecord>Implementations§
Source§impl VerifyReport
impl VerifyReport
Sourcepub fn failure_codes(&self) -> Vec<ErrorCode>
pub fn failure_codes(&self) -> Vec<ErrorCode>
All failure codes in stage order (convenience for tests and CLI).