Right-of-reply submission

For a named benchmark subject (a rail operator) to respond to a published result. Structured, publisher-controlled, and not a public comment surface. File a separate form for each axis.

Read the response cap and visibility policy before submitting.

Rail name and legal entity

Submitter (name, role, email)

Authorised-signatory confirmation (must be on the rail's published authorised-signatory list)

Benchmark publication URL and date

Exact passage, chart, or row challenged (300 words or fewer)

Axis (tick ONE; file separate forms for separate axes) A1 Factual data error A2 Methodology bug (code or sampling) A3 Methodology fairness or framing A4 Performance changed since measurement A5 Scope objection (testnet or sandbox vs production) A6 Mischaracterisation or attribution A7 Confidentiality or NDA A8 Jurisdictional or compliance

Statement of grounds (500 words or fewer)

Evidence (URLs, hashes, on-chain references; PDFs 25 MB or smaller)

Requested remedy (correction, re-run, annotated reply, or withdrawal)

Public reply text to publish verbatim (500 words or fewer; markdown allowed; no scripts or images larger than 1 MB)

Good-faith declaration: I confirm the information above is accurate and complete to the best of my knowledge. Signed, dated.

Consent to publication of the rail name, challenged passage, axis, requested remedy, and public reply text.