Performance Validation

Summary

Validation locations and error flow across the Performance service.

Audience

Engineers, architects, QA, support, security reviewers, and operators working with the Performance module.

Overview

Validation is implemented manually in aggregate factories, aggregate transition methods, value-object factories, application guards, and compatibility services. There is no FluentValidation registration or validation pipeline.

Confirmed implementation

• DomainValidationException represents invariant failures.
• Application services convert domain validation failures into invalid Result values.
• Not-found, conflict, forbidden, and validation categories exist in the result model.
• Tenant context is required by write paths and missing context is translated by middleware.
• Unknown textual list filters are ignored rather than returned as validation errors.

Classification

Implemented manual validation; centralized validation policy is Not implemented.

Requires confirmation

Validation consistency, localization, unknown-filter behavior, and client-visible error governance require confirmation.

Related Articles

• Performance technical documentation
• Performance module

See Also

• Technical known limitations
• Performance business documentation

Keywords

• Performance service
• Validation
• Draft technical documentation

Source References

• microservices/src/performance-service/Domain/Common/ValueObjects.cs
• microservices/src/performance-service/Domain/ReviewCycle/ReviewCycle.cs
• microservices/src/performance-service/Domain/Appraisal/Appraisal.cs
• microservices/src/performance-service/Application/Common/Cqrs.cs

Revision Information

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