Every solved block carries powerW (and heatW), but nothing aggregates them: the assistant cannot answer "do I have enough power for this plan?" or "what's the factory's total electric demand?".
Add a factory power summary the assistant can read — either a small tool or an extension of coherenceAudit: total electric demand across blocks, the top consumers, and the generation side (blocks whose recipes produce electricity), so demand vs generation is one answer. Fluid-fuel MJ flows are already audited as ordinary goods; heat is block-local by design and needs no cross-block rollup beyond the per-block heatW that drafts already report.
Worth deciding during implementation: whether generator blocks are identifiable today (electricity is a pseudo-good that drafts drop from import/export lists), or whether the generation side needs a convention first.
Every solved block carries
powerW(andheatW), but nothing aggregates them: the assistant cannot answer "do I have enough power for this plan?" or "what's the factory's total electric demand?".Add a factory power summary the assistant can read — either a small tool or an extension of
coherenceAudit: total electric demand across blocks, the top consumers, and the generation side (blocks whose recipes produce electricity), so demand vs generation is one answer. Fluid-fuel MJ flows are already audited as ordinary goods; heat is block-local by design and needs no cross-block rollup beyond the per-blockheatWthat drafts already report.Worth deciding during implementation: whether generator blocks are identifiable today (electricity is a pseudo-good that drafts drop from import/export lists), or whether the generation side needs a convention first.