> ## 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. # Complementary feature alignment # Complementary Feature Alignment **Status:** Adopted (docs / product-strategy pass) **Date:** 2026-06-23 **Branch:** `chore/refocus-docs-and-complementary-features` **Scope:** docs / platform-readiness / product-strategy only. **No runtime behavior, routes, product names, or Dune execution change.** This is the planning companion to the runtime hierarchy shipped in *Refocus app on Vault and Quantum* (#1251). This document gives each **complementary** surface a defined job in the Vault + Quantum platform model, so deeper build work (SP1 proofing, proof-packet expansion, verifier flows, stronger readiness evidence) lands on a clean information architecture. It is the strategy layer above the structural classification in the [app-surface vault-readiness audit](../operations/app-surface-vault-readiness-audit.md) (this is "PR G" in that audit's suggested sequence). See also: * [Product Pillars](../product-pillars.md) — the pillar definitions under the new hierarchy * [Vault-first positioning](vault-first-positioning.md) — canonical thesis + red-lines * [App-surface vault-readiness audit](../operations/app-surface-vault-readiness-audit.md) — whole-app relevance classification * [Dune scope & cost audit](../audits/dune-vault-readiness-scope.md) — Dune relevance to readiness (no execution change here) * [Custody & Legal Boundaries](custody-legal-boundaries.md) — custody/financial/language guardrails *** ## 1. Platform hierarchy > **WalletWall maps wallet, stablecoin, and cryptographic exposure, and turns that > intelligence into vault-ready migration paths and read-only evidence packets.** | Tier | Surfaces | Job in the platform model | | --------------------------------------- | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Primary platform surfaces** | **Stablecoin Vault**, **Quantum Intelligence** | Stablecoin Vault owns the vault-readiness workflow, migration decision, readiness packet, and evidence/prototype destination. Quantum Intelligence is the cryptographic exposure and migration-risk engine that feeds it. | | **Complementary intelligence surfaces** | **Holder Wall**, **Whale Watcher**, **Coinstellation**, **Stable Seer**, **Watchlist** | Discovery and signal surfaces that feed candidate wallets, asset context, and relationship context into the primary surfaces. | | **Decision / evidence layers** | **Migration Readiness**, **Readiness Packet** | Inside the vault-readiness workflow: normalize exposure into a verdict and produce read-only evidence. | Complementary surfaces keep their names, routes, and utility. They are **not** equal-weight platform products. *Market Radar* is **not present**: it became Stable Seer in Epic #163 and is retained only as a historical reference. The runtime mirror of this hierarchy is `PRODUCT_TIERS` in [`src/lib/products.js`](../../src/lib/products.js), guarded by [`app-vault-quantum-focus.test.mjs`](../../test/app-vault-quantum-focus.test.mjs): `stablecoinVault` + `quantum` = `primary`; `holders` + `whales` + `coinstellation` + `stable` = `complementary`; `vault` (simulator) + `watchlist` = `supporting`. *** ## 2. Complementary product jobs Each complementary surface maps **current role → target role → improvement direction** (the build direction that ties it to Vault + Quantum). Improvement directions are **strategy, not committed scope** — and each respects the read-only, no-custody, no-new-Dune-execution boundaries in §4. | Surface | Current role | Target role | Improvement direction (feeds Vault + Quantum) | | -------------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Holder Wall** | Holder and concentration discovery. | Stablecoin concentration, dormant value, exposed-signature value, and vault-candidate discovery. | Feed candidate wallets into Stablecoin Vault readiness and Quantum Intelligence; surface dormant/exposed value as readiness entry points. | | **Whale Watcher** | Wallet activity and whale monitoring. | Large stablecoin and treasury-like wallet monitoring. | Identify monitored wallets that warrant readiness review, packet generation, or quantum-risk assessment. | | **Coinstellation** | Wallet graph visualization. | Wallet relationship and movement context for readiness decisions. | Support entity/context reasoning — counterparties, clusters, and movement trails that explain a readiness recommendation. | | **Stable Seer** | Stablecoin asset intelligence. | Stablecoin compatibility and asset-risk context. | Issuer, liquidity, peg, and holder-distribution context feeding the readiness decision for a candidate's stablecoin holdings. | | **Market Radar** *(not present)* | Legacy/general token or market discovery (renamed to Stable Seer in Epic #163). | Superseded by Stable Seer. | Do **not** reintroduce as an equal-weight product. Any residual asset/liquidity discovery belongs **under Stable Seer**; the name remains a historical reference only. | | **Watchlist** | Saved wallets/items. | Readiness watchlist for vault candidates, exposed wallets, and monitored stablecoin treasuries. | Track **review state** (e.g. monitor / prepare / rehearsing), not generic bookmarks. | > **Whale Watcher and Coinstellation** still read as generic analytics in the app > today (the audit classifies them `reframe` and `demote`). Their target roles above > are the direction; the copy/IA reframe is tracked as a separate follow-up PR, not > done here. *** ## 3. Complementary feature roadmap A phased path from docs/IA cleanup to readiness-evidence integration. Each phase is gated by the boundaries in §4. Phases 2–4 are **direction**, sequenced after the IA is clean — they are not authorized scope in this PR. | Phase | Theme | What it covers | Status after this PR | | ----------- | ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | | **Phase 0** | Docs / IA cleanup & stale-doc archival | Re-anchor pillars; define complementary jobs (this doc); archive/annotate stale docs (`staking-radar.md`, `intel-mode-roadmap.md`); reframe stale equal-weight framing. | **Done (this PR).** | | **Phase 1** | Feature role alignment & tests | Reframe Whale Watcher / Coinstellation copy + IA toward their target roles; align Holder Wall / Stable Seer entry framing to "feeds readiness"; add hierarchy/role tests. | Direction defined; runtime reframe is a follow-up PR. | | **Phase 2** | Candidate handoff into Stablecoin Vault / Quantum | Make "send this wallet to readiness / quantum assessment" a first-class action from each complementary surface (read-only deep-link/handoff, no new Dune execution). | Planned. | | **Phase 3** | Readiness packet evidence integration | Let complementary context (concentration, treasury movement, counterparties, asset risk) appear as **read-only evidence references** in the Readiness Packet. | Planned. | | **Phase 4** | Future-proofing / SP1 proofing integration points | Define where proofing/evidence work plugs in (see §5). Integration points only — **no SP1 implementation**. | Planned. | *** ## 4. Boundaries (apply to every phase) This is a read-only platform. Alignment work must add **no**: * custody, wallet connection, deposit, withdrawal, pooling, signing, yield, or on-chain write behavior; * new Dune queries, and no execute/refresh/mutate of existing Dune queries (Dune stays read-only / cache-only per the [Dune guardrails](../operations/dune-query-guardrails.md)); * product renames or route removals for any surface; * overclaim language — *quantum-proof*, *guaranteed*, *insured*, *production custody*, *quantum-resistant platform*, *protected*/*secured* (funds sense), *mainnet-ready*, *deposit now*, *earn yield* are all forbidden; quantum framing is always *exposure / readiness*. SEO-safe vault-readiness language is preserved throughout: WalletWall is a **read-only vault-readiness platform powered by wallet intelligence**. *** ## 5. Future-proofing note (SP1 / proofing integration points) This PR does **not** scaffold SP1 routes, components, contracts, or provers. Future proofing work should plug into three existing, bounded seams — and nowhere else: 1. **Quantum Intelligence** — as the exposure/migration-risk input that a proof would attest to (readiness, never protection). 2. **Readiness Packet** — as a read-only evidence reference, generated outside the app and surfaced hash-only; SP1 proving remains gated in this app. 3. **Stablecoin Vault evidence boundary** — as a testnet/rehearsal readiness signal, kept as a separate gate alongside PQ evidence and testnet rehearsal. Anything beyond these integration points (actual SP1 proving, on-chain verification, new provers) is out of scope until separately specified and reviewed. See the [ZK / SP1 proof-artifact roadmap](../vault/zk-proof-artifact-roadmap.mdx) and [vault-first positioning → readiness signals](vault-first-positioning.md#readiness-signals-how-the-vault-verdict-is-supported).