Passive reservoir prototype
A raised soil zone, two wicking columns, fill tube, overflow level and air space form the current physical prototype.
Technology
Begin with reliable physical function. Add technology only where it helps.
Prototype 1 uses passive reservoir watering and capillary wicking. Moisture, temperature and light sensing are separate optional concepts under evaluation—not guaranteed product components.
Third-party monitoring
A sensor concept may measure moisture, temperature and light when paired with compatible supporting equipment. Reliability and customer setup burden still require testing.
Alerts and AI-assisted guidance
Future software may explain observations and possible actions with uncertainty and human review. It is not an autonomous growing system.
01
Prototype testing
Plant and garden layer
Compatible edible plants, a moisture-managing growing medium and the shared root zone are being tested as one physical growing system.
Data and purposeGarden type, crop selection, planting date and grower observations.
02
Prototype testing
Reservoir and wicking layer
The built prototype stores water below a raised soil zone and uses two soil-filled columns to support capillary movement into the root area.
Data and purposeReservoir refill timing, root-zone moisture observations, overflow behavior and grower-recorded actions.
03
Under evaluation
Sensor layer
Tested third-party sensors may provide soil-moisture, temperature and sunlight readings as operational indicators rather than laboratory measurements.
Data and purposeTime-stamped sensor readings, device status and data freshness.
04
Future development
Controller and automation layer
Certified third-party timers or controllers may run bounded watering schedules. Manual operation and clear overrides remain part of the design.
Data and purposeSchedule settings, controller status and recorded watering events.
05
Future development
Data and alert layer
Readings and garden context may support condition-based alerts for stale data, unusual conditions and practical events that deserve the grower’s attention.
Data and purposeAlerts, acknowledgements and actions taken. Notifications are intended for useful events, not constant messaging.
06
Future development
AI guidance layer
AI-assisted care and problem diagnosis may combine approved crop playbooks with garden context to explain possible next steps, assumptions and confidence.
Data and purposeThe minimum context needed to create guidance. Photos and precise location would be optional if introduced.
07
Design requirement
Grower control and manual override
The grower remains responsible for the garden. Basic irrigation and care must remain understandable when connectivity or a digital service is unavailable.
Data and purposeGrower preferences and optional feedback used to improve future guidance.
Responsible limits
The grower remains in control.
During the pilot, AI will not control safety-critical watering decisions. Any scheduled controller must use bounded rules, manual overrides and understandable fallback operation.
MarketBrug will not promise universal sensor compatibility, laboratory-grade readings, outdoor durability or subscription terms until specific configurations are tested and approved.
Follow the connected pilot