Skip to main content

Asset Clearance Storage

Audience​

Developers, QA and support engineers, data reviewers, implementation partners, solution architects, privacy reviewers and security reviewers.

Reference Content​

Summary​

Asset Service owns asset and assignment history plus local audit, timeline, processed-event and outbox records. It exposes clearance-oriented query behavior, but compatibility exit does not invoke or persist that clearance result.

Clearance boundary​

Selected objects​

Assets, AssetAssignmentHistory, AuditLogs, TimelineEntries, ProcessedEvents and OutboxMessages are lifecycle-relevant. Document references exist but are outside this selection.

Integrity​

Assignment history is configured as an Asset child and cascades with the aggregate. Tenant filters cover tenant business/evidence objects; operational event ledgers are not globally tenant-filtered.

Missing lifecycle gate​

No persisted clearance decision, exit-request reference, automatic return task or transaction spanning Asset and exit state was found. Exit approval can therefore proceed independently of Asset Service state.

Requires confirmation​

Unless explicitly confirmed above, production migration governance, rollback, reconciliation, retention, privacy, performance, concurrency and operational ownership require confirmation.

Source References​

  • microservices/src/asset-service/Infrastructure/AssetDbContext.cs
  • microservices/src/asset-service/Application/Queries/AssetQueries.cs

See Also​

Keywords​

  • Onboarding database
  • Offboarding database
  • Lifecycle persistence

Revision Information​

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