KEEP THE MODELS / KEEP THE EVIDENCE
Take the workshop with you.
Move the application, retained histories and any separate planning drafts together.
No cloud account required
01 / APPLICATION FILES
The simulator package.
Models, source code, original geometry, reference examples and the bundled Three.js library. Install Node.js on the destination, extract the package and run its local preview.
The package excludes browser histories and the Node.js runtime. Its reference examples are authored demonstrations, not your retained archive.
02 / RETAINED BROWSER RECORDS
Your saved histories and studies.
Includes saved timber journeys, calibration / experiment runs, calibration-linked worksheets and scale, device, patterning and passive-component studies, plus discovery plans, their linked evidence, the learning journal and specimen/process case histories. Unsaved controls, board-monitor samples and session-only fallback storage are not included. Export session-only work from its original tab.
Planning drafts to export separately
The power load plan, recovery stream study and seasonal workspace each have their own Save and Export controls. They are editable drafts outside the ten archives above. Unsaved material-case revisions also need their own draft export. Pixel studies export edited dimensions and assumptions separately. Optical comparison worksheets export their readings, calculations and uncertainty scope; export before leaving or reloading that workbench. Crop-trial diagrams and harvest-station context have separate reference exports; save the corresponding Discovery plan if you want a retained plan version. The reference-mass desk exports a blank reference register and, separately, a load plan with the raw proposed masses; neither has an import control and a reload clears the desk draft. Save unfinished Discovery plans to retain their open fields; unsaved form text is not in the archive. Export these from their workbenches before moving computers.
Transfer files saved in this project
03 / RESTORE ON THE NEXT COMPUTER
Inspect before importing.
Open a transfer JSON file or paste its complete contents. Every record is validated and compared with the destination archive before the import button becomes available.
Checksums detect changed contents; they do not authenticate an author. Import adds missing identities and keeps identical records. Conflicts stop preflight. The archives are written separately; if storage fails partway through, the report identifies what remains and the same bundle can be checked again.