The seed as an address

Evidence

Built directly. Harness: probe-cf.mjs, results in probe-cf.json. Playwright/Chromium, --use-gl=swiftshader, clipboard permissions granted.

What it is

Reproducibility should be shareable. Three things:

1. ?date=<ISO> in the address opens the page at that climate. The value is validated with Date.parse and passed to the ephemeris as opts.date; the ephemeris reads its origin once, at mount, so nothing downstream touches the clock — which is what makes the address stable.
2. The ephemeris's state is written into <head> as <meta> on every change: metanomicon:date, metanomicon:seed, metanomicon:citation. A machine can read the day's seed without running a frame — CANON-SEED rule 3, machine legibility is aesthetic.
3. "cite this frame" copies the citation Part III demands — field · <ISO> · seed <hex> · pitch 8 · v1.0 — and the note beside it rises from o-4 to o-1 and settles over one beat. Where the clipboard is refused the note shows the string instead, so the reader still gets it.

Measured, at ?date=2026-03-03T12:00:00Z

ephemeris date                    2026-03-03T12:00:00.000Z
seed                              8c7536d2
meta metanomicon:date             2026-03-03T12:00:00.000Z   (matches)
meta metanomicon:seed             8c7536d2                   (matches)
meta metanomicon:citation         field · 2026-03-03T12:00:00.000Z · seed 8c7536d2 · pitch 8 · v1.0
clipboard after the control       the same string
control                           167 × 45 px, tabIndex ≥ 0, sigil :focus-visible
note after the control            data-on="1", "copied · field · …"
same address, two fresh contexts  field canvas hash 1146480644 in both; 61,235 lit px in both
console errors                    0

"Same seed, same output" was an asserted discipline. Two contexts opening the same address and rendering the same bytes is the first time the page itself has demonstrated it.

Not established

• The citation's v1.0 is a literal; it does not read the artifact's own version label. A later publish without updating it would cite the wrong version. It is the one string in the stratum that is typed, not derived.
• Dates before the ephemeris's tested range (the Meeus formulas are Gregorian) were not exercised; Date.parse accepts them.
• Clipboard behaviour in browsers that require a transient activation stricter than Chromium's; the fallback path (show the string) was not exercised because Chromium granted the permission.