Recruitment Audit and History

Summary

Commands write audit records and human-readable timeline entries; candidate stage history, interview feedback, offer revisions, and offer approvals provide additional domain evidence.

Audience

Recruitment operations, hiring stakeholders, product, engineering, QA, support, and architecture teams. Candidate-facing behavior is identified explicitly.

Overview

Commands write audit records and human-readable timeline entries; candidate stage history, interview feedback, offer revisions, and offer approvals provide additional domain evidence.

Evidence layers

Layer	Purpose
Audit record	Entity, action, actor, time, and selected metadata
Timeline entry	Human-readable business occurrence
Candidate stage history	From/to stage, notes, actor, and time
Interview feedback	Recommendation/rating evidence and narrative
Offer revision	Previous and revised offer fields
Offer approval	Approver, outcome, notes, and time

Foundation read surfaces exist for audit and timeline. Retention, immutability guarantees, access policy, redaction, legal hold, correction, and export governance Require confirmation. Sensitive narratives and values are intentionally excluded.

Requires confirmation

Formal ownership, production policy, authorization parity, and approved operating procedures require confirmation.

Source References

• microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
• microservices/src/recruitment-service/Domain/Recruitment/Candidate.cs
• microservices/src/recruitment-service/Domain/Recruitment/Offer.cs
• microservices/src/recruitment-service/Application/Commands

Related Articles

• Recruitment module
• Recruitment business documentation
• Recruitment limitations

See Also

• Recruitment module overview
• Recruitment business rules

Keywords

• Recruitment
• Hiring lifecycle
• Audit and History

Revision Information

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