Updates.

Voided 1.0.1

Browser recovery metadata now identifies the exact derived key; older unverified metadata fails closed unless explicitly opted into after independent recovery verification. Compression rejects malformed text. The downloadable local-source MCP now limits file reads to Voided knowledge and source files and requires an explicit root.

Interactive encryption fundamentals

Added a free secondary Learn route for people who want the ideas before the APIs. It keeps the three-page primary navigation intact while separating general cryptography education from the Developer Lab.

• Bytes and UTF-8 visualization
• Live encoding, SHA-256 hashing, and Voided WASM encryption
• Symmetric and public/private key models
• E2EE trust-boundary journey and authenticated tamper rejection
• Four state-driven cryptographic terminals for plaintext, key custody, network routing, and authentication
• PBKDF2 teaching lab, recovery hierarchy, limits, and knowledge check

Three-page developer site and interactive lab

Primary navigation is now Home, Developer, and Updates. The Developer Lab consolidates runtime guides, an API decision tool, artifact explorer, Fuse preset comparison, recovery rotation model, complete surface map, diagnostics, compatibility, AI references, and MCP access.

• Guided and Expert documentation modes
• Thirteen structurally distinct Recovery Deck UI compositions
• Real browser WASM round-trip trace with raw key, bytes, artifact, and restored output
• AI HTML, llms.txt, full text, JSON, and source-aware MCP remain directly addressable

Recovery Deck protocol and browser component

Added a stateless 52-card recovery credential backed by canonical permutation ranking and deterministic, domain-separated derivation. The deck and derived Recovery Key are never persisted; only the opaque stable-root wrapper may be stored.

• 29-byte canonical permutation rank
• 32-byte transient Recovery Key
• 80-byte opaque root wrapper
• Fresh CSPRNG rotation without changing application keys or re-encrypting data
• Framework-free modal or inline UI with application-owned styling

Fuse-centered 1.0 architecture

Documentation and release surfaces now center the current VOF3/Fuse system. Normal integrations use protect/open; shell and primitive APIs remain explicit opt-in layers for callers that own more of the format.

Cross-runtime release gates

Verified Rust source, native Node packages, browser WASM assets, CJS and ESM entry points, package manifests, provenance, and platform selection. These checks preceded the public 1.0 release; Windows runtime execution is still pending.