Generate review proposals
Use captured sources, role choices, and receipts without confusing generation with approval.
An App can generate review proposals from captured sources using its configured domain interpretation. Start generation explicitly after checking the source set and any required document roles. Generation can consume a model budget, so recover an uncertain attempt before starting another.
What generation saves
The request binds the source review revision and its options. The result is published as saved pending proposals with a generation receipt. A generated proposal is not an approved fact, and generation never makes the human decision.
Some interpretations use several coordinated model requests. Strive validates the complete result before publishing proposals rather than presenting an incomplete batch as a finished result. Validation can request bounded corrective work for a completely received answer; this does not silently retry an uncertain provider call.
Read the receipt
Inspect the attempt's outcome, source revision, options, and available usage information. A proposal's receipt follows that proposal's immutable generation request, so a later attempt does not replace its original provenance.
Reopening a generated proposal reads the saved receipt. It does not need to call the model again. If receipt lookup fails, the proposal can remain readable while reload is offered; Strive does not borrow a different proposal's receipt to fill the gap.
Failure and uncertainty
A known failure can show an error. An unknown or interrupted attempt can retain its reserved budget while the outcome is unresolved. Read its receipt before starting another billable request. Replaying the same recorded request returns its saved outcome rather than spending again.
Changes to the source review or selected roles require a new deliberate intent. An old attempt cannot be repurposed silently with a different source basis.
Review the resulting values and cited evidence, then use the human decision controls.