readsLaunch Library's T−0 times
becomesimminence → mass, recomputed every second
writes--w
you seethe next launch literally gains weight as T−0 approaches — time itself drives the field

No canvas is drawn here — the field is invisible; these variables are its only output. Without it you would build: a countdown per row and a cron that re-sorts.

Data honesty

Data source: Real Launch Library 2 data (thespacedevs.com) — upcoming rocket launches with T−0 times, free API (attribution).
Snapshot: Committed snapshot in src/data/examples/, stamped snapshotAt on refresh via scripts/snapshot-examples.mjs — the build never fetches, so it is deterministic.
Live refresh: Upgrades to live in the browser; additionally, imminence (mass) is recomputed every second in-page as T−0 approaches. The committed snapshot is the SSR baseline.
Not claimed: The field reads imminence as mass. It does not predict whether a launch will happen on time or succeed — it makes the countdown drive weight in real time.

Fundamental · invisible fields · calendar

The next launch pulls hardest.

A launch schedule lists every mission at the same weight: a rocket lifting off in nineteen hours sits in the same row style as one penciled in for the end of the month. This is the same schedule from Launch Library 2 run as a field: imminence is gravitational mass, and the weight ramps as T−0 approaches — heavier type, darker ink, a stronger left anchor.

This is the one page where the field's input is time itself. The soonest launch is the biggest thing on the wall — a featured "next up" card with the countdown as its centerpiece — and the rest lay out as a day agenda, a seven-column week, or a month grid: three calendar geometries over the same thirty launches. A 1-second clock recomputes every weight and re-picks the featured launch in whichever view is mounted, so when a window passes the wall advances on its own; passed and undated launches drift to a dimmed "unscheduled" cluster. Toggle the field off and the wall flattens — but the countdowns keep ticking, because they're data, not field.

Field

Layout

Color by

size = imminence — weight ramps as T−0 approaches, recomputed every second · color = launch status — Go is confirmed, TBC awaits confirmation

