Change a model

Where: Overview→Step 5 Backlog→Develop

Every structural change to a model goes through its backlog. Each item says where it came from. You Preview it on a trial solve, then Apply it, and every applied change becomes a revision you can revert. To change the model's numbers rather than its structure, see Edit data.

⤢ Open · replay

Reopen the whole model

Edit model, in the model home header and on each Model Library row, opens the model in the steps it was built in, to revise the description, answers, data or design from the start. It's disabled while the model is building, mapping, solving or reconciling, and hidden for the Operator and Executive personas (Roles and personas). To change only the brief, the goal or your answers, use Edit and Change answers on Step 1; see Model home.

Read the backlog

Open Step 5 Backlog on model home. The Develop zone's summary reads Your model's backlog · then N open · N gaps vs your brief · N applied, or "Nothing open. Ask RIA for ideas or run a review." A Gaps chip marks unmet items. The zone starts collapsed and opens itself when there are gaps, when you arrive from Review & improve or a Suggested next row, and when a change for this model lands in the console.

At the top sits the model's certification, Certified, Certified with concerns or Checks not passing (with "· predates latest changes" when the model has moved since), then how many checks are proven and the review's confidence. When it's stale or failing, Re-check opens the validation record.

⤢ Open

Items are grouped, each group with its count:

Each row names its source in one line: Set aside when we built it, A limit in your brief, Recognized, not yet carried, Your data, Flagged by the independent review, Suggested improvement, Validation flagged this, An unmet requirement, A question you left for later, You asked for this, From a what-if you liked, A metric worth adding, Your data changed. Click Expand on a row to see its detail and the quote it came from.

Work an item

An open row shows only the actions that can succeed for it.

The proof block reads What this does (proven on a trial solve) with now $X → after $Y and the change, or what a KPI would read on the base plan. An infeasible chip means the change can't be made to work. Applying answers in one of three ways:

• "Rebuilding the model with “…”. You will review the Model Design before it builds; the change is marked applied when the rebuild lands."
• "Applied “…”: new revision N created. Revert any time from the version history; stale scenarios can be regenerated from Scenarios." See Versions and history.
• "Applied “…”.", sometimes followed by what the change did.

On a model built straight from a workbook, a design choice can end in Map again, which maps your data again onto the dataset version you chose.

When a preview or apply is refused

A call that fails rather than being refused shows Try again, which repeats it: "That took too long to come back; the engine may still be working on it. Try again.", "You can see this model but not change it. Ask its owner for edit access.", "The engine isn't available right now. Try again in a moment.", or "That didn't reach the server. Try again."

Set aside and take back

Set aside (✕) on a row asks "Why set this aside? (e.g. this doesn't apply to us)". Type a reason and click Set aside. Nothing is dropped quietly:

• You set aside · N lists what you dismissed, with your reason. "Things you told us do not apply. Take back to reopen one." Take back reopens it.
• Recognized, not buildable yet · N holds what eode can't build today. "These are honest gaps in what the tool can build today; we track them as demand for what to build next."

An empty backlog reads "Nothing to develop yet. Rebuild the roadmap from your brief and the model's own design, or ask RIA in chat for an improvement." Rebuild the roadmap fills it again from the brief, the design, your data's needs and the latest review. It needs a model with a Model Design.

Have RIA review the model

Where: Overview→Review & improve

Review & improve has RIA read the model and its solve and propose improvements. The door card on model home opens Step 5 and starts the review; in the zone, click Review the model (Review again after): "RIA is reviewing the model and its solve…" Results are sharper on a solved Base; until there is one, the door card says "Solve the base first — then RIA can review the results."

Proposals come one at a time. The basis line says what was reviewed: the best result, solve time, checks passed, scenarios, and capabilities used. Each proposal box has its title, an impact tag (High, Medium or Low impact) and N of M; a category (Performance, Functionality, Efficiency or Effectiveness); Why this?, a fold with the rationale and its evidence; and the next step it implies.

A proposal that wasn't filed says "Not added to your backlog — it can be set aside, or run the review again." and has no Take it. The rail beside the box groups proposals by impact; click one to jump to it. The footer keeps count ("N taken · N for later · N set aside.") and states the rule: "Nothing is changed until you apply an item from your backlog. Take what's worth doing, leave the rest for later." With nothing to propose, the review says "No improvements surfaced: the model looks well-built on the dimensions RIA checked. Ask about a specific aspect below.", or "Solve the base scenario first, then RIA can review the results and propose sharper improvements."

Ask RIA to look at something takes a sentence, such as "how could I speed up the solve?". Click Ask RIA; a filed result echoes Added to your backlog: “…”. It appears once a review has run in this visit.

The review after the build

A model built straight from a workbook is reviewed automatically after the build. Before you run a review, Step 5 shows "The review after the build, read from the solved model." and What the solve says, the solve read back in plain sentences: Your books, Demand, Purchases, Machines, the fullest first, Sites, Relief used and Rows. Its findings are on the backlog; the proposal walk starts from them.

Track what you said the model must do

Where: Overview→Requirements

Requirements, below the KPI card on model home, lists what you said the model needs, each with a verdict. Its summary reads N/M verified plus how many are in place, not met, need review or wait on you, and "— model changed since" when stale. A Not passing chip appears, and the zone opens itself, when anything is not met.

1. On an empty ledger, click Seed from what I said. eode proposes requirements from your brief and answers.
2. Under Needs your input, confirm (Confirm this requirement) or dismiss (Dismiss — not a requirement) each proposal.
3. Add your own in Add a requirement (e.g. 'gross margin at least 20%') and press Add or Enter; it's confirmed at once. The note under it says whether it will be checked automatically or show as needs review because no machine can check it.
4. Check now re-checks every requirement against the current model and its solve.

Gaps lists confirmed requirements the model doesn't meet. Where the design set a capability aside, tick it (it shows set aside) and click Add N back & rebuild once. "Re-adds these capabilities and rebuilds the model. Revertible." The answer reads "Added N capabilities — rebuilt (objective now X). Revert available in the model's version history." or "Couldn't add these — the model's structure may not support them yet. Try unchecking one and re-adding the rest."

Built & running groups the rest, weakest first: in place - values unchecked, needs review, accepted - not machine-verified, produced, verified, other.

Each row also says where it came from: from your brief, from the import interview, from chat, from discovery, added by you, or placeholder created by RIA.

Decide a change RIA files in the console

A change you ask RIA for in the console is filed on this backlog and shows there as a Change filed: … card you can preview, apply or set aside in place; see RIA's proposals. Open in Develop brings it here.

Bring in an updated workbook

A model built from an Excel workbook takes a newer copy through Refresh from workbook on its Scenarios screen (Data connections). A workbook that failed its checks is re-uploaded with Re-upload the workbook on the model home status card. For a model built straight from a workbook, edit your inputs in your own sheets; see Start from a workbook.

Limits

• A review times out after 90 seconds; Ask RIA to look at something after 60.
• Finished change orders past 200 per model are archived off the backlog.

Related

• Versions and history: revert an applied change
• Validation: the checks behind the certification line
• Credentials: what was built and set aside
• Edit data: change the model's numbers
• RIA proposals: every card the console shows