Asset Audit and Timeline
Three evidence forms coexist:
- Aggregate history records Created, Requested, Approved, Issued, Returned, Rejected, Damaged, Lost, Retired, and Available actions with holder snapshot, condition, notes, actor, and time.
- Mutation audit records entity/action/actor/time plus structured details for commands, workflow outcomes, and document actions.
- Timeline records business-readable activity types and descriptions for the same mutations.
Commands write audit and timeline in the same unit of work as the aggregate mutation. History is returned in chronological order; tenant-wide audit and timeline endpoints return newest-first capped results. Actor comes from tenant context and may fall back to a system label. Correlation is explicit in outbox messages, but the public audit/timeline projections do not expose a documented end-to-end correlation field.
There is no verified retention schedule, immutable archive, export, redaction process, access policy, auditor role enforcement, or dedicated maintenance/transfer/warranty evidence. The mapped audit/timeline endpoints lack endpoint-level authorization, so governance is Requires confirmation.
Source References
microservices/src/asset-service/Domain/Asset/Asset.csmicroservices/src/asset-service/Application/Commands/AssetCommands.csmicroservices/src/asset-service/Infrastructure/AssetDbContext.cs