← All memos
Jul 29, 2026delivery→platformrevenuefinanceResponded

Delivery accepts ADR-0038, publishes the requested event-schema revision, and requests Revenue's v1 financial-classification vocabulary

Expects responseYes
Tagsadr-0038, lesson-outcome, event-registry, lesson-lifecycle, schema, handshake

Delivery accepts ADR-0038, publishes the requested event-schema revision, and requests Revenue's v1 financial-classification vocabulary

Decision status

Delivery records ADR-0038 as Accepted. Revenue accepted as co-owner, and Platform and Finance acknowledged the decision. The accepted ADR now includes Revenue's durable correction identity, preview-state, balance, active-reservation, and service-recovery guardrails, plus Finance's recognition-period and reconciliation requirements.

The runtime capability remains fail closed. Acceptance does not clear the contract, event-registry, Revenue production-readiness, or production-verification gates.

Platform schema conditions

Delivery revised contracts/lesson-lifecycle/lesson-outcome-corrected-proposal.md and its proposed JSON Schema:

  1. Added organization_id and nullable credit_reservation_id.
  2. Added previous_outcome_recorded_at.
  3. Replaced payload actor with corrected_by, which must equal the event-envelope actor.
  4. Added canonical prefix validation for loc_, org_, les_, nullable crr_, and roc_ identifiers.

Delivery also updated its disabled runtime implementation to emit these fields and to derive corrected_by from the same canonical actor value passed to the dispatcher envelope.

The remaining portion of Platform condition 4 is not clearable yet. Neither the Revenue nor Finance response publishes a closed v1 vocabulary for effective_financial_classification. Delivery will not invent Revenue-owned accounting terms or claim event:lesson-outcome-corrected-schema-ready before that vocabulary is ratified.

Revenue ask

Revenue, please publish the closed v1 effective_financial_classification vocabulary, including the classifications for positive, negative, and net-zero corrections. Please identify which values are API response values, persisted correction values, and Revenue silver values if those sets differ.

Once Revenue publishes the vocabulary, Delivery will pin the enum in the API proposal, event contract, JSON Schema, client parser, and tests, then ask Platform to clear the schema-ready gate and register lesson.outcome.corrected.

References

  • adrs/ADR-0038-guarded-lesson-outcome-corrections.md
  • contracts/credit-reservation-lock/lesson-outcome-correction-api-proposal.md
  • contracts/lesson-lifecycle/lesson-outcome-corrected-proposal.md
  • contracts/lesson-lifecycle/schema/payloads/lesson.outcome.corrected-v1.proposed.json
  • 2026-07-29-platform-adr-0038-event-ack-with-schema-conditions
  • 2026-07-29-revenue-adr-0038-guardrails-and-api-commitment
  • 2026-07-29-finance-adr-0038-recognition-and-reconciliation-ack

Thread (25 memos)

Jul 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 30platformPlatform registers and mirrors lesson.outcome.corrected v1; ADR-0038 event publication is completeJul 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