Many of the names in the BLD abstract syntax do not conform to the proposed Arch/Naming_Conventions without significant amendment.
All-Caps Names: BLD uses all-caps names for non-leaf classes. Below, it is assumed that capitalization is as in the proposed Naming Conventions.
Operator-Style Names: Where concepts in BLD correspond to well-known operator or connective (such as "and" and "exists"), do we use the name of the operator or the name of the kind of formula formed by the operator (eg "conjunction" and "existentially quantified formula")? Although "And" is not a noun, perhaps it can be understand as short for "an 'And' formula", and thus stands in for a noun.
Condition (non-leaf class CONDITION): In the broad Rules context, is this difference between "Condition" and "Formula" understood? If not, then a name should be chosen which communicates what kind of Formula this is.
(Exists) declare: Not a noun. How about "variable" or "var"? (plural if it remains an ordered list in the abstract syntax). However, 'declare' is easily understood to refer to a variable declaration.
(Exists) formula: Maybe this should be "subformula"? But this would often be misunderstood as a subformula of the Exists-scoped formula. Is it clear what the "formula" of an existentially-quantified formula is? Taken together, declare and formula clarify the intended roles.
Uniterm: Somewhat confusing abbreviation of uniform+universal Term (although Unisex is pretty well understood), but no better name has been proposed.
(Uniterm) arg: Should be "args" or "arguments" if it's a list.
(Equal) side: Should this be "left" and "right" (it used to be "lhs" and "rhs")? Used to be a list for reasons of formalization in the abstract metalanguage.
Const: Generally understood as an abbreviation for "Constant" but is it worthwhile to abbreviate here? (reduce from 8 to 5 chars; for earlier Con from 8 to 3 chars)
Var: Generally understood as an abbreviation for "Variable", but is it worthwhile to abbreviate here? (reduce from 8 to 3 chars)