Asset Event Boundaries
Summary
Asset Service publishes six asset lifecycle contracts and exposes clearance query behavior, but no onboarding/offboarding event interaction connects those capabilities to Employee creation or exit.
Audience
Asset and lifecycle developers, integration engineers, QA, support, and architects.
Reference Content
AssetRequested, AssetAssigned, AssetReturned, AssetRejected, AssetLostOrDamaged and AssetRetired are implemented asset-domain events with shared contracts. They are not counted in the 19 onboarding/offboarding transition catalog because source does not raise them from onboarding or exit.
Notification consumes all six for asset notifications. Asset Service does not consume EmployeeCreated or status/termination events.
Compatibility exit does not call the clearance query, subscribe to asset events or publish an exit event. A blocking asset state therefore does not prevent exit approval/access revocation in the verified implementation.
Classification: asset event infrastructure is implemented; onboarding/offboarding linkage is Not implemented.
Requires confirmation
Unless explicitly confirmed above, live delivery, consumer deployment, replay, reconciliation, retention, contract governance, monitoring and production ownership require confirmation.
Source References
microservices/src/asset-service/Domain/Asset/AssetDomainEvents.csmicroservices/src/contracts/Events/AssetLifecycleEvents.csmicroservices/src/asset-service/Application/Queries/AssetQueries.csControllers/HrOperationsController.cs
Related Articles
See Also
Keywords
- Onboarding events
- Offboarding events
- Integration contracts
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly