What should happen?
Use the product specification for the promised behavior and explicit exclusions.
Documentation
Read the system.
The product, security model, architecture, evidence, and release gates are documented separately so a claim cannot quietly outrun its implementation.
Canonical documentsVersioned with the codeClaims tied to evidence
Source of truth
Start with what you need to verify.
- 01
Product specification
Canonical wallet behavior, supported flows, invariants, and explicit exclusions.
docs/product-spec.md - 02
Security model
Assets, trust boundaries, required controls, residual risk, and current release blockers.
docs/security-model.md - 03
Architecture
The Svelte, Tauri, Rust, BDK, persistence, network, and hardware boundaries.
docs/architecture.md - 04
Implementation status
Capability-by-capability separation of fixture, native implementation, evidence, and release state.
docs/implementation-status.md - 05
Mainnet checklist
The evidence that must exist before mainnet can be enabled.
docs/mainnet-release-checklist.md - 06
Roadmap
Work ordered by security dependency rather than marketing priority.
docs/roadmap.md
Reading order
Behavior. Boundary. Evidence.
Where is trust placed?
Use the security model and architecture for secret, persistence, hardware, and network boundaries.
What is proven today?
Use implementation status and the release checklist before treating a capability as ready.