Skip to content

Document when Sigima contract versions change - #433

Merged
PierreRaybaut merged 1 commit into
developfrom
docs/contract-versioning-rule
Oct 25, 2026
Merged

PierreRaybaut merged 1 commit into
developfrom
docs/contract-versioning-rule

Conversation

@PierreRaybaut

Copy link
Copy Markdown
Contributor

Closes #432 — companion of DataLab-Platform/Sigima#97 (same branch name).

  • Provenance page (and French translation, msgid checked against the extracted catalog): Sigima increases a contract version whenever a change of the computation changes its result, whatever the DataLab version; consequence for replay and re-application; link to the Sigima page Operation contracts and versions.
  • Agent instructions: Sigima examples with \operation_id, \contract_version\ and \qualification; mandatory versioning rule (independent of DataLab releases, one-off 1.4 exception no longer applies) and provenance tests to update.

Sigima increases the version of an operation contract whenever a change of
the computation changes its result, whatever the releases of DataLab
(DataLab-Platform/Sigima#96). The provenance page now says so, with the
consequence for replay (explicit refusal of activities recorded with an
earlier version; compute again to record with the current version) and a
link to the Sigima page, with French translation. The instructions for AI
agents show Sigima computation functions with their contract and state the
versioning rule and the provenance tests to update.

Closes #432

Assisted-by: Claude Opus 5.5
@PierreRaybaut
PierreRaybaut merged commit 5bcd603 into develop Oct 25, 2026
6 checks passed
@PierreRaybaut
PierreRaybaut deleted the docs/contract-versioning-rule branch October 25, 2026 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant