Raw Drafts Space / Live laboratory
Nine experiments for a web that can expose tools to agents, run intelligence locally, stream interfaces, move money through HTTP, and keep human control legible.
Agent-native website
WebMCPCheckingThe page registers a read-only browser tool for agents when WebMCP is available. The note form below also uses declarative tool annotations as progressive enhancement.
document.modelContext.registerTool({ name: "inspect_raw_drafts_web_futures" })Chrome currently exposes this behind testing flags or an origin trial. Without it, the page remains a normal semantic website.
HTTP-native payment
x402 flowCheckingRequest a protected resource, inspect the 402 challenge, approve the cost, and retry with a payment signature header. This lab uses a transparent local simulation, not an onchain settlement.
Spatial interface
HTML-in-CanvasCheckingIn supported Chrome builds, the browser draws a real DOM card into the canvas while preserving selection, forms, accessibility, and agent readability. Other browsers see an explicit DOM fallback.
The content stays usable instead of disappearing behind a compatibility wall.
Private intelligence
Browser AICheckingThe summarizer tries the browser's local LanguageModel API first. If the model is unavailable, a deterministic no-network fallback keeps the interaction useful and honest.
Local-first substrate
IndexedDBCheckingNotes are stored in the browser and synchronized between open tabs with BroadcastChannel. No account, API key, or server round trip is required.
No local notes yet.
Progressive delivery
Streaming HTMLCheckingThe server sends independent audit fragments as they become ready. Experimental browsers stream directly into the element; the compatibility path incrementally inserts trusted same-origin chunks.
HTTP/3 transport
WebTransportCheckingThe browser client can open an HTTP/3 WebTransport session with reliable streams and datagrams. Paste a compatible secure endpoint to attempt a real connection, or simply check client support.
Browser-mediated identity
Digital CredentialsCheckingThe browser can mediate credential presentation without exposing the user's whole wallet to the website. This probe only checks whether a protocol identifier is allowed; it never requests identity data.
Portable execution
WebAssemblyCheckingA tiny isolated module calculates a score through a typed WebAssembly export. The browser demo uses core Wasm; a production WASI component host would add richer capabilities and explicit permissions.
plugin.add(40, 2) → 42Less framework, more platform
Native UI stackCheckingPopover, CSS anchor positioning, and cross-document view transitions reduce the amount of interaction code a modern interface needs. The controls degrade to ordinary HTML where support is incomplete.
Focus handling, escape behavior, and top-layer placement come from the platform.
Design judgement
New browser capabilities matter when they remove hidden infrastructure, expose meaningful control, or make a previously inaccessible interaction possible. Every card above shows both the ideal path and the fallback because the future arrives unevenly.
Optional Google Analytics and Microsoft Clarity measure content performance and usability. They load only if you allow them. Form values, email addresses, and chat messages are never included in analytics events.