Loading...
Loading...
One picture of how the whole cultivation stack fits together. A record of what's growing flows into building + zone simulation, into HVAC control plans, into the steam/chiller plant — while the species catalog feeds setpoints and learns back from harvests. Each box below is a real app; the dot is its health right now.
The pipeline runs upstream-to-downstream: a building model (IFC/BIM) and the live cultivation record feed the simulators, the simulators size and drive HVAC, and HVAC pulls species envelopes from the catalog. Arrows point the way the data actually moves — every one maps to code that exists today. A couple are annotated honestly: the space-sim → steam link is wired but waiting on a live token, and the lifecycle → catalog link is a cross-database read of rolling harvest aggregates. The bioreactor and cavitation apps are part of the org but have no live data edge yet, so they sit on their own with no arrows.
Checking the forest…
Edges — what flows
Node health
This map is the overview. For the per-app detail — what each service owns, what it depends on, and its response time — browse the running forest.
We'd rather hear what you're actually trying to build than ship you a generic deck.
Get in touch