Waiting for a garden to open

A generated address gives a garden a name. Opening it requires the name to resolve, a certificate to be provisioned, and the browser to reach the place through HTTPS.

In April I changed the entry flow to wait for both active provisioning and a successful browser request. The system could record a certificate before the browser could enter. That interval needed an interface state of its own.

The pause gives infrastructure a perceptible duration. Naming a place and arriving there are separate events, agreed by different systems. I want the garden's entry to let someone feel that distinction rather than conceal it behind an immediate success message.

Later local rehearsal, 27 September 2026: a generated address waits for verified HTTPS. Disposable test data; this capture illustrates the entry condition described in the April note.