# Voided

> Voided protects application data as one authenticated artifact across Rust, Node.js, and browser WASM. The default API is protect/open.

Voided is at 1.0 release-candidate state. Package publication has not happened. macOS arm64, Linux x64, browser WASM, CommonJS, and ESM release gates passed. Real Windows x64 execution remains pending.

## Read first

- [Direct AI reference](https://voidednetwork.com/ai.html): Semantic HTML with the core rule, API decision table, runtimes, artifact rules, Recovery Deck, security boundaries, and a pasteable agent prompt.
- [Full standalone reference](https://voidednetwork.com/llms-full.txt): Complete plain-text context for agents that need to work without the website or MCP.
- [Structured machine reference](https://voidednetwork.com/ai.json): JSON facts and invariants.
- [Developer documentation](https://voidednetwork.com/docs.html): Human implementation guides and examples.
- [Encryption fundamentals](https://voidednetwork.com/learn.html): Plain-language semantic course with local experiments for bytes, encoding, hashing, encryption, keys, E2EE, integrity, password derivation, recovery, and limits.
- [Interactive developer lab](https://voidednetwork.com/docs.html?guide=lab): API selection, artifact stages, Fuse presets, and recovery rotation.
- [Complete library map](https://voidednetwork.com/docs.html?guide=library): Layered public API and runtime capability map.
- [Updates](https://voidednetwork.com/updates.html): Current release state, changelog, and compatibility notices.
- [Voided MCP](https://voidednetwork.com/mcp.html): Read-only local source-aware knowledge server.
- [Reusable Voided skill](https://voidednetwork.com/downloads/voided-skill.md): Portable SKILL.md workflow for API selection and security boundaries.
- [Compact AGENTS.md instruction](https://voidednetwork.com/downloads/voided-agents.md): Persistent repository guidance for coding agents.
- [Source map](https://voidednetwork.com/source.html): Repository, packages, release integrity, agent resources, license, and project routes.

## Core routing rule

- Use protect/open for normal application data.
- Use fuse/unfuse only when the caller already owns and has prepared the inner bytes.
- Use encrypt/decrypt only when the caller deliberately owns serialization, the outer format, and lifecycle.
- Treat keyless inspection as attacker-controlled metadata until keyed open authenticates the artifact.
- Never persist or log plaintext, raw keys, Recovery Deck order, the derived Recovery Key, or the stable root.

## Runtime routes

- Browser: https://voidednetwork.com/docs.html?guide=browser
- Node.js: https://voidednetwork.com/docs.html?guide=node
- Rust: https://voidednetwork.com/docs.html?guide=rust
- VOF3 and Fuse: https://voidednetwork.com/docs.html?guide=fuse
- Recovery Deck: https://voidednetwork.com/docs.html?guide=recovery
- Security boundaries: https://voidednetwork.com/docs.html?guide=security
- Support and verification: https://voidednetwork.com/docs.html?guide=operations
- General encryption education: https://voidednetwork.com/learn.html

## Source

- Source map: https://voidednetwork.com/source.html
- Repository: https://github.com/voided-network/voided
- Support: https://voidednetwork.com/support.html
- MCP project descriptor: https://voidednetwork.com/mcp.json