> ## Documentation Index
> Fetch the complete documentation index at: https://docs.walletwall.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Vault first positioning

# Vault-first positioning

**Status:** Adopted (positioning/docs pass)
**Date:** 2026-06-21
**Branch:** `docs/vault-first-positioning`

## Product thesis

> **WalletWall is a read-only vault-readiness platform powered by wallet
> intelligence.**

Vault readiness is the center of gravity. Wallet intelligence is the front door —
the input layer that reads public on-chain data and decides a single question:
*is this wallet exposed, and what would it take to prepare it for safer vault
migration before funds move?*

The intelligence surfaces (Holder Wall, Whale Watcher, Stable Seer, Quantum
Intelligence, Coinstellation) are how a wallet enters the platform. The Stablecoin
Vault is where that read-only assessment lands as a **vault-readiness** outcome. No
funds move anywhere in WalletWall: the whole platform is read-only, and the vault
work is testnet/rehearsal research, not custody.

## What changed in this pass

The prior pass framed the product as a *"quantum-resistant stablecoin vault
platform."* That framing has two problems this pass fixes:

1. **It overclaims.** "Quantum-resistant vault platform" reads like a production,
   funds-protecting product. WalletWall is read-only and the vault surfaces are
   testnet/rehearsal research. The canonical language guard
   ([Custody & Legal Boundaries §11](custody-legal-boundaries.md)) only allows
   "quantum-resistant vault *readiness*" — the readiness qualifier is load-bearing.
2. **It drifted from the wallet-intelligence front door.** The homepage hero and
   alignment audit settled on **wallet risk intelligence** as the entry framing. The
   thesis now names both halves explicitly: wallet intelligence is the front door,
   vault readiness is the destination.

This pass also folds in the now-merged Vault/PQ readiness foundation (PQ Evidence,
Testnet Rehearsal status, Proof Artifact Status, and the ZK/SP1 disclosure) and
explains those as **readiness signals**, not protection guarantees.

## The three layers

| Layer                                        | Role                                                                                                                                                                               | Surfaces                                                                          |
| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| **Front door — wallet intelligence (input)** | Read public on-chain data and surface exposure: holder concentration, wallet behavior, stablecoin structure, and quantum/signature exposure.                                       | Holder Wall · Whale Watcher · Stable Seer · Quantum Intelligence · Coinstellation |
| **Center of gravity — vault readiness**      | Normalize exposure into a read-only readiness verdict and a migration-readiness path: Monitor · Prepare · Testnet Rehearsal · Not Enough Data.                                     | Migration Readiness engine · Quantum Vault Readiness                              |
| **Flagship path — Stablecoin Vault**         | The destination the intelligence feeds. A read-only vault-readiness journey that can hand off to the Sepolia testnet Vault Simulator for rehearsal — never mainnet, never custody. | Stablecoin Vault (`vault.walletwall.org`) → Vault Simulator (`/vault`)            |

Holder Wall, Whale Watcher, Stable Seer, Quantum Intelligence, and Coinstellation
are no longer presented as peer destinations. They are the **input layer** that
prepares exposed wallets for safer vault migration.

## Product hierarchy

| Rank | Product                            | Role                                                                                                                                                                                                         |
| ---- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| 1    | **Stablecoin Vault**               | Flagship path / destination — read-only vault-readiness journey (`vault.walletwall.org` / `/stablecoin-vault`). The Vault Simulator (`/vault`) is the Sepolia testnet rehearsal detail, not a peer flagship. |
| 2    | **Quantum Intelligence**           | Front door — signature/exposure and migration-readiness signals; routes vault candidates into vault readiness.                                                                                               |
| 3    | **Holder Wall**                    | Front door — wallet / entity profile intelligence; routes valid EVM wallets into vault readiness.                                                                                                            |
| 4    | **Stable Seer**                    | Front door — stablecoin peg, liquidity, holder/flow structure that feeds the readiness assessment (`stable.walletwall.org`).                                                                                 |
| 5    | **Whale Watcher / Coinstellation** | Front door — movement intelligence and wallet-relationship context that enrich the assessment.                                                                                                               |

