Attendance Event Catalog

Summary

The current catalog contains five domain events and five one-to-one integration contracts.

Audience

• Developers, QA engineers, architects, service owners, support engineers, and catalog automation

Reference Content

Domain event / integration contract	Category	Trigger	Producer	Confirmed consumers	Delivery	Version	Idempotency expectation	Maturity	Source
AttendancePunchedDomainEvent / AttendancePunchedEvent	Capture	Punch created	Attendance Service	None	Transactional outbox and broker	1	Event-ID based	Foundation consumption	S1-S3
AttendanceSubmittedDomainEvent / AttendanceSubmittedEvent	Review	Unapproved computation saved	Attendance Service	Payroll, Integration	Transactional outbox and broker	1	Consumer ledger; Payroll staleness check	Transitional	S1-S5
AttendanceApprovedDomainEvent / AttendanceApprovedEvent	Review	Approved/recalculated result saved	Attendance Service	Payroll, Integration	Transactional outbox and broker	1	Consumer ledger; Payroll staleness check	Transitional	S1-S5
AttendanceRejectedDomainEvent / AttendanceRejectedEvent	Review	Daily outcome rejected/cleared	Attendance Service	Integration	Transactional outbox and broker	1	Integration processed ledger	Transitional	S1-S5
AttendanceReopenedDomainEvent / AttendanceReopenedEvent	Reopen	Approved reopen applied	Attendance Service	None	Transactional outbox and broker	1	Event-ID based	Foundation consumption	S1-S3

Source keys

Key	Repository-relative source
S1	microservices/src/attendance-service/Domain/Attendance/AttendanceDomainEvents.cs
S2	microservices/src/contracts/Events/AttendanceLifecycleEvents.cs
S3	microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
S4	microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
S5	microservices/src/integration-service/Domain/IntegrationEntities.cs

Totals: 5 domain events, 5 integration contracts, 5 mappings, 2 directly consuming services, 5 direct consumer subscriptions across the contracts, and schema version 1 for every mapping. A consumer entry denotes current source subscription, not deployed health.

Source References

• microservices/src/attendance-service/Domain/Attendance/AttendanceDomainEvents.cs
• microservices/src/contracts/Events/AttendanceLifecycleEvents.cs
• microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
• microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
• microservices/src/integration-service/Domain/IntegrationEntities.cs

Related Articles

• Attendance events
• Attendance technical documentation
• Attendance database documentation

See Also

• Attendance API documentation
• Attendance business documentation

Keywords

• Attendance events
• Integration contracts
• Eventual consistency

Revision Information

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