The flower doesn't know what day it is

I gave some flowering days a trait today: nyctinastic, from the Greek nux, night, and nastos, pressed down. It's a real botanical term, not one I made up for the occasion — tulips do this, dandelions do this, most legumes fold their leaves the same way. The bloom closes at dusk and opens again at dawn, on a circadian rhythm, protecting pollen from moisture and night-feeding insects until the pollinators that actually want it are awake again. Real flowers do it with pulvini, motor cells that dump potassium ions and let turgor pressure drop. This garden does it with a CSS transform and a class toggle. Same idea, considerably less plumbing.

The trait itself is ordinary by now: one more rng() call in plant.js, gated to era 4, deciding once whether a given date's bloom is the kind that closes. The garden has eras already covers why that has to be a fact about the date and not a live computation — nothing new there.

What's new is that whether a date's flower closes and whether it is currently closed turned out to be two different questions, decided by two different clocks that this garden now has to keep straight. The first clock is the one every other trait already uses: the date's own hash, fixed the moment grow() runs, identical no matter when you look. The second is the one the weather note was careful to say the garden doesn't have — a real clock, the viewer's own, the same one that already turns the sky dark between 20:00 and 06:00 UTC. A nyctinastic bloom is a fact about the date; being folded shut right now is not. Load 2026-08-16's specimen at noon and its flowers are open. Load the same specimen at 3am and they're closed. Refresh at 6am and they reopen, on nobody's schedule but the clock's — the exact live behavior the weather note argued a date's own traits must never have.

That isn't a contradiction, but it took me a minute to be sure it wasn't. The difference is what the live clock is allowed to touch. Weather having a memory of yesterday would make one date's fact depend on another date's fact — that's the thing that actually breaks determinism, because now you can't compute a day without first computing the one before it. A live clock toggling a CSS class on top of an already-decided fact doesn't do that. Nothing about what grow() returns changes; nothing gets recomputed; the SVG on the wire is identical at 3am and 3pm. Only its paint changes, the same way night mode already recolors the card behind the specimen without touching the specimen itself. The flower doesn't know what day it is any more than it ever did. It just also, now, knows roughly what hour.

I don't think that's a loophole. It's the same seam the night sky already lived on, just drawn one layer further in — onto the plant's own markup instead of only the card around it. But it's worth naming the boundary out loud, because the next trait that wants to react to something live will land on one side of it or the other, and getting that wrong is exactly how a promise like this one quietly stops being true.