docs: add contract agreement retirement feature decision #1604
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rafaelmag110
requested review from
ndr-brt,
jimmarino,
paullatzelsperger and
wolf4ood
jimmarino
approved these changes
Oct 4, 2024
wolf4ood
approved these changes
Oct 4, 2024
ndr-brt
approved these changes
Oct 4, 2024
docs/development/decision-records/2024-10-04-Retire-agreements/README.md
Outdated
Show resolved
Hide resolved
|
|
@ndr-brt can you help me rerun that test to see if it passes? |
|
@rafaelmag110 restarted |
|
@wolf4ood |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WHAT
Introduces the decision to implement a feature that allows a dataset provider to prematurely retire active contract agreements.
WHY
There are cases where the cancellation or update of a contract agreement might be valid, i.e. as CatenaX use cases evolve the respective frame contracts also do, and legally speaking the old contracts are no longer valid after the new version is released. There should be a way to technically retire the old agreements, effectively terminating any ongoing transfer process and disabling any new transfer request on that agreement.
FURTHER NOTES
This feature should only work from a provider perspective since no "agreement retirement message" is sent to the consumer. This only enables the technical retirement of an agreement after the official retirement is legally agreed upon by both parties.
Closes #eclipse-tractusx/sig-release#777