River Logiceode docs

RIA's proposals

Make, apply, approve or set aside what RIA proposes in a conversation: what-ifs, model edits, change orders and workspace layouts.

Needs a model openOwner or contributor

Where: A model's conversation→a proposal card above the message box

When RIA, eode's assistant, suggests a change in a conversation, it doesn't make it. It puts a card between the conversation and the message box, and nothing happens until you click the card's button. One card shows at a time, and the message box waits until you decide it.

Decide one proposal at a time

Cards come in this order: model edits and workspace layouts, then what-ifs, then change orders, each kind newest first. When more are waiting, a pager above the card reads Proposal <i> of <n>; the arrows (Previous proposal, Next proposal) move between them without deciding any. When you decide or hide one, the next takes its place.

A card belongs to the conversation RIA made it in. It shows only while that conversation is open, and only for the model in view or the workspace on screen. A page with no model open shows none. If you can only read the conversation, its cards don't show.

Every card has an X in its corner (Hide this card). On a what-if, a model edit or a layout it drops the proposal, the same as No or Discard. On a change order it only hides the card: the change order stays on the model's backlog.

Undecided model-edit and layout cards live in the page. Reload and they're gone; ask RIA again. An undecided what-if card comes back when you reopen the conversation it was made in, and change orders are kept on the backlog.

Answer a card before you type

Some cards wait on you: an objective RIA proposes (Your objective), figures RIA asks you for (Your figures), and any proposal on this page. While one waits, the message box is off, and a line above it reads "The card above comes first: answer it or dismiss it, then send your message." ("2 cards above come first: answer or dismiss each, then send your message." when two wait). Show the card takes you to it; with two, a second click takes you to the next.

Answer the card on the card itself:

  • Your objective: Accept this objective, or type what you'd rather have in its box and click Reply.
  • Your figures: fill in the cells and click Done.
  • A proposal: its own buttons, below.

Or click Dismiss on an objective or figures card to close it without answering. It then reads Closed without an answer, and the message box is free again. A dismissed objective stays open on the model's record: ask RIA to propose it again when you're ready. Dismissed figures stay asked for on the record too.

You can still add a file while a card waits; it goes with your next message. Go to the chat on the model's record takes you to the waiting card, which says "This card comes first: answer it or dismiss it, then send your message."

Let RIA carry on after you decide

When you click Apply or Discard on a model edit, Approve or Discard on a workspace layout, or Apply, Set aside or Dismiss on a change order, RIA takes one more turn without being asked and carries on with what it said would follow. If RIA said it would propose a second change once you'd dealt with the first, the second card comes up on its own. RIA takes one turn per card; anything after that waits for your next message.

Run a proposed what-if

When you describe a change, RIA proposes it as a what-if. The card asks Would you like me to open a separate conversation for this what-if? and shows:

  • the what-if's name and RIA's reason
  • WHAT CHANGES: one row per change, with the value it sets, such as Croissant: price per unit → $4.80. Details shows the same changes as the model names them. When RIA proposes no exact change, the row quotes your request with The scenario conversation works out the changes from this request.
  • Compared against Base at $<n>.: the number the result will be judged against. There are no before-and-after numbers until it runs.

Click Yes, open it (Opening conversation…). eode opens a new conversation for the what-if with your request as its first message, and the card reads Opened a conversation for “<name>”. Tell RIA “Looks right” there when you are ready to build and solve it. As the card's note says, A solve starts after Looks right. No, or the X, drops the proposal and makes nothing. Working the what-if out and running it is on Run a what-if.

Apply a model edit

A model edit changes the model itself. The card is tagged model edit and shows its proof before you decide:

RowShows
Base cost or Base objectiveThe Base number today, or not solved yet
ProposedThe number with the change, its signed difference and the percentage
feasible / infeasibleWhether the changed model still has an answer
validation passedThe edit passed the model's checks
What changes (<n>)Open it for each change, from → to

Apply rebuilds the model with the change and saves a new version: Applied as version <n>. Revert any time from the model's version history. See Versions and history. Discard drops it.

