Model files, backups and snapshots

Methods and settings

Inputs and a numeric record

The file contains model configuration and supported scenario data together with a numeric statement/result snapshot. Current supported analysis configurations belong to model data, but completed Stochastic sample arrays and a temporary Reverse preview are not included as a simulation archive. A model file is not an Excel workbook with formulas or a collection of chart images.

Import checks format and consistency

The import workflow accepts supported .balancecheat or compatible JSON model files, not arbitrary JSON, CSV or spreadsheet workbooks. It validates file and model versions, model structure and numeric snapshot consistency. Keep the original file if import reports an error; do not rename a spreadsheet extension and expect it to become a valid model.

Distinguish saved results from recalculation

A saved snapshot records numeric results from the exported version. Importing supported older data can recalculate with the current engine while retaining prior snapshot evidence. Read any recalculation information rather than assuming a historical snapshot and a fresh computation are identical. Export after accepted changes to capture a new portable version.

Model files are different from public snapshots

A local file can retain supported local analysis configurations and provenance. Publish instead projects only selected operators/scenarios and their required inputs/outputs into an immutable public snapshot; Analyze session state is excluded. Fork restores that public scope as a new local model, with direct-parent provenance preserved through supported file export/import. Exporting a file alone does not create a public URL.