| O1 · “Can’t I just Google this?” |
High |
Public answers don’t know your grower’s specific calibers, dig windows, or Dan’s calibration on Beech Leaf Disease or ALB in your region. The wedge is Goodmark’s plants, against Goodmark’s availability, with Goodmark’s register — not generic plant knowledge. |
| O2 · “Does it have all 399 SKUs?” |
High |
32 today — the seed records, fully calibrated and citation-grade. Extension methodology documents how we reach 399. ~85 hours for first install; ~15 hours per additional grower. Calibrated depth on what your crews actually spec, expanding as gaps surface. |
| O3 · “What about daily availability changes?” |
Medium |
Today: dated xlsx refresh — freshness signal flags rows > 30 days old. v0.1 path is live-feed integration (cron or API). Typically discussed during the Dan calibration call. Not load-bearing for v0; meaningful for v0.1. |
| O4 · “Is it just an LLM with a system prompt?” |
High |
No. Authority-disciplined retrieval against a citation-traceable knowledge layer. Public LLMs hallucinate plant facts — wrong zones, wrong dig windows, made-up patent numbers. This agent reads the evidence layer or doesn’t write the attribute. Grounded retrieval, not smarter generation. |
| O5 · “What if a plant isn’t in the layer?” |
Medium |
Agent says so honestly. Click Hostas:
“This plant isn’t in Goodmark’s current calibrated knowledge layer. Want Goodmark’s availability listings, or escalate to Dan?”
Two follow-up paths. Honesty over coverage.
|
| O6 · “Does Dan have to maintain this?” |
Medium |
Methodology covers ongoing maintenance — it’s not Dan’s role to populate fields. First calibration captures his register and microclimate notes. After that, extension is a documented process. Dan’s time is the constraint we’re relieving, not the constraint we’re multiplying. |
| O7 · “What about Wilson, Fiore, MGC?” |
High |
Extension methodology covers them at ~15 hours per grower after the first install. v0 is Goodmark-only by scope — clean wedge, validate the pattern. Multi-grower extension is v0.1, named on the demo as the next build. |
| O8 · “Where does this run?” |
Low |
Demo runs at becomingiq.com/_demo/plant-specialist; production deploys per your install practice (operator dashboard, crew-side app, or grower portal). v0 is operator-side: your crew queries your grower. v0.1+ supports posture-toggle when grower-side becomes the answer for your shop. |