The belts/inserters/loaders tables and the pure throughput math in app/src/lib/logistics.ts power the per-row logistics readout in the block editor (#21), but the assistant has no access to any of it. It can't answer "can one yellow belt feed this?" or include belt/inserter counts when asked to cover a plan's construction needs — the buildingBill tool is deliberately machine-items-only.
Add a logisticsFor(good, rate) tool: for an item, the belts of each unlocked tier needed (count + saturation) and inserter/loader options with counts; for a fluid, say so (pipe throughput is out of scope unless it's already modelled). Respect the researched tech (stack bonuses in tech_stack_bonuses already feed the in-app math).
Update the assistant prompt's plan workflow so building-coverage requests can include the logistics half: machines from buildingBill, belts/inserters from this tool.
The belts/inserters/loaders tables and the pure throughput math in
app/src/lib/logistics.tspower the per-row logistics readout in the block editor (#21), but the assistant has no access to any of it. It can't answer "can one yellow belt feed this?" or include belt/inserter counts when asked to cover a plan's construction needs — thebuildingBilltool is deliberately machine-items-only.Add a
logisticsFor(good, rate)tool: for an item, the belts of each unlocked tier needed (count + saturation) and inserter/loader options with counts; for a fluid, say so (pipe throughput is out of scope unless it's already modelled). Respect the researched tech (stack bonuses intech_stack_bonusesalready feed the in-app math).Update the assistant prompt's plan workflow so building-coverage requests can include the logistics half: machines from
buildingBill, belts/inserters from this tool.