Reproducible tests

Lab evidence matrix

This page is not a product dashboard — it documents how we plan to prove claims on the public site. The lab injects known faults on sim.punchop.com; scenario definitions live inpunchop-lab. The investigator never uses that answer key during a real case.

Until the Enterprise lab run finishes, the table below is expected visibility from the scenario catalog, not measured lag or live BigQuery results. After the run, we publish observed cells and dates here (same method as guides marked verification: lab).

Method

  1. Emitter fleet sends with X-Punchop-Scenario and known fault fixtures.
  2. Receiver + Enterprise export + Reports API capture events.
  3. coverage-matrix tool compares expected vs observed visibility.

Expected coverage (catalog — not yet measured on tenant)

ScenarioFaultBigQuery exportReports APIReceiver
transport_greylistgreylist_451partial—yes
gmail_5_7_26gmail_auth_policyyesyesyes
async_dsn_bounceaccepted_not_deliveredyes—yes
outlook_5_7_515outlook_high_volumeyes—yes

Full JSON: regenerate with go run ./cmd/coverage-matrix/ after each lab run.

Evidence method · Official sources