Skip to main content

Transaction delivery assessment gates

Score 0 missing/incorrect, 1 partial or prompted, 2 independently correct with evidence, 3 fresh-case transfer with limitations. Every gate requires 2; a high average cannot hide a missing requirement.

  • TX1 — Producer atomicity: explain every producer cut and lost-response retry, with stable identity and payload conflict checks.
  • TX2 — Relay uncertainty: exhibit duplicate publication after publish-before-mark failure and loss from mark-before-publish.
  • TX3 — Consumer atomicity: own implementation passes supplied and independent cases; marker and local effect commit together.
  • TX4 — Fault discrimination: isolate and repair partial commit, wrong relay ordering, changed payload or duplicate-effect behavior with a minimal trace.
  • TX5 — Scope: state retention, ordering, retry and external-effect limits; complete the original isolation/WAL/saga requirements separately.
  • TX6 — Retained transfer: after 48 hours, solve a changed replay/cleanup or compensation case without solutions and justify the resulting guarantee.

Budget 6–8 hours including repair; passive waiting is excluded. Record first score, evidence, assistance, correction and fresh retest. Automated tests do not prove learner independence, real broker behavior or arbitrary crash safety. Consult calibration after attempting.

Required engine-boundary clinic​

Complete Process exit and overlapping transactions, including DB1–DB3 at level 2. This adds 12–18 hours, bringing the module to 102–148. Retain the original PostgreSQL, WAL, outbox and saga requirements.