From description to model
Why eode asks what it asks, when it pauses for your sign-off, and what it builds on before your data arrives.
A model needs four things: what you decide, what limits you, what each choice is worth, and the one number to push up or down. The New Model wizard gets them from you in that order, and only asks about the ones your description leaves open.
What eode reads from your description
| You write | eode takes it as |
|---|---|
| "We bake sourdough loaves and croissants" | The things you decide how much of |
| "One oven, 40 hours a week" | A limit every plan must respect |
| "Loaves sell for 8, croissants for 4" | What each choice is worth |
| What to optimize: Maximize weekly profit | The number every plan is scored on |
Anything it can't settle becomes a question on the Clarify step, one per screen. Suggest Answer and Use what the brief says fill an answer in for you to check. See Describe your business.
Three ways a model gets built
What happens after Clarify depends on what you gave eode:
| You gave | eode does |
|---|---|
| A description with no numbers in it yet | Drafts a Model Design, pauses for your sign-off, then builds and proves the structure on generated sample data. You load your own data afterwards. |
| A description that already carries the prices, limits and quantities | Builds from your own numbers straight after you describe it, then asks you to check the design. There is no sample-data stage, and no separate checks are recorded for the build. |
| A workbook or dataset | Reads your sheets first and shows you how it understood them, and asks about anything it can't read for certain, such as Names written more than one way. After you confirm the design, it maps your workbook into the model and builds and solves on your rows. |
The step rail on the left of the wizard always shows which of these you're on. Each path ends at a solved Base. See Review the design and Load your data.
Why a design comes first
The Model Design is the model in plain words: the decision, its scope, the rules, what was assumed, where your data lands, and what was left out. Signing it off before the build means a misunderstanding costs you a sentence, not a rebuild. You can send it back with a note instead.
Sample data
A model built from a description alone has no real numbers. eode fills it with generated sample values so it can prove the structure solves. Results on sample data show the shape of the answer, not your answer. The model home says so until you load your data.
If your description says how many plants, distribution centers or accounts you have but names fewer, the sample makes up the rest with numbered stand-ins, such as DC 2 and DC 3 beside the one DC you named. The design lists them as stand-ins, and the data you're asked to load asks for each one's real name.
What you get at the end
- A solved Base: Your baseline.
- Your model, described: the design as a workbook, PDF or Markdown file to share.
- The build's evidence on the Credentials record.