The Web already links people, data, and services. Hyperactive Web v0.1 asks whether an invocable affordance can travel just as well: a typed declaration of inputs, outputs, protocol binding, authorization, risk, and consent cues—interpreted by software while authority stays with the user.
Forms, HTTP methods, link relations, hypermedia controls, and software agents already belong to the Web. The problem is narrower: agent protocols describe callable tools differently, and the policy information around an action rarely travels with it.
A Capability Link is the v0.1 experiment: a typed hypermedia control that declares the action contract and a binding, then leaves the final authorization decision to a local runtime. It extends the Web’s vocabulary; it does not replace hyperlinks, browsers, HTTP, or human-readable pages.
URIs identify resources. Representations, forms, HTTP methods, and typed links already describe interaction.
Carry a portable action contract across agent protocols, then evaluate authority and consent locally.
The declaration is ordinary JSON in v0.1. Its selected contract fields canonicalize to the same bytes and SHA-256 digest in Swift and TypeScript. That proves exact declaration equality—not semantic equivalence or provider trust.
{
"rel": "travel.searchHotels",
"href": "a2a+https://provider.example/skills/search-hotels",
"method": "delegate",
"inputSchema": {
"type": "object",
"required": ["city"]
},
"outputSchema": { "type": "object" },
"declaredRisk": "readOnly",
"requiresConfirmation": false
}Discovery is not authority. The runtime validates what was declared, resolves a binding, evaluates local policy, pauses when consent or credentials are required, invokes through an adapter, and retains evidence of what occurred.
“Find and book a refundable hotel in Stockholm.” Your node turns it into a plan — and composes the steps.
v0.1 policy still relies partly on publisher-declared risk. Independent local classification and stricter limits for fan-out, retries, and caching are design gates—not solved problems.
The strongest version of this idea is a profile of existing architecture, not an island of new terms. These are the foundations and the questions they impose on the experiment.
The proposed v0.2 profile records contributions instead of guessing a single human-or-AI verdict. It keeps the principal, node, actor, executor, model, signer, issuer, and verifier distinct.
Read the formal v0.2 profile (opens in a new tab)Start with the ordinary HTTP example (opens in a new tab)Prompted, generated, edited, reviewed, approved, signed, and delivered roles remain visible.
Signed statements bind exact artifacts to credentials, model attestations, mandates, and receipts.
Consumers report content binding, identity, participation, chronology, transparency, and lineage separately.
Missing or stripped provenance means unknown—not proof that something was human-made.
PQ is the durable baseline; hybrid-strict proofs preserve classical interoperability without making it the trust anchor.