Performance Service Responsibilities

Summary

Confirmed ownership and non-ownership boundaries of the Performance service.

Audience

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

Overview

The service owns review cycles, appraisals, goals, staged reviews, reports, audit/timeline entries, compatibility projection, lifecycle event creation, and performance-data backfill tooling.

Confirmed implementation

• Owns canonical cycle and appraisal state transitions.
• Owns goal and review child entities inside appraisals.
• Owns read-side list, detail, and cycle reporting operations.
• Owns the Performance slice of the legacy HR workspace compatibility shape.
• Does not own employee profiles, Workflow task execution, Notification delivery, Document operations, or Payroll actions.

Classification

Transitional because canonical service ownership and a legacy-shaped adapter operate together.

Requires confirmation

Long-term compatibility ownership, downstream consumer ownership, and operational accountability require confirmation.

Related Articles

• Performance technical documentation
• Performance module

See Also

• Technical known limitations
• Performance business documentation

Keywords

• Performance service
• Responsibilities
• Draft technical documentation

Source References

• microservices/src/performance-service/Program.cs
• microservices/src/performance-service/Api/PerformanceEndpoints.cs
• microservices/src/performance-service/Application/Compatibility/PerformanceCompatService.cs
• microservices/src/performance-service/Backfill/PerformanceBackfillRunner.cs

Revision Information

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