Party Codename and Queue Isolation Design

File: projects/ores.sql/create/refdata/refdata_parties_create.sql

1. Add the column definition after short_code:

   "codename" text not null default '',
   

   The empty-string default is required for the initial CREATE TABLE to succeed for databases being recreated from scratch. The backfill migration (Task 1.3) will assign real values; the trigger will reject empty codenames on any subsequent insert.

2. Add a check constraint within the table definition:

   check (length("codename") <= 32),
   check ("codename" = '' or "codename" ~ '^[a-z][a-z_]+$')
   

   The second check allows the empty-string default only before backfill; the trigger (Task 1.2) prevents empty strings from reaching active rows after provisioning.

3. Add partial unique index after the existing index block:

   create unique index if not exists ores_refdata_parties_codename_uniq_idx
   on "ores_refdata_parties_tbl" (codename)
   where valid_to = ores_utility_infinity_timestamp_fn() and codename <> '';
   

File: same as above (ores_refdata_parties_insert_fn())

In the if found then branch (updating an existing party), before the update ores_refdata_parties_tbl set valid_to = ... statement, add:

-- Codename is immutable: restore from the active row, ignore caller's value.
select codename into NEW.codename
from "ores_refdata_parties_tbl"
where tenant_id = NEW.tenant_id
  and id = NEW.id
  and valid_to = ores_utility_infinity_timestamp_fn();

In the else branch (new party), validate the supplied codename:

-- New party must supply a valid codename.
if NEW.codename = '' or NEW.codename is null then
    raise exception 'codename is required for new parties'
        using errcode = '23502';
end if;
if NEW.codename !~ '^[a-z][a-z_]+$' then
    raise exception 'codename must match ^[a-z][a-z_]+$ got: %', NEW.codename
        using errcode = '23514';
end if;

File: projects/ores.sql/migrate/backfill_party_codenames.sql (new file)

A PL/pgSQL anonymous block with an embedded vocabulary of ~40 adjectives and ~60 nouns. The block iterates over all active parties with codename = '', generates a random word-pair, checks uniqueness, retries on collision, and updates the row directly via SQL (bypassing the immutability trigger by operating on rows that have codename = '').

Run this script once, immediately after deploying the schema change, before starting the updated application binary.

Verify that projects/ores.sql/recreate_database.sh includes the new backfill script after the main schema creation, so fresh installations are also populated correctly.

File: projects/ores.refdata/include/ores.refdata/domain/party.hpp

Add after the short_code field:

/**
 * @brief Globally unique human-readable codename for this party.
 *
 * Assigned once at creation using an adjective_noun pattern (e.g.
 * "willow_flower"). Used as the prefix for pgmq queue names and in
 * operator tooling. Never exposed to end-users in the UI.
 */
std::string codename;

File: projects/ores.refdata/include/ores.refdata/repository/party_entity.hpp

Add after short_code:

std::string codename;

File: projects/ores.refdata/src/repository/party_mapper.cpp

In both map() overloads, add r.codename = v.codename; after the short_code mapping line.

• projects/ores.refdata/src/domain/party_json_io.cpp — include codename in the JSON serialization (if manually implemented) or verify it is picked up automatically if rfl::json is used directly on the domain struct.
• projects/ores.refdata/src/domain/party_table_io.cpp — add codename to the operator<< display, e.g. << " codename" << v.codename=.
• projects/ores.refdata/src/repository/party_entity.cpp — add codename to the entity operator<< output.

File: projects/ores.refdata/src/generators/party_generator.cpp

Add codename generation using the existing faker-cxx dependency:

#include <faker-cxx/Word.h>

// In generate_synthetic_party():
r.codename = std::string(faker::word::adjective())
           + "_"
           + std::string(faker::word::noun())
           + "_"
           + std::to_string(idx);

The idx suffix guarantees uniqueness in generated test data sets without needing collision-check loops.

File: projects/ores.refdata/src/service/party_service.cpp

In the save() path, when saving a new party (party.codename.empty()):

1. Loop up to 10 times: a. Generate candidate = faker::word::adjective() + "_" + faker::word::noun(). b. Attempt to save. If a unique-constraint violation (SQLSTATE 23505) is thrown, continue to the next iteration. c. On success, break.
2. If all 10 plain attempts fail (extremely unlikely), append _2, _3, … until success.

When saving an existing party (party.codename is non-empty), pass it through unchanged — the trigger will preserve it anyway.

File: same (party_service.cpp)

After a successful first-save (version = 1= after save), create the queue:

#include "ores.mq/pgmq/client.hpp"

if (saved_party.version == 1) {
    mq::pgmq::client mq;
    const auto queue_name = saved_party.codename + "_report_events";
    mq.create(ctx, queue_name);
    BOOST_LOG_SEV(lg(), info) << "Created queue: " << queue_name;
}

pgmq::client::create() is a no-op if the queue already exists, so this is idempotent.

File: projects/ores.refdata/src/CMakeLists.txt

Add to PRIVATE link libraries:

ores.mq.lib

File: projects/ores.reporting/src/messaging/reporting_message_handler.cpp

In handle_schedule_report_definitions_request, after fetching the report definition, add:

#include "ores.refdata/service/party_service.hpp"

// Resolve the owning party's codename to construct the queue name.
refdata::service::party_service party_svc;
const auto parties = party_svc.get(ctx_, {report_def.party_id});
if (parties.empty()) {
    BOOST_LOG_SEV(lg(), error) << "Party not found for report definition";
    co_return std::unexpected(error_code::not_found);
}
const std::string queue_name = parties.front().codename + "_report_events";

Replace the hardcoded 'report_events' string in both the pgmq.send() SQL command and any log output with queue_name.

File: projects/ores.reporting/src/CMakeLists.txt

Add ores.refdata.lib to PRIVATE link libraries if not already present.

File: projects/ores.qt/include/ores.qt/ClientPartyModel.hpp

Add Codename to the Column enum between ShortCode and FullName:

enum Column {
    BusinessCenterCode,
    ShortCode,
    Codename,          // new
    FullName,
    TransliteratedName,
    PartyCategory,
    PartyType,
    Status,
    Version,
    ModifiedBy,
    RecordedAt,
    ColumnCount
};

File: corresponding .cpp (ClientPartyModel.cpp):

• headerData(): return "Codename" for the new column.
• data(): return QString::fromStdString(party.codename) for Qt::DisplayRole.

File: projects/ores.qt/src/PartyMdiWindow.cpp

After setting the model on the table view, hide the column:

tableView_->horizontalHeader()->hideSection(ClientPartyModel::Codename);

Operators can right-click the header to show it when needed.

Locate the party detail dialog UI file and implementation. Add a read-only QLineEdit (or QLabel) labelled "Codename" populated from party.codename. The field must be non-editable (codenames are immutable after creation).