Loading demo configuration…
b.BLUCCA / SYSTEMS LAB Source & local setup

INTERACTIVE WORKING SAMPLE ABOUT 60 SECONDS

An approval that
survives the retry.

Correct the invoice. Approve that exact revision. Watch a lost ERP response replay with one business write.

01

Document approval gate

  1. 1
    Correct the amountReview revision 1
  2. 2
    Freeze approvalOne reviewed snapshot
  3. 3
    Lose the responseERP accepts the write
  4. 4
    Retry the same keyRecover the receipt
YOUR NEXT STEP

Loading your synthetic invoice…

Review desk

LOADING
EXTRACTED INVOICEREV 1

Synthetic Paper Company

DEMO-20482026-10-01

The source total is $125.80. Correct the extracted amount.

Approved snapshotAwaiting review
Available after a correction

ERP delivery

Waiting for approval
0HTTP attempts
0Business writes

Demo-wide counters across all synthetic invoices.

The first delivery deliberately loses its response after the ERP accepts the invoice. Retry to recover the same receipt.

Runs the next queued delivery.

DELIVERY IDEMPOTENCY KEYCreated on approval

The ERP uses this key to recognize a repeated request.

Production single-write behavior requires ERP-side persistent idempotency. This synthetic ERP holds receipts in memory.

Inspect the frozen payload 
Approve a revision to freeze its payload.
02

Follow the evidence

IN-TAB SIMULATED EVENTS

    The browser sample models the workflow in this tab. The companion implementation runs on PostgreSQL with real HTTP delivery and a synthetic ERP.

    Read the 13-scenario run

    TAKE THIS INTO YOUR WORKFLOW

    Your reviewed invoice.
    Your ERP. A clear handoff.

    Connect your existing review UI and extracted JSON inputs to a revision-aware approval and delivery service.

    One schema · one sandbox endpoint · eight agreed checks · one revision round

    Proposed first milestone

    $2,400 fixed scope

    Plan for five working days once scope and interfaces are ready. Exact dates agreed before payment.

    Discuss your invoice flow