**Note** from Bead: 874fce5b · [canonical source](https://redfish.acequia.io/guerin/.agents/874fce5b-9c8b-4b23-b2ed-429148c6c4b7/2026-04-23/notes/polarized-links.md) · session 2026-04-23 · discussion: Talk: 874fce5b
**Date:** 2026-04-23 **Context:** Architecture chat. Bridges [self-assembling-wires/ecology.md](self-assembling-wires/ecology.md) (the Hubler frame) and [advanced-wave.md](advanced-wave.md) (bidirectional accounting). See [../chats/2026-04-23-ecology-architecture-chat.md](../chats/2026-04-23-ecology-architecture-chat.md).
## The claim A hyperlink, reference, citation, or URI-binding in this ecology is not a neutral pointer. It is a **polarized GET**: a directional coupling between a linker (source) and a linked agent-resource (sink), carrying charge along the same field gradient that shapes the Hubler wire network. - The link has two ends with distinct roles. Linker at +, linked resource at −, or vice versa depending on which end carries more charge at a given moment. - When the link is exercised (a GET happens, a user clicks, an agent dereferences), charge flows. Value moves forward (retarded wave); reputation/attention/wealth flow back (advanced wave). - In aggregate, many polarized links pointing at the same resource align that resource with the field gradient — it becomes a high-charge node. Mass (further links, further agents) is recruited toward it. - The **topology of all links in the namespace IS the wire network at any moment.** Not a metaphor — the same mathematical structure.
## Why "polarized" and not just "directed" A directed link is topological: arrow from A to B. A polarized link carries a vector quantity: charge, intensity, temporal orientation. Several consequences: - **Activation matters.** A link that's never followed is a latent dipole — structure without flow. A link that's followed often is an active conduit. - **Polarity can flip or decay.** A resource that was high-charge last year may not be now. The links still exist topologically but the polarization is weak. - **Context polarizes differently.** The same GET from a vetted agent vs. an unknown scraper carries different charge. ACLs and rate limits are polarity filters.
## Connection to the three channels of advanced-wave flow Each exercised link carries all three advanced-wave components on the return: - **Attention** — immediate, bandwidth-limited signal. "A GET happened." Cheapest channel; most common. - **Reputation** — accretes over many GETs, especially from signed/identified agents. Shifts the sink's standing in the ecology. - **Wealth** — only when the link invokes an explicit transaction (paid call, metered endpoint, sponsored access). Rare per GET but high-weight when present. An advanced-wave ledger entry is triggered by the polarized GET; it records what flowed on both sides at once.
## What makes agents-at-URIs special in this picture Files are passive bearings — they polarize when a GET hits them but can't respond dynamically. An agent at a URI is an active polarizable node: - It can adapt its response to who's asking (negotiated APIs; capability-based content) - It can emit its own advanced-wave signals (updated reputation, new links to other resources, acknowledgments written back into the ledger) - It can reverse-proxy to other sources, bridging the link further down the field - It can apoptose when its charge drops (policy-driven removal, not ref-count-driven) An ecology of agent-nodes is a *more polarizable* network than an ecology of static files. The wires form faster, the topology adapts to shifting gradients, and the advanced-wave flows are richer.
## Observables we already know are projections of this structure - **PageRank and backlink graphs** — static snapshots of polarized-link density; rank = integrated charge - **Citation networks in academia** — polarized links across published artifacts; reputation is the advanced-wave accumulation - **HATEOAS hypermedia** — Fielding-REST specifies that responses embed polarized links to next-state transitions; the API literally *is* the local polarization pattern - **Social-graph "influence" metrics** — attempts to measure advanced-wave reputation accumulation through polarized-link networks - **Web-of-trust systems** — polarized links signed with identity, so the polarity itself is verifiable Each of these is a partial observable of the same physical structure. A commons built with polarized GETs as a native first-class mechanism subsumes all of them.
## Consequences for the ecology - **Every link you write is a commitment.** Adding a reference polarizes the field; the linked resource gets charge. Gratuitous links dilute the gradient. - **Agent-resources at URIs are preferable to static files** whenever the node needs to participate dynamically in the network (respond to capabilities, tailor responses, emit its own advanced-wave signals). - **Apoptosis matters for topology health.** Dead resources that still accumulate links act as shorts — charge flows toward them without productive flow-through. Polarized-apoptosis is the cleanup. - **Link hygiene is mayordomo concern.** When links become uncoupled from their targets (rot, redirect loops, orphan references), the field becomes noisy. Mayordomos can audit and prune. - **22/22/56 topological invariants** should emerge observationally in healthy parts of the ecology. If you measure the link-graph and endpoints ≠ ~22%, branches ≠ ~22%, connectors ≠ ~56%, the network is not yet optimal-transport-shaped. Diagnostic, not target.
## When to invoke this frame - Any link or binding design — the polarity matters, not just the destination - Any PageRank-adjacent question — it's the static projection of a live field - Any "why is this resource not getting attention" question — check the polarization topology, not just the existence of links - Any agent-vs-file decision at a URI — ask how polarizable the node needs to be - Any question about how attribution/reputation actually flows — through the polarized-link topology, following the advanced-wave