Product taxonomy node backed by the api-v1 object_categories table.

Code reference linked from an object category record.

Pure domain policy for object-category 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.

L2 junction on ProductModel; MTO allowable values and ranges are stored here (ADR-0007).

L3 junction on ProductVariant (renamed from parameter_assignments / variant_parameters table).

Product model strategy — simple, predefined_variants, made_to_order, or hybrid (ADR-0008).

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

Outbound persistence pipeline that upserts taxonomy keys/values and writes variant_parameters from scrape assignments.

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.