Published model workflow

Telion separates editable model declarations from the geometry, mesh, and result data that have actually been built. This distinction keeps the visible state reproducible while parameters, selections, or boundary conditions are still being edited.

The Mesh feature reference is resolved from its stable feature ID when the release is composed, so this guide cannot drift to a hand-maintained route.

Build order

1. Define parameters and geometry operations.
2. Build Geometry and inspect the resulting entities.
3. Assign source-backed materials and physics features to explicit entity sets.
4. Build Mesh and review element sizing and topology.
5. Configure a compatible System Solver and solve.
6. Publish the selected plot before exporting a figure, table, or report.

Warning. A draft expression or model-tree edit does not certify a new geometry, mesh, or solution. Rebuild the affected stage before using it as evidence.

Numerical state

For a solved finite-element system, the published state satisfies the assembled residual contract

$$R(u, p) = 0,$$

within the recorded solver tolerances for the saved parameter vector $p$, selected solver configuration, and recorded mesh identity. A linear stationary system may reduce to $K(p)u=f(p)$. A plotted field is a view of that solution dataset; changing plot styling does not change the authoritative solver state.

Release check

Keep the project file with the generated figure or table so another user can reproduce the exact release state.