Profile: Artefact staging only

Models an entity whose real production data lives somewhere other than a same-component bi-temporal table: either it is queried directly from the DQ artefact/staging table with no publish step at all (its own ores_dq_artefact_types_tbl row has null target_table=/ =target_subject), or its artefact-type row publishes onward to a table owned by a different component. Either way, generating the standard domain_entity main table (SQL create/drop, notify trigger) alongside the artefact table would produce an orphan nobody designed for – a duplicate, wrongly-owned table with no reader or writer.

Deliberately enablement-only: this profile carries no feature Assignments (no opinion on tenant scope, Qt tier, key shape – those vary per entity). It exists to be bound alongside a shape profile (e.g. :profile: simple-lookup, artefact-staging-only), composing two orthogonal traits rather than duplicating one profile's shape logic into another.

lei_entity — GLEIF LEI golden-copy data queried directly from dq_lei_entities_artefact_tbl; its own artefact-type row has null target_table=/=target_subject, i.e. explicitly terminal.

This profile carries no feature Assignments – see Purpose. Its only effect is the Physical space table below.

One row per physical-space address this profile fixes admission for – any address not listed here is left to whatever else resolves it (a more specific/general override on the binding entity, or the node's own #+default:). A bound entity's own Physical space table (if any) always wins over these.

• ORE Studio Variability Model — the axis definitions and feature bundles this profile composes.