If the edit didn't pass, the card reads That change needs a tweak first instead, with What was proposed (<n>), what went wrong with each change, and try this with a way round it. Dismiss closes it.

Work a change order

A change order is a change RIA files on the model's backlog, the list every structural change goes through, instead of making it there and then. It arrives as one line: Change filed: <title> with Open ⌄. Click it to open the card: the title, the group it belongs to, RIA's detail (or You asked: “…” with your request), and your words quoted.

  1. Click Preview. eode runs a trial solve and shows What this does (proven on a trial solve) with the Base and proposed numbers, infeasible, or doesn't move the plan's result.
  2. Click Apply. It appears only after a successful preview. The card reads Applied as version <n>. Revert any time from the model's version history. A larger change rebuilds the model, which will pause at its Model Design first for your sign-off.
  3. Or click Set aside, type why (Why set this aside? (e.g. this doesn't apply to us)), and click Set aside with this reason. Cancel backs out.
  4. Or click Dismiss to decline it without a reason. RIA won't propose it again.

Have RIA prewrite a reply has RIA write the reply you'd send about this proposal and puts it in the message box for you to edit and send. If RIA writes nothing, the card says RIA didn't write a reply this time. Try again, or write your own below.

Away from the model's own page (on a workspace, for example), Open on the model page opens the model's page with this card at the front of its proposals.

Some models can't preview a change order:

  • With no Model Design, the card says This model has no Model Design to change, so this can't be previewed.
  • Where eode wrote the model's design from your description, it says This model's design was written from your description, so this can't be previewed on it. Add it to your description and the model is built again with it.

On a model you built from a description, Add to my description sends the change to RIA as your message, to add to your description; the card then reads Sent to RIA to add to your description.

When a change order can't go through, the card says why and what to do:

The card saysDo
This change is no longer on the model's backlog. Open the model page to see what is.Open the model page.
This is a what-if, so it runs as a scenario instead of changing the model. Open it on the model page to run it.Ask RIA for it as a what-if; see Run a what-if.
This one needs to be described as a specific change before it can be previewed. Open it on the model page to work on it.Tell RIA the exact change in the model's conversation.
The tool can't build this capability yet, so it stays on the backlog as demand, not a to-do. Set it aside if you don't need it.Set it aside, or leave it.
This change is already part of the model. Revert it from the version history if you need to.Nothing to do.
The model already works this way, so there is nothing to change. Set it aside.Set it aside.
This change doesn't fit the model as drafted. Ask RIA to describe it again, or open it on the model page.Ask RIA again.
This model's structure can't be changed here. Open it on the model page to see what it can take.Open the model page.
The change didn't build cleanly, so the model is unchanged. Open it on the model page to see why.Open the model page.
This change didn't go through. Open it on the model page to work on it.Open the model page.
This model no longer exists. Hide this card.Hide it.
You can see this model but not change it. Ask its owner for edit access.Ask the owner.
The engine isn't available right now. Try again in a moment.Try again.
That took too long to come back; the engine may still be working on it. Try again.Try again.
That didn't reach the server. Try again.Try again.

Approve a workspace layout

On an open workspace, RIA can propose a layout. The card is tagged workspace and counts <n> widgets in the refined layout. Adjusted to fit your data lists widgets RIA changed to fit; Couldn't be added lists ones it dropped.

Approve saves RIA's widgets and layout to the workspace. If the save fails, the card stays with the reason, such as Couldn't save the layout. Discard drops it.

Who can decide what

Cards show only to people who can write in the conversation, which is anyone who can change the model (Share and govern):

Your role on the modelSees
Owner, contributorEvery card, with all its buttons: Yes, open it, Apply, Approve, Preview, Set aside
Org adminThe same, on every model
Viewer, approver, promoterThe conversation, read-only, and no cards

A refused Apply shows the reason in the card: a missing edit permission, the name of whoever has the model locked, or a model whose structure isn't editable yet (imported models and older builds). Your persona doesn't change any of this.

Limits

  • Up to 8 undecided proposals of each kind, newest first.
  • The stack takes at most 40% of the console's height and scrolls.

On this page