docs(intent): a retired target stops blocking its source - #207
Merged
Conversation
The at-most-once guard of an event-driven create-from was documented as "returns the existing target", which reads as "no duplicates from the same event". It is stronger than that: it holds for the LIFETIME of the target - which is why a voided document used to block its replacement forever (eclipse-dirigible/dirigible#6814). States the semantics precisely and documents the state-aware half: a target whose status is classified `cancelled` or `void` is retired and stops satisfying the guard, so void-and-reissue works; draft and live ones still block. Covers the no-lifecycle, unclassified (warning) and cross-model cases, and points the `mode: append` warning at the real answer instead of leaving it as "that needs a state-aware guard". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Documents eclipse-dirigible/dirigible#6814 (platform PR eclipse-dirigible/dirigible#6850).
The at-most-once guard of an event-driven create-from was described as "returns the existing target instead of creating a second one", which reads as no duplicates from the same event. It is stronger: it holds for the lifetime of that target — which is exactly why a voided document used to block its replacement forever, silently.
event:bullet now says so, and links to the new section.cancelledorvoid(stage:) is retired and stops satisfying the guard, so void-and-reissue works;draftandlivestill block, both documents are kept, and the no-lifecycle / unclassified-nomenclature (warning) / cross-model cases are stated.mode: appendwarning already said "that needs a state-aware guard onmode: once" — it now points at the section that delivers one.stage:section names its second consumer.Nothing new to author: the classification the report
scope:already resolves through is what the guard reads.🤖 Generated with Claude Code