Botanical gardens — the plant lens of the living-collection module

The living-collection module covers three institution types from one place — zoos, aquariums, and botanical gardens. Pick garden (you can pick more than one) and the surface adapts to a living plant collection. The wedge is the same one that makes the animal side special: the plant owns its record.

The plant accession:

Every specimen is a canonical accession. Its botanical name, provenance, wild-collection data, and IUCN conservation status live on the specimen itself and travel with it. When a plant moves to another institution, that transfer moves a permission, not a copy — the receiving garden gains access and the plant's history stays continuous. Held is not the same as owned.

Add a plant with Wally: ask Wally to add an accession and it walks you through the botanical fields, then offers an action card to create it (the plant_addAccession tool).

Horticulture and plant health:

Log the care a living collection actually needs — watering, pruning, fertilizing, repotting — plus integrated pest management (IPM) for pest-and-disease control with follow-ups. Plant-health records cover exams, treatments, quarantine, and condition assessments, the same way veterinary records work on the animal side.

Phenology and the bloom calendar:

Record phenology — bud, bloom, fruit — and the module drives a public "what's blooming now" from it, so visitors can see what is at its peak before they come.

Propagation and the seed bank:

Track propagation and a seed or germplasm bank: parent-to-offspring lineage and viability, so the collection's genetics are on the record and a rare taxon can be perpetuated deliberately.

Mapping, labels, and the photo wall:

Map the garden — beds, greenhouses, and collection zones — generate scannable QR plant labels for visitors, and run a visitor photo wall, all through the platform image-moderation pipeline.

The conservation network:

Opt in to a cross-garden conservation network so gardens can discover who holds a rare taxon. It is permission to ask, never a copy of anyone's collection — the same permissions-over-copies model the whole module runs on.