River Logiceode docs

Versions and history

See every revision of a model and every event on it, compare a revision with the one before it, and revert to an earlier one.

Needs a model open

Where: Overview→Versions

Every change to a model's structure or data writes a new revision. Three places read them back: Versions lists the revisions with a field-by-field diff and a revert, Change history tells the same story as a timeline with what each change did to your goal, and the Audit log records every event on the model, including the ones that don't make a revision.

Open version history

Click Versions in the model home header, or the history icon (Version history) on a Model Library row. The Version history drawer opens on the right, headed with the model's name and its head revision. Click outside it or ✕ to close.

Revisions are listed newest first. Each row shows:

  • who made it (a person, RIA, or the system), rev 0004, and their name;
  • a Head chip on the current revision;
  • a kind chip (below);
  • the change's summary and chips for what moved: +N icons, −N icons, +N links, −N links, KPIs changed, Topology changed;
  • the date and time.
Kind chipThe revision
StructureChanged what the model is.
DataChanged the model's data, for example a base-model edit.
KPIsChanged the KPIs.
ValidationsChanged validation rules.
NewsChanged the market factors.
MetadataChanged details.
MigrationAn upgrade by eode.

Renames, permission changes, locks and promotions aren't listed here; they're in the Audit log. A new model reads "No versions yet — the first mutation will snapshot rev-0001."

Compare a revision with the one before

Click Diff vs rNN on a row. A Field / From / To table opens under it, listing each value that changed against the parent revision (Loading diff… first). When nothing moved it says "The Model Design changed at this revision; no structural field moved." or "No field-level changes (snapshot identical to parent)."

Revert to an earlier revision

Model owner or Org Admin
  1. In Version history, click Revert on any revision that isn't the head.
  2. A Plan confirm card opens at the top of the drawer: Revert to rev 0003, "Restores the snapshot from …" with its date and summary, and "A pre-revert checkpoint is taken first, so the revert itself is reversible."
  3. Click Run revert (Running…), or Cancel.

eode saves a checkpoint of the current head, restores the older revision's structure as a new revision on top, updates the Base scenario's result to match, and records the revert in the audit log. The owner, organization, tier and permissions are never restored.

  • On a locked model, Revert is disabled ("Unlock the model first") and the footer reads "Unlock the model to revert." See Share and govern.
  • Anyone else reads "Owners and org admins can revert. You can view + diff."

You can also revert from Change history.

Follow the change history

Where: Overview→See history →

Once a model has two or more revisions, model home shows a line above the steps: N changes · +$X since the first build, with a small chart and See history →. It opens Change history. You can also ask RIA to take you there.

The header totals the changes and how far your goal moved in objective since the first build. Filter the timeline with All, Structural or Data. Renames, permission changes, locks and tier moves aren't on the timeline.

Each revision is a row with a plain headline:

HeadlineThe change
Reverted to revision NA revert.
New capability: … / Removed … / Added …A capability came in or went out.
Made a scenario permanentA what-if was built into the model.
Brought in your real dataYour data replaced sample data.
Changed what the model optimizes forA new goal.
The change's own summary, or Structure change, Data, KPIs, Market factors, Validation rules, MigrationAnything else.

Beside the headline: the goal's value and how much it moved (objective $X), a current chip on the head, rev N · who · when and where it came from (from the independent review, you asked for it, from a what-if you kept, your data, a gap in your brief), and a certification chip: a confidence percentage, certified, or the verdict, with passed/total when checks fall short, or —.

Click a row to see its detail: rev N ← rev P, then Why (the request or quote it came from) and What moved (the goal after the change, capabilities added or removed, KPIs changed, or "No solve-affecting change (details/governance).").

Show field-level diff lists the names of the fields that changed against the parent, without values. For the values, use Diff vs rNN in Version history.

Undo a change from the timeline

Owner or contributor
  1. Select a revision that isn't the head.
  2. Under Undo, click Revert to this revision.
  3. Confirm Restore rev N? with Revert, or Cancel.

It's the same revert as in Version history. The timeline reloads with the revert on top. If someone else holds the model's lock, or you don't have edit access, the confirm closes and nothing changes.

Before anything has changed, the screen reads No changes recorded yet — "Every structural change to this model is tracked here as a revision — with what it did to the objective and its certification. Make a change from Develop and it appears on this timeline." — with Back to the model.

The console on this screen answers questions about the timeline: "Ask what changed, or why a number moved…"

Read the audit log

Where: Overview→Audit log

Click Audit log in the model home header, Full audit log → under Recent activity, or the Audit log icon on a Library row. The drawer lists every event on the model as a sentence, newest first, with N events in its header.

Filter by family (All, Locks, Promotions, Authoring, Scenarios, Data, Workflows + runs, Permissions) and by person (All actors). Reverts and backlog events (applied, set aside, reopened, change requests) show only under All.

FamilyExample sentences
Locks and promotion"… locked “…”: reason", "… took over the lock on …", "… unlocked …", "… force-released the lock on …", "… promoted … to …", "… demoted … to …"
Changes"… reverted … to rev N", "… edited … (fields)", "… authored …", "… re-authored … from chat", "… applied a change to …: title"
Scenarios and backlog"… added a what-if to …", "… set aside a suggestion on …", "… reopened a suggestion on …", "… queued a what-if to make permanent on …", "… added a change request to …"
Data"… updated data integration on …", "… downloaded the Excel template for …"
Permissions"… granted role on … to …", "… revoked …"

Each row also shows the date and the revision, and a robot mark when RIA or an agent did it. The log is append-only: removing old revisions never removes events.

Limits

  • Diff vs rNN shows 25 fields; longer values are cut at 80 characters.
  • Show field-level diff lists the first 25 field names.
  • The audit log shows the newest 300 events.
  • A revert never restores owner, organization, tier or permissions.

On this page