Skip to content

Independent Rerun Dossiers

The independent rerun dossiers exist to answer one hostile question:

Can the current flagship workflow sentence survive a second checked challenge lane, or is it still leaning on one unusually convenient flagship package?

These dossiers now matter more because the repository has stronger workflow packets than before. Once a flagship package starts looking convincing, the next honest question is whether the sentence survives a second lane with a different pressure shape instead of one unusually favorable corpus.

Each dossier pairs one flagship runtime lane with one companion lane that changes the pressure shape:

  • dda: MaxQuant import plus cross-engine Comet companion package
  • dia: primary DIA review lane plus matrix-shift companion lane
  • lfq: study-scale cohort lane plus sparse-contrast companion lane
  • ptm: primary localization lane plus ambiguity-stress companion lane
  • targeted: primary transition lane plus carryover companion lane

What A Dossier Must Show

  • the flagship package id and companion package id
  • the runtime entrypoint for both lanes
  • the checked public package paths to open first
  • the validating tests that keep the lanes live
  • the exact drift questions the companion lane is supposed to answer
  • the limits that still block broader authority language

How To Read A Dossier Honestly

  • open the flagship lane first so the baseline sentence is visible
  • open the companion lane second so stress arrives before anyone widens the family claim
  • treat validating tests as part of the dossier because a challenge lane that cannot be rechecked is only a story
  • keep the remaining limits attached to the dossier instead of treating them as optional footnotes

Why These Dossiers Exist Beside Trust Pages

  • a trust page can still sound too claim-oriented on its own
  • a rerun dossier turns that claim into a paired challenge lane
  • the dossier is narrower than the external review kit because it focuses on rerun pressure, not the full outsider packet

What A Strong Dossier Proves

  • the flagship sentence survives a second checked lane with a different stress profile
  • drift remains visible instead of being normalized away
  • the repository is willing to keep narrower language when the companion lane weakens the primary result

What A Dossier Does Not Prove

  • it does not prove broad third-party reproduction outside the repository
  • it does not erase runtime, comparator, or consequence limits from the family
  • it does not replace the external review kit, which still packages the wider outsider route

Honest Boundary

These dossiers are not broad external reproduction. They are repository-owned challenge lanes that make current bounded workflow language less dependent on maintainer explanation and more dependent on paired, openable proof surfaces.