## Readiness signals (how the vault verdict is supported)

The Vault/PQ foundation surfaces four read-only **readiness signals**. They are kept
as **separate gates** — none implies the others, and none is a protection claim. The
full statement lives in
[PQ Evidence, Testnet Rehearsal & ZK/SP1 Status](../vault/pq-evidence-and-rehearsal.mdx)
and the [public reference sync map](../vault-pq-public-reference-sync.md); the
positioning summary is:

| Readiness signal                           | What it shows                                                                                            | What it is **not**                                                                           |
| ------------------------------------------ | -------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| **PQ Evidence**                            | A hash-only, read-only record that the open ML-DSA-65 verifier accepted a test vector.                   | Not custody, not mainnet support, not a ZK proof, not on-chain verification.                 |
| **Testnet Rehearsal** (rehearsal metadata) | Whether documented Sepolia/testnet simulator metadata is present and safe to surface (mock assets only). | Not PQ evidence, not proof artifact status, not production protection.                       |
| **Proof Artifact Status**                  | Read-only metadata for a reproducible proof-artifact example **generated outside the app**.              | Not a live proof, not on-chain verification — and **SP1 proving remains gated** in this app. |
| **ZK / SP1 disclosure**                    | Research/disclosure status only: an SP1 smoke lane and ZK/PQ status matrix exist in the reference repo.  | No ZK proof runs behind any readiness state; this is **not production quantum protection**.  |

These signals are aligned to the public reference repo
[`Wallet-Wall/walletwall-vault`](https://github.com/Wallet-Wall/walletwall-vault);
see the sync map for the current pinned version. The app consumes only local,
read-only shapes — it does not fetch the repo at runtime, run SP1, or call any
verifier service.

## Language guardrails

The canonical statement is [**Custody & Legal Boundaries §11**](custody-legal-boundaries.md);
its public mirror is [`/vault/boundaries`](../vault/boundaries.mdx). This thesis uses
those guardrails.

**Preferred phrasing:**

* vault-readiness platform powered by wallet intelligence
* read-only vault readiness
* prepare exposed wallets for safer vault migration · before funds move
* readiness signals · separate gates
* generated outside the app · SP1 proving remains gated
* testnet prototype · research prototype · migration readiness

**Avoided (overclaim):** quantum-proof · protected · secured · vaulted funds ·
mainnet-ready · deposit now · yield · production quantum protection. Also avoided are
the action/financial terms the copy guards already enforce (custody, APY/APR,
interest, returns, earn, real funds, mainnet deposit).

## Safety boundary

This positioning adds no custody, no wallet writes, no contract writes, no signing,
no mainnet deposits, no yield, no production quantum-protection claim, no Dune execute
paths, and no runtime public-vault dependency. It is positioning, copy, and docs only.

## Out of scope (unchanged by design)

No changes to provider calls, Dune query behavior, scoring math, wallet-connection
behavior, routing, or contract logic. The homepage scroll-snap journey order,
`PRODUCT_NAV_ITEMS`, and per-section narrative arrows are left for a follow-up so this
pass stays low-risk and docs-only.

## Related documents

* [Custody & Legal Boundaries](custody-legal-boundaries.md) — canonical custody, financial, and language guardrails (§11).
* [PQ Evidence, Testnet Rehearsal & ZK/SP1 Status](../vault/pq-evidence-and-rehearsal.mdx) — the readiness signals in full.
* [Vault/PQ public reference sync map](../vault-pq-public-reference-sync.md) — pinned public-repo version and capability status.
* [Vault/PQ Readiness v0](../releases/vault-pq-readiness-v0.md) — the merged readiness release package.
* [Stablecoin Vault & Vault Simulator](../features/vault.mdx) — the flagship readiness journey and the Sepolia rehearsal detail route.