Asset Compatibility and Transition
Transitional surface
Compatibility routes own only assets, asset requests, asset status actions, deletion, and the asset slice of the shared workspace. AssetCompatService maps legacy request/response shapes and status vocabulary to canonical commands. Requested and Approved collapse to the legacy Submitted label; compatible update/create can issue after saving. The workspace returns assigned assets and empty defaults for unrelated sections.
A compatibility numeric identity is retained alongside the aggregate identifier. Backfill code maps legacy status/condition values and supports migration verification. Gateway cutover is feature-controlled with rollback to existing owners and a shadow route.
The compatibility workspace cannot compose other module data itself, shared-workspace route precedence is transitional, and cutover completion/legacy retirement criteria are not encoded in source.
Requires confirmation
Production ownership, authorization governance, operational policy, and future architecture require confirmation where the source does not enforce them.
Source References
microservices/src/asset-service/Api/AssetCompatEndpoints.csmicroservices/src/asset-service/Application/Compatibility/AssetCompatService.csmicroservices/src/gateway-api/Program.csmicroservices/src/asset-service/Backfill/AssetBackfillTypes.cs