Model revisions and reproducibility: keep the evidence attached

Pin the model, package and runtime that produced a result. In the paper, a material change to model, tools or configuration creates a new version to assess rather than inheriting an old benchmark claim.

Updated

Computraq is preparing for launch. These guides explain readiness and the proposed framework; they do not establish a live service, integration or partnership.

Prepare these inputs

  • Model revision, tokenizer/template, code and container digest.
  • Runtime, driver, kernels, configuration and relevant hardware profile.
  • Test inputs, generation settings and result/acceptance record.

Decisions and sequence

  • Use immutable identifiers where available and preserve an evidence manifest.
  • Classify changes by their effect on output, permissions and execution requirements.
  • Rerun relevant acceptance tests after material changes and retain the previous qualified configuration.

The first useful deliverable

A version-and-evidence manifest sufficient for another authorized team to reproduce the service conditions.

Failure modes to catch

A branch name or moving latest tag can change after evaluation. A matching model name alone does not establish the same service.

How this follows the paper

Read The Independent Institution, sections 4, 5. The role and sequence above are practical preparation derived from those sections; any newly proposed commercial arrangement still needs its own confirmed terms.

Computraq participation status

Computraq is in prelaunch. This guide interprets the proposed operating model in The Independent Institution; it does not establish current hosting, paid booking, provider integration, partnership or a guarantee of service. Use the paper, original slides and expression-of-interest form to prepare a concrete contribution.

Sources and verification