UTTORI ASM · IN DEVELOPMENT

Analysis backup and recovery

Back up and restore an analysis project without losing SQLite or external ROM data.

A Git clone retains editable source, tracked research and accepted generation ancestry. Back up the private original ROM, original captures and SQLite evidence separately, outside the working disk. Git history cannot reproduce capture facts when their archives are missing.

Back up safely

Use SQLite backup facilities for a live evidence store, or stop every process/editor using it before copying the whole evidence directory, including any WAL and watcher pointer. Do not delete the WAL or copy only the main database while connections are open. Back up ignored .uttori-local/ bindings and private asset-interchange records if you need to retain saved export/review authority.

Restore and validate

Restore into a new directory and rebind .uttori-local/project.json to matching local ROM/evidence paths. Validate the original ROM content identity before preparing a generation. Build restored working source; verify any new pure generation, preview its integration and use a native Git merge. Do not replace an open evidence database.

source abort restores the checkpoint of an active regeneration merge. source clean reclaims proven-owned abandoned scratch and pins. Interrupted asset publication uses asset recover --direction before|after, which validates journal/current bytes before restoring or completing the operation. See saved asset editing.

For stale SQLite revisions, reload and reapply intent rather than reusing an old replacement with a new token. The runnable project workflow demonstrates offline evidence copying; transactions describe database durability limits.