Updates

What is in each build, as evaluators see it inside the application.

0.1.0 — Evaluation build

The first build circulated for evaluation. Everything below is new because everything below is the first time anyone outside the project has seen it.

Invite-only. An administrator creates your account; there is no sign-up.
Three ways in: a six-digit code by email, a sign-in link by email, or a password an administrator issues you. You cannot change your own email or password — ask the administrator, who can reset either.
Your session ends by itself after twelve hours of inactivity.

Projects are private to your account. Nobody else can open them, and an administrator who opens one for support leaves a record that they did.
Three worked examples are waiting in your dashboard the first time you sign in. They are ordinary projects: edit them, break them, delete them.
Everything saves as you work. There is no save button to remember.
History keeps up to twenty points you can come back to. Press ⌘S or Ctrl+S to keep one, name it, and restore it later — restoring checkpoints where you are first, so you can undo an undo.
Deleting a project is reversible for 30 days.

Change an input after calculating and the results are marked stale, on the dashboard and in the project. Reports made from stale results carry a watermark saying so.
A design the engine could not complete is never filled in with a plausible value. It says NOT DESIGNED, in the tables and on the drawings, and it cannot be exported as a PDF at all.
Every page of every report carries the evaluation notice, naming the build, you, the project and the time.

The Feedback button is in the header on every screen. Attach a screenshot by pasting, dropping a file, or capturing the screen.
If a number looks wrong, choose Calculation error and say what you expected. Those go to the top of the pile.
Known issues in the user menu is the honest list of what we already know about. Reading it first saves you reporting something already in hand.

AutoCAD DXF export is switched off. The button is visible so you can see the feature exists; it does nothing in the evaluation.
PDF export may be unavailable depending on how this deployment is configured. The HTML report always works and prints from your browser — the page headers and "Page N of M" footers will be your browser's rather than ours.