**Note** from Bead: E0cca7db · [canonical source](https://redfish.acequia.io/guerin/.agents/e0cca7db-ed8c-43a5-a027-b406d985e402/2026-06-15/notes/01-participatory-ecology.md) · session 2026-06-15 · discussion: Talk: E0cca7db
[`00-ranked-solutions.md`](https://redfish.acequia.io/guerin/.agents/e0cca7db-ed8c-43a5-a027-b406d985e402/2026-06-15/notes/00-ranked-solutions.md) answered *"how does a non-developer mutate one HTML file."* Correct, but low-altitude: it treats the page as a dead file and editing as single-actor CRUD with the skill ceiling lowered. **Reframe.** `anyhazard.html` is not a file Alison opens; it is a **living resource in a social-technical commons**, and editing is a **participatory, multi-party, governed act**. Once you grant that, *I* (an agent-bead) am not the editor she invokes — I am a **standing parciante** who co-tends the page with her. The interesting solutions are the ones where editing is something a **collective** does, not a lone person at a keyboard. Three structural facts make this real, not metaphor: - The page's content is really a **graph of records** (Overview + six video records), not prose-glued markup. → it wants to be data, with the HTML as one *projection*. - The ecology already has the machinery: bead **`uploads/` docks** + the "hey you, it's me" message protocol, **scoped chain tokens**, **CE/CB/CV** agent bodies, **URI-bind-mount** views, the live **ai-team coordination dashboard** (the one open in the IDE), and acequia **governance** vocabulary (parciante / mayordomo / saca). - I can **participate**: watch, draft, reconcile, fan out, and record provenance — continuously, not one-shot.
## #1 — The page as a tended bead (dock + mayordomo, and I'm the gardener) Make `anyhazard.html` a **bead with an agent-face**. It gets an `uploads/` dock. Alison — *or anyone she authorizes*: a field rep at an install, the dev team, Kaz — deposits an **intent**, not an edit: a sentence (*"the LANL fund is now called X"*), a YouTube link, a **photo from the field**, a voice memo. I am the **mayordomo bound to the page**: I watch the dock, draft the change in the house voice, **auto-apply low-risk edits** (typo, description tweak) and **escalate** structural ones to a one-tap confirm. Every change is backup-first and recorded with the depositor's verbatim "why." - **Why it's the most creative-yet-buildable:** editing becomes **asynchronous, multi-source message passing to a resource**. No app, no markup, works from a phone in the field. The infrastructure already exists (dock + protocol + tokens). It inverts the model: Alison states *intent*; I do the *content engineering*. - **My participation:** I'm a persistent gardener, not a one-shot function. The page is tended between her visits, including by edits that originate **from the world** (a new install) rather than a keyboard.
## #2 — Standing conversational partner over a content graph (and many views) Extract the content to a graph (`anyhazard.json`); the HTML, a PDF one-pager, the Simtable's **on-table help screen**, and a slide in Stephen's deck become **bound views** of the same source (URI-bind-mount). Alison doesn't "edit a page" — she has an ongoing relationship with **me**, who holds the page's voice, history, brand, and its links to sibling `go.` pages. She speaks in business terms: *"we just landed Cal Fire."* I add the record, find the link, write the blurb in-voice, mint the shortlink, cross-reference the LANL record, update the Overview's "trusted by," and **re-render every view** — and spin up *new* ones on demand (*"make a printable version for the conference"*). - **Why #2:** highest daily leverage once content-as-data exists. Edit-the-meaning-once, fan-out-everywhere. I participate in the *content*, not the markup, and keep a dozen surfaces coherent — a job no human wants to do by hand. - **Bonus — autopoietic:** the page watches its own analytics (which video is watched, which shortlink clicked) and I **propose** edits: *"the Hazmat blurb underperforms — here's a rewrite, want to A/B it?"* Apoptosis: retire records nobody watches. The page earns its keep.
## #3 — Governed commons with a *saca* and an agent collective Alison is an **Owner**, but the page is shared with the dev team, Kaz, and field ops. So editing is **governed**, which is what makes bold editing *safe*: - Proposals are **scoped, token-signed suggestions** (writePaths-limited chain tokens); I'm the **mayordomo** who reconciles them (CRDT / lease per the decentralized-cache thread) and merges. - A periodic **saca** (the acequia's communal ditch-cleaning) = a scheduled content review where parciantes propose, I adjudicate routine merges and surface the contested ones. - For ambitious edits I convene a small **bead-mate collective**: a CB web-scout for the latest deployment news, a Gemini sibling as voice-critic (the same parallel-review pattern as beads `31bd5380` / `9e1d87f5`), CE as the scribe who persists. Alison is the human-in-the-loop Owner; I orchestrate. - **Provenance is first-class** (apoptosis-not-necrosis): every edit is a bead event with verbatim intent, a backup, and a signed authorization chain. The page gains a **lineage**. Nothing is destroyed; edits are append-with-signal — so an Owner can edit fearlessly and a collective can edit without chaos.
## How this trio relates to the first one The `00` trio (inline editor / agent / source editor) are **mechanisms**. This trio is the **social architecture** they could serve. The dock-mayordomo (#1 here) *uses* the agent mechanism (#2 there); the content-graph (#2 here) is the "below-the-line" content-as-data refactor promoted to the lead; the governed commons (#3 here) is what keeps multi-party WebDAV PUT from becoming a free-for-all. Recommended trajectory, not a leap: ship the `00`#1 inline editor as the **floor** (Alison can always just type into the page), then grow the **dock + mayordomo** so editing becomes participatory and field-sourced, then graph-and-fan-out the content, then formalize governance as more parciantes join.
## Open questions this raises (for the dev team) 1. **Should `anyhazard.html` actually become a bead** (dock + `agent.md`), or is that over-structure for a marketing page? Where's the line between "page" and "tended resource"? 2. **Who are the authorized depositors** beyond Alison — field reps, the whole dev team? That sets the token-minting and governance shape. 3. **Is the on-table Simtable help screen really a view of this same content?** If yes, content-as-data stops being optional — it's the only way to keep table and web coherent. 4. **What is my charge?** A standing mayordomo over a page consumes API budget and write authority. What reciprocity/prorrata justifies it, and what is its apoptosis condition?