B. The export today
File > Export MBF and File > Import MBF now provide native review, save and import for a declared subset. Export writes an SI pilot model and companion identity file after review and an explicit local-private choice. Import reads bounded SI and English forms, requires a material-provenance declaration, shows losses and assumptions, and adopts an admitted model through the normal open/unsaved-changes guard. Imported models start unsaved.
A bound import verifies the companion file against the MBF bytes and the regenerated writer output. It restores the identities the pair preserves; designated-source checks can establish the stated identity set, not equivalence of the entire model. Edited or externally rewritten files have an unbound interpretation and stricter source-dependent refusals. The writer’s subset still excludes tees, rigid-family components, nonlinear supports, hangers and other unsupported families. Combinations are omitted and disclosed; some newer combination forms block export.
Invented subset round-trip checks are implemented. Complete reference-system coverage and the required round trip through the actual desktop build remain unestablished. Target-version and record-family questions remain open. A saved or imported pair establishes no receiving-program acceptance or comparison result. Model transfer reads no solve result and has separate privacy, loss, size and memory gates. An unknown export-save outcome still blocks another export until reload or restart. See interchange scope.
1.Other exports.
Other surfaces prepare a straight-run PCF subset, native packages, CSV or JSON result exports, centerline geometry and local-detail handoffs. These packages have different input, loss and eligibility conditions. A package’s presence does not establish target compatibility or professional validation.
Current exact-route pressure-2 and pressure-source-1 results can reach desktop outputs including:
result JSON, stress-neutral JSON and user rule checks. The native reader must admit the source and numerical standing.
Pressure-source results with load/reference states remain ineligible; ordinary pressure-2 load/reference-state results can qualify.
Eligible current results on both routes can produce local-private reports and packages. Report composition and a separately confirmed shareable-package action are implemented, with numerical-standing, privacy and size restrictions; readable solved exact-route results may render with ineligible standing stated while their package save remains refused. See report limits. Results and comparison tables also offer local-private CSV export, separate from the stress-neutral interchange file. PCF and other model-transfer packages retain their separate exact-route restrictions. MBF model export has its own admission, independent of result-output policy. Byte-exact files for other programs, including stress-neutral CSV, are withheld while session values are private.
Stored or copied source-result bytes alone do not supply the required live invocation binding
(Status).
The separate retained-precision successor method remains dormant and is outside the v1.0 target. Saved or copied result bytes do not supply the live native capture required by prepared successor policies. Prepared result JSON and stress-neutral policies admit a successor only with eligible standing and a live native capture. These preserved policies do not make it a current application feature. Other successor output surfaces remain refused.
2.How the export will be checked.
A complete interchange check must compare three representations: the defined problem, a model built by hand in the receiving program, and the exported model. Each feature must be identified as exact, approximate, omitted or untested. A file that opens does not establish faithful transfer. Current pilot-subset checks screen package structure and disclosed losses; they do not establish complete target execution or equivalence (Part VI).