Skip to main content

Asset Verified Event Catalog

Summary

The single authoritative catalog of Asset events. Each event appears exactly once, with its domain event, integration contract, trigger, consumer, and reliability attributes.

Audience

Engineering, integration, QA, architecture, security, and product reviewers.

Reference Content

Catalog totals

MeasureVerified total
Distinct events6
Domain events6
Outbound integration contracts6
Inbound contracts consumed by asset-service0
Confirmed consumer services1 (Notification)
Notification template keys6
Contract schema version1

Event catalog

Event (EventType)ClassificationProducerTriggerDomain eventContractConsumerVersionCorrelationRetry
AssetRequestedLifecycle (request)asset-serviceCreate requestAssetRequestedDomainEventAssetRequestedEventNotification (Asset.Requested)1CorrelationId on envelope/outboxOutbox retry
AssetAssignedLifecycle (assignment)asset-serviceAssign / issueAssetAssignedDomainEventAssetAssignedEventNotification (Asset.Assigned)1CorrelationId on envelope/outboxOutbox retry
AssetReturnedLifecycle (assignment)asset-serviceReturnAssetReturnedDomainEventAssetReturnedEventNotification (Asset.Returned)1CorrelationId on envelope/outboxOutbox retry
AssetRejectedLifecycle (request)asset-serviceRejectAssetRejectedDomainEventAssetRejectedEventNotification (Asset.Rejected)1CorrelationId on envelope/outboxOutbox retry
AssetLostOrDamagedLifecycle (condition)asset-serviceMark damaged / mark lostAssetLostOrDamagedDomainEventAssetLostOrDamagedEventNotification (Asset.LostOrDamaged)1CorrelationId on envelope/outboxOutbox retry
AssetRetiredLifecycle (terminal)asset-serviceRetireAssetRetiredDomainEventAssetRetiredEventNotification (Asset.Retired)1CorrelationId on envelope/outboxOutbox retry

All six map to the outbox via AssetDbContext.Map, share the uniform AssetLifecycleData payload, and are validated by EnsureComplete before staging.

Boundaries that are not events

InteractionMechanismCatalogued as
Workflow start and callbackHTTPNot an event (Workflow boundaries)
Document store and fetchHTTPNot an event (Document boundaries)
Gateway routingHTTPNot an event (Gateway boundaries)
Employee / user referenceNumeric identifier in payloadIdentifier-only (Employee boundaries)

Catalog uniqueness

Each of the six events appears exactly once above. There are no duplicate, aliased, or hidden asset event types in the verified source.

Source References

  • microservices/src/contracts/Events/AssetLifecycleEvents.cs
  • microservices/src/asset-service/Domain/Asset/AssetDomainEvents.cs
  • microservices/src/asset-service/Infrastructure/AssetDbContext.cs
  • microservices/src/notification-service/Application/EventNotificationResolver.cs

See Also

Keywords

  • Event catalog
  • Verified contracts
  • Event inventory

Revision Information

  • Status: Draft
  • Last reviewed: 2026-07-17
  • Review cycle: Quarterly