Performance Logical Schema Reference

Summary

Verified logical catalog of Performance persisted objects without physical deployment details.

Audience

Backend engineers, database reviewers, architects, QA, support, operations, security reviewers, and product owners.

Overview

This is the canonical logical persistence catalog for the current source checkout. It intentionally omits generated statements, physical deployment names, and sensitive content.

Confirmed persistence behavior

Logical item	Classification or owner	Tenant/filter	Identity or mapping	Relationship or purpose	Index or behavior
ReviewCycle	Aggregate root	Tenant filtered	Generated identity	Owns CyclePeriod; logical Appraisal link	Tenant and status
Appraisal	Aggregate root	Tenant filtered	Generated identity plus unique compatibility identity	Owns Goal and Review; logical external references	Tenant/status, tenant/cycle, Workflow, compatibility
AppraisalGoal	Child entity	Tenant filtered	Application-assigned identity	Required Appraisal foreign key; three owned values	Parent and tenant/parent
AppraisalReview	Child entity	Tenant filtered	Application-assigned identity	Required Appraisal foreign key; two owned values	Parent and tenant/parent
PerformanceAuditLog	Technical history	Tenant filtered	Generated identity	Logical entity reference only	Tenant and occurrence
AppraisalTimeline	Business history	Tenant filtered	Generated identity	Logical entity reference only	Tenant and occurrence
OutboxMessage	Outbound operational	No global tenant filter	Generated identity	No aggregate foreign key	Unique event; status and occurrence
ProcessedIntegrationEvent	Inbound ledger foundation	No global tenant filter	Generated identity	No aggregate foreign key	Unique event

• Eight logical persisted objects, eight logical primary keys, two configured child foreign keys, seven owned mappings, and six query filters are present.
• No Calibration, Feedback, Objective, KPI, promotion, development-plan, compatibility-map, or standalone checkpoint persisted object exists.

Classification

Implemented logical catalog; transitional objects and operational policy gaps are noted per page.

Requires confirmation

Data classification, retention, ownership, archive destinations, and future model evolution require confirmation.

Related Articles

• Performance database documentation
• Performance technical documentation

See Also

• Performance API documentation
• Performance business documentation

Keywords

• Performance persistence
• Schema Reference
• Draft database documentation

Source References

• microservices/src/performance-service/Infrastructure/PerformanceDbContext.cs
• microservices/src/performance-service/Infrastructure/Migrations/PerformanceDbContextModelSnapshot.cs
• microservices/src/performance-service/Domain/ReviewCycle/ReviewCycle.cs
• microservices/src/performance-service/Domain/Appraisal/Appraisal.cs

Revision Information

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