Saltar para o conteúdo

9 min read

How tool data stays linked

Stable inventory IDs and shared calculation engines keep battery, tank, and budget rows consistent—without auto-scaling price or dry mass.

Last updated November 9, 2026

Single source of truth

Budget rows own name, quantity, price range, and dry-mass range. Technical fields (battery V/Ah, tank litres, solar watts) attach to those rows by stable ID. Deleting a row clears its links; dangling references are rejected by schema.

Anonymous calculators keep their own share URLs and formulas. Projects call the same shared engines with project-backed inputs so you are not maintaining two conflicting battery sizes.

What updates automatically

Changing a linked battery Ah updates usable energy and autonomy estimates. Changing tank capacity updates water endurance and water mass. Voltage mismatches between battery and inverter surface as warnings.

  • Price and dry mass never auto-scale when Ah or litres change—re-estimate those yourself.
  • Water content mass uses ~1 kg/L for the water only; tank dry mass stays a separate field.
  • Recommendations (suggested Ah or tank size) stay distinct from installed specifications.

What stays independent

Standalone tool pages remain valid for quick what-ifs. The project connection opens the corresponding section of your saved build; it does not import the current anonymous inputs. Use the budget calculator’s explicit import action to create a project from its inventory, or edit linked specifications in the project itself. Region or unit switches must not silently change physical distances you already entered.

Carry dimensions between comfort tools

Vehicle-library links prefill the reference length, width and height in heater, insulation and ventilation tools. Replace these with finished usable measurements when floor and wall layers reduce the space.

Related links between comfort calculators carry the current dimensions. Heater and insulation links also carry the selected materials and thicknesses. Copy inputs link preserves that calculator's editable assumptions. These standalone assumptions are not automatically saved into a Build document or written into its budget and weight rows.