Purpose

Records the birth of a RevitParameterProjection — one Revit expression of exactly one canonical ParameterKey. Most projections are created automatically in draft by the ensure path after ParameterKeyApproved, then completed and approved by a steward.

Payload

Envelope is { name, occurredAt, payload } (apps/api-v1/src/modules/shared/domain/events/DomainEvent.ts). All seven RevitParameterProjection* events share one payload type; occurredAt appears both on the envelope and in the payload.

Field	Type	Meaning
projectionId	string	Projection domain_id
parameterKeyId	string	The one canonical key this projection expresses
occurredAt	Date	When the change happened

Raised by

• RevitParameterProjection.create — apps/api-v1/src/modules/bim-ontology/core/domain/revit/RevitParameterProjection.ts, only when a clock is supplied
• CreateRevitParameterProjectionUseCase — apps/api-v1/src/modules/bim-ontology/core/application/use-cases/RevitProjectionAuthoringUseCases.ts. EnsureRevitProjectionForParameterKeyUseCase reaches it through ensureBuiltIn / ensureShared, choosing the definition form from CommonParameterProjectionPolicy on the key’s handle
• HTTP: createRevitParameterProjection

Consumers

No subscriber in this module. No handler is registered for any of the seven projection events in bim-ontology.composition.ts; only the '*' DomainEventAuditLogger sees them. Every automatic consequence around projections is driven by a ParameterKey* or ParameterGroupChanged event flowing into the projection side.

Related

• RevitParameterProjection, ParameterKey
• ParameterKeyApproved — what triggers the automatic create
• RevitParameterProjectionApproved