CLI Domain Sub-menus Design

• All 9 entity commands are at the root of the CLI, with no logical grouping.
• The validate_command_name() function will need to grow with every new entity, making it a maintenance burden.
• Help output lists all entities in a single undifferentiated block, making discovery difficult.
• The flat structure does not map to the underlying schema domains (ORES.REFDATA, ORES.IAM, ORES.DQ, ORES.TRADING, ORES.VARIABILITY), making the CLI inconsistent with the rest of the system.

• Introduce a domain layer between the top-level ores.cli invocation and the entity commands, yielding a three-level syntax: ores.cli <domain> <entity> <operation> [options].
• Group existing entities under their correct domain.
• Update help output to show commands grouped by domain.
• Update all parser tests.
• Preserve all existing entity parser logic without modification.

• Backward-compatible aliases for the old flat commands. The project is in an early stage and a clean break is the correct choice.
• Adding new entity commands (out of scope; this plan only restructures existing ones).
• Changing entity option structs or application dispatch logic.

Dispatches to currencies_parser and countries_parser.

Files:

• include/ores.cli/config/domain_parsers/refdata_parser.hpp
• src/config/domain_parsers/refdata_parser.cpp

Dispatches to accounts_parser, roles_parser, permissions_parser, and login_info_parser.

Files:

• include/ores.cli/config/domain_parsers/iam_parser.hpp
• src/config/domain_parsers/iam_parser.cpp

Dispatches to change_reasons_parser and change_reason_categories_parser.

Files:

• include/ores.cli/config/domain_parsers/dq_parser.hpp
• src/config/domain_parsers/dq_parser.cpp

Dispatches to feature_flags_parser.

Files:

• include/ores.cli/config/domain_parsers/variability_parser.hpp
• src/config/domain_parsers/variability_parser.cpp

The positional options currently accept command (1 token) then args (-1). Update to accept domain (1 token), command (1 token), then args (-1):

positional_options_description make_positional_options() {
    positional_options_description r;
    r.add("domain", 1).add("command", 1).add("args", -1);
    return r;
}

Also update make_top_level_hidden_options_description() to add:

("domain", value<std::string>(), "Domain sub-menu.")

Rename the existing handle_command() to handle_domain_command() and route by domain, not entity:

std::optional<options>
handle_domain_command(const std::string& domain_name, const bool has_help,
    const parsed_options& po, std::ostream& info, variables_map& vm) {

    if (domain_name == refdata_domain_name)
        return domain_parsers::handle_refdata_command(has_help, po, info, vm);
    if (domain_name == iam_domain_name)
        return domain_parsers::handle_iam_command(has_help, po, info, vm);
    if (domain_name == dq_domain_name)
        return domain_parsers::handle_dq_command(has_help, po, info, vm);
    if (domain_name == variability_domain_name)
        return domain_parsers::handle_variability_command(has_help, po, info, vm);

    return {}; // unreachable
}

Group entities by domain in help output. Top-level --help shows:

ORE Studio is a User Interface for Open Source Risk Engine (ORE).
CLI provides a command line version of the interface.

ores.cli uses a domain-based interface: <domain> <entity> <operation> <options>.
See below for a list of valid domains and their entities.

Global options:
  ...

Domains:

  refdata    Reference data: currencies, countries.
  iam        Identity and access management: accounts, roles, permissions, login-info.
  dq         Data quality: change-reasons, change-reason-categories.
  variability  Feature flags and variability: feature-flags.

For entity and operation specific options, use:
  <domain> <entity> <operation> --help

Each domain parser prints its own entity list when invoked with --help but no entity. Example for refdata:

refdata: Reference data management.

  currencies   Manage currencies (import, export, list, delete, add).
  countries    Manage countries (list, delete, add).

Use: ores.cli refdata <entity> <operation> --help for details.

const std::string refdata_domain_name("refdata");
const std::string refdata_domain_desc("Reference data: currencies, countries.");

const std::string iam_domain_name("iam");
const std::string iam_domain_desc("Identity and access management: accounts, roles, permissions, login-info.");

const std::string dq_domain_name("dq");
const std::string dq_domain_desc("Data quality: change-reasons, change-reason-categories.");

const std::string variability_domain_name("variability");
const std::string variability_domain_desc("Feature flags and variability: feature-flags.");

The existing entity name constants (currencies_command_name, etc.) move from parser.cpp into the respective domain parsers.

All test cases that use the old flat syntax must be updated to the new three-token syntax. For example:

Add new negative test cases:

• Invalid domain name → parser_exception with helpful message.
• Valid domain, invalid entity → parser_exception with helpful message.
• Domain-only with --help → prints domain help without exception.

Files:

• projects/ores.cli/tests/parser_tests.cpp