Beads are "acequia components": more "web" than "web components" (Wedtech Beads 2026 07 08)

**Note** from Bead: Wedtech Beads 2026 07 08 · [canonical source](https://redfish.acequia.io/guerin/.agents/9d343253-c279-47ac-a066-cc31ce505782/2026-07-08/notes/04-acequia-components-more-web-than-web-components.md) · session 2026-07-08 · discussion: Talk: Wedtech Beads 2026 07 08

Beads are the component model for the acequia and for browsers. The claim to defend on stage: they are more "web" than "web components".

## The contrast - **Web components** compose inside one page: custom elements registered in a DOM, bundled and shipped, alive only while that tab lives. Their namespace is the page. - **Acequia components (beads)** compose across the web itself: each is a stable URI on an origin, composed with the verbs every HTTP client already has (GET, PUT, PROPFIND, MKCOL). Their namespace is the commons, scoped per consumer through `names.json` bindings. | | web components | beads | |---|---|---| | unit | custom element | URI-addressable resource | | registry | page's CustomElementRegistry | the namespace itself (plus per-bead `names.json`) | | composition | DOM nesting | linking and mounting by URI | | lifetime | the tab | persistent; apoptosis when unreferenced | | interface | JS properties/events | HTTP verbs + content negotiation | | consumer | that one page | any agent, browser, or human with a URL | - Distribution is free: a bead ships by being addressable. No bundler, no registry publish, no version pinning ceremony; caching, auth, and naming ride the HTTP substrate. - Browsers are first-class parciante nodes here: a page can GET a bead, compute, and PUT results back. The component boundary is the origin membrane, with the goes-inta/goes-outa discipline at the edge.

## Talk beats - One slide of the table above. - The rhetorical turn: web components made the page composable; beads make the web composable.

## Open questions - [ ] Does the audience need a web-components refresher slide first? - [ ] Anti-reification check on wording: present beads as riverbed and gates (URIs plus auth), avoiding a "component framework" reading of our own pitch.