# Vaultfire V3 architecture atlas

This public atlas is generated from `full-v3/manifest/protocol/modules.manifest.json` (16f37e0ff3ece34e76de0035cda1051d5dd9e51aa286f2e0304e46c036317f2a). The manifest, not this presentation, is authoritative.

## Status language

- **Live V2:** observed legacy V2 operation; this label does not advance V3.
- **Source candidate:** source exists for review. It is not an independent audit, deployment, or authorization.
- **Locally testable:** a linked checked command or artifact exists; unlinked tests remain blocked.
- **Externally audited:** no independent human V3 audit is recorded.
- **Deployed:** no authorized V3 deployment is recorded on Base or Solana.
- **Blocked:** required evidence or authority is absent; do not infer readiness.

## ML-DSA claim boundary

The native ML-DSA-65 core, SP1 guest architecture, and Base/Solana adapters are implemented and locally tested as a FIPS 204 algorithm target. Production chain-bound verification remains blocked: there is no final SP1 guest ELF or digest, final program vkey, real Groth16 proof, production verifier pin, real-proof chain test, independent cryptography/chain-integration audit, or FIPS 140 validation. No quantum-resistance or production-readiness claim is made.

## Safety disclosure

V3 is not ready for funds, signing, payments, deployment, activation, or partner production use. No FIPS 140 validation, independent conformance certification, quantum-proof property, independent human V3 audit, two-chain deployment, or V3 payment readiness is claimed.

## Release identity injection

The checked atlas intentionally contains exact release-time placeholders: `__VAULTFIRE_SOURCE_COMMIT_AT_RELEASE__`, `__VAULTFIRE_SOURCE_TREE_AT_RELEASE__`, and `__VAULTFIRE_PUBLIC_ORIGIN_AT_RELEASE__`. A release pipeline must replace all three with exact values and reject any unresolved placeholder before publication.