Saved versions and local changes

A saved revision preserves what you selected

Reusable content helps you prepare several applications from the same experience. An automatic update across every résumé could also change wording you already reviewed.

River avoids that surprise by saving exact revisions. A draft keeps the library content and evidence revisions it selected until you choose an update.

Suppose you revise a project bullet for one application. An earlier draft can still retain the original bullet and its original evidence links.

A stale warning exposes a difference between a saved reference and a changed record. The warning calls for comparison rather than an automatic replacement.

Local changes belong to one résumé

A local wording change tailors a Content item for one placement. A local composition change adjusts a placed block or section.

Neither change automatically rewrites the reusable library. Promotion saves a reusable revision, while a fork creates a separate reusable identity.

This distinction supports both kinds of work: a change for one employer and an improvement worth keeping for future applications.

Checkpoints preserve a reviewable document

A draft is the working composition. A checkpoint captures an exact saved draft and its supporting information.

The checkpoint can exist before rendering, evidence review, or export completes. Those outcomes are separate from the saved composition.

Once you export a checkpoint, its files and original review remain in history. Later edits cannot silently change the document associated with that export.

A branch provides a new draft from saved content. Restoring through a branch lets you continue an earlier version while retaining the original work.

Changed inputs require another decision

A review is meaningful only for the material the reviewer saw. AI proposals therefore record their input revisions and target.

If a relevant input changes, applying the old proposal could introduce wording that no longer matches its support. River requires a new reviewed proposal.

Export acknowledgments follow the same principle. If the applicable evidence issues change before export authorization, the updated issue set needs review.

Document-source refinement produces a separate checkpoint. A return to structured editing regenerates source from the structured base, so source-only changes can be excluded.

Archival changes visibility

Archival removes an item from active lists and new-content pickers. Existing placements, checkpoints, and history retain their saved references.

Archiving a library section does not archive its blocks or content. Restoration makes the item available again without rewriting its earlier revisions.

Archived evidence can still appear as an issue in an export review. Library organization and evidence review are separate decisions.

Related guides

Edit a résumé covers local wording and library updates.

Compare and restore versions covers checkpoints and branches.

Export a résumé covers review and downloads.