Delivery publishes lesson.outcome.corrected v1 and clears the schema-ready gate
What changed
Delivery published the final lesson.outcome.corrected v1 sub-spec at
contracts/lesson-lifecycle/lesson-outcome-corrected.md and the final payload
schema at
contracts/lesson-lifecycle/schema/payloads/lesson.outcome.corrected-v1.json.
The proposal filenames and draft markers are removed.
The event schema pins exactly the four Revenue-owned successful classifications approved by Platform:
consumed_by_data_correctionforfeited_by_data_correctionreleased_by_data_correctionpending_outcome_after_data_correction
review_required remains preview-only and is excluded from the event schema.
Delivery's Revenue client now accepts the five-value preview vocabulary, accepts
only the four successful values from apply, and fails closed on unknown values.
The Lesson Lifecycle Contract is updated to v1.2.0 and names Platform warehouse ingestion as the v1 consumer. Delivery's canonical domain page now lists the event while retaining the ADR-0038 runtime gate.
Gate cleared
This memo clears event:lesson-outcome-corrected-schema-ready.
Platform can now register lesson.outcome.corrected at schema_version: 1,
point it at the final schema, and mirror the registry and payload schema into
the dispatcher package.
Runtime remains gated
Schema readiness does not enable the operator feature. Delivery will keep
LESSON_OUTCOME_CORRECTIONS_ENABLED=false until Revenue clears
event:revenue-lesson-outcome-correction-api-ready, Platform publishes the
registry and dispatcher mirror, and Delivery completes the exact production
verification required by ADR-0038.
References
2026-07-30-revenue-effective-financial-classification-v12026-07-30-platform-adr-0038-final-event-enum-approved2026-07-29-delivery-adr-0038-accepted-schema-revisionadrs/ADR-0038-guarded-lesson-outcome-corrections.md