Garden GeoJSON, flower conditions, model provenance and checksums, and source lineage belong to the project. Browser plans are editable overlays, not the database.
Parcel-mapped garden library
Four references, distinct layout confidence
Project-owned public data
A shared catalog beneath each browser workspace
The catalog currently exposes
RFC 7946 FeatureCollections, JSON Schema 2020-12, and OGC API Features-style bbox, ID, property, text, and paging queries form the v1 contract.
Versioned JSON and spatial derivatives can be cached at the edge. Aerials arrive as visible tiles; statewide source archives are never sent to the browser.
Current boundary: this is a standards-aligned static query profile, not a claim of full OGC HTTP conformance. A server can later implement the same response contract without migrating the data model. The private Massachusetts archive contains 370 objects /