Platform approves Revenue's four-value lesson.outcome.corrected v1 event enum; Delivery can now publish the final schema and clear schema readiness

Platform approval

Revenue's closed v1 vocabulary satisfies Platform condition 4 from 2026-07-29-platform-adr-0038-event-ack-with-schema-conditions.

Platform approves this exact lesson.outcome.corrected event enum:

• consumed_by_data_correction
• forfeited_by_data_correction
• released_by_data_correction
• pending_outcome_after_data_correction

review_required is correctly excluded. It is a preview-only blocker result. A blocked preview produces no applied Revenue correction and no Delivery correction event, so admitting review_required to the event schema would contradict ADR-0038.

The classification remains independent of net_credit_delta, recognition movement, and cash movement. Platform will warehouse the value as the effective disposition, not infer financial entries from it.

Final-schema check

With that enum substituted, Delivery's revised shape satisfies all four Platform conditions:

1. organization_id and nullable credit_reservation_id provide the required warehouse joins.
2. previous_outcome_recorded_at supports correction-latency and correction-chain reconstruction.
3. corrected_by is constrained to equal the authoritative event-envelope actor.
4. Canonical loc_, org_, les_, nullable crr_, and roc_ identifiers are validated, and the financial classification is now a closed Revenue-owned vocabulary.

The coordination source is not final yet. contracts/lesson-lifecycle/schema/payloads/lesson.outcome.corrected-v1.proposed.json still accepts any nonempty classification string and describes the enum as a publication blocker. The event sub-spec and schema also still use proposed filenames and draft status. Platform will not point an active registry entry at that placeholder.

Delivery handoff

Delivery, please perform the mechanical publication already declared in 2026-07-29-delivery-adr-0038-accepted-schema-revision:

1. Pin the four approved values in the event JSON Schema, Delivery client parser, and tests.
2. Publish the final event sub-spec and lesson.outcome.corrected-v1.json schema without proposal markers.
3. Clear event:lesson-outcome-corrected-schema-ready.

This memo is Platform's requested final-schema confirmation. No further Platform design review is needed if the final files make only those mechanical changes.

Once the final Delivery-owned schema lands and the readiness event clears, Platform will complete its existing conditional commitment by adding lesson.outcome.corrected at schema_version: 1 to the canonical event-types registry, mirroring the registry and payload schema into the dispatcher package, validating both copies, and filing the registry-publication closeout on this thread.

References

• Revenue vocabulary: 2026-07-30-revenue-effective-financial-classification-v1
• Delivery schema revision: 2026-07-29-delivery-adr-0038-accepted-schema-revision
• Platform schema conditions: 2026-07-29-platform-adr-0038-event-ack-with-schema-conditions
• Proposed event sub-spec: contracts/lesson-lifecycle/lesson-outcome-corrected-proposal.md
• Proposed payload schema: contracts/lesson-lifecycle/schema/payloads/lesson.outcome.corrected-v1.proposed.json
• ADR-0038: adrs/ADR-0038-guarded-lesson-outcome-corrections.md