How do I add a new codegen entity model?

projects/ores.compass/compass.sh add entity_org \
    --slug <entity> --component <component> \
    --description "<one-line description of the modelled entity>" \
    --shape <shape>

--shape is the important part: pick the domain_entity shape that matches the entity being commissioned — simple-text-key (country-like), fk-scoped (book-like), hierarchical-composite (party/counterparty-like), richest (currency-like, every optional knob exercised), or timeseries (market_observation-like, no Qt). Each pre-populates the scaffold's Flags/SQL/Qt sections with that shape's knobs already set correctly, sampled from a real, proven-correct reference entity — omit --shape only to get the old bare, unknobbed skeleton. Individual --entity-<knob> flags (e.g. --entity-has-workspace-id false) override any preset value. Anything a shape can't derive (actual columns, foreign-key targets, display fields, …) is left as a visible, one-line TODO in the output — never silently omitted. See Codegen org-entity meta-model for the full knob catalogue behind each shape.

The scaffold writes projects/ores.<component>/modeling/ores.<component>.<entity>.org with the required frontmatter (#+type: ores.codegen.entity and friends) and the shape's knobbed sections (Flags, Primary key, Natural keys, Columns, SQL, optionally Foreign keys=/=Insert trigger, C++, optionally Qt).

Open the scaffolded file and resolve every TODO — the shape sets knobs, not entity-specific facts like actual columns, foreign-key targets, or display fields. The meta-model documents every required property and the well-known block kinds (e.g. additional repository declarations / implementations / includes) that custom methods attach to via :implements <kind-UUID>. Once the model compiles and generates cleanly, work through the post-generation checklist — the fixed manual integration steps (registrar wiring, NATS event-relay wiring, …) codegen does not and will not wire up for you.

If projects/ores.<component>/modeling/ is the first org model in this component, add a modeling_dir entry to the component's COMPONENTS record in projects/ores.codegen/src/codegen/manifest.py:

"<component>-cpp": Component(
    name="<component>-cpp",
    models_dir="projects/ores.codegen/models/<component>",
    entity_glob="*_domain_entity.json",
    exclude_suffix=None,
    modeling_dir="projects/ores.<component>/modeling",
),

Existing components that already have modeling_dir set need no change to add another entity.

./compass.sh codegen regenerate \
    --component <component>-cpp --address ores.cpp

Codegen unions matches from the legacy JSON glob and the new modeling_dir (org files whose #+type: says ores.codegen.entity).