Verified Memory 0.3.0

Claude Desktop add-on

Download verified-memory-0.3.0.mcpb: lets Claude Desktop search your memory pack and quote it exactly, offline and read-only.

SHA-256: bda22e402f73d8fbdc6ca72df504c04822738a3ca98c9dbe31920756d25c274a

Install in 4 steps

1. Download verified-memory-0.3.0.mcpb (link above).
2. Double-click it. Claude Desktop opens and asks to install it. Windows may ask which app opens the .mcpb file: choose Claude. Alternatively, drag the file into Claude Desktop → Settings → Extensions.
3. Unzip your pack first (Windows: right-click → Extract All), then pick your pack folder when asked: the folder that contains MEMORY.md, README.md, records.jsonl and SHA256SUMS. The folder picker shows folders only, so the pack folder will look empty; that's normal. You can also paste the folder path.
4. Make sure the extension is switched on (Settings → Extensions → Enabled) before asking. Then ask, for example: "Using verified memory, what did … ?"

No pack yet? Make one from your ChatGPT or Claude export with the pack maker, which runs entirely in your browser.

Please note

• Tested by hand on macOS and Windows (install, configure, and asking Claude). The add-on's automated tests also pass on Windows on Node 22 and 24.
• Claude Desktop shows a standard "not verified by Anthropic" warning when installing. That is normal for add-ons installed from a file rather than Anthropic's directory.
• A signature proves who signed a pack, not that its content is true. Checksums prove the files are unchanged; neither shows that what the pack says is accurate or complete.
• If anything in the pack fails its checks, the add-on refuses to start instead of serving it.

---

Signed and dated packs (PACK.json), --strict, sign-pack, and a Claude Desktop one-click bundle. See plugins/verified-memory-mcp/README.md#signed-and-dated-packs.

Release-2 drill evidence (verifiable)

Publishes the material you need to check the release-2 recovery-tested pin yourself.

Start here: evidence/release-2-drill/VERIFY.md

git clone --branch release-2-drill-evidence-2026-10-03 https://github.com/python1/data-lore-hive.git
cd data-lore-hive/evidence/release-2-drill
python3 verify_evidence.py

The folder contains:

• the release-signing public key (SHA256:ZozTASM/tPWZPMpUaYnP5tYJsVWNbANnRnjjYkx5j4A)
• the signed release-2 manifest and the signed recovery-tested pin
• the sealed drill evidence index the pin signs over
• the 28 indexed evidence files that passed a leak scan, byte-for-byte unchanged

verify_evidence.py (Python standard library plus ssh-keygen) checks both signatures, checks that the pin names exactly this release manifest and this evidence index, and checks every published file against its index hash.

What this does not prove. The release code is private: the bundle and the recovered checkout are withheld. 289 of the 317 indexed files are withheld, including the raw model trials, the integrity report and the release's evidence.json. Each one is listed with its index hash. The main machine being off is the operator's statement, and the replica's acceptance of the pin is operator-reported. VERIFY.md covers each of these in detail.

This tag and release are not signed. The signed objects are the files inside evidence/release-2-drill/.

Signed code releases and the recovery-tested pin

Adds signed code releases and the recovery-tested pin.

• Signed code releases: every new master commit is backed up to the replica as an unsigned candidate. Only a release signed with a human-held key can become the approved version. Signed manifests carry monotonic sequence numbers, and the upload account cannot approve a release or advance the pin.
• Recovery-tested pin: with the main machine off, the recovery machine recovered signed release 2 and the 26-event memory checkpoint. Integrity and pristine-memory checks passed, and the recovered release passed 212/212 of its own tests. The nine fixed model trials gave 6 correct / 3 abstentions / 0 false accepts / 0 errors, which missed the 9/9 quality target but met every pin-eligibility gate. The operator then signed a pin over the sealed evidence index. The main machine being off and the pin upload are operator-reported.
• Offline suite: 226 tests, 225 pass and 1 is skipped (it needs private Git history).

This is a redacted export. Install kits, drill evidence, receipts and operator runbooks are not included; see REDACTIONS.md. This tag and release are not signed.