Module verify

Expand description

Complete ERS sequence execution; historical acceptance is explicitly injected.

Structs§

Checked: Result for one original token; editing public facts cannot create a receipt.
Historical: Facts for historical validation, never a request to infer trust from genTime.
InputPlan: Original-bound schema preflight and exact chain-algorithm request mapping. A format-derived input can prepare its per-algorithm recipe once and reuse this SAME plan for execution, without reparsing timestamp information.
OrderFinding: One actual adjacent pair whose required chronological order is not proven.
Report: Complete, possibly negative sequence report, bound to this original record.
Selection: Actual certificate and effective key to use for this timestamp’s common check.
Verified: Closed complete record receipt. This incorporates the caller’s historical decisions; it does not choose application trust or claim CAdES conformance.

AlgorithmError: Algorithm inspection preserves unavailable capability separately from syntax and resource errors, including inside a temporary carried TSTInfo source.
Decision: Caller-established historical validation of the supplied actual participant.
OrderCause: Complete temporal comparison outcome; uncertainty is never positive order.
PlanError: Failed preflight retains the actual original source and carried source map.
VerificationError: Complete operation refusal; no successful partial sequence is returned.

Authorities: Caller selection; the ERS mechanism executes the check on the actual token.

order_evidence: Orders two actual authenticated TSA facts using RFC3161 §2.4.2’s SAME-TSA ordering rule or complete stated-accuracy intervals. This is shared by in-record ERS renewal and CAdES cross-proof preservation closure. A readable unsigned poeDate is never substituted for either authenticated generation.
token_algorithm: Resolves the actual carried imprint with the same source-mapped syntax preflight used by ERS. Unknown capability, malformed fields and resource refusal remain distinct; this does not establish timestamp mathematics.

VerificationResult: Complete record result with unchanged acquisition, provider, selector, recognizer, historical and profile causes; diagnostics allocate nothing.