Asset API Validation
Validation boundaries
Minimal APIs provide route and JSON binding. Route constraints require typed aggregate, document, employee, or compatibility route parameters. Commands validate tenant context, required values, duplicate asset code, lifecycle transitions, assignee presence, rejection reason, deletion eligibility, and workflow-managed conflicts. Value objects normalize and limit asset code, name, and serial values.
Workflow callback validation covers body presence, terminal decision vocabulary, subject type, target resolution, and optional state mismatch. Document upload validates filename, base64 content, non-empty bytes, and asset existence. Invalid list status text is ignored instead of rejected.
Employee existence, employee/asset ownership, serial uniqueness, role permission, callback caller authenticity, document access, request-size policy, and cross-service consistency are Not implemented. No DataAnnotations, FluentValidation types, endpoint filters, or generic validator pipeline were found.
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/Api/EndpointResults.csmicroservices/src/asset-service/Application/Commands/AssetCommands.csmicroservices/src/asset-service/Application/Commands/DocumentCommands.cs