Asset Reference Overview
Summary
This page is the entry point for the Asset Management reference catalog. The reference pages distil the authoritative Business, Technical, API, Database, and Events documentation into quick-lookup tables and diagrams. They summarize and cross-link; they do not replace the authoritative pages they point to. Every fact here is reconciled to the verified source documents produced in earlier epics.
Audience
Developers, QA engineers, support engineers, solution architects, security engineers, product owners, and implementation partners who need a fast, verified lookup surface for asset behavior, terminology, statuses, routes, permissions, validation, events, integrations, persistence, maturity, and limitations.
Reference Content
Catalog map
| Page | Purpose |
|---|---|
| Asset Terminology | Glossary separating Domain, UI, Compatibility, Integration, and Persistence terms. |
| Status and Transition Reference | The 10 statuses, transition matrix, and lifecycle diagram. |
| Route Reference | The two frontend routes and the legacy redirect. |
| API Summary | Grouping of the 31 verified method/route pairs. |
| Permissions Matrix | Per-action UI visibility, guards, and API authorization posture. |
| Validation Catalog | Validation rules by category and enforcement layer. |
| Event Summary | The six lifecycle events and the outbox delivery model. |
| Integration Reference | Inbound and outbound integrations and failure boundaries. |
| Database Summary | Persisted object sets, filters, and indexes. |
| Implementation Maturity | Nine-dimension maturity assessment. |
| Consolidated Limitations | Grouped, deduplicated known gaps. |
| Source Map | Grouped catalog of authoritative source files. |
Scope and reconciliation
The asset-service owns the asset lifecycle. It exposes native endpoints alongside a monolith-shaped compatibility surface, publishes six lifecycle events through a transactional outbox, and integrates with workflow, document, and notification services. This reference is transitional: native persistence coexists with compatibility identity, and the in-service inbound event consumer remains foundational. For authoritative depth, follow the cross-links into the API, Database, Events, and Technical documentation.
Source References
microservices/src/asset-service/Domain/Asset/Asset.csmicroservices/src/asset-service/Api/AssetEndpoints.csmicroservices/src/asset-service/Api/AssetCompatEndpoints.cs
Related Articles
See Also
Keywords
asset reference, catalog, overview, asset management, lifecycle, transitional
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly