Versions and corrections

The rubric is versioned

What each level requires is published as a numbered rubric version (x1, x2, …). A published version never changes: improving the rubric publishes the next one. Every evaluation records the version that judged it and the evidence it used, so any past result can be explained exactly.

• The EBRAINS default is one version at a time, and it is the one the checklists show.
• Catalogues follow it by default. An organisation can instead lock its catalogue to a specific version, or assess against a rubric of its own. Results from an organisation’s own rubric are labelled as such and are not the EBRAINS default.
• Existing results keep their version until the service is evaluated again. A service page in Ready shows which version produced its current level.
• The AI assessment, where enabled, uses guidance and a model fixed by the same version, so its readings can be traced too.

How the rubric changes

The EBRAINS Ready team edits the rubric in Ready, not in code. Before a version can be published, every condition must be checkable from evidence or explicitly waived. A new version is checked against reference services, and its effect on every service is previewed before it is applied. The version history is visible to signed-in users in Ready under Methodology.

When evidence is wrong

Evidence is collected automatically, and collectors can be wrong or blind to something.

• Service owners cannot edit collected evidence; that keeps levels comparable. They can declare the answers only they can give, under Only you can answer these on the service page, and withdraw them.
• Ask for a correction through EBRAINS support, naming the service and the condition. The EBRAINS Ready team can correct the value; a corrected value is always labelled as entered by hand.
• A condition that cannot apply to your service (a status page cannot monitor itself) can be marked not applicable. It then drops out of the level instead of failing it.
• When a collector is at fault, the fix goes into the collector, so it corrects every service from then on rather than one by hand.