Reads the fleet. Names what's deployable.
A specialist agent over the operator's equipment substrate — machinery, attachments, trailers, maintenance history, hours, assignment state. Reads operator intent — an RFQ that needs a piece of iron, a deployment plan that needs a crew with attachments, a service-planning gesture that needs a window — and returns specs, current state, deployability, sourcing detail when augmentation is needed.
Equipment data lives in three uneven places: the operator's own head, a shop-floor whiteboard or spreadsheet, and a service schedule someone keeps next to the maintenance shed. Equipment Specialist reads what exists today and defers to the operator on the rest — same posture Plant Specialist takes with field knowledge.
Pending. Build queued behind Vendor Specialist as the sister flagship on the Specialists Line. The crew shape is named; the asset substrate calibrates with the first operator who has fleet data worth wiring.
- The family blueprint — four-position crew inherited from Plant Specialist; equipment-substrate parallel to Plant's plant substrate.
- The wedge — equipment data lives in operator's head + a shop spreadsheet + a service schedule. Equipment Specialist reads what exists; never auto-populates fields it can't verify.
- The read surface — operator intent comes in three forms today: RFQ (job needs iron), deployment (week needs crews + attachments), service planning (window needs windows).
- The deference rule — operator knows their fleet's real condition; agent reads recorded substrate only.
- The cross-cutting reach — serves residential maintenance routes, commercial bid arcs (fleet against the scope), wholesale-supply's own asset-facing surface.
- The first operator fleet — substrate calibrates with whoever opens the first build. Likely the Operator Console N=1 operator as a seam.
- The fleet substrate format — Excel · paper · whiteboard photo · a telematics export · QB asset register · hybrid. Each operator arrives shaped differently.
- The maintenance read — service intervals stored where, by whom, against what schedule (calendar · hours · seasons). The substrate decision shapes the agent.
- The deployment seam — does Equipment Specialist read the Operator Console's Schedule & Visits surface for current assignment state, or hold its own deployment ledger? Decided at first wire-up.
- The asset-vs-equipment distinction — "Equipment" locked in over "Asset" on the Line, but if a future operator needs a separate asset register (buildings · vehicles · IP), the specialist may split.
Four positions. One specialist agent.
Crew shape inherited from the Plant Specialist family blueprint and recalibrated to the operator's fleet. Substrate behind each position calibrates with the first operator's real equipment data.
The Iron Inventory
— Reads what they own. Reads what attaches to what.
Loads the operator's fleet substrate — machinery, attachments, trailers, hours, model + year + serial, attachment compatibility. Pure read; never invents records. When fleet data is sparse, the gap surfaces rather than getting filled by guess.
The Service Schedule
— Reads when it last ran. Reads what's due next.
Reads maintenance history and current service state — last service date, hours since, intervals due, parts on order. Names current condition based on recorded substrate; defers to operator for actual mechanical judgment. Substrate calibrates per operator (some run paper logs, some run telematics, some run heads-up).
The Operator Ask
— Reads what the work needs. Returns what the fleet has against it.
Reads operator intent across three forms — RFQ (job needs iron + attachments), deployment plan (week needs crews equipped), service planning (window needs scheduling). Validates against the operator's actual fleet; unknown asset routes to clarification rather than guess.
The Iron Verdict
— Names what's deployable. Names what needs sourcing.
Composes the deployability read from fleet + maintenance + intent. Returns: which assets are deployable for the ask, which are flagged for maintenance, which attachments aren't on hand. When the fleet can't cover, surfaces sourcing options (rent · borrow · buy) rather than recommending a buy. Operator decides.
The four reads on the specialist.
Sister flagship to Vendor Specialist on the Specialists Line. Pending and build-queued; crew shape carries against the Plant family blueprint, substrate calibrates per operator at first build.
A specialist agent over the operator's equipment substrate — machinery, attachments, trailers, maintenance history, deployment state. Reads operator intent, returns deployability verdicts and sourcing reads. Cross-cutting — any crew with iron in the work.
Fleet read + maintenance join + intent match. Connection method calibrates per operator (paper · spreadsheet · whiteboard · telematics · QB asset register). v0 build accepts any combination; substrate decides shape.
For the operator running a real fleet against real work weeks. Most likely first wire-up: the Operator Console N=1 operator, whose Schedule & Visits substrate already names the deployment seam. Cross-class — residential maintenance, commercial bid arcs, wholesale-supply asset surfaces all read against the same agent.
Equipment data lives in heads, on whiteboards, in shop spreadsheets. The operator either remembers what's deployable on a given Tuesday or builds a meeting around figuring it out. Equipment Specialist reads what's recorded and names the gaps so the operator stays in judgment without re-typing the fleet.
“Reads the fleet. Joins the maintenance.
Names what's deployable for the work.
Surfaces the gaps. Stays out of the buy call.”
— EQUIPMENT SPECIALIST · pending · build queued · 2026-05