The site is the public window into the desk: it shows the desk's live

net asset value next to three benchmarks it must beat (holding BTC,

holding an equity index proxy, and a deterministic coin flip), the full

onchain decision log, and a connected wallet's position.

Pages and sections:

1. Landing (/)

   • One-line description: an onchain trading desk run by a swarm of AI agents, trading in public.

   • Status pill: live / awaiting deployment, read from the PerformanceOracle.

   • Four NAV tiles: HiveDesk desk, BTC benchmark, equity index benchmark, coin flip benchmark. Each tile shows the current value, the change

     since the fixed start block, and a link to the onchain event that

     produced the number.

   • Performance chart: one line per series (desk line emphasised, three benchmarks thinner), plotted from PerformanceOracle history.

2. Desk (/desk)

   • Token: name, symbol, total supply, contract address, Etherscan link.
   • DeskVault: current balance, NAV, strategy wallet address.
   • PerformanceOracle: the three signer addresses, last published timestamp, and the count of published observations.
   • BenchmarkTracker: start block, the three benchmark definitions.

3. Decisions (/decisions)

   • Append-only table of every strategy entry from StrategyRegistry: id, timestamp, decision hash, executor address.
   • Each row links to the transaction that recorded it.
   • Filter by executor address.

4. Position (/position)

   • Connect wallet panel.
   • Shows the connected wallet's HVD balance and its claim on the desk, read directly from the contracts.
   • Read-only: the site never requests a transaction signature and never asks for a private key or seed phrase.

Every number displayed must link to the onchain event that produced it,

so any visitor can verify it independently. No number may be hardcoded

or estimated.

The site must read from the live contracts only. Do not add an owner

role, an admin panel, a pause switch, or any write function that

requires privileged access.

Stack: static site, no backend, no server-side secrets.