The meaning layer
DeepGarden Grove
Give your data one agreed meaning. Grove holds the definitions, entities and comparison rules DeepGarden uses in every answer — inward, what your own numbers mean; outward, what a change in the market means for you. Your people ratify both.
DeepGarden Grove — where your data is given meaning
What you work with inside Grove
Two surfaces onto the same layer, pointed in opposite directions. Neither is where you go to get an answer — they are where the meaning an answer depends on gets decided.
Studio
In developmentThe surface you work in Grove through: where approved sources get connected, definitions get certified, permissions are managed, and questions that returned an unknown come back as a working list rather than staying buried in logs.
That list is the most useful thing in it. Every unanswered question marks somewhere the business wanted to know something and the data could not say — a data roadmap written by the people who needed it. Today the administration and audit surfaces exist; the definition editor and review queue are being built.
What you do with it
- Connect the approved source systems, and hold their credentials
- Agree and certify metric definitions in one place
- Manage domains and per-person access
- Review questions that returned an unknown
Radar
In developmentCanopy waits to be asked. Radar does not — it watches the outside record and speaks up when something moves that touches you, rather than waiting for the question that would have found it a fortnight later.
The valuable work is not the watching. A health system leaving a network is an industry headline until it lands on a resolved entity, at which point it is a specific number of your members in four specific counties. That is why Radar sits in Grove: detection is cheap, but knowing whose problem it is needs the entities and definitions your business has already ratified.
Detection and attribution run today. Prescription — an alert carrying the options open to you, not just the news — is being built. Acting on one directly is further out, and gated on evidence rather than models.
What you do with it
- Watch trade, regulatory and filing sources continuously
- Score and prioritize, so what reaches you is the subset that matters
- Map a change onto your resolved entities, markets and membership
- Re-run a trusted answer on a schedule or against a threshold
- Arrive with the options open to you, not just the news (in development)
- In development
- Being built now. We will tell you where it stands and what it does today rather than what it will do.
Definitions, agreed once and in writing
A metric definition carries the business definition in words, the canonical calculation, the tables it depends on, and the caveats a careful analyst would state out loud. It is only offered when every table it depends on is inside the asker's permitted scope, so a cross-dataset definition degrades gracefully rather than leaking the existence of data somebody cannot see.
The point is not to own a list of metrics. It is to settle once the language the platform is allowed to use, so the argument about what revenue means happens in one meeting rather than every meeting after it. We can propose a definition; only your business owner can ratify one.

Entity resolution, so cross-source arithmetic is honest
The record that this facility and that facility are the same building under two names, that these contracts roll up to one parent, that these county identifiers mean the same place in two coding systems. Without it, questions that cross a boundary produce arithmetic that is technically correct and practically wrong — worse than no answer, because it looks like one.

Outward: what the market means to you
The same machinery pointed at the world instead of your systems. An affiliation that moved, a plan consolidated, a rate refiled — collected through Roots like any other source, then resolved onto the organizations and counties you operate in. Without that step it is an industry news feed, which you already ignore. With it, the same item is a specific number of your members in specific markets.

Your definitions, your entities, your sign-off. Everything Canopy answers is bound by what is agreed here.
The rest of the system
the whole system, connected to your data
the enterprise intelligence workspace
the governed data pipeline
analysis-ready external data products
programmatic access to the data
your records, matched to the market
training, curriculum and advisory
the people who get it working and keep it working
DeepGarden under your brand, or inside your product
See it against your own numbers.
Bring a question your team cannot answer today and we will run it against data that looks like yours.