Like a DOM for the project — the current rendered state of the project graph. Not a bounded context or api-v2 module. Persisted in Postgres (api-v2); may be serialized to JSON for APIs and visualization. The app materializes POM views from committed state plus in-flight workflow.

JSON or API projection of project nodes and relationships used for rendering and integration; not a separate module folder.

Official project data owned by bounded contexts (e.g. design-management design/spec graph, construction-management cost/execution). Mutations after approval go through module ports, often invoked by project-coordination after commit gates.

In-flight change proposals, approvals, and workflow status owned by project-coordination until commit.

Aggregate in project-coordination representing a proposed change awaiting review/approval/commit.

Domain-specific JSX language that encapsulates complex project configuration logic; evaluated in app/runtime context, not a backend module name.

api-v2 module — cross-role workflow orchestration (approvals, proposals, tasks). Process manager / saga; does not own product catalog or committed POM slices.

Role-specific API composition under apps/api-v2/src/apps/** (e.g. client-portal-api). Not a bounded context; composes module inbound ports and api-v1 HTTP during cutover.

apps/api-v2/src/apps/{bff-name}/ — routes, controllers, presenters, composition; no core/domain folder.

The canonical classification node other contexts attach to — "what kind of thing is this?". A single-parent tree (ADR-0046). Owned by bim-ontology; product-marketplace assigns classes to products rather than defining them. Full definition on the bim-ontology language page.

The canonical identity and meaning of one parameter — one key per concept, defined once, independent of where it is used. Owned by bim-ontology, consumed by product-marketplace (ADR-0063). Full definition on the bim-ontology language page.

The assignment of a parameter key to an object class, with the local rules governing it. Always called an assignment, never a binding — "binding" is reserved for Revit placement.

The Revit-facing expression of an approved parameter key — one definition identity plus optional placements. A projection of a key, not a second definition of it.

The parentless ancestor at the top of a class's lineage, derived and persisted on each row. Explicitly not an input to Revit category resolution — that was a DAG-era rule retired with ADR-0046.

Displayable-but-unvetted. ParameterKey is the only aggregate with this state (ADR-0052). A scraper maps onto an approved key (or follows a mapped alias to that target) or creates a new key in active so scraped data is live while flagged for steward mapping.

Source key folded onto exactly one approved target. The source row is the mapping table (ADR-0057). Not usable. Product-marketplace scrape resolves the alias to the target identity. No scraper_parameter_mappings table.

Airtable steward-UI mutation pattern (ADR-0047) — flag-based action table. Calls the API; never writes domain state directly.

Airtable steward-UI mutation pattern (ADR-0047) — record-detail action button. Calls the API; never writes domain state directly.

Airtable steward-UI mutation pattern (ADR-0047) — create-request table. Calls the API; never writes domain state directly.

Airtable steward-UI mutation pattern (ADR-0047) — watched-field recompute. Calls the API; never writes domain state directly. AT-A* / AT-B1 written fields and AT-C1 watch lists must stay disjoint.