Core concepts
The vocabulary eode actually uses: models, Base, scenarios, workspaces, workflows, and RIA.
RIA
RIA is eode's assistant. It runs the discovery interview, authors and edits models, creates what-ifs from chat messages, proposes workspaces and workflows, and reviews results. The RIA Console is the sidebar on every screen — and the one rule that governs it everywhere: RIA proposes, you approve. Model changes arrive as a Plan confirm card (Run plan / Edit / Cancel); nothing is applied silently.
Model
A model is eode's working representation of your decision: sites, products, demand, capacities, costs, and the objective — the UI calls it "what you're optimizing for." You build one by interview, brief, or import (three doors), and every build is proven on test data before your numbers move.
Models live in the Model Library in two tiers: Personal (yours) and Organizational (promoted and shared, with versions, locking, permissions, and an audit log). Every model has a home page — where it stands, what it's worth, and every door into it.
Base and scenarios
A model's accepted data and its original solve are the Base scenario — read-only, the reference point. A scenario is a what-if branched from it: "What if flour costs jump 30%?" Every scenario carries its own solve, its own KPI values, and deltas against Base. Scenarios are cheap — chat messages on the Scenarios screen become them — and disposable, comparable, and verifiable. Imported workbooks also start with BASE DATA: the imported values as stated, before any solve.
KPI
KPIs are the numbers that matter for your decision. RIA proposes them from the model's objective and constraints; you accept, add, or remove. Every solved scenario reports its KPI values with deltas against Base, and each tile traces to where the number came from.
Workspace
A saveable analysis canvas of widgets — metrics, charts, tables, maps, narratives — bound to one or more scenarios. Build by hand, from a preset, or by describing what you want to RIA.
Workflow, run, stage, gate
A workflow is a published recipe — stages with widgets, roles (viewer, contributor, approver, owner), and gates between stages (manual advance, approval required, auto on complete). A run is one execution: assignees fill stages, approvers sign gates, scenarios and analyses attach as evidence.
Personas and roles
Your persona — Modeler, Analyst, Operator, or Executive — shapes which surfaces you see. Organization roles (Org Admin, Promoter, Member) govern promotion and administration.