ENGINEERING INDEX / ENTRY 02
CASE 02 / COMMERCE / HUMAN RECOVERY
The sale did not end at checkout.
James designed a purchase-to-delivery flow for J-Bot: map a Stripe product to configured Drive links, address a fulfillment email to the buyer, and report the outcome to him. The inspected order shows a human recovery step, not a verified automatic send by that worker.
When a purchase needed a human handoff, what was recorded and what still needs reconciliation?
Where the handoffs happen.
The configured worker checks a session-keyed ledger and can send text-only emails containing Drive links. In this inspected record, however, the product is marked unmapped and the message reference is manual. The code's post-attempt alert is a notification, not an approval gate.
- 01Recorded order
- 02Manual handoff
- 03Buyer-addressed email
- 04Second send to reconcile
What the record earns.
A positive-amount local row marked manual; a buyer-addressed email sent at the matching time; another sent the next day.
- Observed receipt
- The local row has a positive amount, no row error, an unmapped product label, and a manual message reference. The connected sent mailbox has a buyer-addressed delivery email at the matching time and a second message to the same buyer the following day. Twenty-six focused catalog and checkout-eligibility tests passed on September 28, 2026; those tests do not explain the two sends.
- Source and scope
- Read-only local ledger inspection and two connected sent-mail records, compared by recipient and time; J-Bot fulfillment worker, product catalog, and focused tests at commit 9f94d83. No private identifiers are published here.
What this does not prove.
Neither the local row nor the sent mailbox proves Stripe settlement, recipient inbox delivery, buyer access to the links, or that J-Bot automatically sent this order. The cause of the second send is unknown. Code inspection also found a send-before-ledger-write crash window, so exactly-once delivery is not established. James defined the workflow; exact code authorship is not asserted.
Where the work goes next.
Reconcile the payment and both sent messages privately, then prepare a redacted timeline that distinguishes the designed worker from this manual recovery event.