How much of the building Baler understands
Points by who classified them. Proposed and escalated points are waiting for a person here; unmapped points have no class and no proposal yet (run python -m baler.autotag).
Waiting for a person
Grouped by naming pattern and ranked: patterns a fault rule needs first, then points on a site with an active Cx project, then the rest. One answer covers the whole group; accepting a group also saves it as a site rule, so later points with that pattern are classified without asking a model.
Equipment relationships
Proposed from the data, never written until you accept: points with no equipment grouped by their topic, and an AHU that feeds a VAV (its supply air temperature tracks the VAV's discharge air temperature).
Naming conventions
Mark up one label and Baler parses every point on the site the same way: literal text, with {role:text} around the parts that vary. Roles: equip_type, equip_id, point, ignore. Example: fbf/{equip_type:ahu}-{equip_id:1}/{point:SAT}. Then say what each code means; one entry covers every point with that code. Preview writes nothing.