Retired name for bim-ontology's ObjectClass — the product taxonomy node. Product-marketplace stores objectClassId on ProductModel and CadAsset. Airtable object_classes.

Retired name for ObjectClassCode — a code reference linked from an object class record.

Retired name for bim-ontology's ObjectClassGraphService — pure domain policy for object-class tree changes.

Canonical parameter concept (one record per handle). Owned by bim-ontology and consumed here — see the ParameterKey entity page under that domain. Product-marketplace assigns a class to a product and uses the associated parameters.

Retired name for ParameterUsage (variant_option, product_spec, bim_parameter, mfg_takeoff, qto_takeoff). In bim-ontology "scope" means Revit category scope and nothing else; use usage for this concept.

Retired name for bim-ontology's ClassParameter — the assignment of one parameter key to one object class, with allowed-value children. Product-marketplace does not own this junction.

A shared product spec, or the variant-option catalog for one dimension. The catalog's parameter_values list every option on the variants. A product spec the variants do not all share has no model row.

One parameter key plus one parameter value inside the product model, linked to every variant that has that pair. A second variant with the same pair does not get a second record. Usage stays variant_option or product_spec.

Product model strategy — simple, predefined_variants, made_to_order, or hybrid (ADR-0044). The identity PATCH may set it. is_made_to_order is derived from the mode and is not a body field. A patch that omits the mode does not write those Airtable fields.

In-memory index of synced taxonomy keys/values used during scrape persistence to reuse canonical records by name, handle, or domain_id.

Scrape-persist encoding of ParameterUsage (`product`, `variant`, `qto_takeoff`) plus scrape-only `product_model_spec` (attach a product_spec on the ProductModel). Not a sixth catalog usage; Airtable still stores product_spec. Aliases on read include productModel, product_model, and family.

Outbound persistence pipeline that upserts taxonomy keys and values, writes a model parameter when every loaded variant carries the same value, and writes a variant parameter for a key-value pair the variants do not all share.

Deferred variant_parameters link queued when PM mirror records are not yet synced; reconciled by ReconcilePendingParameterLinksUseCase.

Policy that computes inherited effective parameter templates across category ancestors.

Product-marketplace organization projection backed by vendor records.

Product-marketplace person projection backed by seller records.

Deprecated product-marketplace name that now means VendorProductCollection; user-curated collections belong to design-management.

Product-specific catalog of stable fields a refresh scrape is allowed to update.

Policy that combines scrape run scope with catalog persistence behavior.

User-driven workflow that validates a source URL and starts scrape/persist processing for a product.

Update allowed fields for an existing product model while preserving records outside the refresh field set.

Re-scrape and replace a broader set of scrape-owned records for an existing model or family.

Workflow that publishes Airtable-linked product images to persistent media URLs and writes attachment state back.

Design-owned maintenance job that rematerializes already-assigned project products from current catalog snapshots. Not AT-C1; see design-management.