Asset Workflow API
Callback and outbound interaction
POST /asset/workflow/callback accepts WorkflowCallbackDto. It validates the decision and optional subject type, resolves the request by subject/asset or workflow reference, optionally compares live workflow state, and applies issue or rejection. Duplicate terminal callbacks are acknowledged without re-emitting lifecycle events.
The typed outbound client starts a workflow and reads instance state while propagating tenant, actor, role, and correlation context. Transport failures are converted to start failure or unavailable state. No inbound message consumer, callback authentication policy, retry endpoint, orchestration engine, or workflow task API exists in Asset Service.
Classification
The API is Transitional. Capabilities explicitly described as absent are Not implemented. Host diagnostics and evidence routes are Foundation. Production exposure, ownership, and governance Require confirmation.
Source References
microservices/src/asset-service/Api/AssetEndpoints.csmicroservices/src/asset-service/Application/Commands/AssetCommands.csmicroservices/src/asset-service/Application/WorkflowIntegration.csmicroservices/src/asset-service/Infrastructure/WorkflowServiceClient.cs