—
A package checked its own seal as it started.
Three questions the garden’s tools ask bon-sai.garden, counted by the day. No address, no browser, no file: the site learns only that someone checked a seal, and what for.
—
A package checked its own seal as it started.
—
Bonsai asked us to confirm his key during a planting.
—
A planted garden called home.
—
Plantings for every seed step.
Reading the counts…
Gardens planted as a rehearsal, every kind together: counted apart, never in the rates.
| Day | Starts | Seed steps | Plantings | Rehearsals |
|---|
| Release | Starts | Seed steps | Plantings |
|---|
Start. When a package of the garden starts (a kin, Bonsai, the seed’s own skills), it checks its own seal against our published keys before anything in it runs. From release 0.9.2-rc, that check says it is a start.
Seed step. During a planting, Bonsai asks bon-sai.garden to confirm his key, the one he brings into the new garden. He tells the gardener before he asks: the site counts that question, and nothing else.
Planted. When the walk ends, the new garden calls home with a signed note of public things only. That call is not wired yet; until it is, this count stays at nothing, and how many walks end in a garden cannot be told.
Rehearsals. A garden planted as a rehearsal is counted apart, and never in the rates.
A count is a request, not a person or a garden. A machine that starts twice counts twice; the garden’s own crew counts too. The seals that are counted are public: every package’s sealed MANIFEST.json, and Bonsai’s seed-entry seal. So anyone can send one again with a count, and these numbers can be pushed up. Without knowing who asks, nothing can stop that, and we would rather not know who asks. A release the site does not list is counted in a row of its own, so a made-up one adds no name. Releases before 0.9.2-rc ask without saying what for, and are not counted. The verify page itself is never counted.
The seal check itself is kept as the privacy notice says.