Decades ago, HyperCard gave us cards connected by buttons that didn't just navigate — they did things. The document web kept the link and dropped the button. The Hyperactive Web restores it: a service card is a card; a capability link is a button that acts — now networked, governed, and self-describing.
Most of the time your node works on your behalf and hands you off between services. When you want control, you zoom in — not visual scale, but meaning. A compact node becomes primary actions, then the full catalog, then the policy and provenance underneath. Progressive disclosure as a steering dial, always within your reach.
Try the +/− controls
Just as content-addressed storage dissolved a file's location, contract-addressing dissolves a capability's location. A capability is identified by what it promises — its intent, schema, and risk — as a name, not a server. Any provider that honors the contract can fulfill it; read-only answers can come from anywhere, even from cache, while actions that change the world stay exactly-once. Intelligence becomes ambient — and your node is how you reach into it on your terms.
Some capabilities cost money — data, compute, a booking fee. The hyperactive web revives HTTP's dormant 402 Payment Required: a provider answers a paid request with a payment challenge, your node authorizes through a wallet or a shared payment token, and the request is retried with proof. It is payment-agnostic — stablecoins or ordinary cards — and it is just another gate: nothing is delivered until you authorize, and every payment leaves a retained receipt. Because price lives with the provider, not the capability, many providers can offer the same contract at different prices — resolution becomes a market, and your node spends only within the limits you set.