Managers give context. VaultVision keeps the data independent.
Manager OS starts as a trust and proof layer. Vault managers can claim a VaultVision page, add official links, strategy notes, capacity and risk context, then show that beside independent TVL, NAV, drawdown, flow, and deposit-status analytics.
The workflow starts with verified context
Confirm the official manager identity, links, vault address, and public contact route.
Add strategy, best and worst regimes, capacity, fee, withdrawal, and risk notes.
Show manager context next to independent VaultVision metrics, not mixed into them.
Give depositors a public read page and update card that can be checked before sizing.
What the page contains the small version
Trust rules before any public context goes live
Manager context is labeled.
Users should never confuse a manager note with VaultVision's independent read or with an endorsement.
VaultVision data stays independent.
TVL, drawdown, flow, entry quality, and deposit state remain computed from public data and internal methodology.
Risk notes must include the downside.
A proof page that only repeats the upside is not useful. Worst regimes, capacity limits, and lockups belong on the page.
Proof does not mean approval.
Verification confirms source/context, not performance quality, safety, audited status, or suitability for any depositor.
Rollout small enough to ship now
Claim page
Let a manager verify official links and the vault address they operate.
Add context
Capture strategy, risk, capacity, fees, withdrawal rules, and LP update notes.
Pair with data
Render the context beside VaultVision TVL, NAV, drawdown, flow, and deposit-state analytics.
Publish read
Create a public proof page and a share card the manager can reference if fair.
Track signal
Measure page views, vault opens, deposit intent, manager replies, and allocator questions.