1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
//! Fresh application-owned restore safety; no installed provider or fence lifecycle effects.
use crate;
use Error;
/// Application-owned actual same-release source and irreversible-work safety qualification.
///
/// Providers qualify source authenticity/completeness/stable custody, actual
/// target-local load snapshot ID and complete metadata/data association to the
/// original source, current context/inventory/lifecycle, a fresh unique challenge and prior per-call
/// accounting. The no-irreversible-effects lane requires application knowledge
/// about restored intent and timers, never a generic standalone default. The
/// fenced lane requires continuous exact whole-selection custody outside the
/// rewindable source, original membership/external-obligation revisions and
/// qualified settlement/replay prevention. Before start, qualify source-specific
/// restored-state acceptance and isolated execution under the retained fence.
///
/// No provider is installed. This observes existing obligations, never acquires/
/// releases fences, signs/dispatches loads or starts, settles lost load replies,
/// refunds spending or releases source references. Failure, timeout, death or
/// dropping values retains original obligations. Terminal replay never invokes
/// this provider; fresh verification is a distinct operation.
/// Redacted provider failure; never changes original allowance or obligation custody.