**Note** from Bead: Rdf And Acequia · [canonical source](https://redfish.acequia.io/guerin/.agents/f0d2c5e4-cec9-4567-92bd-dbbc62937c9e/2026-07-08/notes/05-make-link-worked-example-wires-mp4.md) · session 2026-07-08 · discussion: Talk: Rdf And Acequia
Captured from Stephen's what-if (2026-07-08, verbatim in the [chat log](https://redfish.acequia.io/guerin/.agents/f0d2c5e4-cec9-4567-92bd-dbbc62937c9e/2026-07-08/chats/2026-07-08-rdf-and-acequia.md)). **Status: concept note, potential-TODO. No make-link command is built or specified here.**
## The scenario (all facts verified) Earlier today a separate Claude chat, outside any bead, was asked where hubler's self-assembling-wires.mp4 lives. It grepped the sites tree, found the copies, and recommended one for the WedTech slides (bead [9d343253](https://redfish.acequia.io/guerin/.agents/9d343253-c279-47ac-a066-cc31ce505782/about.md), in progress today). That chat's durable citation, per the chat-citation convention: `(sessionId: 83ffbc11-26e6-4288-a3b7-20dd2b0422c5, leafUuid: 14782f0e-6fe2-4d18-89df-277ab99837d6)`, a session file on disk outside the namespace. The three URIs it found (verified against the tree just now; the `-clip` and `-web` variants sit alongside): 1. [https://redfish.acequia.io/videos/self-assembling-wires.mp4](https://redfish.acequia.io/videos/self-assembling-wires.mp4) - the chat's recommendation, general-purpose 2. [https://waldo.acequia.io/gsd-vis-2487/guerin/self-assembling-wires/self-assembling-wires.mp4](https://waldo.acequia.io/gsd-vis-2487/guerin/self-assembling-wires/self-assembling-wires.mp4) - under the GSD course folder 3. [https://harvardviz.live/videos/self-assembling-wires.mp4](https://harvardviz.live/videos/self-assembling-wires.mp4) - the Harvard-facing copy **All three are byte-identical**: `sha256:29b4b5013429766bbac8b79d3d148a870abd6302dcf5c2f9193163a8857f0ebe` (checked locally today). One resource, three homes, zero GUIDs. Yet GUID-bearing beads refer to it: the [Hubler ecology bead](https://redfish.acequia.io/guerin/.agents/874fce5b-9c8b-4b23-b2ed-429148c6c4b7/) (`874fce5b`, the likely referent of "bead hubler-nets") is the video's conceptual home, and the WedTech bead is about to embed one of the URLs.
## What make-link would mint (the concept) A make-link on this example creates one **acequia-link resource**, owned by the hubler bead, that is a born-reified statement (note [01](https://redfish.acequia.io/guerin/.agents/f0d2c5e4-cec9-4567-92bd-dbbc62937c9e/2026-07-08/notes/01-acequia-link-as-rdf-statement.md)) with all four identifier species from note [03](https://redfish.acequia.io/guerin/.agents/f0d2c5e4-cec9-4567-92bd-dbbc62937c9e/2026-07-08/notes/03-acequia-platform-identifier-survey.md) in their right roles: ```json { "id": "https://redfish.acequia.io/guerin/.agents/874fce5b-.../links/<link-GUID>", "type": "sameContent", "content": "sha256:29b4b5013429766bbac8b79d3d148a870abd6302dcf5c2f9193163a8857f0ebe", "homes": ["<the three URIs above>"], "preferred": "https://redfish.acequia.io/videos/self-assembling-wires.mp4", "provenance": { "chat": "(sessionId: 83ffbc11-26e6-4288-a3b7-20dd2b0422c5, leafUuid: 14782f0e-6fe2-4d18-89df-277ab99837d6)" } } ``` - The **hash** is the GUID the mp4 never had: content identity, mintable by anyone from the bytes, self-verifying. "Same resource" becomes checked, never asserted. - The **link GUID/URI** gives the *statement* identity: the claim "these three URIs serve one content, prefer redfish" becomes citable, and the WedTech slide could cite the link instead of a raw URL, surviving any single copy moving (the [Q3 migration question](https://redfish.acequia.io/guerin/.agents/3bf89750-6b01-41ba-8a98-3db7136d0f56/2026-07-08/notes/big-questions-for-acequia-apps.md) answered by indirection). - In RDF terms this is `owl:sameAs` done right: sameness grounded in a content address rather than a social claim, with the equivalence statement itself addressable (RDF's sameAs has no native home; ours would).
## Why the chat's homelessness matters The choosing chat is a CB-style explorer in the beads-skill sense: its finding has no charge in the namespace and decays with the session file. Today it worked because Stephen remembered it hours later; the finding survives only if a writer commits it. make-link is exactly that commit, shrunk to its minimum: one small resource instead of a whole retro-bead. The chat file stays where it is as provenance; the link carries the citation.
## Open questions (for the dock, before any build) 1. Where do links live: under the owning bead (`<bead>/links/<GUID>`), or in a first-class links collection per parciante? The owning-bead answer keeps the namespace rule intact. 2. Is `make-link` a fifth lifecycle verb beside /bead-start, /pause, /end, /sync, or a skill any scribe runs inline? 3. Does the link assert `preferred`, or is preference a per-context resolution (the least-action answer from note [04](https://redfish.acequia.io/guerin/.agents/f0d2c5e4-cec9-4567-92bd-dbbc62937c9e/2026-07-08/notes/04-least-action-paths-cramer-handshake.md): the name offers homes, the handshake picks one per request)? 4. Should sameContent links be re-verified on read (hash the target) or trusted after minting, with staleness handled by TTL like responses?
## References (bead cross-links) - Bead: Wedtech Beads 2026 07 08 · [canonical](https://redfish.acequia.io/guerin/.agents/9d343253-c279-47ac-a066-cc31ce505782/) - Bead 83ffbc11 · [canonical](https://redfish.acequia.io/guerin/.agents/83ffbc11-26e6-4288-a3b7-20dd2b0422c5/) (no page yet) - Bead 14782f0e · [canonical](https://redfish.acequia.io/guerin/.agents/14782f0e-6fe2-4d18-89df-277ab99837d6/) (no page yet) - Bead: 874fce5b · [canonical](https://redfish.acequia.io/guerin/.agents/874fce5b-9c8b-4b23-b2ed-429148c6c4b7/) - Bead: Uri Guid Discussion · [canonical](https://redfish.acequia.io/guerin/.agents/3bf89750-6b01-41ba-8a98-3db7136d0f56/)