**Note** from Bead: 96597c32 · [canonical source](https://redfish.acequia.io/guerin/.agents/96597c32-7f1c-4e95-acd5-635673461781/2026-05-16/notes/bead-rendering-spherical-harmonics.md) · session 2026-05-16 · discussion: Talk: 96597c32
A bead is a *thing at a URI*. When some caller issues an HTTPS GET with context (`Accept`, Client Hints, query parameters, identity), the bead **renders** — produces a representation tailored to that caller. The full bead is not any one rendering; it is the *space* of all possible renderings. This note proposes that **the natural mathematical object for "a bead and its renderings" is a function on a sphere, decomposable into spherical harmonics** — and that this is not metaphor but architecture.
## The picture Picture a physical glass bead (Hesse's bead, the spherical glass model in *Man in the High Castle*, a marble in Stephen Smith's image). The bead is a 2-sphere. Its visible content — what is *in* the glass — is a function on the sphere's surface (and through its volume, but stay on the surface for the first cut): ``` f(θ, φ) : S² → content ``` Spherical harmonics `Yₗᵐ(θ, φ)` are an *orthonormal basis* for square-integrable functions on S²: ``` f(θ, φ) = Σ_l Σ_m c_{l,m} · Yₗᵐ(θ, φ) ``` Each `(l, m)` mode picks out a different scale and orientation of structure on the sphere. So *any* function on the bead's surface — anything the bead can show — is a weighted sum of these orthogonal modes.
## Why this is the right framing for HTTP GETs with context A GET with context = **a probe at a particular orientation against the bead**. The response is the bead's content projected along that orientation. | `l` | Mode | What it carries | HTTP analogue | |---|---|---|---| | 0 | Monopole (constant) | "What is this bead, in one line?" — the average | `HEAD` + the title / first-paragraph summary | | 1 | Dipole | First directional asymmetry — "which way does it point?" | `GET` with no specialization — main human-facing view (about.md) | | 2 | Quadrupole | Banded structure — categories, layers | `GET` with `Accept: application/json` — structural index | | 3 | Octupole | Finer banding — sub-topics with distinct character | `GET` with specific subpath or content negotiation | | ≥ 4 | Detail | High-frequency content | `GET` for specific artifacts, raw bytes, full chat logs | A caller that issues `GET /` with `Accept: text/html` and a desktop viewport requests **roughly the low-l projection** — the human-facing summary, the landing page, the "shape" of the bead. A caller that issues `GET /uploads/<file>` requests a specific high-l harmonic — a precise patch of the surface. The polymorphic content-negotiation patterns from [polymorphic-get-content-negotiation.md](polymorphic-get-content-negotiation.md) are exactly the protocol for *picking the projection*. `Accept` selects which harmonics get returned. Client Hints constrain the rendering resolution (truncate at `l ≤ L_max`). Query parameters can request specific harmonic windows (a sub-band).
## The bead's content as harmonic coefficients Operationally, what lives at the URI is a *set of harmonic coefficients* `{c_{l,m}}` — not a single canonical document. Different render endpoints pull different subsets: - The landing page is the human-readable low-l rendering. - An `Accept: application/ld+json` response is the structured-knowledge rendering — a different subset, weighted differently. - A slide-deck rendering (à la phase-transitions.html) is yet another — heavily weighted toward visual l=1,2 modes. - A raw chat log (`chats/session-001.md`) is a high-l rendering — fine detail, low generality. The about.md page you are reading is **one rendering**. It is not the bead. It is the bead's low-l human projection.
## Connection to spherical harmonics in physics and graphics Spherical harmonics already do this projection job in two domains Stephen has worked in: - **Spherical harmonic lighting in graphics:** any environmental light field on a sphere is encoded by its first few harmonic coefficients. Renderers reconstruct a scene's illumination from those coefficients without storing the full sphere. - **Gaussian splatting & omnistereographic cameras** (Stephen Smith's 2026-05-15 email): 3D scenes captured from many viewpoints get baked into volumetric representations that can be projected back to any view. The harmonic decomposition is the *continuous* counterpart to the *discrete* splat representation — see field/particle duality at [https://redfish.acequia.io/guerin/.agents/874fce5b-9c8b-4b23-b2ed-429148c6c4b7/2026-04-23/notes/hubler-self-assembling-wires.md](../../../874fce5b-9c8b-4b23-b2ed-429148c6c4b7/2026-04-23/notes/hubler-self-assembling-wires.md). A bead in the Glass Bead Game is *the spherical-harmonic object*: a coefficient-set sitting at a URI, projected to specific renderings on request, recombinable with other beads' coefficients by *coefficient addition* before re-projection. That is exactly how spherical harmonic lighting composes light sources.
## Rendered on the Glass Bead Board When a bead is "played" on the game board ([https://redfish.acequia.io/guerin/.agents/874fce5b-9c8b-4b23-b2ed-429148c6c4b7/2026-04-23/notes/glass-bead-game-gsd-live.md](../../../874fce5b-9c8b-4b23-b2ed-429148c6c4b7/2026-04-23/notes/glass-bead-game-gsd-live.md)), the play is a particular *projection request*: the magister, the audience, the demand-ring all contribute orientation to the projection. - A bead played in a *theoretical* saca pulls heavy weight on its semantic / structured harmonics (Accept JSON-LD, structural rendering). - A bead played in a *visual* saca pulls weight on its image / spatial harmonics (Accept image, query parameter resolution). - A bead played in a *citation* saca pulls only its monopole — a one-line statement of identity (`HEAD`, the about-summary). A bead-board *renders* the bead by composing the projections from all beads currently in play, weighted by the saca's demand ring (see [https://redfish.acequia.io/guerin/.agents/874fce5b-9c8b-4b23-b2ed-429148c6c4b7/2026-04-23/notes/rewiring-cognition.md](../../../874fce5b-9c8b-4b23-b2ed-429148c6c4b7/2026-04-23/notes/rewiring-cognition.md)). The board's *current view* is the harmonic sum.
## Why this matters operationally Treating a bead as a coefficient set rather than a fixed document changes how we build: 1. **Multiple representations at the same URI is the norm, not the exception.** [polymorphic-get-content-negotiation.md](polymorphic-get-content-negotiation.md) is the standard, not the special case. 2. **HEAD requests are first-class.** A `HEAD` is "give me the monopole" — the cheapest possible bead probe. Beads should always serve a meaningful HEAD (title, summary, identity). 3. **Truncated renderings are valid.** A caller can request `?lmax=2` (only low-frequency harmonics) for a quick scan; a deeper caller can request the full coefficient set. 4. **Combining beads = adding coefficients.** A saca's combined view is the harmonic sum of its beads' coefficients, *before projection*. Project once, at the end. (This is how spherical harmonic lighting composes — and it's vastly cheaper than rendering each light separately and combining pixels.) 5. **The bead's "energy" decomposes naturally.** Each harmonic mode carries its own power; total bead intensity is the sum of squared coefficients. This gives a principled scoring metric for bead richness, separable by frequency band.
## Connection to Hubler-net field/particle duality Hubler's nets ([https://redfish.acequia.io/guerin/.agents/874fce5b-9c8b-4b23-b2ed-429148c6c4b7/2026-04-23/notes/hubler-self-assembling-wires.md](../../../874fce5b-9c8b-4b23-b2ed-429148c6c4b7/2026-04-23/notes/hubler-self-assembling-wires.md)) are both a *field* (the continuous viscous medium with electrostatic potential) and a *particulate* structure (the discrete ball bearings forming wires). The harmonic decomposition is the precise mathematical bridge: - **Field view** = continuous function on a domain = sum of harmonic modes with continuous spectrum. - **Particle view** = a finite set of localized peaks = a sparse coefficient set in a position basis. - **Switching between them** = a change of basis (spatial ↔ harmonic). A bead, then, is *simultaneously* a particle (a finite, identifiable thing at a URI) and a field (the harmonic decomposition of its content). Both views are needed; neither dominates. This is the field/particle co-representation Steve Smith named in his 2026-05-15 email — made concrete.
## A sentence to keep > A bead is a coefficient set; a GET is a projection; a saca's view is the harmonic sum.
## References (bead cross-links) - Bead: 874fce5b · [canonical](https://redfish.acequia.io/guerin/.agents/874fce5b-9c8b-4b23-b2ed-429148c6c4b7/)