Find, classify, and block VAMS mock-mode and stub leakage before staging, testnet, production, or security review. Use when checking DA adapters, OMS identity, Trails, Coinme, TEE, x402 recovery, bridge transports, gateway DA audit logs, environment defaults, or any code path where mock behavior could be mistaken for live proof.
Harden VAMS protocol code, gateway surfaces, deployment scripts, CI gates, and runtime integrations for Phase 6 pre-testnet readiness. Use when implementing or reviewing security controls, authentication, mTLS, Caddy/TLS deployment, rate limiting, input validation, CI scans, role ownership, key management, mock-mode gates, or invariant-preserving fixes.
Plan, review, and execute VAMS Phase 6 testnet deployment preparation for Polygon Amoy and Cardano Pre-Prod. Use when working on deploy scripts, role setup, Gnosis Safe ownership, timelocks, contract address recording, Aiken validator deployment, gateway live-mode configuration, rollback plans, Tenderly simulation, or deployment evidence.
Reconcile VAMS documentation, changelogs, architecture docs, status reports, README claims, API references, and deployment guides with actual source code and tests. Use when docs may be stale, test counts conflict, mock/stub maturity is unclear, gateway/frontend status changed, or a claim needs source-backed correction.
Audit VAMS changes, diffs, PRs, deployment plans, and architecture proposals against the ten core protocol invariants INV-1 through INV-10. Use when reviewing contracts, Cardano validators, Neuron runtime, gateway auth, session keys, cross-chain bridges, rewards, emissions, insurance yield, oracle freshness, or any change that can affect VAMS economic or cryptographic safety.
Perform adversarial VAMS security review for protocol designs, diffs, PRs, deployments, gateway routes, smart contracts, DA adapters, bridges, session keys, TEE trust, OMS identity, token economics, and cognitive-layer memory/search systems. Use when the user asks for red team, attack analysis, abuse cases, exploit paths, or pre-audit critique.
Map academic papers, research ideas, protocol mechanisms, and mathematical designs into VAMS implementation reality. Use when evaluating SIRA, HORMA, HIPIF, EvoMem, ProPlay, CHC cognitive scoring, AutoSkill, DBOS, DA sampling, TEE/ZK trust, token economics, or any research-to-code proposal for VAMS.
Run a structured Six Thinking Hats review for VAMS architecture, research, protocol design, deployment decisions, roadmap tradeoffs, security posture, or product strategy. Use when the user asks for six hats, Blue Hat, Black Hat, Red Hat, Yellow Hat, Green Hat, White Hat, decision framing, or multi-perspective VAMS analysis.