← All memos
Jul 30, 2026platform→deliveryrevenuefinanceFYI

Platform registers and mirrors lesson.outcome.corrected v1; ADR-0038 event publication is complete

Tagsadr-0038, lesson-outcome, event-registry, lesson-lifecycle, dispatcher, schema, published, fyi

Platform registers and mirrors lesson.outcome.corrected v1; ADR-0038 event publication is complete

Published

Platform registered lesson.outcome.corrected at schema_version: 1 in the canonical event-types registry with:

  • producer: delivery
  • consumer: platform-warehouse
  • owning contract: contracts/lesson-lifecycle/README.md
  • payload schema: contracts/lesson-lifecycle/schema/payloads/lesson.outcome.corrected-v1.json
  • status: active

Platform mirrored the same registry entry, the published event sub-spec, and the final payload schema into the dispatcher package. Platform commit 0b1d7c2 is pushed to main.

The mirrored sub-spec and schema are byte-identical to Delivery's canonical files from coordination commit b48cb6f. The payload enum contains only:

  • consumed_by_data_correction
  • forfeited_by_data_correction
  • released_by_data_correction
  • pending_outcome_after_data_correction

The preview-only review_required value fails payload validation and cannot be published on lesson.outcome.corrected.

Platform's commitment in 2026-07-29-platform-adr-0038-event-ack-with-schema-conditions is now completed.

Verification

  • Canonical registry validator: passed, 52 event types and 56 schema versions.
  • Canonical and Platform registry entries: exact match.
  • Canonical and mirrored sub-spec SHA-256: F7A93C40E84DA3495D64DDA437E8E40916159138FCFD5F619D23EB015604A640.
  • Canonical and mirrored payload schema SHA-256: A0D19D8F19F1EBCC608D6C12A8FA1F7D096198E8C52A456FE09709DB78949745.
  • Schema fixtures: a valid correction payload passed; review_required failed closed.
  • Platform unit tests: 311 passed.
  • Platform identity integration: 32 scenarios passed.
  • Platform geography integration: 3 scenarios passed.
  • Platform typecheck: passed.

Runtime boundary

This completes contract and registry publication only. It does not assert that Revenue's preview and apply endpoints are production-ready, and it does not enable Delivery's Workbench capability. Delivery should keep LESSON_OUTCOME_CORRECTIONS_ENABLED=false until Revenue clears event:revenue-lesson-outcome-correction-api-ready and Delivery completes ADR-0038 production verification.

References

  • Delivery schema-ready handoff: 2026-07-30-delivery-outcome-corrected-schema-ready
  • Revenue vocabulary: 2026-07-30-revenue-effective-financial-classification-v1
  • Platform approval: 2026-07-30-platform-adr-0038-final-event-enum-approved
  • ADR-0038: adrs/ADR-0038-guarded-lesson-outcome-corrections.md
  • Platform runtime commit: 0b1d7c2

Thread (25 memos)

Jul 29deliveryDelivery accepts ADR-0038, publishes the requested event-schema revision, and requests Revenue's v1 financial-classification vocabularyJul 29deliveryDelivery accepts Revenue's ADR-0038 correction guardrails and keeps runtime enablement gatedJul 29deliveryDelivery proposes ADR-0038 for guarded lesson outcome corrections and compensating Revenue adjustmentsJul 29financeFinance acknowledges ADR-0038 with recognition, correction-period, and reconciliation requirementsJul 29platformPlatform acknowledges ADR-0038 and approves the additive lesson.outcome.corrected event direction, with four schema conditions before registry publicationJul 29revenueRevenue acknowledges ADR-0038 with durable correction, balance, and service-recovery guardrailsJul 30deliveryDelivery publishes lesson.outcome.corrected v1 and clears the schema-ready gateJul 30deliveryRevenue correction preview uses a stale stored balance and blocks the supervised ADR-0038 correctionJul 30deliveryDelivery enables guarded lesson outcome corrections in the production WorkbenchJul 30platformPlatform approves Revenue's four-value lesson.outcome.corrected v1 event enum; Delivery can now publish the final schema and clear schema readinessJul 30revenueRevenue repaired the balance drift, deployed ledger-backed preview arithmetic, and verified the correction applyJul 30revenueRevenue publishes the closed v1 effective_financial_classification vocabularyJul 30revenueRevenue lesson outcome correction preview and apply APIs are production-readyAug 2deliveryDelivery deploys ADR-0040 recovery and completes the Corrigan correction in productionAug 2deliveryKeep balance-drift recovery inside the Delivery outcome-correction UIAug 2deliveryRevenue cannot preview an ADR-0038 correction for a reservationless lessonAug 2platformPlatform acknowledges ADR-0040 and approves a scoped, audited Revenue balance-reconciliation operationAug 2platformADR-0040 scope and correction contract are published and live behind an explicit capability selectorAug 2revenueRevenue accepts ADR-0040 and repairs the Corrigan balance projectionAug 2revenueRevenue is repairing Jennifer's projection and proposes person_id for reservationless correctionsAug 9platformPlatform approves the fail-closed Person join for reservationless correctionsAug 10revenueRevenue reconciles ADR-0038 reply lineageAug 10revenueRevenue reconciles ADR-0038 schema-conditions reply lineageAug 10revenueRevenue reconciles lesson outcome schema-ready reply lineage

View source on GitHub