# SQLite Backup and Restore Workbench 1.0.0 Python3.10+ with Tkinter and `pip install -r requirements.txt`. Run `python app.py` or `python checker.py input.json new-receipt.json`. A local tool for a consistent SQLite online backup, AES-256-GCM encrypted archive, independent restore drill, row-count assertions and create-only restore. No account, network or hosted database required. New backup format sqlite-backup/1 is independent of earlier tar-based formats. First request: `{"action":"generate-key","keyFile":"private-backup.key"}`. Save an offline copy of that random32-byte key. Backup request example is in examples/input.json. Verify takes action=verify, keyFile and archive. Restore takes action=restore, keyFile, archive and a **new destination directory**, optionally assertRows mapping table names to exact counts. Every backup runs an independent decrypted restore plus full integrity/foreign-key/count checks before writing the archive. Wrong assertions or authentication errors cannot produce a successful receipt. Existing archives and directories are refused. Optional blob inventory: `"inventory":{"table":"documents","idColumn":"id","deletedColumn":"deleted_at","suffix":".enc"},"blobDirectory":"files"`. Only live rows (null deleted column) require a blob. Missing live blobs fail the backup; no success archive is written. IDs must use letters/digits/underscore/hyphen. Restored blobs always use `blobs/.bin`; adapt that extension when importing into your application. Blobs must be immutable for the duration of backup; coordinate with your application before running. The SQLite snapshot is transactional, a separate mutable file store is not. Bounded edition: 64MiB uncompressed archive,1000 blobs,16MiB per blob,1000 tables,30-second snapshot budget. It uses bounded in-memory encryption and ZIPs; not for multi-gigabyte databases. Plaintext scratch directories are removed after validation; this is not forensic erasure and Windows ACLs inherit from your private temp directory. Use full-disk encryption. Key and backup must be stored separately. No automatic retention/deletion or offsite upload. Restore does not replace live files or start the original application; perform its own read/import acceptance against the restored copy. Test `python -m unittest discover -s tests -v`. Source design prioritizes online snapshot, isolated restore/inventory proof and key custody. Fixture tests leave a real WAL connection open while taking the backup, test deleted versus missing blobs, exact data on restore, wrong key/tamper and no-overwrite. Primary references checked: https://docs.python.org/3/library/sqlite3.html#sqlite3.Connection.backup and https://cryptography.io/en/latest/hazmat/primitives/aead/ .