# Encrypted Local Vault Kit 1.0.0 Standalone Windows/macOS/Linux developer kit. Node 20+ and Python 3.10+ with Tkinter for the native interface. Run `python app.py`; no account or network service required. CLI accepts one JSON request on stdin: `node vault-workbench.mjs`. Do not put passwords or recovery codes in command arguments, shell history or saved request files. Choose a new **root** directory and Create, enter a password (10–256 characters) and confirm that you will save the returned recovery code offline. Save that code before closing the result. Add takes an existing input file and returns an opaque document ID. List returns IDs. Export takes a listed document ID and a new output path outside the store; output is plaintext. Backup writes a new, self-contained encrypted JSON backup outside the store. Restore takes that backup as input, its password and a new root. It authenticates all encrypted documents before committing the restored directory. Change-password takes the current and new password. Recover takes the saved code and a new password and issues a replacement recovery code. Original filenames are not stored: keep a private record mapping IDs to your documents. AES-256-GCM chunked document encryption and password/recovery key wrapping from the included core. PBKDF2-SHA256 600,000 password iterations and 100,000 recovery iterations, HKDF subkeys; 130-bit random recovery codes. Reads bound wrapper parameters before stretching. Maximum 8 MiB per file, 100 documents, 64 MiB encrypted store. One-shot child processes end after each operation; no persistent unlocked session. No plaintext temporary files. New outputs never overwrite existing files. Use only one writer at a time. Store in a private local directory, not a shared or synchronized folder. Backup copies remain unlockable by the credentials current when they were made. Rotating a password/code does not revoke old backups. Protect/recycle those separately. Recovery cannot help if both password and recovery code are lost. This kit has no external cryptographic audit, password-strength certification, forensic erasure guarantee or cloud sync. JS strings/OS paging may retain transient secrets; use full-disk encryption. Export intentionally creates plaintext. Native visual acceptance is recorded separately from automated tests. Test: `node --test tests/product.test.mjs`. Tests use real production KDF settings and cover create/add/export, backup/restore, password rotation, recovery-code replacement, wrong credentials, tampered files, unsafe backup paths, existing-output preservation and KDF bounds.