docs(connectors): align decision reply and closure contracts - #1589
Merged
Merged
Conversation
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.
The decision-card spec still routes a pending-but-closed receipt through “Already ruled” and describes workspace-only fan-out. This amendment records the agreed behavior shipped in #1572 and #1586: explicit exceptional reply copy and relative-time rules, internally supplied origin, current recipient eligibility, unconditional receipt closure, detached provider sends, and the sweep's complete state table.
It also aligns the ledger, reply grammar and acceptance seeds with those rules, including held-row expiry, missing linked users and the remaining card-lookup reference in seed 9b. The card-pod authorization paragraph from #1571 is preserved with the origin argument added to its call example.
Validation: compared the three exceptional copy strings with the merged resolver; checked the fan-out, origin route and sweep against merged source; checked removed stale clauses, balanced fenced blocks, and
git diff --check. Documentation only; no runtime tests rerun. Review basis: pod rulings 64295–64299, Vera's PR 3 plan, and the detached-send/linked-user refinements at 64642–64647.