Receipt
Who accepted the handoff, when it was accepted, and which warning or limitation was included. It keeps the next review step clear without turning an estimate, candidate, or coverage limit into an unsafe cleanup decision.
Request Evidence Control docs
Build and review a JSM evidence pack.
Use Request Evidence Control when a JSM request needs a durable handoff: what was reviewed, what evidence was used, what could not be verified, and what was accepted.
ReceiptManifestSource statusCaveats preserved
Evidence-pack contents
A review-ready pack keeps the record understandable after the ticket is closed.
Manifest
Pack metadata, export identifiers, checksum metadata, generated timestamps, and delivery status. It keeps the next review step clear without turning an estimate, candidate, or coverage limit into an unsafe cleanup decision.
Source status
Which source records were included, unavailable, outside scope, or carried forward for review. It keeps the next review step clear without turning an estimate, candidate, or coverage limit into an unsafe cleanup decision.
Caveats
Warnings and limitations remain visible so the reviewer does not overstate what was proven. It keeps the next review step clear without turning an estimate, candidate, or coverage limit into an unsafe cleanup decision.
Recommended workflow
Open the JSM request, review evidence coverage, resolve or acknowledge blockers, build the pack, then export or deliver the review record with preserved caveats.
Limitations
If historical group membership or another source is not available from collected records, keep that limitation in the handoff. The app should not turn missing evidence into a positive proof claim.
Related pages
Continue to the product page, security statement, or support page for Marketplace evaluation.