Profile: Tenant-scoped junction

Models a plain many-to-many association between two entities (currency ↔ calendar, party ↔ country, tenor convention ↔ tenor, …): a row is just a pair of foreign keys plus a scoping column, with no natural key of its own, no self-standing lifecycle, and — with one exception — no Qt surface. Junctions default has_tenant_id to false (the opposite of a domain_entity), so authoring it true is a genuine, recurring choice, not incidental boilerplate — the ores.refdata junction survey found 9 of 9 junctions sharing this exact value with nothing else varying. One of the 9, calendar_date, additionally carries its own independent Qt list drawer (it is a materialised fact table, not a pure link table) — that drawer sits alongside this profile's binding untouched, exactly as an entity's own extra features sit alongside Fully-featured lookup.

currency_calendar — links a currency to the holiday calendar used for its spot/settlement date computation; the plainest, most representative instance of the shape.

One row per feature this profile fixes a value for — any feature not listed here is left to the model's own choice. Feature names are literal — exactly what ORE Studio Variability Model documents them as, so this table can be read directly by whatever eventually resolves :profile: bindings, with no translation layer:

• ORE Studio Variability Model — the axis definitions and feature bundles this profile composes.
• Simple lookup — the domain_entity metatype's own tenant-scoped-only sibling; this profile is its junction-metatype counterpart.