Aa size = imminence — the next launch is the biggest thing on the wall
color = status (Go teal · TBC amber · TBD dim)
T− the countdown is live — when a window passes, the wall re-picks "next up"
the ink is live — --w is the clock's imminence and --cat the status lens; --d is the engine's local density (hold a card and the field gathers — the hero's countdown burns brighter) and --field-attention the pattern's eased attention as you scroll.

Next up

Mir | Demo Flight

Agency for Defense Development · Mir

ADD Offshore launch platform · Sea Launch

T− 16:35:19 TBC

Wednesday, November 4UTC

Mir | Demo Flight Agency for Defense Development · Mir ADD Offshore launch platform · Sea Launch

T− 16:35:19 TBC LEO

Thursday, November 5UTC

Long March 2C | Unknown Payload China Aerospace Science and Technology Corporation · Long March 2C Launch Complex 3 (LC-3/LA-1) · Xichang Satellite Launch Center, People's Republic of China

T− 2d 03:35:19 Go
Long March 12 | SatNet LEO Group TBD? China Aerospace Science and Technology Corporation · Long March 12 Commercial LC-2 · Wenchang Space Launch Site, People's Republic of China

T− 2d 08:50:19 Go LEO

Friday, November 6UTC

Ceres-2 | Unknown Payload Galactic Energy · Ceres-2 Launch Area 95A · Jiuquan Satellite Launch Center, People's Republic of China

T− 3d 11:10:19 Go

Saturday, November 7UTC

Falcon 9 Block 5 | USSF-432 SpaceX · Falcon 9 Block 5 Space Launch Complex 4E · Vandenberg SFB, CA, USA

T− 3d 12:21:19 Go LEO

Monday, November 9UTC

Falcon 9 Block 5 | USSF-xxx ("R-5") SpaceX · Falcon 9 Block 5 Space Launch Complex 4E · Vandenberg SFB, CA, USA

T− 5d 14:52:19 TBC LEO

Friday, November 20UTC

Long March 8A | SatNet LEO Group TBD? China Aerospace Science and Technology Corporation · Long March 8A Commercial LC-1 · Wenchang Space Launch Site, People's Republic of China

T− 16d 22:35:19 TBC LEO

Tuesday, November 24UTC

Soyuz 2.1b | Progress MS-36 (97P) Russian Federal Space Agency (ROSCOSMOS) · Soyuz 2.1b 31/6 · Baikonur Cosmodrome, Republic of Kazakhstan

T− 20d 16:38:19 TBC LEO
Long March 12 | SatNet LEO Group TBD? China Aerospace Science and Technology Corporation · Long March 12 Commercial LC-2 · Wenchang Space Launch Site, People's Republic of China

T− 20d 18:35:19 TBC LEO

Thursday, November 26UTC

Spectrum | AT-Astra and Others (Spectrum Flight 3) Isar Aerospace · Spectrum Orbital Launch Pad · Andøya Spaceport

T− 23d 07:35:19 TBC SSO

Sunday, November 29UTC

Falcon 9 Block 5 | Cygnus CRS-2 NG-25 SpaceX · Falcon 9 Block 5 Space Launch Complex 40 · Cape Canaveral SFS, FL, USA

T− 26d 03:24:19 Go LEO

Unscheduledwindow passed · date TBD

Electron | The Sea God Surveys (iQPS Launch 9) Rocket Lab · Electron Rocket Lab Launch Complex 1A · Rocket Lab Launch Complex 1, Mahia Peninsula, New Zealand

window passed · snapshot Success LEO
Kinetica 2 | SpaceSail Polar Group #17 CAS Space · Kinetica 2 Launch Area 140 · Jiuquan Satellite Launch Center, People's Republic of China

window passed · snapshot Success PO
Vulcan VC6L | Amazon Leo (LV-01) United Launch Alliance · Vulcan VC6L Space Launch Complex 41 · Cape Canaveral SFS, FL, USA

TBD TBD LEO
Electron | The Mountain God Rises (iQPS Launch 10) Rocket Lab · Electron Unknown Pad · Rocket Lab Launch Complex 1, Mahia Peninsula, New Zealand

TBD TBD LEO
Ariane 64 Block 2 | Amazon Leo (LE-04) Arianespace · Ariane 64 Block 2 Ariane Launch Area 4 · Guiana Space Centre, French Guiana

TBD TBD LEO
Long March 2F/G | Shenzhou 24 China Aerospace Science and Technology Corporation · Long March 2F/G Launch Area 91 (SLS-1 / 921) · Jiuquan Satellite Launch Center, People's Republic of China

TBD TBD LEO
Falcon 9 Block 5 | NROL-195 SpaceX · Falcon 9 Block 5 Space Launch Complex 4E · Vandenberg SFB, CA, USA

TBD TBD LEO
Falcon 9 Block 5 | OneWeb 21 SpaceX · Falcon 9 Block 5 Space Launch Complex 4E · Vandenberg SFB, CA, USA

TBD TBD PO
Falcon 9 Block 5 | Starlink Group 15-21 SpaceX · Falcon 9 Block 5 Space Launch Complex 4E · Vandenberg SFB, CA, USA

TBD TBD LEO
LVM-3 | Gaganyaan-1 Indian Space Research Organization · Launch Vehicle Mark-3 (GSLV Mk III) Satish Dhawan Space Centre Second Launch Pad · Satish Dhawan Space Centre, India

TBD TBD LEO
PSLV-XL | TDS-01 Indian Space Research Organization · PSLV XL Satish Dhawan Space Centre First Launch Pad · Satish Dhawan Space Centre, India

TBD TBD GTO
Starship | Flight 15 SpaceX · Starship V3 Orbital Launch Pad 2 · SpaceX Starbase, TX, USA

TBD TBD LEO
Ariane 62 | Metop-SG B1 Arianespace · Ariane 62 Ariane Launch Area 4 · Guiana Space Centre, French Guiana

TBD TBD SSO
Falcon 9 Block 5 | SDA Tranche 2 Transport Layer D SpaceX · Falcon 9 Block 5 Unknown Pad · Cape Canaveral SFS, FL, USA

TBD TBD PO
Falcon 9 Block 5 | SDA Tranche 2 Transport Layer E SpaceX · Falcon 9 Block 5 Space Launch Complex 4E · Vandenberg SFB, CA, USA

TBD TBD PO
LVM-3 | GSAT-32 (GSAT-N3) Indian Space Research Organization · Launch Vehicle Mark-3 (GSLV Mk III) Satish Dhawan Space Centre Second Launch Pad · Satish Dhawan Space Centre, India

TBD TBD GTO
New Glenn | Blue Ring-1 Blue Origin · New Glenn Launch Complex 36A · Cape Canaveral SFS, FL, USA

TBD TBD GTO
Falcon 9 Block 5 | BlueBird 14-16 (Block 2 #9-11) SpaceX · Falcon 9 Block 5 Space Launch Complex 40 · Cape Canaveral SFS, FL, USA

TBD TBD LEO
Falcon 9 Block 5 | CHORUS SpaceX · Falcon 9 Block 5 Unknown Pad · Cape Canaveral SFS, FL, USA

TBD TBD LEO

How it's built

Every launch is an ordinary <li> with its NET timestamp in a data attribute. A 1-second clock turns distance-to-T−0 into a weight, writes it back as a CSS custom property, and the type carries the measurement. No canvas, no chart library — the only moving part is time. On top of the clock sit two live channels the engine writes back every frame — --d (local density, gathered by data-hot on hover) and --field-attention (the pattern's eased attention) — which touch only ink; the 1 Hz weight ramp is untouched. The day / week / month toggle re-renders the records zone from the same launch list and re-applies the scoped field over the new bodies — full cards in day, compact cards in week, chips in month — and every channel keeps working.

1 — each launch is a field body

HTML

<!-- each launch is a body. data-feedback: the engine writes
     --d (live local density) back every frame. data-hot:
     hover/focus a card and the field gathers toward it —
     hold the hero and its countdown burns brighter. -->
<li
  data-body="attract"
  data-strength="1.43"
  data-feedback
  data-hot
  data-net="2026-06-11T04:00:00Z"
  data-status="Go"
  style="--w: 0.646; --cat: #2dd4bf;"
>
  <!-- name · provider · countdown -->
</li>

data-net — the no-earlier-than instant the clock measures against
data-strength — gravitational mass, re-set every second
--cat — the status color the CSS mixes in
data-feedback — opt in to --field-* writebacks (--d)
data-hot — hover/focus gathers the field toward this card

2 — one clock, three geometries

// the world-time kernel — 1 at T−0,
// log-ramping from 0 across the horizon:
import { imminence, weightToStrength }
  from "@fundamental-engine/core";

// every second, for every launch:
const netMs = Date.parse(row.dataset.net);
const w = netMs > Date.now()
  ? Math.max(0.08, // the page's floor
      imminence(netMs, Date.now(),
        30 * 24 * 36e5)) // 30-day horizon
  : 0.08; // window passed · snapshot

row.style.setProperty("--w", w);
row.dataset.strength =
  weightToStrength(w).toFixed(2);
// the 0.4..2.0 attract-body contract

// the scoped field runs invisible (renderless)
// and asks for the attention metric lane —
// the pipeline writes --field-attention per
// card (eased 0..1):
field = applyPattern(zone, base, {
  renderless: true,
  extraMetrics: ["attention"],
  /* …bodies below */
});

// three geometries, one contract — every
// view renders the same 30 launches
// as the same bodies:
const render =
  { day, week, month }[view];

viewAc?.abort(); // the old view's
viewAc =         // listeners die with it
  new AbortController();
zone.innerHTML = render(records, now);

// the bodies changed — destroy the
// scoped field and re-apply the pattern
// over the new geometry:
field?.destroy();
const bodies = [
  ...zone.querySelectorAll("[data-body]"),
  hero,
];
field = applyPattern(zone, base, {
  bodies,
  annotateBodies: false,
  renderless: true,
  extraMetrics: ["attention"],
});

// the field doesn't care about the
// layout — it measures whatever
// geometry you give it.

The soonest launch is the heaviest; as its T−0 approaches the ramp steepens, so the page's center of gravity slides toward the pad. The day / week / month toggle swaps the entire geometry under the same bodies — the field doesn't care about the layout; it measures whatever geometry you give it. That's the lesson of this page.

3 — CSS reads the field's output

CSS

.cal-row {
  /* --w = imminence (1 Hz clock) · --d = live engine
     density, data-hot gathers it · --field-attention =
     the pattern's eased attention */
  --live: var(--d, 0);
  opacity: calc(0.58 + var(--w) * 0.42);
  box-shadow: 0 0 calc(var(--live) * 16px) -6px
    color-mix(in srgb,
      var(--cat) calc(var(--live) * 55%), transparent);
}
/* the rail dot charges with the density */
.cal-row::before {
  transform: translateY(-50%)
    scale(calc(1 + var(--live) * 0.35));
}
/* hold the hero — the T-minus digits burn brighter */
.cal-hero-count {
  text-shadow: 0 0 calc(var(--live) * 18px)
    color-mix(in srgb,
      var(--cat) calc(var(--live) * 65%), transparent);
}

Read the docs → See patterns →