Field guide
A local-first agentic garden planner
The Garden Steward combines practical garden planning with a transparent agent loop: observe local context, plan bounded missions, ask a person to act, verify the outcome, and learn from a private history.
Open plannerWhat makes it agentic?
A normal garden calendar displays dates. The Steward reads a context stack—USDA zone, season, crops, growing method, equipment, crop conditions, completed tasks, and regenerative goals—then sequences a small mission queue. Each recommendation names the signal and tool behind it.
- 01
Observe
Read climate, crops, conditions, goals, and field history.
- 02
Plan
Choose a short queue from deterministic garden rules and curated resources.
- 03
Act
Open the correct tool or learning path; the gardener does the real work.
- 04
Verify
Log only outcomes a person confirms, with undo available.
- 05
Learn
Use browser-local history to improve the next cycle.
Why local-first matters
Garden context can be personal and hyperlocal. The current Steward needs no account or remote model: your profile, crop observations, task history, saved learning paths, regeneration ledger, and agent audit trail stay in browser storage on this device.
Regeneration beyond crop yield
The local ledger tracks human-confirmed work that builds soil, keeps water on site, grows habitat, saves resilient seed, and shares abundance. A safety-aware Field Library extends the system into tool repair, material reuse, e-waste triage, and low-voltage garden projects without treating risky electrical work as a casual DIY task.
About this field guide
A local-first garden agent and neighborhood commons planner for food, water, tools, repair, clean energy, and resilient communication. Your profile and garden history stay on this device.