Invisible fields · the examples, explained
No particles. That is the point.
Every page in this section is a real interface on real data — an inbox, a market, a backlog, a calendar. Each one runs a full physics field, and none of them draw it. The field is a measuring instrument here, not a picture: data becomes bodies, the field measures them every frame, and the measurements come back as CSS variables your styles consume. What you see — type gaining weight, ink deepening, a row sinking toward quiet — is the field.
The one pipeline, all twelve pages
- dataa real dataset — citations, listens, launches, incidents
- bodieseach record becomes a body: its quantity sets
data-strength/ mass - measurethe field measures every frame — density, attention, load
- variablesmeasurements return as CSS custom properties (
--w,--d,--field-attention,--load) - you seeCSS renders them: weight, ink, anchor, fill — no canvas, no swarm
The page-level lesson, true of all twelve: the field does not care about the layout; it measures whatever geometry you give it. A list, a grid, a front page, a calendar — same instrument, different surface.
Why this beats hand-rolling it
Each page replaces a category of code you would otherwise write and maintain: the scoring scheme and the re-sort pass, the staleness timers, the priority tiers that drift until a meeting renormalizes them. Here the question each of those answered — what matters, what's related, what's gone stale — is answered continuously by the field, and the readout is simply already current. The scope is honest: the field measures the field — emphasis, attention, decay in the interface — never your users, your data layer, or your analytics.
Every example, as a correlation
- Evidence log-normalized trust → each paper's mass → heavier-cited work sits heavier in the type — weight, ink, and an anchor that deepens with consensus
- Inbox urgency (recency · votes · views) → mass inside ONE conserved budget → fresh asks read bold and sink as they age; brightening one literally dims the rest
- Market cap → mass (area + ink); the move → polarity → big caps take more page; direction is hue, magnitude is intensity
- Backlog activity + recency → mass; references bind items → active work reads heavy; referenced items move together; the cycle fills like a vessel
- Calendar imminence → mass, recomputed every second → the next launch literally gains weight as T−0 approaches — time itself drives the field
- Threads subtree size → mass; reply tempo → hue → big subthreads loom in the type; fast exchanges run warm, slow ones cool
- Dependencies downloads → mass; an advisory → charge → core dependencies read heavy; one advisory turns its line red and the graph feels it
- Fleet incident involvement → mass; severity → heat → troubled services swell and warm; quiet ones recede to gray
- Catalog review consensus → mass — the Evidence math, retargeted → well-attested books carry weight; each subject tints its spine
- Library listens → mass; the queue is a sink with capacity 8 → popular tracks read heavy; the queue visibly fills, saturates, and releases
- Memory the forgetting curve → decaying mass; review re-binds → unreviewed words fade in real time; a review springs the word back
- Newsroom pageviews → mass (placement + weight); day-over-day → polarity → the lead earns its slot; risers run warm, fallers cool, new entries gray
The honesty contract
Every page states its data provenance in a chip — live · checked Ns ago
after a successful refresh, snapshot · date otherwise — and each one's
explainer band names exactly which variables the field writes. If a page can't prove a
claim live, the claim isn't made.