Workspaces Backups and Recovery

Workspaces, Backups, and Recovery

Gridoryn is built for local data ownership. That only works if the operational model is explicit.

Data Model

Gridoryn stores data locally in a per-user application data location managed by Qt. That includes:

• The primary SQLite database
• Workspace-specific snapshots
• Logs
• Persistent UI state and settings
• Themes

Workspace Profiles

Workspace profiles let you manage multiple local databases explicitly.

Typical examples:

• Work
• Personal
• Client-specific planning spaces
• Safe sandboxes for experimentation or imports

Each workspace keeps its own:

• Layout
• Perspective and view state
• Column visibility
• Related UI state

The current workspace name and database path are shown in the status bar.

Switching Workspaces

Use File > Workspace profiles or the command palette to:

• Create a workspace
• Register an existing database
• Switch safely
• Remove a workspace with explicit confirmation

The active workspace cannot be removed, and the application keeps at least one workspace available.

Snapshots and Snapshot History

Gridoryn keeps versioned restore-point snapshots with retention rotation.

Snapshot history shows:

• Timestamp
• Reason
• Task counts
• Archive counts
• File size
• Snapshot file name

Restores are intentionally safe:

• Restore into a new database copy, or
• Restore into a new workspace

The live database is not overwritten in place from snapshot history.

Backup Import / Export

Manual backup flows are available from the File menu and command palette.

Key properties:

• Backups are local and portable
• Import validates integrity metadata
• Theme export/import is separate from data backup so styling can move independently

Diagnostics and Logs

Gridoryn includes:

• Diagnostics dialogs
• Repair preview flows
• Crash logging
• Operation logging
• An in-app log viewer

Use diagnostics when:

• Startup fails
• A migration is rejected
• You suspect integrity damage
• You need a preview before a repair operation

Migration Safety

Schema migrations are versioned and validated. Combined with snapshots and logging, this reduces the risk of silent data damage during upgrades.

Recommended Safety Habits

• Keep at least one separate workspace for experiments
• Use snapshot history before high-risk cleanup or imports
• Export backups before major upgrades
• Use the log viewer when a workflow fails unexpectedly