Sources and evidence capture
Link App documents and preserve verified bytes before making a decision.
A review links source files from the current App. Upload the documents through the App or select existing App files. A review cannot use an arbitrary hidden storage location as though it were an authorized App source.
Select roles where offered
Some Apps ask you to assign a role to each selected document before generation. A role tells the App how to interpret that source in its domain. Choose it deliberately; the same document used in a different role can produce a different interpretation.
Role choices are bound to the source content and review revision. Changing the reviewed source basis clears obsolete choices. An uncertain generation retry preserves its original options rather than silently applying new role selections to the old request.
Capture every selected source
Capture creates a separate retained copy of the selected bytes and records a content hash, size, and read interval. Every selected source must be captured before approval. A current original that happens to have the same filename is not a substitute for a missing capture.
The retained copy remains independent of later original edits. Downloading evidence verifies those retained bytes against its receipt. If verification fails, Strive does not fall back to the mutable original.
HTML sources preserve their original markup as content. Captured evidence downloads as a safe attachment rather than allowing embedded content to act as application instructions.
Source changes require renewed review
Relinking or capturing changes the review basis and returns the review to pending. Inspect the new evidence before deciding again. Multiple sources are captured individually, so their capture intervals do not imply one atomic provider-wide snapshot.