How themes work

A theme is a basket of mirrors with target weights, bands and rules, published by a creator on ThemeRegistry with a spec whose hash is on chain. Following it lets the theme's agent keep your account in the basket — trading inside your own account, never holding your money. Follow a theme walks the screens.

Follow

One transaction from your account authorizes the agent's access key and records the follow, with your caps, on ThemeRouter. The relay sponsors exactly that pair, never the key's authorization alone. A theme past five stocks adds the rest of the key's scopes in chunks of five, which the relay sponsors only after reading your follow.

The key may only call the router's rebalance and approve tokens to the router. Each token it can approve has its own daily limit, and an approval to anyone else is refused on chain (CallNotAllowed).

Rebalance

Ops' theme-agent holds each follower's key, sealed. When a stock drifts out of its band inside the theme's hours, it rebalances through the guarded pools, within your per-trade, daily and slippage caps — signed by that key as your account, its network fee inside the key's pathUSD limit. The router pulls only the exact approvals the key raised and sends every output to you — it has no recipient argument. The only tokens it ever holds are creator fees owed.

On testnet today

ThemeRegistry and ThemeRouter are deployed on Moderato and configured: the guard set, the five mirrors' pools registered, the oracle set. On 13 October three themes were published with the app's encoder and followed, and the theme agent was registered as ERC-8004 agent #82 and named on all three; its registration file is served at /api/themes/agent/registration.json. Its first rebalance was planned and stopped: the guard reads every member as halted until the stock sync's first delivery, which waits on testnet ETH on Robinhood Chain (evidence).