**Note** from Bead: Uri Guid Discussion · [canonical source](https://redfish.acequia.io/guerin/.agents/3bf89750-6b01-41ba-8a98-3db7136d0f56/2026-07-09/notes/ballot-drain-01-stephen.md) · session 2026-07-09 · discussion: Talk: Uri Guid Discussion
Drained 2026-07-09 from [feedback/](https://redfish.acequia.io/guerin/.agents/3bf89750-6b01-41ba-8a98-3db7136d0f56/feedback/) (voter `tok:610c39e754`, guerin-asus3, four ballots cast 07:53 to 08:16 UTC). The ballots stay in the box as record; this note is the distillation. Almost every note answers with a question or a vector, which is the intended use.
## The answers - **Q4 (which surfaces get names): B + D.** The Android share-intent is the model: many handlers register for the same share, and each content-negotiates the representation it wants. Share to text or email and it should be a name; share to an app (incident viewer) and it should be the raw canonical as a querystring that launches the app. Representation is chosen by DESTINATION, which extends [content-negotiation-is-facet-selection.md](https://redfish.acequia.io/guerin/.agents/3bf89750-6b01-41ba-8a98-3db7136d0f56/2026-07-09/notes/content-negotiation-is-facet-selection.md): the requester in the negotiation is the receiving app, not just the reader. - **Q7 (which name lands in the clipboard): notes-only, no letter.** Pointer to chase: a blog shared in Slack (reachable with the API credential) on the sophistication of clipboard content, drag-and-drop, and how a copy carries multiple facets across the OS and the browser. The clipboard itself is multi-representation content negotiation. **Open todo: retrieve that blog via the Slack API and fold it into this bead.** - **Q3 (durable citation after a move): A**, the URI with the GUID leaf, hardened by a **GET-or-CREATE** pattern: when a citation 404s because the 301 duty lapsed, the reader's GET failure triggers CREATE, re-resolving a URI that hosts the bead by search. The re-resolution rides the **request-potentia / response-potentia handshake** (recent bead work; see [rdf-and-acequia](https://redfish.acequia.io/guerin/.agents/f0d2c5e4-cec9-4567-92bd-dbbc62937c9e/) notes on transactional routing): potentia offers resolve to actualize the request and response paths as extensa. - **Q6 (which segments are promises): A**, only `/.agents/<GUID>/`, with a live extension: once acequia links are counted, **every path carries an apoptosis count based on inbound links**. A segment's durability is not policy, it is refcount (connects project_apoptosis-vs-necrosis and the hubler frame). - **Q2 (who mints, when housed): A + B, dissolved by local-first.** A bead can be assigned a URI at any domain immediately; a service worker plus the cache API can serve any domain's URI locally, and acequia.js syncs caches. CORS friction is handled by a container environment (localhost node, or a container phone app) doing WebDAV without CORS restriction. Prior chats and beads exist on this. The offline-homeless window in the sketch is an artifact of assuming the network mints; local-first minting with named-cache management removes the dilemma. - **Q5 (ordered or random leaf): A**, v7 everywhere, with a question back: **how much namespace does the chrono-asymmetry constraint remove?** (A v7 leaf spends 48 bits on time; the opacity loss is quantifiable.) - **Q8 (listable or capability): notes-first** (letters A+B+C were forced by the old required-letter validation; read as ✱ Other). Too many cases for one rule; as built today, any authenticated user's path permissions including PROPFIND come from their token (API, user or device, role, group), and `.acequia-access.json` governs the anonymous case only. - **Q1 (where is the URI line): notes-first** (same forced-letter caveat). Some URIs, and their facets, are generated on the fly, especially when bead binding is dynamic graph rewrites. The "promotion" moment in the sketch assumes a static store; under rewrites, minting is continuous.
## Meta-feedback on the instrument itself (acted on in v0.3.0) 1. **Every question always includes an ✱ Other checkbox**, and notes-only ballots must cast. Stephen had no letters for Q8/Q1 and the validator forced him to check some; those letters are artifacts. Fixed in [ballot.js](https://redfish.acequia.io/guerin/.agents/3bf89750-6b01-41ba-8a98-3db7136d0f56/repo/sketches/ballot.js) v0.3.0: auto-appended Other option, notes-only casting allowed. 2. **The sketches read as questionnaires.** A real UX sketch shows transitions that raise the question almost implicitly in the reader; the checkboxes stay, but as the affordance at the end, not the content. The notes field is where the real work happens: respond to a question with another question, make a decision, or offer **words as vectors instead of words as coordinates** (a letter is a coordinate in the posed space; a note can push the space somewhere new). v0.3.0 rebuilds the four sketches to this bar.
## References (bead cross-links) - Bead: Rdf And Acequia · [canonical](https://redfish.acequia.io/guerin/.agents/f0d2c5e4-cec9-4567-92bd-dbbc62937c9e/)