Inspectable example
A useful place to start, with a route to the related result.
Inspectable example
Synthetic webhook signature test vectors: six deliveries, one accepted
Invented secret, invented body and real HMAC-SHA256 digests show exactly which small changes make a signature check fail, with a verifier you can run.
Inspectable example
Synthetic delivery ledger: the same event arrives three times and the action runs once
A made-up sender delivers six requests, including retries, a tampered copy and an unsigned one; the ledger shows which are accepted and how many actions run.
Inspectable example
Synthetic polling trace: five strategies over the same five records
One invented record is slow to appear and one run crashes; five ways of remembering your place give five different results, from a lost record to nine actions for five records.
Inspectable example
Synthetic price list: a page-by-page row count that finds two mistakes a matching total hides
An invented three-page price list shows why rows are counted per page. A first extraction matches on the total, 14 of 14, while page 1 is a row short and page 2 has an extra row.
Inspectable example
Synthetic merged-cell report flattened: nine rows in, five records out, every total reconciled
An invented printed-style sales report with merged region labels, subtotal rows and a spacer becomes a flat five-record table, with a reconciliation showing 9 original rows = 5 records + 4 removed.
Inspectable example
Synthetic quotation: why the same three lines total 4.38 or 4.39 depending on the rounding rule
Three invented lines of 1.30 plus a 12.5 per cent add-on give 4.38 if the add-on is rounded per line and 4.39 if it is rounded on the total. The rule must be written down.
Inspectable example
Synthetic rename manifest: three clean renames with matching checksums and four held names
An invented seven-file folder shows a dry run and a manifest with a row for every file, with three renamed files whose checksums match, and four held, a pair of names that differ only in letter case, a reserved device name and a name ending in a period, all listed, not guessed.
Inspectable example
Synthetic date column: which rows a rule can settle, and which must stay on the ambiguity list
Nine invented entries show day-first and month-first typing, a two-digit year, a row where only one reading is possible, an impossible date and a four-year shift, with the decision and reason for each.
Inspectable example
Synthetic webhook test vector: why a re-formatted body makes a genuine event fail verification
Five versions of one made-up event, each shown in full with its real SHA-256 digest, show that re-formatting the body changes the hash and that a one-character change is rejected.
Inspectable example
Synthetic test vectors for a Slack events endpoint: signature, five-minute window and repeated events
Five invented requests with their computed signatures show which a verifier should accept and which it should reject, and why an event ID must be claimed before the work is queued so a repeat or a simultaneous duplicate does not run it twice.
Inspectable example
Synthetic invoice reconciliation: identical net lines, two different tax totals
Three invented small-value lines show how line-level and invoice-level tax rounding can disagree even when net values and line counts match.
Inspectable example
Synthetic invoice retry matrix: source operation, attempt and target draft are different IDs
Concrete made-up references specify when a retry retains one target draft and when changed contents, a second organisation or multiple matches need a separate decision.
A need we have not covered yet?
Tell us what you need accomplished. We confirm whether we can offer a useful scope before accepting work.
Describe a custom outcome