Conventions for asp names

The asp code is organized around conceptual modules. It should strive to adhere to the following conventions

the name of user-facing / interface predicates should

• optionally start with a module name followed with an underscore _
• use mixed case

the name of cross-module predicates should

• start with a module name
• follow with an underscore _
• end with the name of the concept the predicate stands for, in mixed case

the name of predicates internal to a module should

• start with an underscore _
• follow with a module name
• follow with an underscore _
• end with the name of the concept the predicate stands for, in mixed case

the name of grounding/meta variables should

• be written an all caps
• separate words with underscores.

Example:

• optimize_maximizeSum and optimize_precision are two interface predicates from the optimize module.
• _set_foldStep is an internal predicate from the set module.
• in the following snippet, the predicate _main_defaultEngine is internal to the main module whereas defaultEngine is intended to be user-facing, and ENG is a grounding variable.

_main_defaultEngine(ENG) :- defaultEngine(ENG).
_main_defaultEngine(compile) :- not defaultEngine(_).

Naming conventions for function symbols have not been decided yet.

No files or tests are named in the issue. Start by inventorying predicate names across the ASP modules and comparing them with the listed interface, cross-module, internal, and grounding-variable rules. Done means the applicable conventions are documented or adopted consistently, with a separate decision for function-symbol naming.