Asset Employee Boundaries
Summary
Asset events reference employees and users only by numeric identifier in the payload. Asset-service does not consume employee events and holds no HTTP client to the employee service in the verified source.
Audience
Engineering, integration, QA, architecture, and security reviewers.
Reference Content
Identifier-only references
Each asset event payload carries two optional numeric identity fields:
| Field | Meaning | Reference type |
|---|---|---|
AssignedToUserId | The holder's user identity | Identifier-only |
LegacyEmployeeId | The holder's labor/employee identity | Identifier-only |
These are plain integers copied from the aggregate snapshot (AssignedToUserId, LaborId). They are not database foreign keys and are not resolved by asset-service into employee records at emit time.
No employee event consumption
The verified source contains no employee-event subscriber, handler, or employee HTTP client in asset-service. Asset-service neither reacts to employee lifecycle events nor enriches asset payloads with employee-service data before emitting.
Downstream resolution
The Notification consumer resolves the recipient from these identifiers (labor first, then user, then the AssetAdmin role fallback) and delivers email only when RecipientEmail is present. RecipientEmail is null at emit and is populated by a downstream enrichment step; the enrichment owner requires confirmation.
Classification
The employee association is an identifier-only reference, not a database-enforced relationship and not an event contract between asset and employee services.
Source References
microservices/src/contracts/Events/AssetLifecycleEvents.csmicroservices/src/asset-service/Domain/Asset/AssetDomainEvents.csmicroservices/src/asset-service/Program.cs
Related Articles
See Also
Keywords
- Employee reference
- Identifier only
- Labor reference
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly