01
A new media type, not a new picture.
Images and video are passive — they render the same forever. A capability surface is active hypermedia: its content is actions you can take. Its ancestor is HTML, not JPEG.
Images and video are passive — they render the same forever. A capability surface is active hypermedia: its content is actions you can take. Its ancestor is HTML, not JPEG.
Through content negotiation, one address can return a human web page or a machine-readable capability card depending on what asks for it.
Services publish a card at a well-known address, and ordinary pages can advertise their capability layer with a simple link relation. A normal browser can already fetch it.
Capability addresses ride on plain HTTPS, so every CDN, proxy, and firewall already understands them. The browser shows the page; an agent runtime follows the actions.
How services and agents introduce themselves and hand off work; an agent's card is its homepage.
The substrate of tools and resources an agent draws on.
Safe, native, agent-generated interfaces rendered across platforms without running arbitrary code.
The open protocol by which a node remembers everything it has seen, said, retrieved, and done; proves what happened; and carries a portable, durable self across services. It is what lets a personal node represent a human: persistent memory under the person's control, with an auditable trail behind every action.
Typed, policy-aware links that bind discovery, tools, surfaces, and memory into something you can navigate.
A2A is the etiquette, MCP the materials, A2UI the workspace, OpenMind the memory — and the self that remembers. Capability links are the contracts that bind them.
The base protocols are real but siloed — MCP tools don't know about A2A agents, neither renders through A2UI without bespoke glue, and today's agent stacks are hand-wired one orchestration at a time. The Hyperactive Web is the layer that makes them compose. A contract address names what is wanted, so any provider on any protocol can satisfy it; a capability link carries the schema and risk, so one capability's output flows into the next without custom plumbing; and affordances let a result advertise its own valid next actions, so flows assemble themselves instead of being scripted. It borrows the composability of smart contracts, the addressing of IPFS, and the etiquette of the web — but for capabilities, and governed.