LMS Assessment Events

Summary

Assessment submission conditionally constructs one passed or failed integration contract without exposing assessment content.

Audience

Engineering, integration, QA, architecture, security, product, and support reviewers.

Reference Content

Submission evaluates the implemented result boundary and constructs either AssessmentPassedEvent or AssessmentFailedEvent. Both are outbound version 1 contracts, receive new event identities, participate in the local outbox save, and are recognized by Notification. The result details remain within protected application data and are intentionally omitted here.

Terminal-state checks prevent the same completed attempt from being submitted again. No separate retry or resubmission event was verified. Attempt start and scoring-governance events are not implemented.

Source References

• microservices/src/training-service/Api/TrainingEndpoints.cs
• microservices/src/training-service/Infrastructure/TrainingDbContext.cs
• microservices/src/contracts/Events/TrainingLifecycleEvents.cs

Related Articles

• LMS Events documentation
• Producer behavior

See Also

• Idempotency and duplicate handling
• Verified event catalog

Keywords

• Assessment outcome
• Training contracts
• Terminal state

Revision Information

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