Skip to content

docs(glue): a retired target returns its source - #38

Open
delchev wants to merge 3 commits into
mainfrom
docs/reopen-on-retire
Open

docs(glue): a retired target returns its source#38
delchev wants to merge 3 commits into
mainfrom
docs/reopen-on-retire

Conversation

@delchev

@delchev delchev commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Documents sourceStatusOnRetire — the inverse of the create-from's completion hook — in docs/spec/glue.md, under the event-driven create-from.

Why it is needed. A retired target stops satisfying the at-most-once guard, which frees the source's slot. But the completion hook exists to move the source OFF the status its own trigger qualifies on, and a lifecycle graph declares no edge back — so once it has run the source can never re-qualify, and voiding the target frees a slot nothing can refill. Where a button is also declared, a person can click; an event-only rule has no reissue path at all.

sourceStatusOnRetire declares the move back, so the reissue is the ordinary path: retiring the target returns the source, that transition is announced on the source's own channel, the trigger re-fires, the guard steps over the retired target, and the replacement is minted. Nothing new declares what "retired" means — it is the same classification the guard reads.

The section is self-contained: it explains the retirement inline rather than linking to it, because #37 (the superseding section) is still an open PR. Worth a read-through together if both land.

Spec proposal: IntentFile/intent-specification#48. Reference implementation: eclipse-dirigible/dirigible#6868.

delchev and others added 3 commits August 21, 2026 15:52
Documents the declared reopen: sourceStatusOnRetire, the inverse of the
create-from's completion hook. Superseding frees the source's slot; where the
hook has moved the source off the status its own trigger qualifies on, nothing
could refill it, and an event-only rule had no reissue path at all.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A retirement is delivered at-least-once, so it can arrive again after the
replacement already exists - and by then the source is standing at sourceStatus
once more, because the reissue put it there. The standing-status test alone would
re-open a source with a live target against it. The reopen now runs exactly when
a creation would be allowed through.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A create-from triggered only by a button carries no at-most-once guard, so
nothing blocks a replacement - the button is itself the reissue, and there is no
trigger for a reopen to re-fire.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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