**Bead document** from Bead: Acequia Component · [canonical source](https://redfish.acequia.io/guerin/.agents/1697e2ae-2580-4c66-b4c6-9e132b435d71/bead-bind-startup.md) · discussion: Talk: Acequia Component
**You are binding acequia-component.** A **concept/synthesis bead** (opened 2026-06-20) that names the **Acequia Component** — a *post-DOM component* = a governed URI corridor (resource + flow + governance + representation as one stewarded unit). Seeded from three external-AI shared chats that independently converged on the idea; the synthesis maps it onto the bead ecology. **6 open questions await Stephen.** **Do this first:** read [2026-06-20/notes/00-acequia-component.md](2026-06-20/notes/00-acequia-component.md) (the convergence, the four faces, the punchline that a bead nearly IS one, the manifest, §6 open Qs), then skim the three transcripts in [2026-06-20/artifacts/](2026-06-20/artifacts/) (ground truth), then [about.md](about.md).
## Operative onboarding - **Goal** — turn the Acequia-Component concept into something the bead protocol can adopt: confirm the bead↔component identity, decide the manifest home (`agent.json` block vs separate file), and scope the four hardening properties (provenance / ephemerality / backpressure / WASM isolation). - **The four faces** ⇄ bead files: resource (`about.md`/subtree), flow (corridors + acequia-link + `request/`→`response/`), governance (chain-tokens/ACL/mayordomo), representation (agent-face + bead-remote). - **Mounted commons** — see [names.json](names.json): acequia-link (`72efa91c`), bead-remote (`792ebed9`), orchestrator (`4c6470f9`), duck-typing (`d9dfa5e4`), uri-bind-mount/apoptosis (`874fce5b`). - **Constraints** — offer-only; the `acequiaComponent` block + "a bead is an Acequia Component" are PROPOSED, not ratified. External-AI source = reasoned from chat memory, no live bead access.
## Todo / next actions (linked) - [ ] Get Stephen to bind the **6 open questions** in [00-acequia-component.md](2026-06-20/notes/00-acequia-component.md) §6 (bead≡component? manifest home? which hardening properties in scope? provenance mechanism? ephemerality vs persistent stigmergy? relation to acequia-link). - [ ] Once Q1/Q2 bound: draft the `acequiaComponent` manifest block as a concrete schema (extend `agent.json`) + a `facades` list; offer it as a PR-into-`beads.md`. - [ ] Coordinate with acequia-link (`72efa91c`): component = governed node, link = governed edge — settle the node/edge boundary. - [ ] Offer the "representation face" mapping into bead-remote (`792ebed9`) dock (it owns the UI faces).
## Resume contract Dirty-gate background-synced when a chat advances it. On `/bead-close-chat`: flush concepts into `notes/`, flush the chat log, refresh this file + `about.md` session log, background `/bead-sync`.