Reyn Studio documentation
Projects, autosave, recovery, and conflicts
Keep project evidence durable and know what happens after a crash or stale save.
Understand portable Reyn projects, immutable run history, separate recovery snapshots, and current conflict handling.
Projects are durable engineering objects
A project contains sources, case revisions, immutable runs, and evidence links. Content is addressed by SHA-256 so missing, changed, or duplicated objects can be diagnosed without rewriting old run history.
- Editing a case creates a new revision and can mark dependent stages stale.
- A completed run is immutable. Rerunning creates a new parented attempt.
- Stored runs and evidence remain reviewable when compute dependencies are missing.
- Save and Save As write complete project bytes atomically.
Autosave and recovery
- The default autosave interval is 120 seconds and can be set from 30 to 3600 seconds.
- Autosave writes a separate recovery snapshot. It does not silently replace the project file.
- Recover opens the snapshot as an unsaved, dirty project and keeps the original path only as a save target hint.
- A successful explicit save clears the active recovery snapshot when possible.
- Malformed local recovery state is isolated so the app can still open a usable blank project.
Save conflicts
Version 0.4.1 compares the on-disk project hash before replacing it. If another writer changed the file, Reyn refuses to overwrite those bytes and offers Reload, Save As, or a unique timestamped sibling conflict copy.
This is optimistic conflict detection, not a process lock or a collaboration system. It prevents ordinary stale overwrites but cannot promise a cross-process compare-and-swap guarantee on every filesystem.
Request beta credentials.
All documentation and packages are public; approved beta credentials unlock the desktop application.