From the catalog crew · the specialist that reads plants
Crew Bio · Plant Specialist · operator-confirmed · build queued
BecomingIQ · becomingiq.com
Live demo · Surface A · Plant Lookup · Goodmark evidence layerSee it live
FROM THE CATALOG CREWCROSS-CUTTING · ALL CLASSES

Reads the plants. Names what fits.

A specialist agent that reads plant catalog and supplier inventory together. Takes operator intent — a Project Intake capture, an RFQ line, a design intake row — and returns plant specifications, alternatives, and sourcing reads. Sits cross-cutting; serves any crew that needs to put a plant against a row.

Plant data lives in three uneven places: nursery catalogs, supplier-of-the-week availability, and the operator's own field knowledge. Plant Specialist reads the first two and defers to the operator on the third. The output is specs and sources the operator can use, not a plant the operator never asked for.

Operator-confirmed. Build queued. The shape is known; the production substrate calibration arrives when the build kicks off.

PositionPlant Specialist · Catalog Crew · Cross-Cutting
PLANT CATALOG · SUPPLIER INVENTORY · OPERATOR INTENT · SPECS + ALTS
What's known about Plant Specialist
  • The crew shape — four positions, named below, agent-fabric ready.
  • The read surface — operator intent comes in three forms: capture, RFQ, design intake.
  • The output shape — plant specs + alternatives + sourcing reads, not opinions about the design.
  • The operator deference rule — field knowledge stays with the operator; the agent reads catalog + supply only.
What's not yet
  • The catalog substrate — which sources, which formats, which freshness.
  • The supplier-availability connection — API, scrape, manual feed, or hybrid.
  • The operator intent grammar — how each form (capture / RFQ / intake) hands off cleanly.
  • The first-operator calibration — whose catalog, whose suppliers, whose field knowledge first.
— And here is your crew (forming)

Four positions. One specialist agent.

The crew shape is named. The substrate behind each position calibrates with the first operator. Half-built — voice-honest about which positions are agent-fabric ready and which need substrate.

Operator-confirmed · build queued. The shape doesn't change; the substrate does.
01Position 1 · The Catalog Reader

The Plant Catalog

— Reads what's available. Reads what it actually is.

Reads plant catalog data — botanical name, common name, USDA zone, mature size, sun + water needs, growth rate, availability windows. Catalog substrate decision pending; agent shape ready.

Reads
plant catalog · botanical specs · zone fit · maturity · availability windows.
agent readycatalog pendingN=0 operators
02Position 2 · The Supplier Reader

The Inventory Read

— Reads who has it now. Reads what it costs today.

Joins supplier inventory against catalog reads. Names current availability, pricing, lead time. Supplier connection method calibrates per operator — some operators have API access, others need scrape, others manual feed.

Reads
supplier availability · current pricing · lead time · region + delivery constraints.
join shape knownconnection per-operatorN=0 operators
03Position 3 · The Match Maker

The Intent Reader

— Reads the operator's row. Returns the matching plants.

Reads operator intent across three forms — Project Intake capture, RFQ line item, design intake row. Matches against catalog + supply. Returns specs the operator asked for, not specs the agent wants to recommend.

Reads
operator intent (capture · RFQ · design intake) · context the intent sits in · constraint shape.
3 intent formsdeferential to operatorN=0 operators
04Position 4 · The Alternative Finder

The Sourcing Read

— Names alternatives when the first choice isn't available.

When availability blocks the first match, surfaces alternatives that hold the design intent. Names what's actually different about each alternative — not generic substitutes, but operator-readable trade-offs the design can absorb or reject.

Output
alternative plant list · per-alt trade-off read · sourcing options for each · operator decides which alt holds the design.
trade-off awareno opinions on designN=0 operators
— What · How · Who · Why

The four reads on the specialist.

Operator-confirmed and build-queued. The crew shape is named; the substrate calibrates per operator at first build.

Reads catalog + supply. Defers to the operator on field knowledge. Returns specs + alts + sourcing — not design opinions.
What.

A specialist agent over plant catalog + supplier inventory. Reads operator intent, returns plant specs, alternatives, and sourcing reads. Cross-cutting — serves any crew that has a row that needs a plant.

How.

Catalog read + supplier availability join + operator intent match. Connection method per operator (API / scrape / manual feed). Half-built today; substrate calibrates with the first operator's catalog and supply chain.

Who.

For the operator picking plants under real availability constraints. Operator-confirmed. Build queued. First operator onboarding calibrates the substrate; agent shape stays.

Why.

Plant data lives in three uneven places. Catalog and supply drift on different cycles. The operator's field knowledge doesn't belong inside an agent. A specialist that reads two and defers to the third lets the operator stay in their expertise without re-typing what's already in a catalog.

“Reads the catalog. Joins the supply.
Returns the specs the operator asked for.
Defers on field knowledge. Stays out of the design.”

— PLANT SPECIALIST · operator-confirmed · build queued · 2026-05