Purpose

Records that the non-authoritative stored Revit name was recomputed from canonical metadata. Authored facts and shared-definition identity are untouched. The resync is skipped — and no event is emitted — when nameSource is override or when the derived name already matches, so this event means the stored name genuinely changed.

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 resync happened

Raised by

• RevitParameterProjection.resyncDerivedName — apps/api-v1/src/modules/bim-ontology/core/domain/revit/RevitParameterProjection.ts
• ResyncDerivedProjectionMetadataUseCase — apps/api-v1/src/modules/bim-ontology/core/application/use-cases/RevitProjectionDerivationUseCases.ts, invoked either by the operations below or automatically by CanonicalProjectionMetadataChangedHandler on ParameterKeyUpdated and ParameterGroupChanged
• HTTP: resyncDerivedRevitProjectionMetadata, resyncRevitProjectionsForParameterKey, resyncRevitProjectionsForParameterGroup

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.

The resync itself can have a second effect in the same use case: if the new derived name changes shared-parameter-file output on an approved projection, it is demoted to draft.

Related

• RevitParameterProjection, ParameterGroup
• RevitParameterProjectionDemoted
• listRevitProjectionDerivationDrift — projections whose stored name has drifted from the derived one