Live demo: delivery reports from verified data Live
Demo Viewing as

These reports are built from what merged and what was verified, not from what somebody typed into a tracker. That is the whole difference. A report assembled from the board inherits every error on the board.

Each number traces back to its evidence: the merge that produced it, the criteria that were checked, the confidence behind each verdict, and whether the change was applied in shadow mode or live. An automated change that moved a ticket is recorded with the finding that justified it.

Delivery analytics tools report this sort of thing in far more depth than we do. The difference is that they describe the record and we correct it first.

Payments status report

Last 7 days · auto-generated from ground truth · At risk · Draft

Executive summary (editable - you own the framing)

Last 7 days - progress

  • ENG-812 idempotent refund endpoint#1204
  • ENG-777 ledger reconciliation job#1190
  • ENG-760 webhook retry backoff#1188

Next 7 days - planned

  • ENG-820 checkout uses new identity API[Blocked]
  • ENG-799 3DS challenge flow[In Review]

Risks

  • ENG-820 - Checkout blocked on Identity API (INIT-4, PR #1177 unmerged)
  • ENG-799 - 2/5 acceptance criteria unmet though work looks complete
  • EPIC-51 - Epic still open though all children are done

Asks

  • INIT-4 - Need Identity to prioritize PR #1177 to unblock Checkout
  • PR #1206 is untracked - confirm which ticket it belongs to

Machine-true numbers, human-owned framing. Overriding a machine status is attributed in the audit chain; the original value is kept.